Windows 10: ntoskrnl.exe causing multiple BSOD

Hello everyone,

My computer seems to be randomly crashing, most of the time while I'm gaming or trying to use my Oculus Rift. Sometimes it will crash almost immediately other times it will be hours or sometimes not at all. I've tried somewhat troubleshooting the issue but I now need your help to actually fix it. I'm running Windows 10 Pro, here's a little list of what I've already tried.

• Done all Windows Updates
• Unistalled Avast
• Ran Memtest86+ for about 2 passes (i'm going to do a full 8 tonight)
• Tried using driver verifier but my system wouldn't even boot (why I think its some random driver issue)
• Ran chkdisk on my ssd
• I've stress tested and monitored my gpu so its not overheating

I built this desktop a little over a year ago and its really always had these random crashes. Just recently started playing a bunch of Overwatch Beta and using my new Oculus Rift which is why now I really want to fix it. Anyways, let me know what else I can do or should try. Thanks for any help. Attached is the zip with the info.

:)

 

Multiple BSOD mainly caused by ntoskrnl.exe

Well I am back after trying many things. After learning how to read the errors myself I came to understand that my Graphics drivers were having errors with my Windows OS. I first tried guru3d to uninstall my nvidia drivers and reinstall them. When that
didn't work I used Windows Inplace Upgrade to reinstall my OS without loosing my personal files and apps. This seemed to work so I am lead to believe there was corrupted files somewhere in my OS and whenever my Graphics Drives called upon such files a BSOD
would occur. I use to have BSOD everyday but after a week of using my computer things seemed to be fixed. I'll keep an eye on Event Viewer for now to see if anything important needs to addressed. Thanks for the assistance. Next time I use this site I will
make sure to provide the raw dump files rather than the text information from them.

 

Multiple BSOD mainly caused by ntoskrnl.exe

fffff80f`dbdd0000 fffff80f`dbe00000 tunnel tunnel.sys Thu Jun 4 18:42:24 1981
(157D7150)

fffff80f`da0c0000 fffff80f`da0f9000 ucx01000 ucx01000.sys Tue Feb 22 09:51:48 1994
(2D6A1C04)

fffff80f`da410000 fffff80f`da41d000 UEFI UEFI.sys Fri Sep 30 17:36:44 2022
(6337616C)

fffff80f`d9810000 fffff80f`d9825000 umbus umbus.sys Tue Jul 1 10:26:17 2025
(6863F009)

fffff80f`dacd0000 fffff80f`dad01000 usbccgp usbccgp.sys Sat Jul 21 06:16:10 2018 (5B5307EA)

fffff80f`da4e0000 fffff80f`da4ee000 USBD USBD.SYS Mon Jun 14 00:32:36 1971
(02B9A964)

fffff80f`da450000 fffff80f`da4dc000 UsbHub3 UsbHub3.sys Fri Jul 3 01:25:13 1987
(20EB4039)

fffff80f`da050000 fffff80f`da0b4000 USBXHCI USBXHCI.SYS Sun Jul 17 23:39:46 2005 (42DB2482)

fffff80f`d7f40000 fffff80f`d7f52000 vdrvroot vdrvroot.sys ***** Invalid (C0C6BED0)

fffff80f`d7ba0000 fffff80f`d7c21000 VerifierExt VerifierExt.sys ***** Invalid (FF46AD8F)

fffff80f`da850000 fffff80f`da86a000 vmbkmclr vmbkmclr.sys Fri Oct 29 22:55:38 1993 (2CD1D7AA)

fffff80f`d8080000 fffff80f`d8099000 volmgr volmgr.sys ***** Invalid (D7133847)

fffff80f`d80a0000 fffff80f`d80fe000 volmgrx volmgrx.sys unavailable (00000000)

fffff80f`d8ad0000 fffff80f`d8b34000 volsnap volsnap.sys ***** Invalid (DC1CFF91)

fffff80f`d8ac0000 fffff80f`d8acb000 volume volume.sys ***** Invalid (9CBEE8B7)

As you can see above, there is an issue of file corruption. The dates on your system files are wrong or invalid. Cause? Don't know.

You can try running the she system file checker tool {SFC} and DISM, to see if they can be corrected.

Fix Windows Update errors by using the DISM or System Update Readiness tool.

https://support.microsoft.com/en-us...-by-using-the-dism-or-system-update-readiness

Using System File Checker in Windows 10.

https://support.microsoft.com/en-us...a40be/using-system-file-checker-in-windows-10

If no joy, a reset is your next best option.

Recovery options in Windows 10.

Mini dump and random crash help please

 

Hi Ginja Slice,

Welcome to the 10forums *Smile

I had a short look at the logs, but I'll wait with posting a suggestion until you've completed the memory test.
I'm suspicious of a possible memory control problem given the various crashes where some point indirectly or directly to improper memory handling or memory storing.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

Ran memtest overnight got all 8 passes with no errors. Just filled in my specs. Thanks for the quick response. Here's a more up to date dmp with some more crashes and i believe i actually got driver verifier running during a crash.

 

Do you have a USB network adapter?

This is new for me, an AVG driver flagged in a hardware crash dump.
I suggest that you uninstall AVG and use Windows Defender as alternative.
Code: ffffd001`62859078 fffff800`3b5c1db0Unable to load image avgidsdrivera.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for avgidsdrivera.sys *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys avgidsdrivera+0x41db0[/quote] Make sure your USB device drivers are up to date, both for the motherboard and the USB devices.
I see you have some Razer devices? Razer devices can sometimes cause problems unfortunately so I would suggest that you replace it with another device.
Code: 0: kd> k # Child-SP RetAddr Call Site 00 fffff803`a4b87dc8 fffff803`a2d592e9 nt!KeBugCheckEx 01 fffff803`a4b87dd0 fffff803`a2d59610 nt!KiBugCheckDispatch+0x69 02 fffff803`a4b87f10 fffff803`a2d587f3 nt!KiFastFailDispatch+0xd0 03 fffff803`a4b880f0 fffff800`c6c28901 nt!KiRaiseSecurityCheckFailure+0xf3 04 fffff803`a4b88280 fffff803`a32c072b HIDCLASS!HidpInterruptReadComplete+0x7051 05 fffff803`a4b88360 fffff803`a2c86596 nt!IovpLocalCompletionRoutine+0x16f 06 fffff803`a4b883c0 fffff803`a32c00fd nt!IopfCompleteRequest+0x216 07 fffff803`a4b884e0 fffff800`c3ab7ffb nt!IovCompleteRequest+0x1c1 08 (Inline Function) --------`-------- Wdf01000!FxIrp::CompleteRequest+0xd 09 fffff803`a4b885c0 fffff800`c3ab55f0 Wdf01000!FxRequest::CompleteInternal+0x25b [d:\th\minkernel\wdf\framework\shared\core\fxrequest.cpp @ 861] 0a (Inline Function) --------`-------- Wdf01000!FxRequest::Complete+0x31 0b fffff803`a4b88670 fffff800`c915287f Wdf01000!imp_WdfRequestComplete+0x90 [d:\th\minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 0c fffff803`a4b886d0 fffff800`c915da69 USBXHCI!Bulk_Transfer_CompleteCancelable+0x177 0d fffff803`a4b88730 fffff800`c915b309 USBXHCI!Bulk_ProcessTransferEventWithED1+0x3d9 0e fffff803`a4b887d0 fffff803`a2c7a6a0 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x759 0f fffff803`a4b888c0 fffff803`a2c79db9 nt!KiExecuteAllDpcs+0x270 10 fffff803`a4b88a10 fffff803`a2d5151a nt!KiRetireDpcList+0xe9 11 fffff803`a4b88c60 00000000`00000000 nt!KiIdleLoop+0x5a[/quote]

 

I do not have usb network adapter. I have a PCI wireless card. But, I've uninstalled AVG. I've updated every driver I could which consisted of some motherboard ones and the Razer keyboard driver. I got driver verifier running again with all the drivers selected besides the logitech ones (idk why they are still there i uninstalled). Here's the updated dump with the crash that just happened. Thanks again.

I can try replacing the Razer keyboard later in the week if you think that's the issue.

Edit: the wireless card I have is a tp link tl-wdn4800

 

Sorry for the late response I was waiting for when I had some more free time to complete the stress tests. But I think you might've found the issue right off the bat. When I run prime95 test within 10 seconds my cpu temps skyrocket to 90-100° C (pic below) I stop the test pretty quickly because I don't want to damage anything. I've never overclocked my cpu and I just re did the thermal paste and heatsink, I'm getting the same temps. Thanks, again for the help.

 

What CPU cooler do you use?

 

Just the one that came with the processor.

 

I would like you to keep an eye on the temperature when you stress your system on your own way, thus keep an eye on the temperatures while your system is under load but not by a stress test.