• 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 tests fine but still causes blue screens

spdfreak

Senior member
New build- MSI FM2 MB and 1 8GB stick of Corsair XMS3 1333. It will run any and all tests- memtest, P95, etc all night long but it blue screens just idling sometimes or on startup. I swapped an old 4GB stick of G Skill (also 1333) and it seems to be fine. I actually swapped out the MB thinking it was a bad MB but the new one did the same. Any idea what is wrong here- voltages maybe?
 
Is it truly idle? One test that I sometimes find throws up problems is sitting the computer watching steam on the store. There is a flash program that scrolls back and forth and that often shows up problems with c states and dynamic clock speeds.

You didn't mention if you are overclocking but if you are this could be the cause, its a relatively common problem when overclocking.
 
I had this issue, what are you using to test? Memtest didn't come up with anything but Windows Memory Diagnostic found errors and I ended up getting it RMA'd.
 
no, not overclocking... no software loaded at all. Just Win7 and updates. I didn't try the Windows diagnostic but used memtest, memtest86, p95. It seems like it only did it when it was idle or very close with just windows background stuff running. I'll RMA it since I tried it in 2 different MB with the same results. It's just a strange situation that I'd like to figure out.
 
Give it a quick test with WMD, at least you'll be able to say that you found errors. I had to do this before they would accept my RMA, except they asked me to do it with Memtest.
 
no, not overclocking... no software loaded at all. Just Win7 and updates. I didn't try the Windows diagnostic but used memtest, memtest86, p95. It seems like it only did it when it was idle or very close with just windows background stuff running. I'll RMA it since I tried it in 2 different MB with the same results. It's just a strange situation that I'd like to figure out.
Run Memtest86 much longer, or try Goldmemory.
 
Back
Top