Windows 10: BSOD when PC is idle, caused by ntoskrnl.exe and NETIO.SYS

Page 1 of 2 12 LastLast
  1.    28 Nov 2016 #1

    BSOD when PC is idle, caused by ntoskrnl.exe and NETIO.SYS


    A friend of mine has been having some trouble with BSODs recently, I have been attempting to assist them with their issue. Recently we have used Windows 10's "Reset" feature selecting all options to remove all files from both the boot SSD and storage HDD in an effort to try and start fresh. Unfortunately since resetting Windows, three BSODs have occurred. Each BSOD that has occurred has happened while the PC has been left on to download games and other large files. I would be very appreciative of any help that anyone could give me with fixing this issue.
      My ComputerSystem Spec

  2.    29 Nov 2016 #2

    Start with checking/repairing your windows system files.
    Use SFC to check and repair windows systemfiles.

    See this tutorial
    If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 times restarting the PC after each time to completely fix everything that it's able to.

    If not, then run the Dism /Online /Cleanup-Image /RestoreHealth command to repair any component store corruption, restart the PC afterwards, and try the sfc /scannow command again.
      My ComputerSystem Spec

  3.    29 Nov 2016 #3

    So i can't make out if your OS is a Genuine one , but i can't confirm it isn't so i'm going to TRY and help you.
    The 3 DMP files you gave show different issues. One with bcmwl63a.sys, another with nvlddmkm.sys

    Driver Reference Table --> Broadcom 802.11 Network Adapter wireless driver

    Driver Reference Table --> nVidia Video drivers

    Now they all have one thing in common, they seem to be busy handling USB

    USBXHCI, USBSTOR.SYS are all over the place.

    Now i've know laptops having issues with these files due to docking stations for instance.

    So what i would try to do is,

    fix broadcom driver, fix nvidia drivers.

    unplug as many unneeded USB devices you can

    then run driver verifier and see what happens.
    A tutorial can be found at : Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums
    If your system is stable, then re-enter one USB device at a time, see what happens.

      My ComputerSystem Spec

  4.    29 Nov 2016 #4

    Thanks very much for both of your replies.
    @lifetec: We'll start by doing what you've recommended. EDIT: No errors were found.

    @zztemp: The OS my buddy has installed was installed from a Windows 10 installation disc bought retail, so I'd hope that it was genuine...

    The Broadcom drivers come from the Asus PCE-AC68 Wireless Adapter's driver installation. The drivers were fully uninstalled then reinstalled from the Asus website, using the newest version. Searching reveals that other Windows 10 users have had problems with this device and it's newer drivers, so we'll try out the older drivers recommended in the link.

    As for the Nvidia driver showing up, I find that odd because we also did a full uninstall and reinstall of the newest Nvidia GPU drivers, directly downloaded from Nvidia's website. However we will do another full reinstall of those to cover everything you have mentioned. EDIT: Driver Verifier confirms an issue with with the GPU driver (System_Thread_Exception_Not Handled). I find this utterly perplexing because as far as I know the proper driver was installed. There may however have been user error involved with the download/installation.

    We believe the crash caused by USBXHCI was a faulty external USB storage device that was plugged in at the time. EDIT: Could be related to a USB headset's software (Logitech). Driver Verifier crashes on HIDCLASS.sys (USB Driver). Removing the installed Logitech Gaming Software allows the system to operate outside of Safe Mode for longer than 10sec (with Driver Verifier enabled). Other people have this issue.

    I have a feeling (and I hope) that the issues might be being caused by the Asus Wireless adapter, so we will try the older drivers and see how that goes. I will report back with any news. It may be this along with a bunch of other things.

    Thanks again for your help.

    EDIT: As of right now we have reinstalled the network adapter's drivers, GPU drivers and have decided not to install the Logitech Gaming Software. We are going operate the PC as normal for a day or two and see if any more crashes happen.
    Last edited by DahrkE; 29 Nov 2016 at 23:13.
      My ComputerSystem Spec

  5.    30 Nov 2016 #5

    Sorry dude , swamped with work atm. Your approach seems a good way to go.
    I'll be checking in later to see how you guys are doing.
      My ComputerSystem Spec

  6.    01 Dec 2016 #6

    so, how is the pc, more stable?
      My ComputerSystem Spec

  7.    10 Dec 2016 #7

    Please excuse the delayed reply.

    Unfortunately there have been more BSODs. I'll attach another zip file with the dumps included. I'm really not sure how to proceed with fixing this.

    Thanks for your replies and your time in advance.
    Last edited by DahrkE; 10 Dec 2016 at 09:41.
      My ComputerSystem Spec

  8.    19 Dec 2016 #8

    The files mention usbaudio.sys . Do you have some sort of USB headset connected? Or some sound-device that is connected via USB?
      My ComputerSystem Spec

  9.    19 Dec 2016 #9

    Yes, there is a USB headset plugged in. I believe it's the only audio input/output device that he has. It's a Logitech g633.

    How did you determine that it was usbaudio.sys that caused the crash? I looked through all the files and the dumps in BlueScreenViewer and I couldn't see it mentioned? I'm asking because I want to learn more about BSOD analysis.
      My ComputerSystem Spec

  10. axe0's Avatar
    Posts : 13,615
    Windows 10 Pro
       24 Dec 2016 #10

    Just to answer the question

    That would probably be the stacktrace
    ffffd001`063a7ae0 fffff80a`25a8101a : ffffbb81`764bd048 0000447e`89a94d00 00000000`0000001e ffffbb81`7584ae40 : Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x2a1 [d:\rs1\minkernel\wdf\framework\shared\core\km\fxdeviceapikm.cpp @ 494]
    ffffd001`063a7bc0 fffff80a`25a8044f : 00000000`00000000 00000000`0000000a ffffbb81`764bd048 00000000`00000000 : ucx01000!UrbHandler_USBPORTStyle_Legacy_IsochTransfer+0x17a
    ffffd001`063a7c10 fffff80a`25a752b7 : 0000447e`8a687fd8 ffffbb81`7b216490 ffffd001`063a7cd0 ffffbb81`7b216908 : ucx01000!Urb_USBPORTStyle_ProcessURB+0x347
    ffffd001`063a7c70 fffff80a`21843b8c : ffffbb81`75978020 00000000`00000000 00000000`0000000f ffffbb81`7b216490 : ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x467
    ffffd001`063a7d00 fffff80a`21984577 : ffffbb81`765cf970 00000000`00000000 ffff24dd`a9f1f735 00000000`00000000 : Wdf01000!FxDevice::DispatchWithLock+0x7ec [d:\rs1\minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
    ffffd001`063a7df0 fffff80a`2198420e : ffffbb81`721148b0 00000000`00000007 ffffbb81`7b216908 ffffbb81`79b3b720 : ACPI!ACPIIrpDispatchDeviceControl+0x97
    ffffd001`063a7e30 fffff80a`26fd39fd : 00000000`00000007 00000000`00000000 ffffd001`063a7f00 ffffbb81`76dba7c0 : ACPI!ACPIDispatchIrp+0xce
    ffffd001`063a7eb0 fffff80a`21843b8c : ffffbb81`767fce20 00000000`00000000 ffffbb81`76dba4d0 00000000`00000000 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xf4d
    ffffd001`063a7fc0 fffff80a`21984577 : ffffbb81`76e36b60 ffffd001`034f2000 fffff803`20dc0540 00000000`00000040 : Wdf01000!FxDevice::DispatchWithLock+0x7ec [d:\rs1\minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430]
    ffffd001`063a80b0 fffff80a`2198420e : ffffbb81`72113010 00000000`00000007 ffffbb81`7b216950 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0x97
    ffffd001`063a80f0 fffff80a`2707169e : 00000000`00000007 ffffbb81`7b216490 ffffd001`063a8229 00000000`00000001 : ACPI!ACPIDispatchIrp+0xce
    ffffd001`063a8170 fffff80a`270714d4 : ffffbb81`7b216490 fffff80a`270861e8 ffffbb81`7211ea28 fffff803`20dc0548 : usbccgp!DispatchPdoUrb+0x16e
    ffffd001`063a8290 fffff80a`270711b1 : ffffbb81`770efa28 ffffbb81`770efa20 ffffbb81`7b216490 fffff80a`27086178 : usbccgp!DispatchPdoInternalDeviceControl+0x84
    ffffd001`063a82f0 fffff80a`271b4111 : ffffbb81`770ef8d0 ffffbb81`764bd000 ffffbb81`00000000 ffffbb81`7b216998 : usbccgp!USBC_Dispatch+0x1b1
    ffffd001`063a83b0 fffff80a`271b4507 : ffffbb81`775ca9a0 fffff80a`271b3870 00000000`00000000 ffffbb81`7c6d6c00 : usbaudio!USBType1BuildIsochUrbRequest+0x571
    ffffd001`063a8490 fffff80a`271b45f0 : ffffbb81`775ca9a0 ffffbb81`7c10fc00 00000000`00000000 00000000`00000000 : usbaudio!USBType1ProcessStreamPointer+0x133
    ffffd001`063a84f0 fffff80a`26d6a500 : ffffbb81`7b219018 ffffbb81`7c10fc00 00000000`00000000 fffff80a`00000000 : usbaudio!USBType1ProcessPin+0xc0
    ffffd001`063a8520 fffff80a`26d62917 : ffffbb81`7b219018 00000000`000006e4 ffffbb81`7c10fc00 ffffbb81`7642a530 : ks!CKsPin::ProcessingObjectWork+0xf0
    ffffd001`063a8560 fffff80a`26d6b149 : ffffbb81`7c10fb30 00000000`00000000 ffffbb81`7c10fc00 ffffbb81`7287b130 : ks!CKsPin::Process+0x77
    ffffd001`063a8590 fffff80a`26d6d906 : ffffbb81`7c10fb30 00000000`00000000 ffffbb81`7642a010 ffffbb81`00000000 : ks!CKsQueue::AddFrame+0x1ad
    ffffd001`063a85d0 fffff80a`26d9f7c5 : fffff80a`00000000 00000000`00000000 ffffd001`063a86d0 00000000`00000000 : ks!CKsQueue::TransferKsIrp+0x456
    ffffd001`063a8660 fffff80a`26d7f675 : ffffbb81`7642a518 00000000`20707249 fffff803`20dc0540 ffffbb81`771609f0 : ks!CKsPin::DispatchDeviceIoControl+0x215
    ffffd001`063a86c0 fffff80a`26d61918 : ffffbb81`7642a010 ffffbb81`7713d9d0 ffffbb81`7642a560 fffff80a`26fb1433 : ks!KsDispatchIrp+0x65
    ffffd001`063a8780 fffff80a`26fb14b1 : ffffbb81`7642a010 ffffbb81`7642a560 ffffbb81`7642a560 ffffbb81`7713d9d0 : ks!CKsDevice::PassThroughIrp+0x48
    ffffd001`063a87c0 fffff803`20f15cd0 : ffffbb81`76481760 00000000`00000000 00000000`00000000 ffffbb81`7642a010 : ksthunk!CKernelFilterDevice::DispatchIrp+0xf9
    ffffd001`063a8820 fffff803`20f14bb4 : 00000000`00000000 ffffbb81`76481700 00000000`002f8013 ffffd001`063a8b80 : nt!IopSynchronousServiceTail+0x1a0
    ffffd001`063a88e0 fffff803`20f14536 : ffffbb81`7aee17c0 00000000`000002fc 00000000`00000000 000001ea`d9bf0710 : nt!IopXxxControlFile+0x674
    ffffd001`063a8a20 fffff803`20bdc193 : 00000000`746c6644 ffffd001`063a8b08 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
    ffffd001`063a8a90 00007ff8`e1b24f44 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    000000d2`cacffbb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`e1b24f44

    To learn more about BSOD analysis:
    WinDBG - The Basics for Debugging Crash Dumps in Windows 10
      My ComputersSystem Spec

Page 1 of 2 12 LastLast

Related Threads
Windows 10 Pro x64, browsing Facebook in Chrome when I got a BSOD for system service exception netio.sys Following next login I ran BlueScreenView and it seems to think ntoskrnl.exe is related. Googling leads me to solutions mentioning ASUS ROG...
Solved Various BSOD Caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hi, I'm facing various BSOD. After I open minidump files via Bluescreenview, it's caused by Ntoskrnl.exe. Here's the minidump files Microsoft OneDrive - Access files anywhere. Create docs with free Office Online. Here's the screenshot of...
Solved BSOD caused by ntoskrnl.exe please help in BSOD Crashes and Debugging
Hey all, I've attached 4 minidumps. Can you please help troubleshoot this intermittent BSOD?
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hello! I have recurring blue screens on my laptop and can't seem to figure out what's causing them. Sometimes, the computer also freezes completely without any forewarning and the only way to shut it down is to remoce the battery. I should...
BSOD caused by ntoskrnl.exe in BSOD Crashes and Debugging
BSODs have been happening for a while but I'm not really sure what's the actual cause.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 09:23.
Find Us