Jump to content
Corsair Community

2GB Corsair DDR2 RAM Blue Screen Issues


Recommended Posts

Hi, not very advanced in the computer department, so bare with please!


Basically, every nearly every day, several times in the day, my system will just blue screen, i changed from my old soundcard to the newer onboard one, this stopped the blue screening for 2/3 days then it started happening again, this time with a new message (see below):




Stop: 0x000000 C2 (0x0000007, 0x00000CD4, 0x746C7847,0x£10FD3C4)




I searched various forums and basically, it seemed to come down to being a RAM issue, i used MemTest running the programme simaltanously (spelling!) 1023, only one was increasing on the 'coverage' bar, i let it go to 238% before stopping it (not sure if i need to leave it on much longer?) it came up with 1 error (see below):


"memory error detected! copying between 165e6f0 and 165e5ae did not result in accurate copy.


memtest has dectected that your computer cannot accuratly store data in RAM. you need to fix this"


according to the MemTest my RAM is bad, but id like a 2nd opinion before i return it back to OverClockers, my PC specs are below, if it is any help:


abit IP35-E Off Limits

Intel Core 2 DUO LGA775 E6600 2.40GHz

2GB Corsair XMS2-6400C5 DDR2 Dual Channel Kit


(above all part of a bundle)


EVGA GeForce 8800 GTS 320MB GDDR3 HDTV/Dual DVI (PCI-Express)

Western Digital RE2 500GB SATA-II 16MB Cache

Pioneer DVD-RW DVR-110D (kept from previous pc)

Enermax Noisetaker 535W EG565AX-VE(W) SFMA ATX2.0 SLI Compliant PSU

On Board 7.1 Realtek HD Audio


Sorry if i've rambled on, just wanted to give anyone who can help all the information i think could be helpful, look forward to any help, thanks for your time!



Link to comment
Share on other sites

I tried memtest today on each individual stick of RAM both seemed ok after 2 hours or so of testing, i haven't had any blue screen crashes since (fingers crossed), a friend told me to use my onboard soundcard and remove my old Soundblaster 5.1 from the PC altogether. This hopefully was the cause of the problem, if not im going to send the RAM back and see if that solves it!
Link to comment
Share on other sites


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

  • Create New...