Jump to content
Corsair Community

CMX512-3200C2 Gone Bad


Komodo

Recommended Posts

I've been running four sticks of CMX512-3200C2 for about sixteen months or more in a P4P800 Deluxe. A few days ago, I crashed while in the OS and the system rebooted. The system went to a blue screen and started the continuous reboot. I tried each stick separately, in pairs, and in multiple slot configurations. When using the suspect stick, the reboots would continue. Without it, the OS would boot without issue. I even attempted to re-load the OS using the same testing method. With the suspect module, I would receive various errors during the process which would never complete. With the other units, the OS would load without issue. I would like to continue the returns process as the issue seems very straight forward.
Link to comment
Share on other sites

Can you tell me the bios settings you have set for both CPU and memory and any performance settings that you may have set?

 

Sure, all settings a stock, by SPD for the memory, and default for the CPU, which is a 3.2gig 800.

Link to comment
Share on other sites

  • Corsair Employees

Please set the dim voltage to 2.7 Volts and test the modules one at a time with http://www.memtest.org and the settings should be set manually to the following.

SDRAM CAS Latency: 2T

SDRAM RAS to CAS Delay (tRCD): 3T

SDRAM Row Precharge (tRP): 3T

SDRAM Active to Precharge Delay (tRAS): 6T

And do you have any of the performance options set in the bios? If so, just set everything to defaults and set the timings and frequency manually.

Link to comment
Share on other sites

I attempted to do as you asked me to, and now I'm receiving checksum/bad cmos errors directly after the graphics cards post screen. The system thinks the bios on the video cards are bad so it attempts to find an update via the cd-rom and floppy. I've tried three different video cards to make sure it wasn't the card. The system won't proceed past the bad checksum, so I can never run the memtest. I even changed all the settings you asked for while using the other modules before using the suspect one. All the other modules used together or alone post the system, run a mem test, load an OS and boot into the OS without issue. With the suspect module, I'm not getting anywhere. What would you like me to try next?
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...