PAGE_FAULT_IN_NON_PAGED_AREA, random BSODs

Hello all, and thanks in advance for any assistance provided. I only recently built a new system in February, and I've been getting infrequent blue screens of death ever since installing Windows. The errors have always been one of two types, and the BSODs never name a specific file. The two errors are "Page Fault in Non-Paged Area" and "IRQL Not Less or Equal", with typical stop codes of 0x00000050 and 0x000000D1. I haven't been able to find any specific cause after several straight days of testing, and I'm unsure of what to do next. I've attached the only current dump file as viewed by BluescreenView.

I would have attached a dump file itself, but I hadn't yet switched to minidumps. Whoops.

TROUBLESHOOTING STEPS TAKEN

I have already done an eight pass test on my memory using MemTest, no errors were found. I have not yet done tests on individual sticks.

I have manually reseated everything on the motherboard; memory, video card, hard drive cables.

I have reinstalled Windows after a clean format.

I have done multiple virus scans with Avast, both in and out of Safe Mode.

All drivers have been updated with clean installations.

ANYTHING NOTEWORTHY

So far, all of the BSODs have happened while playing a game or watching videos (either in Media Player Classic or through Flash players on websites such as YouTube). The dump file held no information other than that there was a crash and some numbers I don't personally understand.

That's all the information I can provide currently; thank you in advance for any help that can be provided.

Hi anthonylert.

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup program before you upload another zip.

Avast is failing here, all around.

Code:

fffff880`0e42e268  fffff880`01d28b45Unable to load image aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
 aswSnx+0x60b45

Code:

fffff880`0e42e118  fffff880`04f75ebeUnable to load image aswSP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
 aswSP+0x21ebe

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one, for a safety reason, as the installed AV failed.

Realtek network is also failing.

Code:

fffff880`0e42d010  fffff880`0563b1a4Unable to load image Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x31a4

It may be caused by the network blockage caused by Avast, but dont take a risk. Update it from Realtek .... get the first one of the list, Win7 and WinServer 2008 R2 Driver. Install it following Driver Install - Device Manager.

VBox network is also failing.

Code:

fffff880`0e42d238  fffff880`051d3aa4Unable to load image VBoxNetFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys
 VBoxNetFlt+0x4aa4

The reason may be the same, but still if possible, update the version of VBox.

Let us know the results.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff80000b9bb90, 0, 0, fffff88005b09a79}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+103a79 )

Followup: MachineOwner
---------

Roll back the driver to the earlier one installed.
Device Manager - Roll Back Driver