BSOD when awakening from sleep; ntoskrnl and others

johnhoh said:

The only reason we are using the svga driver is to troubleshoot. It is not meant as a permanent solution. So for now, use the svga mode.

Think of hibernate as a deeper form of sleep. It uses less power but is slower to enter sleep and slower to wake. For our purposes we need it disabled, so do this

Start > run > powercfg -hibernate off (press enter)

After doing that hibernate is disabled, and now you can enter normal sleep by just using the command to do so

Start > run > rundll32.exe powrprof.dll,SetSuspendState (press enter)

Then give it a minute to sleep, and then once its asleep press the mouse or enter key or however you normally wake from sleep, and see if it wakes correctly, or crashes. If it is stable, then use the computer for a a half hour doing random things, then enter sleep again. See if it wakes correctly. If it does, then its probable that your graphics hardware or graphics driver is at fault. And yes, an inexpensive graphics card is then a viable solution, but ONLY IF the computer can repeatedly resume from sleep without crashing while using the svga driver.

And yes simply using hibernate instead of normal sleep is another option, eliminating the need to get a different graphics card. Many computers that fail to sleep/wake in normal sleep mode are able to sleep/wake in hibernate sleep mode. But you will want to see if you are comfortable with the slowness of hibernate sleep and wake. You re-enable it by doing the command from above but substitute on for off.

Are you using a spinning disk, or an SSD disk?

Did msinfo32 show you zero issues for problem devices?

Be aware that no matter how the troubleshooting goes here, its also possible you have a hardware problem (usually on the motherboard) that is causing this. We're just guessing our way through some possibilities now.

John, thank you a million times for all the help!! I am using an SSD, a brand new Samsung. msinfo32 said I have zero problems.

By the way, I was able to cancel the order for the PSU.

I swear this system is cursed.

Based on John's input and my troubleshooting, I bought a $50 Radeon R5 220 card from Best Buy yesterday morning. It booted up fine and installed AMD drivers. When I went to install AMD Catalyst Control Center to update the drivers and maximize the video functionality, I got "failure to install" errors. Spent about 2.5 hours trying to troubleshoot that and got no where. Card was returned to Best Buy.

Ordered an Nvidia card from Newegg that should arrive tomorrow. Fingers are crossed.

since your initial blue screen post showed an atixxxx error, its understandable that a new radeon card also had an error, so moving to nvidia is a good move. If the nvidia card produces errors also, the problem is likely a bad motherboard.

WHAT HAPPENED TO PLUG 'N PLAY!?

johnhoh said:

since your initial blue screen post showed an atixxxx error, its understandable that a new radeon card also had an error, so moving to nvidia is a good move. If the nvidia card produces errors also, the problem is likely a bad motherboard.

Thanks again John!!! We'll see how it goes. My hair is getting grayer by the hour!

The saga continues. Installed the new Nvidia card and all drivers installed with no issue unlike the Radeon card. Still getting BSODs.

I continue to follow John's advice and have therefore ordered a new motherboard along with a new CPU, the Ryzen 3 2200G that has onboard graphics. Those parts arrive tomorrow. We will see how it goes. Along with 8gb of DDR4, this little endeavor is setting me back an additional approx. $275. Lovely.

right before you shutdown the machine for the final time prior to replacing the motherboard and cpu, I recommend following the instructions in the link. Or if you prefer, don't follow them, and just re-install windows from scratch.

Many recommend always re-installing windows from scratch when installing a new motherboard. I have done the below dozens of times when swapping motherboards/cpus and its worked fine every time, so in my view a scratch install is called for only if the below fails.

New hardware upgrade problem.

Install went off without a hitch; did not have to reinstall OS. All tests have been positive thus far thereby pointing to either a bad motherboard (most likely based on John's analysis) or a bad CPU. Fingers remain crossed.