Windows 10: BSOD During downloading.

I've been having two types of issues. One is a straight computer freeze where the audio stutters and makes weird random noises at max volume in my headphones. I have yet to locate any logs for that issue. (possibly unrelated)

The second and persist issue that I'm writing about is when downloading files of any larger file sizes generally over 2gb from peer to peer applications (utorrent or deluge) my computer will BSOD with [PAGE_FAULT_IN_NONPAGED_AREA]. And no I'm not downloading anything illegal.

I've isolated the issue as "most likely" being the Asus PCE-AC68 wireless adapter driver. But, I've tried various versions of this driver to attempt to solve the issue.

The issue is also a new issue. I've had this adapter for over a year with no issues. I installed a new hard drive a few weeks ago and did a full reinstall of the OS. The problem only started happening then.

Please help! Attachment 90209

:)

 

BSOD in windows 10 64-bit 0x0000007E

This should be the mini dump with the information on that BSOD error, which like before happened during start up.

021016-18640-01.dmp

 

BSOD during Steam game download!

Oh! The link on MSI's site for the the driver actually did work; I just changed out the driver by update/files on this computer to implement it. Thank you for the help!

 

Latest dump indicates a hardware problem:

Code: BugCheck A, {ffffffffffffff85, 2, 1, fffff801e16fd0fc} Probably caused by : hardware ( nt!KiPageFault+247 ) Followup: MachineOwner[/quote] Previous dump indicates a problem with bcmwl63a.sys. Normally this belongs to a Broadcom 802.11 Wireless driver but you don't have one, you have a ASUS PCE-AC68 802.11ac Network Adapter as you stated.

Code: lmvm bcmwl63a start end module name fffff800`88cf0000 fffff800`89996000 bcmwl63a T (no symbols) Loaded symbol image file: bcmwl63a.sys Image path: \SystemRoot\system32\DRIVERS\bcmwl63a.sys Image name: bcmwl63a.sys Timestamp: Thu May 14 17:38:53 2015 (555515ED)[/quote] You currently have

Driver c:\windows\system32\drivers\bcmwl63a.sys (7.35.267.0, 10.63 MB (11,151,112 bytes), 7/9/2016 1:53 PM)
Updated driver version to 7.35.315.0 is available.

PCE-AC68 Win 10 X64

Code: Description ASUS PCE-AC68 Utility 2.1.1.4 It is for all sku except EU Support OS: Win 7/8/8.1/XP/10 Updated driver version to 7.35.315.0 [Please note]This version is driver only. Before installing this version, please uninstall pervious PCE-AC68 utility File Size 89.11 MBytesupdate 2015/12/11 Download from Global[/quote]

 

Previous dump indicates a problem with bcmwl63a.sys. Normally this belongs to a Broadcom 802.11 Wireless driver but you don't have one, you have a ASUS PCE-AC68 802.11ac Network Adapter as you stated.

Code: lmvm bcmwl63a start end module name fffff800`88cf0000 fffff800`89996000 bcmwl63a T (no symbols) Loaded symbol image file: bcmwl63a.sys Image path: \SystemRoot\system32\DRIVERS\bcmwl63a.sys Image name: bcmwl63a.sys Timestamp: Thu May 14 17:38:53 2015 (555515ED)[/quote] You currently have

Driver c:\windows\system32\drivers\bcmwl63a.sys (7.35.267.0, 10.63 MB (11,151,112 bytes), 7/9/2016 1:53 PM)
Updated driver version to 7.35.315.0 is available.

PCE-AC68 Win 10 X64

Code: Description ASUS PCE-AC68 Utility 2.1.1.4 It is for all sku except EU Support OS: Win 7/8/8.1/XP/10 Updated driver version to 7.35.315.0 [Please note]This version is driver only. Before installing this version, please uninstall pervious PCE-AC68 utility File Size 89.11 MBytesupdate 2015/12/11 Download from Global[/quote] [/quote]
Ztrucker. I have installed the updated driver, uninstalled it and attempted all versions of the drivers listed on their site one at a time prior to my posting here. I'll update the driver again. The only one I haven't tried is the one listed as "only for EU SKU" which is their most recent driver.

The latest mini dump did seem like a hardware failure but, I think that's unrelated to the main issue. Because I can't reproduce that and it's very uncommon. (once a week or so)

 

You could try using a USB Wireless dongle in place of the PCE-AC68, see if that resolves the problem.

There are some things we can try to see if we can force the failure to id it.

===================================================
RAM:

Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums



Information




MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning
MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note
MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums

===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums

If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..