BSOD PAGE_FAULT_IN_NONPAGED_AREA After Resume From Sleep  

Viewing the before and after they appear the same.
What are all the trash items? Is that in the recycle bin?
Install the first Liteon version and then without turning on wireless turn on windows driver verifier as see if there is a bsod with this driver.
If this driver produces a bsod we will plan to go to the next driver after uninstalling the Liteon driver.
I'll check the mini dump if you have one now.
If there is no bsod with this driver turn on wireless and turn off ethernet to make sure there is good performance.

The trash items are from deleting the files from Ubuntu, goes to random trash folder instead of recycling bin.

Already tried all 3 but I'll try again and post results for each.

Installed Liteon, right as I went to restart to run the verifier, BSOD during restart. When I turned back on, about 30 seconds after loading onto desktop, another BSOD pointing to the USB to Ethernet adapter I'm using. When I turned it back on again, it was good for 5 mins using the USB to Ethernet adapter so I decided to turn wifi back on. Turned it back on, all was good for about a minute so then I removed the USB to Ethernet adapter. 10 seconds later, BSOD.

ERIK-WINDOWS-08_04_17_224415_79.zip - Google Drive

Moving onto Hai now.

Another BSOD with Hai version of driver, moving onto Killer Networking now.

ERIK-WINDOWS-08_04_17_225723_64.zip - Google Drive

There were 4 new bsod mini dump files that were debugged. There was a new misbehaving driver producing the bsod: ax88772.sys

Open device manager > network devices > ASIX network driver fast ethernet controller > right click properties > driver details > confirm ax88772.sys > ok > update driver

Code:

BugCheck 50, {fffff86208018a3c, 2, fffff8020928a31a, 2}Could not read faulting driver name*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption

Code:

BugCheck C4, {2002, fffff802870a42e7, 10, 0}*** WARNING: Unable to verify timestamp for ax88772.sys*** ERROR: Module load completed but symbols could not be loaded for ax88772.sysProbably caused by : ax88772.sys ( ax88772+142e7 )

Code:

AX88772      ASIX AX88772 USB2.0 to ASIX AX88772 USB2.0 to Kernel        Manual     Running    OK         TRUE        FALSE        16,384            90,112      0          6/16/15 9:32:12 AM     C:\Windows\system32\drivers\ax88772.sys          4,096

ax88772.sys

ASIX AX88772/AX88772A Network Driver for AX88772 -- USB2.0 to 10/100M Fast Ethernet Controller with Embedded PHY

http://www.asix.com.tw/products.php?...emID=86;71;101

Code:

BugCheck C4, {9200f, fffff80434a78470, ffff938f60c20200, ffff938f60c20308}
*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption

There is no need to uninstall the replaced driver yet.

On the computer there is 8 GB RAM.
There is 4 GB on 2 DIMM.
Run Memtest86+ for 8 or more passes.
This may take 1 - 2 hours / GB
There are other memory software.
Only run Memtest86+ using this link: Memtest86+ - Advanced Memory Diagnostic Tool
The critical factor in the RAM testing is the number of passes.
The amount of time is irrelevant.
Performing the test with less than 8 passes is insufficient and often produces false negatives.
A false negative is a test in which there is a pass and the RAM is malfunctioning.
So the more passes the better.
If there is just 1 error that indicates faulty RAM. You can then abort the testing of both RAM.
Then test one RAM at a time in the same DIMM for 8 passes.
If both RAM fail when test together and then pass when tested 1 at a time that indicates a DIMM/MB problem.
So if both RAM pass one at a time after failing when testing together you will then move the RAM to another DIMM and retest 1 of the RAM.
This RAM testing is process of elimination.
After each test whether pass or fail use a camera or smart phone camera to take pictures and post the images into the thread.


https://answers.microsoft.com/en-us/...f-ecc7b7ff6461


MemTest86+ - Test RAM Windows 10 BSOD Tutorials

Code:

BugCheck C4, {9200f, fffff80434a78470, ffff938f60c20200, ffff938f60c20308}
*** 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

The reason why the USB to Ethernet adapter driver came up as the cause was because when Windows started, it was not detecting my ethernet so I was unplugging and plugging back in the adapter multiple times which most likely caused the blue screen.

I was using the adapter just fine for over 6 hours today and yesterday without any issues.

Just tried the Killer Networking version of the driver and it did not work as well, another BSOD.

ERIK-WINDOWS-08_04_17_231049_83.zip - Google Drive

If it helps at all, my wifi card is "Qualcomm Atheros QCA61x4A Network Adapter"

Please turn off windows driver verifier and disconnect ethernet and wireless.
Run the memtest86+ for 8 or more passes.
In the bsod debugging I did not see either wireless driver as a misbehaving driver.
So this could be a RAM/DIMM problem.

Multiple drivers often implicate RAM problems.
These are the misbehaving drivers identified so far:
AVIRA
Malwarebytes
Qualcom wireless
Intel graphics
ASIX networking



For Memtest86+ testing the more passes the better.
Please don't use memtest86 and make sure it is Memtest86+ (must have the +) with the link in the earlier post.
Make sure that there are at least 8 passes and that you use a camera to post the results.

Is it really necessary? Ran memtest86+ once with 4 passes once with 10 and no errors. The blue screens literally only happen when wifi is turned on and connected to a network.