BSOD on cold boot only

Also try to enable the special pool option in the driver verifier. Of course, you enable it for all drivers except those from Microsoft

What about the PSU? When cold is it playing up? I also suspect something that is temperature dependant such as a bad solder joint or a low battery voltage.

philc43 said:

What about the PSU? When cold is it playing up? I also suspect something that is temperature dependant such as a bad solder joint or a low battery voltage.

The PSU was brand new in may 2017, so just a few years old. I acctually bought it after reading online that switching PSU might help.... but alas no.
The two oldest parts of my computer are two HDD drives that I just use for storage.

I will try to boot up in safe mode next time, and if that doesn't work I will try each RAM stick in isolation before I do something drastic like switching the battery.

<Sigh> This is so hard to troubleshoot.

- - - Updated - - -

Ok so last night before i shut down the computer, I went into msconfig and enabled safe mode before turning off. Then this morning I booted into safe mode and launched the CPU-Z CPU-benchmark. I then let windows stay in safe mode for about an hour before turning off safe mode and rebooting. When back in "normal" windows I launched the 3DMark Benchmark, and what do you know: it finished without any BSOD's.

So... probably like you guys said some bad solder... or maybe some driver that is acting up when some components (RAM, CPU, Motherboard) is cold. But of course: anyone's guess.

I will try the same tonight, but this time enabling safe mode with networking before I turn off for the night.

I have also read about driver verifier, but I would rather have that as a last resort as I don't want to risk being locked into an infinite crash-boot-loop.

So just a small update: I have now testet each of my two RAM-sticks in isolation, and it seems like the problem only occurs with the one stick. I will do another test later today to confirm, but it seems like I need new RAM. Will post here what the final result will be. In the meantime: thank you to everybody who helped for your time, it is appreciated.

Greetings. I do not think my experience will be relevent in this situation, but nevertheless I had a very similar problem a year ago. After repeated attempts using similar diagnostics I finally just swapped out my monitor and have not had an issue since. Go figure.

MachineLanguage said:

Greetings. I do not think my experience will be relevent in this situation, but nevertheless I had a very similar problem a year ago. After repeated attempts using similar diagnostics I finally just swapped out my monitor and have not had an issue since. Go figure.

That seems quite drastic, but I'm glad it worked out for you.

Grimnir79 said:

That seems quite drastic, but I'm glad it worked out for you.

My Issue persisted for about 6 months intermittently and then consistently. During the logical troubleshooting process I eliminated potential issues. Eventually I borrowed the wife's monitor. It worked immediately so I used for a couple of weeks with no further issues. Finally bought a replacement myself.

Ok so I switched out the RAM and now problem is solved. Will wait a few days and then mark this as solved.

Funny problem you had MachineLanguage, never heard that before.

MachineLanguage said:

My Issue persisted for about 6 months intermittently and then consistently. During the logical troubleshooting process I eliminated potential issues. Eventually I borrowed the wife's monitor. It worked immediately so I used for a couple of weeks with no further issues. Finally bought a replacement myself.

what model was that monitor?