Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ntoskrnl.exe

  • Please log in to reply
1 reply to this topic

#1 raiden453


  • Members
  • 3 posts
  • Gender:Male
  • Local time:07:09 AM

Posted 13 September 2016 - 08:44 PM

System Spec
Computer type:PC/DesktopOS:windows 10 pro 64x CPU:intel 4790kMotherboard:msi z97 gaming 7Memory:2x G.SKILL Ripjaws X Series 8GBGraphics Card(s):evga gtx 970 SC
Samsung Evo 850 500gb ssd
Hello Everyone.
I keep getting this error. This usually happens when the computer is idling for an extended period of time. These are some things I've done to trouble shoot the issue.
1. I've ran sfc and it was clean
2. 99% of the time this happens when my computer is idling.
3. I ran driver verifier and it crashed immediately after rebooting. and ive included the results in the logs
4. checked the logs manually with bluescreen viewer, and I see that ntoskrnl.exe is the main culprit 
5. Ran memtest86 overnight and no errors.
6. nothing is overclocked
Dump File         : 091316-9234-01.dmp
Crash Time        : 9/13/2016 6:22:27 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : 00000000`00000010
Parameter 2       : 00000000`00000002
Parameter 3       : 00000000`00000001
Parameter 4       : fffff803`e030215e
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a0d0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.14393.103 (rs1_release_inmarket.160819-1924)
Processor         : x64
Crash Address     : ntoskrnl.exe+14a0d0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\WINDOWS\Minidump\091316-9234-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 14393
Dump File Size    : 520,028
Dump File Time    : 9/13/2016 6:23:11 PM

Attached Files

BC AdBot (Login to Remove)



#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,084 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:09 AM

Posted 14 September 2016 - 07:21 AM

ntoskrnl.exe (also seen as ntkrnlpa.exe, ntkrnlmp.exe, or ntkrpamp.exe) is the kernel (core) of the Windows operating system.  It is protected by security features and the Windows System File Checker.  As such, if ntoskrnl.exe was to blame, you'd be experiencing many more problems other than the occasional BSOD.

In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own.  When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space.  At this point the OS panics and throws a BSOD to prevent damage to the system.

If the culprit (the offending 3rd party driver) hasn't exited yet, then a BSOD analyst may be able to find traces of it in the reports/dumps.  If the culprit has exited, then the chase is on and further tests/reports will be needed to help identify what actually caused it.

More info here:  https://en.wikipedia.org/wiki/Ntoskrnl.exe

Your UEFI/BIOS (version V1.12) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Although you appear to have a reasonable number of Windows Update hotfixes for this version of your OS, please double check for any new Windows Updates.  It only takes one update to cause a problem, so it's essential that you have all of them.  The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Corsair Link software has been known to cause BSOD's in some WIndows systems.

Please uninstall it


MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

The WER section of the MSINFO32 report shows some sign of video issues.


- download a fresh copy of the latest, W10 compatible video drivers for your system.  Then uninstall the current software (from Control Panel...Programs and Features) and then install the freshly downloaded software

- run these free hardware diagnostics (start with the video tests):  http://www.carrona.org/hwdiag.html



The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Tue Sep 13 21:22:27.311 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\091316-9234-01.dmp]
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Built by: 14393.103.amd64fre.rs1_release_inmarket.160819-1924
System Uptime:0 days 0:39:19.644
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :memory_corruption
BugCheck A, {10, 2, 1, fffff803e030215e}
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803e030215e, address which referenced memory
PROCESS_NAME:  HD-Frontend.exe
CPUID:        "Intel® Core™ i7-4790K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4000
  BIOS Version                  V1.12
  BIOS Release Date             02/16/2016
  Manufacturer                  MSI
  Product Name                  MS-7916
  Baseboard Product             Z97 GAMING 7 (MS-7916)

3rd Party Drivers:

The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Tue Sep 13 21:22:27.311 2016 (UTC - 4:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
corsveng2kamd64.sys         Thu Aug 14 10:08:17 2014 (53ECC2D1)
XtuAcpiDriver.sys           Thu Feb 26 07:51:57 2015 (54EF16ED)
lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
e22w8x64.sys                Sat Aug 29 13:07:56 2015 (55E1E6EC)
asstahci64.sys              Thu Oct  1 03:34:51 2015 (560CE21B)
SeLow_x64.sys               Sun Oct 18 07:12:14 2015 (56237E8E)
SaiBus.sys                  Thu Jan 21 05:46:48 2016 (56A0B718)
SaiMini.sys                 Thu Jan 21 05:46:48 2016 (56A0B718)
bwcW10x64.sys               Fri Jan 22 17:08:51 2016 (56A2A873)
cpuz139_x64.sys             Wed Jan 27 04:18:15 2016 (56A88B57)
asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)
asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)
BstkDrv.sys                 Tue Mar 22 13:10:08 2016 (56F17C70)
nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)
tap0901.sys                 Thu Apr 21 05:10:05 2016 (571898ED)
HD-Hypervisor-amd64.sys     Tue Apr 26 06:07:03 2016 (571F3DC7)
nvhda64v.sys                Tue May 10 04:59:01 2016 (5731A2D5)
tib_mounter.sys             Thu Jun  2 08:37:46 2016 (5750289A)
NvStreamKms.sys             Fri Jun  3 07:28:21 2016 (575169D5)
LGVirHid.sys                Mon Jun 13 14:47:03 2016 (575EFFA7)
LGJoyXlCore.sys             Mon Jun 13 14:47:06 2016 (575EFFAA)
LGBusEnum.sys               Mon Jun 13 14:47:08 2016 (575EFFAC)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
RTKVHD64.sys                Tue Jul 19 06:56:25 2016 (578E0759)
file_tracker.sys            Wed Jul 27 08:37:51 2016 (5798AB1F)
fltsrv.sys                  Wed Jul 27 10:01:09 2016 (5798BEA5)
snapman.sys                 Wed Jul 27 10:26:23 2016 (5798C48F)
tib.sys                     Wed Jul 27 11:30:02 2016 (5798D37A)
virtual_file.sys            Tue Aug  9 15:23:13 2016 (57AA2DA1)
aswRvrt.sys                 Thu Aug 18 10:12:01 2016 (57B5C231)
aswSnx.sys                  Thu Aug 18 10:12:50 2016 (57B5C262)
aswMonFlt.sys               Thu Aug 18 10:30:14 2016 (57B5C676)
aswVmm.sys                  Thu Aug 18 10:30:18 2016 (57B5C67A)
aswSP.sys                   Thu Aug 18 10:30:56 2016 (57B5C6A0)
nvlddmkm.sys                Thu Aug 25 16:31:18 2016 (57BF5596)

cpuz139_x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
BstkDrv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
virtual_file.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users