Overclock.net › Forums › Components › Memory › RAM Causing BSOD maybe?
New Posts  All Forums:Forum Nav:

RAM Causing BSOD maybe?

post #1 of 2
Thread Starter 
My RAM: http://www.newegg.com/Product/Product.aspx?Item=N82E16820231277

I have 4x2 (8gb) of this RAM.

So what's happening exactly is that when I have my ram set to the default values ( 1.5v, 1600, 9-9-9-24) my computer becomes unstable and BSODS. What's even more weird is that when I have it set to 1.5v, 1333, 8-8-8-24. It is completely stable. My motherboard by default sets the RAM to 1.5v, 1333, 8-8-8-24. I don't understand why when the exact ram I have is the ram in the link above. I ran memtest86 and it threw up 12 errors while running at 1.5v, 1600, 9-9-9-24. Windows memory diagnostic said there was no errors at all. So I'm really confused. I've had this ram for 2 years now. Should I RMA it? Is there something wrong with it that I can fix? Or should I just leave it at 1.5v, 1333, 8-8-8-24? Please help!

Edit: None of the error's were red. It just said Errors: 12. I will run memtest86 again and take a picture after a complete round of passes.
post #2 of 2
Provide more specs on your system.

Which motherboard? Are the two compatible?

Did you memtest each stick individually? (Maybe one is bad and one is good, etc).

smile.gif
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
INTEL ASUS XFX  SAMSUNG 
Hard DriveOptical DriveCoolingOS
WD/ST LG KUHLER WINDOWS 
MonitorKeyboardPowerCase
LG/SAMSUNG IBM MODEL M CORSAIR THERMALTAKE 
MouseMouse PadAudio
MS INTELLIMOUSE EXPLORER 3.0 REGULAR LARGE PAD ONBOARD but it USED TO BE A XONAR DG  
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Memory
Overclock.net › Forums › Components › Memory › RAM Causing BSOD maybe?