• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Memory causes BSODs in Windows 8, but only after a cold boot? (warm reboot is fine..)

Dankk

Diamond Member
I've finally managed to narrow down the origin of my computer's BSODs. For a while, the errors were seemingly random and intermittent; but when they did happen, it was always right after starting Windows (usually only a few seconds after logging in). Further: I realized they only happened after a cold boot. After putting my PC through a "warm" reboot, however, no BSODs would occur.

I tested this by leaving my computer off for a while and then doing a cold boot directly into MemTest86. In the previous months when I tested my memory, I initiated the test having already used my PC immediately beforehand, so I technically "warm booted" into MemTest86. I was able to run the test for several hours and it passed with flying colors. No problems whatsoever.

But after cold-booting into MemTest86 proceeding a long period of inactivity, it immediately started throwing dozens of errors. Dozens turned into hundreds. Ergo, my RAM is observably having issues, particularly on cold boot. It would only make sense that I get the BSODs right after I cold-boot my machine.

Now the question is whether or not my memory is simply bad, or if it actually has compatibility issues with my motherboard? If it's incompatible, I don't want to RMA it back to the manufacturer for a replacement (because that obviously won't solve my problem). On the other hand, incompatibility means having to buy new memory altogether (and, you know, memory is really expensive right now).

I looked up my motherboard's RAM compatibility list and it's pretty limited, not to mention MSI doesn't even bother to keep it updated. I'm not sure what route to take. Maybe there's some kind of BIOS tweak that will make my RAM power on and function properly on cold boot so I won't have to deal with either? Does anyone have any ideas on what I should do?

I'm not an expert, so if my idea of incompatibility is obviously wrong or erroneous in any way, let me know.

--------

I should also mention that I've had this RAM for almost a year now. At first, I used it in Windows 7. Windows 7 was very stable with this RAM, save for one or two freak BSODs. But since I upgraded to a clean install of Windows 8 last summer, my BSODs have skyrocketed, and I know it's because of this memory. My hypothesis is that because Windows 8 boots up so much faster, the memory cannot "catch up" (?) with it in time, so it throws errors way more often. It's sounds kind of silly, but I hope that makes sense.

The memory I use is G.SKILL Ripjaws X Series 16GB (2 x 8GB) 240-Pin DDR3 1600. I use Intel XMP to set the memory timings automatically.

The motherboard I use is an MSI 990FXA-GD80 V2.

--------

One more thought: I actually used an MSI 990FXA-GD65 motherboard for a long time before it broke, and I just upgraded to the 990FXA-GD80 this last week. I get the BSODs on both motherboards. So because I've tested it on two motherboards, maybe I've ruled out incompatibility, and the RAM really is just bad? But the two models of motherboards are actually very close, and they are very similar to each other, so I can't be too sure.

I would honestly rather have the memory be bad, so I can simply return it for a replacement and not have to worry about buying new memory.
 
Last edited:
So... it turns out I neglected one of the most basic procedures of testing computer memory: I didn't test each module individually.

So now I've thoroughly tested both modules, individually, alternating back and forth between the two of them.

The result: One of my RAM modules works great. The other RAM module, however, produces errors every time. I repeatedly tested each module - using both slots on the motherboard - until I was certain that one of them was defective, and the other wasn't. I've deduced that the memory is indeed faulty. Don't know why I failed to do this earlier. I've initiated an RMA with G.SKILL and hopefully I'll be receiving some functional memory soon.
 
I had a similar issue. Tested each memory module individually and found the culprit. RMA with Corsair was nice and smooth. Testing using MemTest+ and then each module individually is always the best course of action.
 
Back
Top