• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

PAGE_FAULT_IN_NONPAGED_AREA Reoccurring BSOD

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

istari675

Member
Joined
Jun 7, 2014
I have been experiencing a BSOD regularly while playing certain games, and anytime I try and torrent. It seems to have started when I first upgraded to Windows 10. My Windows 10 installation is on a SSD. SFC Scan returned with no integrity violations. I ran a full MemTest86 and it completed with no errors found. The Bluescreenview info is as follows:

PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code: 0x00000050
Parameter 1: ffff9b80`006f56d8
Parameter 2: 00000000`00000000
Parameter 3: fffff801`aa4e2d02
Parameter 4: 00000000`00000002
Caused by Driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+14a2b0
Crash Address: ntoskrnl.exe+14a2b0

The following is a link to the full .dmp file:
 
Bugcheck code points directly to ram.
1 pass of Memtest isn't enough.
 
I didnt really have options to do multiple passes when I ran MemTest86.

2 things:

1) memtest86+ is newer than memtest86 (you are probably using memtest86+ , but just making sure)

2) memtest is usually "set it and forget it". After the first test is run it will continue with more passes until you tell it to stop. Are you saying your does not do this? Here is some info about using memtest. It states
When the memtest starts basically let it run and your main goal is to get pass (usually around 10 but more is better for ultimate stability).
 
It was easier to just test it using a torrent instead. It seems like I stopped the error from happening when I took out a specific memory stick, so I am in the process of returning it, and I am going to torrent as much as I can tonight to try and cause the error to trigger again. It would always BSOD before the 10 minute mark, and I am currently at the 2 hour mark, so thank you for the help!

EDIT: I actually tested out the sticks I know are working in the slots that the last memory sticks were inserted and the issue reappeared. Could this potentially be coming from the memory slots in the motherboard? This issue did first appear when I installed Windows 10, but now that I think of it that was not too far away from when I had originally purchased this motherboard.
 
Last edited:
It was easier to just test it using a torrent instead. It seems like I stopped the error from happening when I took out a specific memory stick, so I am in the process of returning it, and I am going to torrent as much as I can tonight to try and cause the error to trigger again. It would always BSOD before the 10 minute mark, and I am currently at the 2 hour mark, so thank you for the help!

EDIT: I actually tested out the sticks I know are working in the slots that the last memory sticks were inserted and the issue reappeared. Could this potentially be coming from the memory slots in the motherboard? This issue did first appear when I installed Windows 10, but now that I think of it that was not too far away from when I had originally purchased this motherboard.

Yes. That's why we instruct people to test each memory stick in every slot.

Page faults can also be caused by buggy drivers or apps that have "memory leaks." They don't release memory as they should when closed.
 
Last edited:
This one might be a 'bad' driver issue, 2 drivers held in RAM appear to be corrupt. Possibly malware or AV involvement, one of those drivers, win32k.sys (Windows graphics) is a common target (Flash exploits, etc.) and, as a result, has probably been the most frequently updated/patched Windows driver in the last 5 years.

The number of older drivers in the dump suggest this is an Upgrade to W10, they're the most likely to have issues with older 3rd party drivers down the line.

Code:
Loading Dump File [C:\Users\Me\SysnativeBSODApps\100816-13578-01.dmp]
Built by: 14393.206.amd64fre.rs1_release.160915-0644
System Uptime: 0 days 2:04:58.327
*** WARNING: Unable to verify timestamp for bcmwl63a.sys
*** ERROR: Module load completed but symbols could not be loaded for bcmwl63a.sys
*** 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 50, {ffff9700006f56d8, 0, fffff80049edbd02, 2}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Bugcheck code 00000050
Arguments: 
Arg1: ffff9700006f56d8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80049edbd02, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE
MaxSpeed:     4000
CurrentSpeed: 4000
BiosVersion = 1603
BiosReleaseDate = 08/15/2014
SystemManufacturer = ASUS
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
SystemProductName = All Series
BaseBoardProduct = MAXIMUS VI HERO

The most likely 'bad' drivers involved would be 3rd party and pre dating W10's Release (I don't see any known bad driver versions jumping off the page):

Code:
**************************Sat Oct  8 19:38:28.697 2016 (UTC + 1:00)**************************
WmXlCore.sys                Tue Apr 27 21:09:26 2010 (4BD74476)
WmBEnum.sys                 Tue Apr 27 21:10:19 2010 (4BD744AB)
AsUpIO.sys                  Tue Aug  3 03:47:59 2010 (4C57835F)
truecrypt.sys               Tue Feb  7 09:09:36 2012 (4F30EA50)
AsIO.sys                    Wed Aug 22 10:54:47 2012 (5034AC67)
ambakdrv.sys                Tue Dec 25 08:46:35 2012 (50D967EB)
ammntdrv.sys                Tue Dec 25 08:46:37 2012 (50D967ED)
amwrtdrv.sys                Tue Dec 25 08:46:38 2012 (50D967EE)
speedfan.sys                Sat Dec 29 20:59:35 2012 (50DF59B7)
RTCore64.sys                Mon Mar 11 05:32:06 2013 (513D6C56)
gzflt.sys                   Mon Apr 22 11:21:00 2013 (51750F0C)
file_tracker.sys            Thu Sep  4 13:49:39 2014 (54085FE3)
fltsrv.sys                  Tue Nov 11 12:01:53 2014 (5461FAB1)
snapman.sys                 Wed Nov 12 10:54:05 2014 (54633C4D)
LGVirHid.sys                Fri Apr 24 22:20:53 2015 (553AB3B5)
LGJoyXlCore.sys             Fri Apr 24 22:20:57 2015 (553AB3B9)
LGBusEnum.sys               Fri Apr 24 22:21:00 2015 (553AB3BC)
bcmwl63a.sys                Thu May 14 22:38:53 2015 (555515ED)
iaStorA.sys                 Wed Jun  3 10:38:57 2015 (556ECB31)
lgcoretemp.sys              Tue Jun  9 17:52:10 2015 (557719BA)
tib.sys                     Fri Jul 17 09:27:03 2015 (55A8BC57)
tib_mounter.sys             Fri Jul 17 13:21:34 2015 (55A8F34E)
 
It seems like I have verified that it cannot be bad memory sticks or the slot. I had the blue screen in every configuration rotating sticks and slots. Is there anything I can do in terms of finding the cause? This issue seems to have started when I installed Windows 10, and I had about the same stuff installed at the time so I cant narrow the list down very much.

EDIT: I always assumed they were just a scam, but do you think one of those driver update scans would be worth getting? If so what would be the most reputable and preferably free one.
 
Last edited:
Use the Search facility in the DRT here: https://www.sysnative.com/drivers/

That should give you enough clues for the older drivers listed, if you can't track down a driver for hardware, post the driver name and we'll try to find a recent one. If the driver is for a utility that isn't vital during troubleshooting, uninstall the software package for it, you can always reinstall the latest version once you have regained stability.

Remember, hardware trumps software: if you haven't done 8+ full runs with MemTest86+ on each sick, and in each slot with a known good stick, you'll need to do so if updating all drivers + uninstalling non-vital utilities doesn't fix it.
 
If you're running Memtest86+ from bootable media (bootable USB stick or bootable DVD), which you should be, windows drivers are a non factor. ;)
You have bad ram.
 
I have two pairs of memory and unless they BOTH failed or BOTH of the memory slots are causing the issue that cannot be the problem. I spent two hours today taking memory out, and moving it around and it still causes the error in any memory configuration. I tried updating my drivers and now my system is running into a new BSOD at boot 0xc0000021a
 
It seems like I have verified that it cannot be bad memory sticks or the slot. I had the blue screen in every configuration rotating sticks and slots. Is there anything I can do in terms of finding the cause? This issue seems to have started when I installed Windows 10, and I had about the same stuff installed at the time so I cant narrow the list down very much.

EDIT: I always assumed they were just a scam, but do you think one of those driver update scans would be worth getting? If so what would be the most reputable and preferably free one.

What do you mean when you talk about "driver update scans"? I hope you are not using one of those third party driver update scanners like the ones by Slimware that often are found on OEM computers.
 
Nah I just grabbed what I could from the motherboard page. Guess something didn't go right because it's boot looping now.
 
A 0xc0000021a bugcheck is entirely different, Usual causes (in order of likelihood): User-mode device driver, system service, or third-party application, Mismatched system files. So, you need to clean out those old drivers.

To give us a better chance of figuring out what's going on, please read and follow the instructions here, attach the required files here in a zip (compressed files) format and we can work through them.

Don't expect a reply from me tonight, it's 01:30 and I'm bushed.

Oh, if you are fresh and eager to dig deeper for us, a dump or two from Driver Verifier would be useful, again, read and follow carefully (even if you do, it might still BSOD on Boot!), ensure you make a fresh System Restore point before enabling it: https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html
 
istari,

Tell us about your computer. Give us some details about the hardware: motherboard make and model, RAM make and model. PSU make and model, CPU, CPU cooler make and model, storage make and model (spinner hard drive? SSD?), GPU make and model, etc.

Is this a mass produced computer like from Dell or HP? If so, what is the model number? How long has it been in service?
 
Some of the hardware details are in the code I posted earlier, here's some more before i hit the sack:

CPUID: "Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz"
MaxSpeed: 4000
CurrentSpeed: 4000
[SMBIOS Data Tables v2.7]
[DMI Version - 0]
[2.0 Calling Convention - No]
[Table Size - 3230 bytes]

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
Vendor American Megatrends Inc.
BIOS Version 1603
BIOS Starting Address Segment f000
BIOS Release Date 08/15/2014
BIOS ROM Size 800000
BIOS Characteristics
07: - PCI Supported
10: - APM Supported
11: - Upgradeable FLASH BIOS
12: - BIOS Shadowing Supported
15: - CD-Boot Supported
16: - Selectable Boot Supported
17: - BIOS ROM Socketed
19: - EDD Supported
23: - 1.2MB Floppy Supported
24: - 720KB Floppy Supported
25: - 2.88MB Floppy Supported
26: - Print Screen Device Supported
27: - Keyboard Services Supported
28: - Serial Services Supported
29: - Printer Services Supported
32: - BIOS Vendor Reserved
BIOS Characteristic Extensions
00: - ACPI Supported
01: - USB Legacy Supported
08: - BIOS Boot Specification Supported
10: - Specification Reserved
11: - Specification Reserved
BIOS Major Revision 4
BIOS Minor Revision 6
EC Firmware Major Revision 255
EC Firmware Minor Revision 255
[System Information (Type 1) - Length 27 - Handle 0001h]
Manufacturer ASUS
Product Name All Series
Version System Version
Serial Number System Serial Number
UUID 00000000-0000-0000-0000-000000000000
Wakeup Type Power Switch
SKUNumber All
Family ASUS MB
[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]
Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VI HERO
Version Rev 1.xx
Serial Number 140120946001804
Asset Tag
Feature Flags 09h
-316587376: - (null)
-316587328: - (null)
Location To be filled by O.E.M.
Chassis Handle 0003h
Board Type 0ah - Processor/Memory Module
Number of Child Handles 0
[System Enclosure (Type 3) - Length 22 - Handle 0003h]
Manufacturer Chassis Manufacture
Chassis Type Desktop
Version Chassis Version
Serial Number
Asset Tag Number
Bootup State Safe
Power Supply State Safe
Thermal State Safe
Security Status None
OEM Defined 0
Height 0U
Number of Power Cords 1
Number of Contained Elements 0
Contained Element Size 0
[Onboard Devices Information (Type 10) - Length 8 - Handle 0024h]
Number of Devices 2
01: Type Ethernet [enabled]
01: Description Onboard Ethernet
02: Type Sound [enabled]
02: Description Onboard Audio
[OEM Strings (Type 11) - Length 5 - Handle 0025h]
Number of Strings 4
1 To Be Filled By O.E.M.
2 To Be Filled By O.E.M.
3 Otacon
4 To Be Filled By O.E.M.
[System Configuration Options (Type 12) - Length 5 - Handle 0026h]
[Memory Device (Type 17) - Length 34 - Handle 0042h]
Physical Memory Array Handle 0043h
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelA-DIMM0
Bank Locator BANK 0
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer 0420
Serial Number
Asset Tag Number
Part Number F3-12800CL9-4GBRL
[Physical Memory Array (Type 16) - Length 23 - Handle 0043h]
Location 03h - SystemBoard/Motherboard
Use 03h - System Memory
Memory Error Correction 03h - None
Maximum Capacity 33554432KB
Memory Error Inf Handle [Not Provided]
Number of Memory Devices 4
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 0044h]
Starting Address 00000000h
Ending Address 003fffffh
Memory Device Handle 0042h
Mem Array Mapped Adr Handle 004bh
Partition Row Position [Unknown]
Interleave Position [Unknown]
Interleave Data Depth [Unknown]
[Memory Device (Type 17) - Length 34 - Handle 0045h]
Physical Memory Array Handle 0043h
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelA-DIMM1
Bank Locator BANK 1
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer 0420
Serial Number
Asset Tag Number
Part Number F3-12800CL9-4GBRL
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 0046h]
Starting Address 00800000h
Ending Address 00bfffffh
Memory Device Handle 0045h
Mem Array Mapped Adr Handle 004bh
Partition Row Position [Unknown]
Interleave Position [Unknown]
Interleave Data Depth [Unknown]
[Memory Device (Type 17) - Length 34 - Handle 0047h]
Physical Memory Array Handle 0043h
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelB-DIMM0
Bank Locator BANK 2
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer 0420
Serial Number
Asset Tag Number
Part Number F3-12800CL9-4GBRL
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 0048h]
Starting Address 00400000h
Ending Address 007fffffh
Memory Device Handle 0047h
Mem Array Mapped Adr Handle 004bh
Partition Row Position [Unknown]
Interleave Position [Unknown]
Interleave Data Depth [Unknown]
[Memory Device (Type 17) - Length 34 - Handle 0049h]
Physical Memory Array Handle 0043h
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelB-DIMM1
Bank Locator BANK 3
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer 0420
Serial Number
Asset Tag Number
Part Number F3-12800CL9-4GBRL
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 004ah]
Starting Address 00c00000h
Ending Address 00ffffffh
Memory Device Handle 0049h
Mem Array Mapped Adr Handle 004bh
Partition Row Position [Unknown]
Interleave Position [Unknown]
Interleave Data Depth [Unknown]
[Memory Array Mapped Address (Type 19) - Length 31 - Handle 004bh]
Starting Address 00000000h
Ending Address 00ffffffh
Memory Array Handle 0043h
Partition Width 04
[Cache Information (Type 7) - Length 19 - Handle 004ch]
Socket Designation CPU Internal L1
Cache Configuration 0180h - WB Enabled Int NonSocketed L1
Maximum Cache Size 0100h - 256K
Installed Size 0100h - 256K
Supported SRAM Type 0002h - Unknown
Current SRAM Type 0002h - Unknown
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Other
Associativity 8-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 004dh]
Socket Designation CPU Internal L2
Cache Configuration 0181h - WB Enabled Int NonSocketed L2
Maximum Cache Size 0400h - 1024K
Installed Size 0400h - 1024K
Supported SRAM Type 0002h - Unknown
Current SRAM Type 0002h - Unknown
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Unified
Associativity 8-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 004eh]
Socket Designation CPU Internal L3
Cache Configuration 0182h - WB Enabled Int NonSocketed L3
Maximum Cache Size 2000h - 8192K
Installed Size 2000h - 8192K
Supported SRAM Type 0002h - Unknown
Current SRAM Type 0002h - Unknown
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Unified
Associativity 16-way Set-Associative
[Processor Information (Type 4) - Length 42 - Handle 0052h]
Socket Designation SOCKET 1150
Processor Type Central Processor
Processor Family 01h - Other
Processor Manufacturer Intel
Processor ID c3060300fffbebbf
Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4012MHz
Status Enabled Populated
Processor Upgrade Specification Reserved
L1 Cache Handle 004ch
L2 Cache Handle 004dh
L3 Cache Handle 004eh
Serial Number [String Not Specified
 
I have two pairs of memory and unless they BOTH failed or BOTH of the memory slots are causing the issue that cannot be the problem. I spent two hours today taking memory out, and moving it around and it still causes the error in any memory configuration. I tried updating my drivers and now my system is running into a new BSOD at boot 0xc0000021a

Your BSOD code points at corruption of system files. Direct result of bad ram.
You can deny all you want, but I speak the truth. Test the ram the proper way.
 
Last edited:
Well the memory has been failing for a year now if that is the case, but in the process of troubleshooting I now cannot boot. Made an installation media and the automatic repair failed. Sfc scan just results in Windows resource protection not allowing the scan to complete. For some reason the installation media is asking me to boot off the local drive to run system restore as well.
 
Boot sector is missing or corrupt? Bad memory or failing system disk?
 
Back