Windows 10: BSOD randomly browsing internet; ntoskrnl.exe

All right. Guess there is no other way *Smile

Iin the meantime, another new BSOD, KMODE_EXPECTION_NOT_HANDLED while playing a videogame.

Attachment 51425

This indeed looks like USB and video drivers fault, no? (from bluescreenview).

Another dump included.

Attachment 51427

In the meantime, I'm off to clean the video drivers.
EDIT: drivers cleaned, clean install done:

Attachment 51433

 

Run DDU again and try these drivers: Drivers | GeForce
Code: fffff802`6d3cb418 fffff800`413c35c4Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x1e35c4[/quote] Yes there are USB drivers involved, any USB device attached?

 

The last error happened before nvidia update.


After updating nvidia graphics, I tried to play around wth USB devices, but couldn't come across any errors.

Got a BSOD today, though. All of my devices were connected at that point as I needed them for work.

Attachment 51699

 

The USB ports according to MSI Global
Attachment 51702

According to what you said you have some ports in use.

I'm not sure if it will be a 100% possible, but try to connect each device on another USB port and see if that helps.

Code: 0: kd> k Child-SP RetAddr Call Site fffff801`903763e8 fffff801`8e75fea9 nt!KeBugCheckEx fffff801`903763f0 fffff801`8e75e6c8 nt!KiBugCheckDispatch+0x69 fffff801`90376530 fffff801`c7644d32 nt!KiPageFault+0x248 fffff801`903766c0 fffff801`c7660212 Wdf01000!FxIoQueue:ispatchEvents+0x1e2 fffff801`903767a0 fffff801`ca170e3c Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x622 fffff801`90376890 fffff801`ca170407 ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+0x1ac fffff801`90376940 fffff801`ca1653ee ucx01000!Urb_USBPORTStyle_ProcessURB+0x347 fffff801`903769a0 fffff801`c7641a61 ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x46e fffff801`90376a30 fffff801`c7821367 Wdf01000!FxDevice:ispatchWithLock+0x1f1 fffff801`90376a80 fffff801`c78210be ACPI!ACPIIrpDispatchDeviceControl+0x97 fffff801`90376ac0 fffff801`c910326e ACPI!ACPIDispatchIrp+0xbe fffff801`90376b30 fffff801`c7641a61 UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xf6e fffff801`90376c40 fffff801`c7821367 Wdf01000!FxDevice:ispatchWithLock+0x1f1 fffff801`90376c90 fffff801`c78210be ACPI!ACPIIrpDispatchDeviceControl+0x97 fffff801`90376cd0 fffff801`c918169e ACPI!ACPIDispatchIrp+0xbe fffff801`90376d40 fffff801`c91814d4 usbccgp!DispatchPdoUrb+0x16e fffff801`90376e60 fffff801`c91811b1 usbccgp!DispatchPdoInternalDeviceControl+0x84 fffff801`90376ec0 fffff801`c91b12aa usbccgp!USBC_Dispatch+0x1b1 fffff801`90376f80 fffff801`c91d2392 hidusb!HumInternalIoctl+0x2aa fffff801`90377270 fffff801`c91d20dd HIDCLASS!HidpSubmitInterruptRead+0x152 fffff801`903772f0 fffff801`8e65299d HIDCLASS!HidpInterruptReadComplete+0x73d fffff801`903773d0 fffff801`c764417b nt!IopfCompleteRequest+0x20d fffff801`90377490 fffff801`c7643620 Wdf01000!FxRequest::CompleteInternal+0x24b fffff801`90377550 fffff801`ca12cde7 Wdf01000!imp_WdfRequestComplete+0x90 fffff801`903775b0 fffff801`ca12b226 USBXHCI!Bulk_Transfer_CompleteCancelable+0x177 fffff801`90377610 fffff801`ca11a932 USBXHCI!Bulk_ProcessTransferEventWithED1+0x3aa fffff801`903776c0 fffff801`ca130683 USBXHCI!Endpoint_TransferEventHandler+0x4e fffff801`90377730 fffff801`ca11d572 USBXHCI!UsbDevice_TransferEventHandler+0x87 fffff801`90377790 fffff801`c76e26b0 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x4d2 fffff801`90377890 fffff801`8e656e65 Wdf01000!FxInterrupt:pcHandler+0xe4 fffff801`903778c0 fffff801`8e656540 nt!KiExecuteAllDpcs+0x275 fffff801`90377a10 fffff801`8e75822a nt!KiRetireDpcList+0xe0 fffff801`90377c60 00000000`00000000 nt!KiIdleLoop+0x5a[/quote]

 

So it's an USB device again? oh damn.

I think we can rule off the printer, it was not turned on at all (just connected).

I got rid of the bluetooth radio today and we'll see it that helps.

It might be the HDD, though. I recall now that a few months ago the particular USB3.0 port stopped working and I had to connect the drive to a 3.0 HUB due to being out of 3.0 ports.

I'll see if the error repeats itself without the bleutooth radio. But should I uninstall the CSR Harmony Stack driver for test, or is physical removal of the USB radio enough?

 

First step should actually be to determine if it is software or hardware, if it is software it is a bug in Windows, if it is hardware either the port or the connection of the device is the cause.

In your case, instead of disconnecting, try other ports to see if that improves something.

 

Guess we can scratch the bluetooth radio out, just BSODed when it was disconnected. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

I switched the HDD around to the other 3.0 port, we'll see if that works.

Uploading another log...Attachment 51739

I'm getting REALLY tired of this ****.... Windows 7 never crashed on me for several years... I'm thinking of rolling back.

 

Why don't you switch every connection to another port immediately? *Smile

Windows 7 works different then Windows 10, comparing isn't really fear.

 

Other ports are frontally placed, which is quite an issue with my short cables and tight placement

But I'll try my best.

Did you have a chance to look at the latest BSOD? I saw "nv" at the beginning, which makes me think of graphics driver again... but I have already cleaned them and installed fresh, newest ones... >____>

 

Not yet had a chance, will do it a.s.a.p. *Smile

 

I checked for the sptd, but I didn't see it *Smile

I don't know where your pc is, but is it possible to let the pc run overnight without any USB connection?

It is pretty much the same we already had, USB drivers and Nvidia video driver.
Code: 0: kd> k Child-SP RetAddr Call Site fffff801`903763e8 fffff801`8e75fea9 nt!KeBugCheckEx fffff801`903763f0 fffff801`8e75e6c8 nt!KiBugCheckDispatch+0x69 fffff801`90376530 fffff801`c7644d32 nt!KiPageFault+0x248 fffff801`903766c0 fffff801`c7660212 Wdf01000!FxIoQueue:ispatchEvents+0x1e2 fffff801`903767a0 fffff801`ca170e3c Wdf01000!imp_WdfDeviceWdmDispatchIrpToIoQueue+0x622 fffff801`90376890 fffff801`ca170407 ucx01000!UrbHandler_USBPORTStyle_Legacy_BulkOrInterruptTransfer+0x1ac fffff801`90376940 fffff801`ca1653ee ucx01000!Urb_USBPORTStyle_ProcessURB+0x347 fffff801`903769a0 fffff801`c7641a61 ucx01000!RootHub_Pdo_EvtInternalDeviceControlIrpPreprocessCallback+0x46e fffff801`90376a30 fffff801`c7821367 Wdf01000!FxDevice:ispatchWithLock+0x1f1 fffff801`90376a80 fffff801`c78210be ACPI!ACPIIrpDispatchDeviceControl+0x97 fffff801`90376ac0 fffff801`c910326e ACPI!ACPIDispatchIrp+0xbe fffff801`90376b30 fffff801`c7641a61 UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0xf6e fffff801`90376c40 fffff801`c7821367 Wdf01000!FxDevice:ispatchWithLock+0x1f1 fffff801`90376c90 fffff801`c78210be ACPI!ACPIIrpDispatchDeviceControl+0x97 fffff801`90376cd0 fffff801`c918169e ACPI!ACPIDispatchIrp+0xbe fffff801`90376d40 fffff801`c91814d4 usbccgp!DispatchPdoUrb+0x16e fffff801`90376e60 fffff801`c91811b1 usbccgp!DispatchPdoInternalDeviceControl+0x84 fffff801`90376ec0 fffff801`c91b12aa usbccgp!USBC_Dispatch+0x1b1 fffff801`90376f80 fffff801`c91d2392 hidusb!HumInternalIoctl+0x2aa fffff801`90377270 fffff801`c91d20dd HIDCLASS!HidpSubmitInterruptRead+0x152 fffff801`903772f0 fffff801`8e65299d HIDCLASS!HidpInterruptReadComplete+0x73d fffff801`903773d0 fffff801`c764417b nt!IopfCompleteRequest+0x20d fffff801`90377490 fffff801`c7643620 Wdf01000!FxRequest::CompleteInternal+0x24b fffff801`90377550 fffff801`ca12cde7 Wdf01000!imp_WdfRequestComplete+0x90 fffff801`903775b0 fffff801`ca12b226 USBXHCI!Bulk_Transfer_CompleteCancelable+0x177 fffff801`90377610 fffff801`ca11a932 USBXHCI!Bulk_ProcessTransferEventWithED1+0x3aa fffff801`903776c0 fffff801`ca130683 USBXHCI!Endpoint_TransferEventHandler+0x4e fffff801`90377730 fffff801`ca11d572 USBXHCI!UsbDevice_TransferEventHandler+0x87 fffff801`90377790 fffff801`c76e26b0 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x4d2 fffff801`90377890 fffff801`8e656e65 Wdf01000!FxInterrupt:pcHandler+0xe4 fffff801`903778c0 fffff801`8e656540 nt!KiExecuteAllDpcs+0x275 fffff801`90377a10 fffff801`8e75822a nt!KiRetireDpcList+0xe0 fffff801`90377c60 00000000`00000000 nt!KiIdleLoop+0x5a[/quote] Code: ffffd000`2657d178 fffff800`dc720df5Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x80df5[/quote]

 

Thank you. Got another BSOD right now, IRQL_NOT_LESS_OR_EQUAL. At this point I got rid of everything except mouse, keyboard and external HDD. If HDD may be the cause, I'll get rid of it too for the time being, but that would mean having to buy a new one.

I am at loss what to do with nvidia drivers, though. Since I already cleaned and uninstalled them, and reinstalled new ones, is there anything else to be done on the matter? Could this be defective GPU, or just the drivers?

Any ideas where to go next & what to do from now on? 2 BSODs per several hours is unacceptable, I may really roll back to Win 7 if this continues, which I don't want to do, as it doesn't have the latest DX support.

Including the 9001th dump *Smile

Attachment 51918

 

Please check inside the case for any dust, durt or anything that doesn't belong there and remove it.
Please make sure everything is seated properly, make sure to ground yourself before opening the case, if you haven't cleaned the system of dust recently.

I'll check the files when I wake up within a couple of hours, almost half past 12PM here.

 

Nvidia drivers again
Code: fffff803`48d77680 fffff800`793b734dUnable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0xe734d[/quote] But I would like to focus on old drivers for now.
These are the drivers not in 2015.
Code: GPCIDrv64 Thu Jul 10 14:58:31 2008 (48760777) GPCIDrv64.sys // Gigabyte driver WPRO_41_2001 Mon Nov 07 22:04:48 2011 (4eb847f0) WPRO_41_2001.sys ew_jubusenum Thu Nov 24 12:30:19 2011 (4ece2acb) ew_jubusenum.sys ISCTD64 Tue Nov 27 20:52:34 2012 (50b51a02) ISCTD64.sys HECIx64 Mon Dec 17 20:32:21 2012 (50cf7345) HECIx64.sys imsevent Tue Jan 08 20:33:33 2013 (50ec748d) imsevent.sys ikbevent Tue Jan 08 20:34:06 2013 (50ec74ae) ikbevent.sys mbam Wed Sep 03 19:50:25 2014 (540754e1) mbam.sys SC808HDB64 Thu Dec 18 07:35:56 2014 (549275cc) SC808HDB64.sys // audio driver[/quote] Please remove Gigabyte software

Driver Reference Table - WPRO_41_2001.sys
Driver Reference Table - ew_jubusenum.sys
Driver Reference Table - ISCTD64.sys
Driver Reference Table - HECIx64.sys
Driver Reference Table - imsevent.sys
Driver Reference Table - ikbevent.sys

Please reinstall Malwarebytes: https://support.malwarebytes.org/cus...5311?b_id=6438 & Malwarebytes | Free Anti-Malware & Internet Security Software
When removing Malwarebytes, license data will be removed as well, note any license data before removal.

I can't find driver updates for the audio driver, please check in device manager for driver updates.
Code: Name HD Audio PCI-e Audio Device Manufacturer C-Media Electronics Inc. Status OK PNP Device ID HDAUDIO\FUNC_01&VEN_13F6&DEV_8888&SUBSYS_13F60002&REV_1004\5&311B8301&0&0101 Driver c:\windows\system32\drivers\sc808hdb64.sys (8.0.14.1218, 62,50 KB (64*000 bytes), 2015-11-24 20:55)[/quote]

 

When installing my CPU cooling, I cleaned up the interior thoroughly with compressed air, so I'm sure its dust-free and clean.

The HD audio stuff is a souncard, AIM SC808. I'll try to look for updates.

Removing/deleting the rest of the stuff as requested.

EDIT: no new drivers for the 808, sadly! I installed the latest one couple days ago (11-24 IIRC).

I'll post a new BSOD once it pops (inevitably!)