Quote: Originally Posted by jimbo45
The OP doesn't say if he / she was using X-86 or X-64, whether the processor was dual / quad core, whether RAID was involved, / SATA IDE etc etc.
I replicated it on 64 bit. Using a dual core, 4GB RAM. My C: drive is a RAID 0 setup, which wasn't affected with the bug. My D: drive, which I managed to replicate it on is just a single 500GB SATA drive. You can see the RAM usage shooting up from the screenshot I posted on the first page of this thread.
Quote: Originally Posted by Antman
I can replicate the phenomenon - 500 GB non-RAID. The "issue" did not present until the free space, stage 5/5, was scanned. Waiting patiently for the crash. 102,nnn,nnn free clusters.
I replicated the issue as soon as the chkdsk begun. The RAM began climbing from the start, then at stage 4 was when it peaked at 89% usage.