New RAM + computer goes to hell

progrox

Junior Member
Mar 25, 2005
10
0
0
Okay, I'm frustrated and I'm just gonna list what happened chronologically.

I started getting Memory_Management BSODs once every week or so. I ran a Memtest86+, and one of my pair of Corsair sticks showed up faulty. Other than this, my PC was running fine. I could play demanding games for hours without trouble.

I RMA them, and today get back a pair from Corsair Netherlands. I put them in, won't POST. I switch their places, it works. Bios tells me that it reverted to 2 Ghz speed and I check Bios. Settings okay, I reset, and it displays 2,83 Ghz correctly. I get into Windows and do a bit of browsing, turn on music, and suddenly the PC freezes up and the music plays in a loop. Ctrl-Alt-Del doesn't work, I have to hit the reset button. Now, again, it won't POST.

I try a single stick of RAM, it works, and I run a Memtest. About halfway through the test, the PC reboots by itself. I fiddle with the RAM slots again, once again it tells me 2 GHz, I go into the Bios. While I look around the Bios, it freezes up (!). I have to hit the reset button. I did up the CPU voltage from Auto back to 1.2 though, because it was displayed as 1.05. (there's a switch in the Bios that lowers voltage when not under load, I thought that was the reason)

I get into Memtest, finally, with both sticks plugged in. It runs for a while (in fact it runs past the 27% margin, which is where my old sticks had their faults. This excludes a faulty mobo slot at least), and then it gives me this:

Code:
Unexpected Interrupt - Halting

Type:  fe003c29  eax: 00000000
PC:    00010012  ebx: 00000006
CS:    00012dc9  ecx: 0000002c
Eflag: 000003e8  edx: 00028700
Code:  00000010  esi: 00000031
DS:    90000000  ebp: 00000000
SS:    000296dc  esp: 00000002

CS:EIP: ff ff 8d b6 00 00 00 00 8d bf

Stack:
00000002 eef3f000 00000032 ff73f000
00000006 e2c3f000 00000036 ef57f000
0000000a eef3f000 0000003a ff53f000
0000000e eef3f000 0000003e 1c4ef000
00000012 ff54f000 00000042 f84dc000
00000016 143ff000 00000046 f841f000
0000001a 13e7f000 0000004a aaf8f000
0000001e fea5f000 0000004e e739f000
00000022 e987f000 00000052 9d27f000
00000026 eef3f000 00000056 e82af000

Can RAM cause freezes and reboots like that? I will try and get my hands on two other sticks and see if they work, but in the meanwhile I really wanna know what I'm looking at. The RAM, as far as I got with Memtest, checked out without errors. One stick I got as far as 70% and when both were checked, 30-something.

Specs:

Core2Quad Q9550 2,83 GHz @ 1,2V
Corsair XMS2 2x2Gig 800 Mhz 5-5-5-18 @ 1,8V
Asus P5Q Pro Motherboard
CoolerMaster RealPower M620 (620W)
Leadtek GTX 275, 896 Mb @ stock
2x WD5000AAKS 500Gig
Creative X-Fi XtremeMusic
 
Last edited:

RadiclDreamer

Diamond Member
Aug 8, 2004
8,622
40
91
Run memtest86+ and make sure the ram is good for a day or so, a few hours isnt always enough to show errors
 

progrox

Junior Member
Mar 25, 2005
10
0
0
Well, I can't. I tried to complete MemTest twice and it didn't work.

Think I'll just conclude that they sent me bad RAM.
 

COPOHawk

Senior member
Mar 3, 2008
282
1
81
As this point...I would still look at bad ram. however, if you get a different set of sticks in there and STILL have the same problem...I would replace the MOBO.

I have seen a lot of wierd errors due to failing mobos, and using the logical troubleshooting method, if you replace the ram and the issues still exist, it must be a memory controller issue, bad RAM slot, etc.

HTH.
 

GaryJohnson

Senior member
Jun 2, 2006
940
0
0
I have a P5Q3 and I had to really play around with the BIOS to get my memory stable. I ended up needing to change the AI Clock Twister setting from "AUTO" to "Lighter".
 

TJCS

Senior member
Nov 3, 2009
861
0
71
maybe you can test the ram in the other machine for a while. Sometimes there are compatibility issues between motherboards and ram.
 

progrox

Junior Member
Mar 25, 2005
10
0
0
I'm taking the RAM to my brother's computer next week. My BIOS is already up to date, though. Also note how I used exactly the same kind of RAM before and it was running fine, until it turned faulty and I RMA'ed.