Overclock.net › Forums › General Hardware › General Processor Discussions › Confusing RAM issue
New Posts  All Forums:Forum Nav:

Confusing RAM issue

post #1 of 9
Thread Starter 
Hey forum members,


About a month ago I was playing a game on my computer when everything froze up and the sound jammed, nothing responded and I had to force the computer to shut down, I'm trying to remember when I overclocked my computer and I think it was before the first issue, I also set a new memory profile/voltage.The same thing happened a few times more before I got a bootable hardware checker disk, while running it froze and crashed on the memory test section, every other piece of hardware seemed to be fine. I then ran memtest and the same thing happened - it froze and crashed. So it seemed the issue was coming from a faulty memory stick.
I located what seemed to be faulty stick and removed it, after that everything ran fine at a 4.2Ghz overclock. I decided to put the memory stick back in for some reason and the computer worked fine again for about a week, then crashed and failed to boot, even removing the overclock and resetting, even reflashing the bios did nothing, this 4GB RAM stick seemed to hate my computer. However when checking the single stick of RAM in another desktop with memtest it did a full run with no faults detected. I have tried the working 4GB stick in other slots in the motherboard and it works fine.
Does anybody know what's going on here? The RAM which is causing my computer to freeze with no BSOD or error reports turns up no errors in windows memory diagnostics or memtest. Even with no overclock or memory voltage changes it refuses to work.

Any response would be greatly appreciated, this is driving me insane.
Tiggy.

For reference I have:
2x4GB DDR 3 Corsair Vengeance sticks
Gigabyte Z77x-d3h motherboard
Intel i5 3570k haswell CPU
post #2 of 9
When you tried the "bad" stick in another computer, and it worked, were the speed and timings set the same as they were in the original computer?
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
My System
(15 items)
 
  
CPUMotherboardGraphicsRAM
FX6300 Black M5A99X EVO R2.0 Nvidia GTS450 Team Vulcan PC3 12800 
Hard DriveOptical DriveCoolingOS
Samsung 840 PRO Asus DRW-1608P (x2) Custom Water Cooling Win7 (Ult), Win 8.1 & Win Server 2012 R2 
MonitorKeyboardPowerCase
2 X Samsung 915N Ducky Shine III, Blue Cherry/Blue LEDs PCP&C 1kw Lian Li PC-71 (W/Window) 
MouseAudio
Logiteck G400s none 
  hide details  
Reply
post #3 of 9
Thread Starter 
I'm afraid I don't know, I just put the stick in the other computer and ran some tests.
post #4 of 9
You said it worked in another slot on your MB? Maybe, that mem slot is somehow broke? Did you use too much force installing it?
post #5 of 9
Thread Starter 
I tried the functional memory stick in the other slots and it worked fine, so I don't think it's the slot. I'm always quite careful about installing the RAM as well.
post #6 of 9
Quote:
Originally Posted by ThatTiggy View Post

I tried the functional memory stick in the other slots and it worked fine, so I don't think it's the slot. I'm always quite careful about installing the RAM as well.

This lead me to think it is the slot on the motherboard. In other slots it works fine? right? Just that one slot it gives you issues? yes? Don't use that slot or RMA the board if you can. I didn't have to be you, It could have come a little screwed up. Figure the make thousands of these boards, they certainly do not test each one. Thats why you hear of people getting DOA motherboards and other parts.
post #7 of 9
Thread Starter 
I tried the ram sticks in different slots and it still plays up though which is why I'm confused.
Funnily enough earlier today my computer froze again despite me doing nothing and having the 'functional' ram stick in.
Also worth noting, if I put the two sticks in, most of the time the computer refuses to boot and you can tell because the CPU fan starts then stops, sounds like a definite hardware issue to me yet here I am typing on the same computer with no issues...
post #8 of 9
Quote:
Originally Posted by ThatTiggy View Post


For reference I have:
2x4GB DDR 3 Corsair Vengeance sticks
Gigabyte Z77x-d3h motherboard
Intel i5 3570k haswell CPU

#1 - Intel i5 3570K is not a Haswell CPU, it's an Ivy Bridge. LOL.

#2 - When you popped that memory into another computer and ran Memtest, it passed because it was probably running 1333 MHz 9-9-9-27 timings, which are JEDEC standards. You are probably running your BIOS memory overclock settings a little too hot for that memory. Back it down to some reasonable clock speed and then test it with Memtest86+ and see if it passes. If it does, then manually set it for the rated clock speed and timings from Corsair and see if that helps. If the RAM has XMP profiles, use those. Corsair makes about 50 models of Vengeance RAM, from really slow to moderately fast - and the specifications for every one of them are different.

Greg
post #9 of 9
Thread Starter 
Whoops, wasn't thinking when I typed that sorry, I meant Ivy Bridge.
I have since removed all overclocks and reset default bios settings and the cmos multiple times. I have had issue looking for the recommended settings by corsair but have tried the RAM on XMP profile 1 in the bios (I believe my ram supports XMP).
At this point in time Scan (where I bought all the components) are recommending I send off the CPU, Motherboard and RAM for an RMA. I just want to see if I can fix my computer before disassembling it and sending it off for 2 weeks.
Thanks for the help so far,

Tiggy
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: General Processor Discussions
Overclock.net › Forums › General Hardware › General Processor Discussions › Confusing RAM issue