Windows 10: Kmode_exception_not_handled bsod Solved

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 10 Pro x64
       01 Jul 2016 #1

    Kmode_exception_not_handled bsod

    Hi everyone,
    This is my first post in this forum.
    I have a problem with multiple BSODs on my computer.
    I tried to solve the first couple of BSODs but with no luck at all.
    I then decided to reinstall Windows 10 on my computer but the BSODs kept coming.

    The first one was KMODE_EXCEPTION_NOT_HANDLED (nvlddmkm.sys). Unfortunately I don't have a dump file from this crash because i forgot to configure the dump file.

    I tried to reinstall my Nvidia drivers using DDU and install the latest drivers from Nvidias site.
    In blue screen viewer I can see that TCPIP.sys i also mentioned.

    I have also tried to run sfc /scannow and there was some problems that couldn't be fixed.
    I then used the dism tool to repair it with a windows image.

    After this the computer work for a day or two and it blue screen again.
    This time it said KERNEL_SECURITY_CHECK_FAILURE and i then watch in the "WhoCrashed" program and ut said the source was ntkrnlmp.exe.
    On internet some people said that this was solved by removing Hyper-V switches.
    So I decided to remove Hyper-V from my computer (Awful software).

    It worked again for a day or two and then it crashed again with the message KMODE_EXCEPTION_NOT_HANDLED and the source was: tcpip.sys.
    But blue screen viewer says the source is nvlddmkm.sys.

    I'm really starting to think this is a hardware issue but I hope it's a bad driver.
    I hope some i this forum can help me with this issue I've attached the Zip file as requested.

    Thanks in advance and excuse me if my English is bad.
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 6,218
    Windows 10 Pro X64 17134.191
       01 Jul 2016 #2

    The 7/1 dump inedicates a problem with nvlddmkm.sys and RTKVHD64.sys
    fffff801`7ea78058  fffff801`0092987aUnable 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.sys is part of the driver for your NVIDIA GeForce GTX 970.

    fffff801`7ea79020  fffff801`00000000Unable to load image RTKVHD64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for RTKVHD64.sys
    *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
    RTKVHD64.sys is part of the driver for Realtek Digital Output (Realtek High Definition Audio).

    You have the latest driver for both of these:

    0: kd> lmvm nvlddmkm
    start end module name
    fffff801`00920000 fffff801`01655000 nvlddmkm T (no symbols)
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp: Thu Jun 02 23:11:28 2016 (5750F560)
    CheckSum: 00CEE995
    ImageSize: 00D35000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

    0: kd> lmvm RTKVHD64
    start end module name
    fffff800`fffb0000 fffff801`004ad000 RTKVHD64 T (no symbols)
    Loaded symbol image file: RTKVHD64.sys
    Image path: RTKVHD64.sys
    Image name: RTKVHD64.sys
    Timestamp: Tue Apr 26 07:58:01 2016 (571F57C9)
    CheckSum: 004D28BB
    ImageSize: 004FD000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Try some of the older Nvidia drivers:

    Attachment 87811

    Alternatively, try Driver Verifier:

    Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My ComputersSystem Spec

  3. Posts : 10
    Windows 10 Pro x64
    Thread Starter
       02 Jul 2016 #3

    Hey Ztruker,
    Thanks for the answer.
    I've followed the guide to activate driver verifier.
    So far the computer has not BSODed but I will bee running it for max 48 hours.
    I will post a new dump file as soon as the computer fails again.

    If i remember correctly the Nvidia driver 368.22 ran without any BSOD on the computer.
    Should I wait for Driver verifier to generate a BSOD first or should I just go ahead and install the driver with DDU?
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 6,218
    Windows 10 Pro X64 17134.191
       02 Jul 2016 #4

    Yes, please wait until you have finished with DV. If we don't find anything then try the 368.22 driver.
      My ComputersSystem Spec

  5. Posts : 10
    Windows 10 Pro x64
    Thread Starter
       02 Jul 2016 #5

    Yea sure. Still waiting for the BSOD.
    Right now i got a uptime of about 10 hours.
    I'll check back as soon as a got any update.
      My ComputerSystem Spec

  6. Posts : 10
    Windows 10 Pro x64
    Thread Starter
       04 Jul 2016 #6

    Hi again,
    Today when i booted up the computer it BSODed again.
    This time with the message IRQL_NOT_LESS_OR_EQUAL.
    I checked who crashed and saw that the source was mbfilt64.sys.
    according to google that's a part of Creative Audio Driver.

    I have Creative Sound blaster Cinema 2 installed that came with the audio drivers.
    Should i try to uninstall it or can you check the dump file to see if thats the cause or if it's something else?

    I have attached the dump file to this post.
      My ComputerSystem Spec

  7. Ztruker's Avatar
    Posts : 6,218
    Windows 10 Pro X64 17134.191
       04 Jul 2016 #7

    Dump definitely points to MBfilt64.sys. It's quite old:
    kd> lmvm MBfilt64
    start             end                 module name
    fffff801`b1470000 fffff801`b147e000   MBfilt64 T (no symbols)           
        Loaded symbol image file: MBfilt64.sys
        Image path: MBfilt64.sys
        Image name: MBfilt64.sys
        Timestamp:        Thu Jul 30 23:40:32 2009 (4A7267B0)
        CheckSum:         0000BE1C
        ImageSize:        0000E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Definitely uninstall anything from Creative, see if that helps.
      My ComputersSystem Spec

  8. Posts : 10
    Windows 10 Pro x64
    Thread Starter
       05 Jul 2016 #8

    Yes, I've uninstalled the Creative software and also disabled driver verifier now.
    It's been active for over 40 hours now.
    I'll use my computer as much as possible and if no BSOD has appeared by fri/sat I'll take that as the problem been resolved.

    And again thank you so much for your help.
      My ComputerSystem Spec

  9. Ztruker's Avatar
    Posts : 6,218
    Windows 10 Pro X64 17134.191
       05 Jul 2016 #9

    You're welcome. Looking forward to some good news at the end of the week.
      My ComputersSystem Spec

  10. Posts : 10
    Windows 10 Pro x64
    Thread Starter
       10 Jul 2016 #10

    So my Computer been running fine until today sadly when yet again it blue screened.
    But this time i can't get any useful information from whocrashed or blue screen viewer.
    I've attached the dump file if you will be so kind to look at it again.

    This time the programs only says ntoskrnl.exe is the cause.
    The bsod message was the same as the last blue screen "IRQL_NOT_LESS_OR_EQUAL".
      My ComputerSystem Spec

Page 1 of 2 12 LastLast

Related Threads
BSOD - kmode_exception_not_handled in BSOD Crashes and Debugging
Hey guys, i have a lot of BSOD in the last time. Story: I already had windows 10 running on my old system - without any BSOD. I upgraded some Hardware a while ago (mainboard, graphics and processor) and did a clean installation of Windows...
Bsod - kmode_exception_not_handled in BSOD Crashes and Debugging
Hi, I got this error twice this week. I was just doing regular work with Visual Studio, Chrome, Spotify, Dropbox, TotalCmd running. I checked MEMORY.DMP with WinDbg on the crash today and it shows chrome.exe as the process where the error...
Hello, after upgrading to windows 10 from windows 8 I have been getting some weird BSOD crashes now and again, sometimes its days or weeks in between them and sometimes there are several on the same day. The error message simply says...
Bsod: Kmode_exception_not_handled in BSOD Crashes and Debugging
Been recently encountering BSoDs with KMODE_EXCEPTION_NOT_HANDLED when gaming, specifically the open beta of Monster Hunter Online. Happens after around 2 hours or so. Doesn't happen with other games and has not happened before. Attached my...
Solved Several BSOD KMODE_EXCEPTION_NOT_HANDLED in BSOD Crashes and Debugging
I never really had any problems with my computer until upgrading to Windows 10, now I am having very frequent crashes that all seem to be similar. My guess is memory corruption, but I can't figure out the cause of it. The crashes are pretty random,...
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 02:24.
Find Us