David, as I said before, it doesn't happen on my XP64 system.

DG

Processor(s)

Number of processors 1
Number of cores 2 per processor
Number of threads 2 (max 2) per processor
Name Intel Core 2 Duo E6700
Code Name Conroe
Specification Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz
Package Socket 775 LGA
Family/Model/Stepping 6.F.6
Extended Family/Model 6.F
Core Stepping B2
Technology 65 nm
Core Speed 1600.0 MHz
Multiplier x Bus speed 6.0 x 266.7 MHz
Rated Bus speed 1066.7 MHz
Stock frequency 2666 MHz
Instruction sets MMX, SSE, SSE2, SSE3, SSSE3, EM64T
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 4096 KBytes, 16-way set associative, 64-byte line size

Chipset & Memory

Northbridge Intel i975X rev. A0
Southbridge Intel 82801GB (ICH7) rev. 01
Graphic Interface PCI-Express
PCI-E Link Width x16
PCI-E Max Link Width x16
Memory Type DDR2
Memory Size 8192 MBytes
Memory Frequency 333.3 MHz (4:5)
CAS# Latency (tCL) 5.0 clocks
RAS# to CAS# (tRDC) 5 clocks
RAS# Precharge (tRP) 5 clocks
Cycle Time (tRAS) 15 clocks
Bank Cycle Time (tRC) 21 clocks

System

System Manufacturer
System Name
System S/N
Mainboard Vendor Intel Corporation
Mainboard Model D975XBX2
BIOS Vendor Intel Corp.
BIOS Version BX97520J.86A.2674.2007.0315.1546
BIOS Date 03/15/2007

Memory SPD

Module 1 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
Module 2 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
Module 3 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston
Module 4 DDR2, PC2-5300 (333 MHz), 2048 MBytes, Kingston

Software

Windows Version Microsoft Windows XP x64 Professional Service Pack 2 (Build 3790)
DirectX Version 9.0c

DG

Good luck. [;)]

DG

david it seems i managed to screw up the machine during some tests and am finally in the boat with you :-/

unfortunately i noticed this too late and can't reproduce the step where this issue happened now.

there is no time left for playing around this week so i have to ask you for some more patience ...

christian

edit: you won't beleive it .... it seems the issue is related to corrupt sample data (a sector from a harddisk fails or similar)

solution: open directory manager, remove all content, add some content

(you should notice the memory is increasing to 800 MB only opening the DM without having any VE opened before)

reboot - open VE ... back at 300 something ... (thx to george for the clever idea)

after adding the corrupt data the effect returns ... isn't that weired?

now we just need to find out what affects the taskmanager to show this amount of used memory even without any process listed ...

probably it is less timeconsuming top find which collection contains the corrupted data than to re-install all, the one which is found to be responsible for the issue i would re-copy or re-install of course.

christian

you forgot to reboot between 2) and 3) .. otherwise you wouldn't free the memory and see ... nothing ...

;-) of course you only need to reboot (maybe log off / log on is enough) if the memory goes up again more than normal ...

Hi cm,

Here is my feedback:

I cleaned out the DM and rebooted. Checked my Committed RAM in TM with nothing launched, its 225mb. Opened the DM, FireFox so I can type this, and the TM.  Lastly I open the Windows Explorer. My Committed RAM at this point is 253mb.

Now, I drag and drop the VSL Percussion data folder of the Cube into the DM from Explorer. This folder is 51.3gb. My Committed RAM jumps to 357mb, thats 104mb. Normal? 

Now, I will reboot and re-open the DM and do a scan and see what happens.

I will edit this post when I'm back up...be back in 2 minutes. 

Ok, I'm back.

Launched TM, DM, and Firefox. Committed RAM is at 257mb. Only Percussion data is in DM. Clicking Rescan...Commited RAM jumps up to 358mb, pretty much the same as before.

I'll add another data folder to the DM with the Percussion already there, this time Brass II which is 39gb. Committed RAM goes up to 441mb, thats a rise of another 83mb. 

Adding Orch Strings II 18.9gb, now RAM jumps to 473mb, another 32mb.

I'll finish off this drive and add the WoodWinds II which is 44.8gb, now RAM is at 546mb, a rise of 73mb.

So I started with 225mb with nothing launched. Added Percussion, Brass II, Orch Str II, and WW II to the DM. Total of 154gb of data and my Committed RAM rose to 563mb, thats rise of 338mb. That can't be normal, right?

If we minus the RAM it takes to run the DM we wind up with a Commintted RAM of 554 so its 329mb of vanished RAM.

When I close DM the RAM is not released. I have to reboot to get it all back.

One thing I did not mention is that I have previously loaded only one volume at a time into the DM and rebooted to see if one of the volumes was the problem. After checking and noticing the RAM was still jumping up is when I decided to write this. 

This is driving me nuts!

Any ideas?

Like I said, the data files were copied from another computer to this one via ethernet. My other computer is a WinXP32 system that is now no longer used. I guess all my data could be corrupted from the copying but I bought the Vienna Bosendorfer recently and installed directly to this machineand I have the same problem with that as well.

All my VSL data is spread across 3 internal seagate drives and no matter which drive I use to drop data folders in the DM the RAM goes up like this.

What should I do?

I'll try anything.

David

keep in mind i only proceeded as described above to return to *normal behavior* ..

although before i uninstalled LCC, VI, VE because i assumed the problem here.

uninstall always means here a clean uninstall from control panel - add/remove software making sure no processes are running followed by a reboot.

bad RAM is no probable reason IMO, you would rather get *could not read* or *could not write* at adress 0x1234567 or something similar.

a failing harddrive (loosing and incompletely re-assigning sectors) would be a possible reason though.

christian