Windows 10: Random BSODs caused by ntoskrnl.exe

Hi all,

3 weeks ago I did a fresh install of Windows 10 and since then I'm getting BSODs at least once every 1-2 hours. These BSODs vary from SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED to KMODE_EXCEPTION_NOT_HANDLED. Also these BSODs happen at random moment: when the computer is iddling, when I'm downloading, when I'm listening to music, when I'm playing Battlefield 4.

I've already updated all drivers, but now I'm at a point that I don't know anymore what could be causing these BSODs. So I hope you guys could help me find out what the problem is and how to resolve it.

Thanks in advance.

Kind regards,
Jens

:)

 

0x139 Bug check BSOD happening a lot.

i only know from bluescreenview that the bsods were caused by ntoskrnl.exe and sometimes random drivers.

heres the link to the skydrive containing the 32 minidumps: OneDrive

 

Lots of BSOD's

PS: after my previous/last replie i had 3 more BSOD's:

seems like there are a lot of random once...

MEMORY_MANAGEMENT win32kbase.sys

MEMORY_MANAGEMENT ntoskrnl.exe

ntoskrnl.exe

 

Hi Jens,

Welcome to the 10forums *Smile

Please check your SSD for firmware updates.

Please check your Linksys network adapter for driver updates.
Code: 1: kd> lmvm AE3000w864 Browse full module list start end module name fffff801`751a0000 fffff801`753eb000 AE3000w864 T (no symbols) Loaded symbol image file: AE3000w864.sys Image path: \SystemRoot\System32\drivers\AE3000w864.sys Image name: AE3000w864.sys Browse all global symbols functions data Timestamp: Tue Jan 22 18:36:45 2013 (50FECE2D) CheckSum: 0024D617 ImageSize: 0024B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Please uninstall Kaspersky and use Windows Defender as alternative while troubleshooting.
Driver Reference Table - klflt.sys
Uninstall *Arrow Solved Anti Virus (AV) stand alone removal tools - Windows 10 Forums
Code: ffffd000`273e6368 fffff800`4e36779eUnable to load image \SystemRoot\system32\DRIVERS\klflt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for klflt.sys *** ERROR: Module load completed but symbols could not be loaded for klflt.sys klflt+0x779e[/quote]

 

Hi axe0,

Thank you for replying *Smile

I've checked my SSD firmware and it's the latest version available.
I've also reinstalled the latest driver for the Linksys wireless stick (the bluescreen related to that driver was from before the installation of latest driver).
I've also installed the Windows 10 anniversary update, but I still had 3 bluescreens meanwhile.
My Kaspersky internet security is also uninstalled as you asked.

I went to the MSI driver website and installed the latest audio driver and installed the on-board sata raid/ahci drivers, but still I still get BSODs. Ihave no idea what could be causing all these bluescreens.

A new dump of the crashes + system info is added.

Thanks in advance,

Jens

 

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

axe0,

I completed 10 passes of memtest without any errors:

Attachment 96804Attachment 96804

 

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Hi axe0,

I just run the driver verifier and after reboot I immediately had a bluescreen.

I've added a new dump with the crash files.

Attachment 97012

Kind regards,

Jens

 

It looks like an audio driver is caught, check MSI for driver updates *Smile
Support For Z87-G45 GAMING | MSI Global | Motherboard - The world leader in motherboard design 64
Code: 3: kd> lmvm MBfilt64 Browse full module list start end module name fffff803`574a0000 fffff803`574ae000 MBfilt64 T (no symbols) Loaded symbol image file: MBfilt64.sys Image path: \SystemRoot\system32\drivers\MBfilt64.sys Image name: MBfilt64.sys Browse all global symbols functions data Timestamp: Fri Jul 31 05:40:32 2009 (4A7267B0) CheckSum: 0000F70E ImageSize: 0000E000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Hi axe0, I updated all drivers from the MSI drivers page (except the Intel VGA one). I still got 4 BSODs since last post.
These BSODs started since I did a fresh install of Windows 10 and a BIOS update from 1.5 to 1.9. The reason I did the fresh W10 install was because my Linksys wifistick become unusable (no internet, even after driver reinstall) after an update of the Killer network suite (not only ethernet driver). Could the BIOS update from 1.5 to 1.9 be causing these BSODs?

Dump files:

Attachment 97297Attachment 97297

 

A BIOS update causing a BSOD is doubtful, mainly because it improves many things.

You may want to remove the program related to this driver, because it is known for causing BSODs + is extremely old.
Code: winring0_1_2_0 WinRing0_1_2_0 \??\f:\jens\overclocking tools\realtemp_370\winring0x64.sys[/quote] What I see in the dumps is a large scale of memory corruption, hardware & USB.
I suggest to remove all USB devices that aren't necessary for basic usage, all except for mouse & keyboard.
Code: 256 errors : !win32k (ffffee22d6903ac0-ffffee22d6903bbf) ffffee22d6903ac0 *00 *ea *cf *ff *00 *f2 *cf *ff *00 *fa *cf *ff *80 *f3 *cd *ff ................ ffffee22d6903ad0 *e1 *f3 *cd *ff *40 *f4 *cd *ff *a0 *f4 *cd *ff *00 *f5 *cd *ff ....@........... ffffee22d6903ae0 *60 *f5 *cd *ff *c0 *f5 *cd *ff *23 *f6 *cd *ff *87 *f6 *cd *ff `.......#....... ffffee22d6903af0 *e0 *f6 *cd *ff *40 *f7 *cd *ff *a0 *f7 *cd *ff *00 *f8 *cd *ff ....@........... ffffee22d6903b00 *60 *f8 *cd *ff *c0 *f8 *cd *ff *20 *f9 *cd *ff *80 *f9 *cd *ff `....... ....... ffffee22d6903b10 *00 *02 *d0 *ff *40 *fa *cd *ff *a0 *fa *cd *ff *00 *fb *cd *ff ....@........... ffffee22d6903b20 *60 *fb *cd *ff *c0 *fb *cd *ff *20 *fc *cd *ff *81 *fc *cd *ff `....... ....... ffffee22d6903b30 *e0 *fc *cd *ff *40 *fd *cd *ff *a0 *fd *cd *ff *04 *fe *cd *ff ....@........... ffffee22d6903b40 *60 *fe *cd *ff *c0 *fe *cd *ff *00 *0a *d0 *ff *81 *ff *cd *ff `............... ffffee22d6903b50 *e0 *ff *cd *ff *40 *00 *ce *ff *a0 *00 *ce *ff *03 *01 *ce *ff ....@........... ffffee22d6903b60 *60 *01 *ce *ff *00 *12 *d0 *ff *20 *02 *ce *ff *80 *02 *ce *ff `....... ....... ffffee22d6903b70 *ec *02 *ce *ff *40 *03 *ce *ff *a0 *03 *ce *ff *00 *1a *d0 *ff ....@........... ffffee22d6903b80 *60 *04 *ce *ff *c0 *04 *ce *ff *20 *05 *ce *ff *80 *05 *ce *ff `....... ....... ffffee22d6903b90 *e8 *05 *ce *ff *40 *06 *ce *ff *a0 *06 *ce *ff *00 *07 *ce *ff ....@........... ffffee22d6903ba0 *60 *07 *ce *ff *c0 *07 *ce *ff *20 *08 *ce *ff *85 *08 *ce *ff `....... ....... ffffee22d6903bb0 *e0 *08 *ce *ff *40 *09 *ce *ff *a0 *09 *ce *ff *00 *0a *ce *ff ....@........... MODULE_NAME: hardware # Child-SP RetAddr Call Site 00 fffff803`8a097fe8 fffff803`87fe4129 nt!KeBugCheckEx 01 fffff803`8a097ff0 fffff803`87fe2707 nt!KiBugCheckDispatch+0x69 02 fffff803`8a098130 fffff80a`6d411e39 nt!KiPageFault+0x247 03 fffff803`8a0982c0 fffff803`87ec1922 HIDCLASS!HidpInterruptReadComplete+0x589 04 fffff803`8a0983a0 fffff80a`67ea6907 nt!IopfCompleteRequest+0x112 05 (Inline Function) --------`-------- Wdf01000!FxIrp::CompleteRequest+0xd 06 fffff803`8a0984c0 fffff80a`67ea3190 Wdf01000!FxRequest::CompleteInternal+0x247 [d:\rs1\minkernel\wdf\framework\shared\core\fxrequest.cpp @ 871] 07 (Inline Function) --------`-------- Wdf01000!FxRequest::Complete+0x31 08 fffff803`8a098570 fffff80a`6d12a522 Wdf01000!imp_WdfRequestComplete+0x90 [d:\rs1\minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 09 fffff803`8a0985d0 fffff80a`6d11aeaa USBXHCI!Bulk_Transfer_CompleteCancelable+0x173ae 0a fffff803`8a098630 fffff80a`6d11f185 USBXHCI!Bulk_ProcessTransferEventWithED1+0x2ba 0b fffff803`8a0986e0 fffff80a`6d111753 USBXHCI!Endpoint_TransferEventHandler+0x2f5 0c fffff803`8a098740 fffff80a`6d11aa68 USBXHCI!UsbDevice_TransferEventHandler+0x87 0d fffff803`8a0987a0 fffff803`87ec7001 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x748 0e fffff803`8a098890 fffff803`87ec63ff nt!KiExecuteAllDpcs+0x2b1 0f fffff803`8a0989e0 fffff803`87fdc01a nt!KiRetireDpcList+0x5df 10 fffff803`8a098c60 00000000`00000000 nt!KiIdleLoop+0x5a[/quote]

 

Axe0,

I deleted the realtemp program.

Since some time before the start of the bluescreens I have a new keyboard (Corsair strafe). So as a test I removed the Corsair utility engine software and the driver and disconnected the keyboard from my computer. I also moved my keyboard and mouse from USB3.0 to USB2.0 ports.
But six hours later I've had another bluescreen. This time related to Intel(R) Rapid Storage Technology driver, so I removed that driver aswell (since I don't use it anyway as far as I know)

Then a couple of hours later I had another bluescreen, this time related to atikmpag.sys, so I unistalled my AMD graphic drivers and ran DDU in safe mode. Afterwards I only reinstalled the display driver (not the AMD settings and other stuff).

Still I've had a bluescreen after that. The frequency of bluescreen seems to be less (approximately one every 3 hours, but still something is causing BSODs)

Attachment 97606

Kind regards,

Jens

 

Please try to reseat the GPU or seat the GPU into a different slot.

 

Hi axe0,

I have reseated the GPU and still got bluescreens. Windows update also installed some amd hdmi sound driver and I think that caused a bluescreen aswell. I ran DDU and reinstalled the latest AMD driver (16.8.2).

I also got rid of the Linksys USB wifi stick (because I thought that was causing the problems), but today I had another bluescreen *Sad

I'm beginning to run out of ideas, hope you can help.

Attachment 98245

Kind regards,

Jens