Random BSODs caused by ntoskrnl.exe  

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 10 home 64bit

    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,
      My Computer

  2. Posts : 14,890
    Windows 10 Pro

    Hi Jens,

    Welcome to the 10forums :)

    Please check your SSD for firmware updates.

    Please check your Linksys network adapter for driver updates.
    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
    Please uninstall Kaspersky and use Windows Defender as alternative while troubleshooting.
    Driver Reference Table - klflt.sys
    Uninstall Solved Anti Virus (AV) stand alone removal tools - Windows 10 Forums
    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
      My Computers

  3. Posts : 10
    Windows 10 home 64bit
    Thread Starter

    Hi axe0,

    Thank you for replying :)

    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,

      My Computer

  4. Posts : 14,890
    Windows 10 Pro

    Diagnostic Test


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   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.

    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.
      My Computers

  5. Posts : 10
    Windows 10 home 64bit
    Thread Starter


    I completed 10 passes of memtest without any errors:

    Attachment 96804Attachment 96804
      My Computer

  6. Posts : 14,890
    Windows 10 Pro

    Diagnostic Test


    warning   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   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.
      My Computers

  7. Posts : 10
    Windows 10 home 64bit
    Thread Starter

    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,

      My Computer

  8. Posts : 14,890
    Windows 10 Pro

    It looks like an audio driver is caught, check MSI for driver updates :)
    Support For Z87-G45 GAMING | MSI Global | Motherboard - The world leader in motherboard design 64
    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
      My Computers

  9. Posts : 10
    Windows 10 home 64bit
    Thread Starter

    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
      My Computer

  10. Posts : 14,890
    Windows 10 Pro

    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.
    winring0_1_2_0	WinRing0_1_2_0	\??\f:\jens\overclocking tools\realtemp_370\winring0x64.sys
    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.
    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
      My Computers


  Related Discussions
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 05:34.
Find Us

Windows 10 Forums