Vexing BSOD after W10 install despite working in safe mode and W7

dpark · 13 Jul 2020

I got the video to work by only putting in a single RAM module (previously, all 4 . Thinking this was now the problem, I have tried different configurations. I have 4 slots - A1 A2 B1 & B2. I installed each stick in each of the slots to further troubleshoot (one at a time) - I got some failures to start up / produce any video output as I did before. But when I reseated the stick / moved it, it didn't always replicate the failure. Thus, in trying out 4 sticks in 4 slots, and trying some twice or more if they failed, I probable tried ~24 startup attempts using just one 4GB stick at a time and cycling through each stick. When a stick was installed singularly in B1, the computer failed to start 4 times, and this happened once in slots A1 and A2 as well. B2 had 0.
I now put all 4 back in and it works as well, although in each of these cases, it typically will give me a BSOD sooner or later.

I have tried memtest with no reported errors - Does my RAM behavior help diagnose anything?

As for BIOS updates - I have not done this as I have never done that before, but I could try. I hesitate to given the manufacturers say it isn't usually necessary but if people think that it may help I can try.

This no longer seems to be a W10 problem - should I migrate this question to another hardware site? The only weird thing is that safe mode in W10 and windows 7 still don't have the BSOD problem though, which confuses the hell out of me. ALthough again, perhaps I haven't used those extensively enough to really say if it won't happen. I suppose that is my next step. Thanks again for reading and helping

essenbe · 13 Jul 2020

Are all of your ram modules the exact same make, model and frequency? Were they bought as a kit?

When you are testing ram it can be frustrating and time consuming. I always recommend Memtest86. You are testing the ram as well as the dimm slots. You errors can come from the ram module or from the dimm slot. Even 1 error is a failure. A good stick of ram should test good in every slot. Keep track of which stick you are/have tested and which slots they get tested in. Try to make the determination whether it is the stick or the slot.

Ztruker · 13 Jul 2020

This no longer seems to be a W10 problem - should I migrate this question to another hardware site? The only weird thing is that safe mode in W10 and windows 7 still don't have the BSOD problem though, which confuses the hell out of me. ALthough again, perhaps I haven't used those extensively enough to really say if it won't happen. I suppose that is my next step. Thanks again for reading and helping

This could still be a Windows problem:

What is Safe Mode?
On occasion, your device may be extremely slow to start or may not start at all. Safe Mode allows you to start your device using minimal functionality, limiting the number of apps and processes running. This can be handy as there could be times when your device has malicious files or processes running that’s hindering its performance or blocking you from using it. Safe Mode can stop these nuisances from opening and allow you to remove them by running antivirus scans after your computer starts.

Since the system runs WIndows 10 in Safe Mode then try a Clean Boot. See here: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

dpark · 21 Jul 2020

I wanted to update my progress. I checked the RAM more extensively, and blew out dust and used a super soft brush to dislodge anything in the RAM slots. I very lightly cleaned the actual RAM sticks as well just in case. I thought this might work given how much dust was there and that the RAM was intermittently giving me problems with startup, but also windows 10 safe mode and windows 7 didn't crash, which made me skeptical that this could be the solution.

Well, it has been a week or so now and the computer hasn't crashed since I cleaned it up. It was therefore a RAM hardware issue but a confusing one given memtest86 showed no problems and that it didn't fail consistently. Thanks to all of your suggestions.

essenbe · 21 Jul 2020

Thanks for letting us know.

Ztruker · 21 Jul 2020

I'll agree it was a RAM problem after it's run for a month or more.
Color me skeptical

but hopeful.