
Your observation that memtest sometimes fails and sometimes not is good. You will also face application crashes and BSOD from time to time affecting different applications. Probably the second fastest test is using Prime95 with large FFTs - however this one also has an artificial flavour.Īnyway: My opinion is that you live kind of dangerous in ignoring the memtest failures. The problem however is that it may take a couple of hours to reproduce. Doing these kinds of tests will corrupt real data of yours and not some artificial memory test. You will find more tests in the link I posted above. However, I do hope Intel will come up with a new driver with full DX10 wrote: So unless proved otherwise, I am not concerned with the errors reported by Memtest. As a result Memtest can no longer access the memory and thus the error. At the same time Vista also considers the block free and locks the block for the system. Memtest may have identified a block of memory as being "free" and start testing that block. If I do Memtest during this process it would report errors. If you let the system idle, Vista will cache the memory again and the process will take a few minutes to complete. Right after a successful Memtest the Cached memory reduced down to about 60 MB while the Free memory increased to 1.4GB. In my case with 2GB total memory, the Cached memory was about 1.4GB and Free memory about 56 MB when idle. My theory is this: during idle periods Vista puts some system codes in the Cached memory and leaves only a little free memory.

Stop the test, exit the program, wait for about 5 minutes, and run the test again -> no error! Stop the test, exit the program and restart it right away -> errors immediately.ģ. This is how I tested:ġ. Start Memtest, select "All unused memory", run for about 35 minutes when it reaches 100% coverage -> no error.Ģ. I think it has something to do with how Vista caches memory. On the other hand I am not sure if the driver causes the errors reported by Memtest. Unfortunately a few DX10 apps crashed my system. I did install the driver from unpacked files soon after my initial post.
