Windows 10: BSOD when PC wakes from sleep after windows update

Hello!


I have an MSI GE65 Raider 9SE Laptop running the latest version of Windows 10. However, everything was going smoothly until I updated Windows to the latest version. Now, whenever I put my laptop to sleep and wake it up, it wakes up with a blue screen of death saying "page fault in non-paged area". I have conducted CPU, GPU and RAM stress test, the laptop works fine. I have even used the windows memory diagnostic tool but it returned with no errors. The laptop works fine the only time I get a BSOD is when I wake it up after sleep.


I have attached the dump files here: https://drive.google.com/file/d/1oUZv2B0y2Q4iprcsbLuoWPe0cCe1x8xw/view?usp=sharing


Lastly, I'm sorry if I didn't put this question in the correct format. It's my first post here. Let me know if you need additional information from me.

Thank you very much,


Asbaat

:)

 

BSOD due to netadaptercx.sys after waking the PC from Sleep

Hi Prakhar,

The steps you suggested did not solve the problem. I am still experiencing the BSOD when waking the computer from sleep. If you have an other suggestions they'd be greatly appreciated.

Regards,

Chris

 

Troubleshooting PCs spontaneously waking from sleep

I've also battled with sleep/wake issues over the years, and from experience have learned that trying to find, or rationalise, the root cause is a waste of time. All you need is `powercfg`.

`powercfg -devicequery wake_armed` from an Administrator PowerShell window/Command Prompt will give you a list of all devices that can possibly wake the PC. This command is interesting because very often, it will show devices that you'd never expect being able to wake your computer. I think in one instance I had the chipset device listed!

`powercfg -devicedisablewake "device_name_from_device_query"`will prevent said device from ever waking the computer. This command is 100% the only thing I have found that will resolve sleep/wake problems. Updating drivers, unplugging peripherals, switching to a cleaner power supply (UPS), changing ethernet cables... none of those have helped, yet`powercfg -devicedisablewake` has done the trick.

Note that occasionally, devices you have disabled wake for may start waking up the PC again - this happens if you plug a USB device into a different port, or occasionally when drivers are updated, because Windows sees it as a new device. In that case rerun `powercfg` to find and disable that device again.

If this does not resolve your wake issues, I would start looking at power fluctuations.

 

Troubleshooting PCs spontaneously waking from sleep

First off: I tried disabling wake-up by the mouse on both PCs and disabling USB Selective Suspend too, to no avail.

Thanks, I'll definitely look into that. Good to know that powercfg can list all wake-enabled devices, 'cause when I went through all ... eight-ish PCI-to-PCI bridge devices in Device Manager, none of them had wake events listed (in the "events" tab under Properties), which doesn't quite add up with one/more of them waking the PC a dozen or so times over the last few days. Of course, they don't even have the option to enable/disable waking the PC in the properties menu. I'll take a look at disabling a bunch of stuff through powercfg once I get home from work.

Sorry if I came across as rude, but honestly, your reply did not at all indicate that you'd read my post in the first place. I said I'd been looking at wake-up history in the Windows event log, and I listed several of the devices cited there as having woken up the PC. If you came away with the impression that I hadn't investigated this thoroughly, I suppose I might not have been clear enough, but it's all there in the post. While powercfg does give out some more detail (device IDs and such) than Event Viewer, it only lists the last wake-up, and as such doesn't really help in this instance, as it's clearly not a single device at fault, and tracking wake-ups over time seems more useful. Also, figuring out how to view wake-up events in the Event Log is what you do after you've concluded that powercfg isn't giving you enough information *Wink