BSOD - Page Fault in Non-Paged Area

[lawike.vrk]

(MSI GS63VR 7RF) Blue screen of deaht on power up after periods of being off/asleep (Note that if I immediately bring stuff back from sleep, power the system back up the issue does not occur. If it does). After it restarts the issue doesn't come up till, again, the laptop enters sleep, or is off, for an extended period of time.

The error message is 'page fault in non paged are'. I checked my ram and am currently checking my second SSD. I'm pretty sure it's software related and don't know where to start?

Help?

 

[piechockidocent9]

If checkdisk checkdisk on your drives won't do anything you are probably correct and we have 3 suspects: windows update, driver change/demaged or recently installed software. Have to check if any updates or new apps were installed more or less at time it started occuring and delete them if so, see if no driver is lighting up in device manager and lastly inspect your startup services for anything suspicious running in the background. Possibly lucky for you problem has been touched here before so you might have luck with these too:

http/

http/

 

[lawike.vrk]

If checkdisk checkdisk on your drives won't do anything you are probably correct and we have 3 suspects: windows update, driver change/demaged or recently installed software. Have to check if any updates or new apps were installed more or less at time it started occuring and delete them if so, see if no driver is lighting up in device manager and lastly inspect your startup services for anything suspicious running in the background. Possibly lucky for you problem has been touched here before so you might have luck with these too:

http/

http/

Nothing came up for any of the tests I've done so far, hardware wise. In Device Manager should I manually check for updates on every single one or is there a program that'll do it>

 

[lawike.vrk]

If checkdisk checkdisk on your drives won't do anything you are probably correct and we have 3 suspects: windows update, driver change/demaged or recently installed software. Have to check if any updates or new apps were installed more or less at time it started occuring and delete them if so, see if no driver is lighting up in device manager and lastly inspect your startup services for anything suspicious running in the background. Possibly lucky for you problem has been touched here before so you might have luck with these too:

http/

http/

And another update: It does this only after about a minute of being off / in sleep mode apparently.

 

[piechockidocent9]

Yeah I got it is related strictly to sleep/waking up, it can still be a lot of things from mouse/keyboard to chipset driver. I was hoping for a struck of luck like a device showing yellow "!" in device manager, since there is no obvious symptom we need to dig deeper. Locate and analyze the dumb file from the bsod, upload it if you can so I and any other fellow willing to help can dig through it aswell. Here's the most straightforward way if you haven't done it before:

http/

 

[lawike.vrk]

Yeah I got it is related strictly to sleep/waking up, it can still be a lot of things from mouse/keyboard to chipset driver. I was hoping for a struck of luck like a device showing yellow "!" in device manager, since there is no obvious symptom we need to dig deeper. Locate and analyze the dumb file from the bsod, upload it if you can so I and any other fellow willing to help can dig through it aswell. Here's the most straightforward way if you haven't done it before:

http/

Yeah, I've attached a minidump.

https/i.imgur.com/tq23WTE.png

Screenshot of it.

And here's a link to it too: https/www.dropbox.com/s/4378bjzkhwr6u5k/011218-7031-01.dmp?dl=0

Edit:

So I reverted to Windows 10 version 1703 and it fixed two of the issues

https/i.imgur.com/KmbfI4g.png?1

EDIT 2:

FIXED IT


Went ahead and downloaed WhoCrashed and it stated that my WiFi drivers were the culprit. So I wiped it, reinstalled it after a restart and now I cannot replicate the BSoD.

 

[piechockidocent9]

Guess it was one of the main suspects after all, drag it took so much effort in identyfying particular driver. Was gonna ask ya to inspect ntoskrnl.exe with something like windows performance toolkit but whocrashed does even better job. Glad you managed to get it fixed and apologies for sudden break in response, work's been crazy lately hardly able to squize a coffee in ;-) Live long and bsodless from now on.