BSOD caused by PAGE_FAULT_IN_NONPAGED_AREA ntoskrnl.exe

nazkgv

Prominent
Oct 3, 2017
1
0
510
I have been getting many BSOD crashes in the last few days (~16) mostly when I close a full screen game like Dota 2 and Fifa 18. Please help me solve this. Thank you. Here's the details:

==================================================
Dump File : 092817-31265-01.dmp
Crash Time : 28/9/2017 1:18:04 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff901`47187b08
Parameter 2 : 00000000`00000000
Parameter 3 : fffff960`00af28b3
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14f1a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14f1a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092817-31265-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 417,152
Dump File Time : 28/9/2017 1:19:32 AM
==================================================

here's the minidump file https://www.dropbox.com/s/n36zg2feozg0a7u/dmp.zip?dl=0

 
Solution
Most likely an issue from RAM - you can run memtest86 on your RAM, see if it throws any errors.

It could also be a result from maybe installing a new piece of hardware or drivers for your hardware. Have you changed anything in the past 2-3 weeks? Did you install a new driver a few weeks back? Did you install some new hardware a few weeks back?

Either something has broken (could be an issue with RAM or even possibly HDD) or something had been changed (new hardware/driver/software). The trick is, trying to pinpoint the exact issue and getting it fixed.

neatfeatguy

Respectable
May 24, 2016
192
1
1,860
Most likely an issue from RAM - you can run memtest86 on your RAM, see if it throws any errors.

It could also be a result from maybe installing a new piece of hardware or drivers for your hardware. Have you changed anything in the past 2-3 weeks? Did you install a new driver a few weeks back? Did you install some new hardware a few weeks back?

Either something has broken (could be an issue with RAM or even possibly HDD) or something had been changed (new hardware/driver/software). The trick is, trying to pinpoint the exact issue and getting it fixed.
 
Solution