Overclock.net banner

Is Your Dram Stable - Are You Sure???

362 Views 1 Reply 2 Participants Last post by  internal
Q = " Is My DRAM Stable?

One of the most serious problems that can afflict an overclocker's PC is "error creating memory". The vast majority of RAM modules work perfectly at their stated speed (SPD = Serial Presence Detect) making RAM troubles a rare malady, however they can easily create errors when overclocked. These errors, when in Windows can be hidden due to ECC (Error Correction Code). Windows makes use of ECC and programs run in Windows are not really a true test of memory error, rather they are a test of memory with ECC enabled. Basically this means that your memory can be creating errors but the ECC (Error Correction Code) is taking care of it with multiple read/write/verify steps until the dram bit is correctly streamed.

If you are failing in memtest then you are failing in windows. However, as mentioned, the computer uses a technology called "ECC" which is Error Correction Code. This means that when your ram is failing on a read/write/verify step it redoes the step until the verification is correct. If it finds a correct verify the code then passes the strap back to the program to continue running. After five iterations of the error there is a flush of the cache and a new read/write/verify of the data occurs. This is done three times and if the failure continues to occur an errata event is created in the event log and in the program you are running which often means either a crash or stall. Thus if your system is finding error (and it is if memtest is giving errors) it is validating the errored data through ECC validation and the program is continuing. If you are failing in the program you are running that means that the bit read/write/verify is continuning through to the failure algorithmic strap which passes the failure to the event log and halts the program (Prime95). This is the same event that will happen in a game, etc. Every time your ram creates errors it is stalling the system. If it errors through to one to four iterations every five data streams of read/write/verify then your system is slowing down and all the overclocking you are doing is not meeting it's best overclock. It is the antithesis of overclocking.

So, have you tested your memory with memtest V3.2? No? I advise you to do so to be certain that you are not either stalling your system or creating irrecoverable errors in bits.

ISO images suitable for creating a bootable Memtest86 CDROM

Download this:


Download - Memtest86 v3.2 ISO image (zip)

Burn the ISO as an image to CD and set the system to boot from CD. The memory test will immediately start.

This is the best way to test the memory overclock stabilty.

Hope this helps,

See less See more
  • Rep+
Reactions: 2
1 - 2 of 2 Posts
I think your post finally motivated me to create a bootable memtest CD.
1 - 2 of 2 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.