Windows 10: KMODE EXCEPTION NOT HANDLED after clean install

Page 1 of 5 123 ... LastLast
  1.    22 Jan 2018 #1

    KMODE EXCEPTION NOT HANDLED after clean install


    I have been having issues since I built my PC a month ago and decided to do a fresh install on my SSD yesterday. Everything went well and was gaming for a while yesterday with no issues. Today, it decides to crash and give me KMODE EXCEPTION NOT HANDLED with no driver name referenced. Looking for any possible help with what is causing these crashes.
    KMODE EXCEPTION NOT HANDLED after clean install Attached Files
      My ComputerSystem Spec


  2. Posts : 17,735
    windows 10 professional version 1607 build 14393.969 64 bit
       22 Jan 2018 #2

    Hi, MentholSushi ,

    Welcome to Ten Forums BSOD forum.

    There were 3 BSOD mini dump files.
    When debugged there was no definitive misbehaving driver.

    1) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.
    Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool
    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM BSOD Tutorials

    2) For any BSOD please run this version of the log collector and post a new zip into the thread:
    log collector v2-beta08.zip


    Code:
    1/22/2018 10:58 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1e
    P2: ffffffffc0000005
    P3: fffff800c721c3d8
    P4: 0
    P5: ffffffffffffffff
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012218-6109-01.dmp
    \\?\C:\Windows\TEMP\WER-8250-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B65.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B84.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_3a148b6f928cc481e9014fedb8250c53ad65_00000000_cab_03702b94
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 748dbd65-85c7-4ca0-8843-ad304f1dd329
    Report Status: 4
    Hashed bucket:1/21/2018 10:10 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80028f3c41a
    P4: ffffbd8083ad4430
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-2859-01.dmp
    \\?\C:\Windows\Temp\WER-3703-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER150E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER152D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER153E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_b089a02750edec71cbb4944aa63c27ff64272b11_00000000_cab_02ec153d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: bf2d719e-d713-4d0d-a02b-6fb0f18567f3
    Report Status: 4
    Hashed bucket:
    1/21/2018 10:32 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80028f3c41a
    P4: ffffbd8083ad4430
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-2859-01.dmp
    \\?\C:\Windows\Temp\WER-3703-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER150E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER152D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER153E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_b089a02750edec71cbb4944aa63c27ff64272b11_00000000_cab_02ec153d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: bf2d719e-d713-4d0d-a02b-6fb0f18567f3
    Report Status: 6
    Hashed bucket:
    1/21/2018 10:01 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80314cd5d43
    P4: ffffe30167e632a0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-12906-01.dmp
    \\?\C:\Windows\Temp\WER-14296-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4074.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4083.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4094.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_1e3b68a5c682a97d68ee0c6fa427ba5f4affc95_00000000_cab_02e840a2
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7bc37085-0c5f-4823-bb92-2bdee20266e1
    Report Status: 4
    Hashed bucket:
    1/21/2018 9:57 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff8038a90c794
    P4: ffffda8159ceaec0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-2937-01.dmp
    \\?\C:\Windows\Temp\WER-3796-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1608.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1618.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1648.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_2036ed849639a059c5a6dd1155b7d1d294f_00000000_cab_02a81656
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d0cb6a69-fac2-4f27-be41-f70480c34856
    Report Status: 4
    Hashed bucket:
    1/21/2018 10:16 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 88497758-3a90-4c74-8700-a1ebd99feb57
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff8038a90c794
    P4: ffffda8159ceaec0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-2937-01.dmp
    \\?\C:\Windows\Temp\WER-3796-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1608.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1618.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1648.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_2036ed849639a059c5a6dd1155b7d1d294f_00000000_cab_02a81656
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d0cb6a69-fac2-4f27-be41-f70480c34856
    Report Status: 4
    Hashed bucket:
    Code:
    1/21/2018 10:16 PM    Windows Error Reporting    Fault bucket LKD_0x15E_Mini_Nbl_Leak_IMAGE_Netwtw04.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0ac1fe58-c90c-4433-849c-5247297ea8f9
    
    Problem signature:
    P1: 15e
    P2: 30
    P3: ffffa105c92241a0
    P4: ffffa105c93cb060
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\NDIS\NDIS-20180121-1354.dmp
    \\?\C:\Windows\Temp\WER-267015-0.sysdata.xml
    \\?\C:\Windows\LiveKernelReports\NDIS-20180121-1354.dmp
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BA2.tmp.WERInternalMetadata.xml
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_15e_9f6b86ffb9d93bc2d96b23071eb3a97c1917b38_00000000_cab_22341c3f\WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
    \\?\C:\Windows\Temp\WER1C11.tmp.etl
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C1F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C40.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_15e_9f6b86ffb9d93bc2d96b23071eb3a97c1917b38_00000000_cab_18e97b52
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 747e6fae-0f0c-46ab-9a8a-81fa291e10bc
    Report Status: 268435456
    Hashed bucket:
    Code:
    1/22/2018 11:27 PM    Windows Error Reporting    Fault bucket 0x1E_c0000005_R_nt!KiEndCounterAccumulation, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 1d7d3cb1-8d1d-4bfa-8e93-7b3329b10d57
    
    Problem signature:
    P1: 1e
    P2: ffffffffc0000005
    P3: fffff800c721c3d8
    P4: 0
    P5: ffffffffffffffff
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012218-6109-01.dmp
    \\?\C:\Windows\TEMP\WER-8250-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B65.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B84.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt
    \\?\C:\Windows\Temp\WER7E49.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_3a148b6f928cc481e9014fedb8250c53ad65_00000000_cab_03702b94
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 748dbd65-85c7-4ca0-8843-ad304f1dd329
    Report Status: 388
    Hashed bucket:1/21/2018 11:04 PM    Windows Error Reporting    Fault bucket 0x3B_nt!CmpCreateKeyControlBlock, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: bb062bae-c3ba-4d24-99ea-11bf2b409cfa
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80028f3c41a
    P4: ffffbd8083ad4430
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-2859-01.dmp
    \\?\C:\Windows\Temp\WER-3703-0.sysdata.xml
    \\?\C:\Windows\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER150E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER152D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER153E.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_b089a02750edec71cbb4944aa63c27ff64272b11_00000000_cab_248b4259
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: bf2d719e-d713-4d0d-a02b-6fb0f18567f3
    Report Status: 268435462
    Hashed bucket:
    1/21/2018 10:28 PM    Windows Error Reporting    Fault bucket 0x3B_nt!KiDeferredReadyThread, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 5bae6abb-3678-4771-809f-d3e00e8a54c7
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff80314cd5d43
    P4: ffffe30167e632a0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-12906-01.dmp
    \\?\C:\Windows\Temp\WER-14296-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4074.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4083.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4094.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_1e3b68a5c682a97d68ee0c6fa427ba5f4affc95_00000000_cab_05bf6080
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7bc37085-0c5f-4823-bb92-2bdee20266e1
    Report Status: 268435456
    Hashed bucket:
    1/21/2018 10:28 PM    Windows Error Reporting    Fault bucket 0x3B_nt!SepDuplicateToken, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 88497758-3a90-4c74-8700-a1ebd99feb57
    
    Problem signature:
    P1: 3b
    P2: c0000005
    P3: fffff8038a90c794
    P4: ffffda8159ceaec0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\Minidump\012118-2937-01.dmp
    \\?\C:\Windows\Temp\WER-3796-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1608.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1618.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1648.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_2036ed849639a059c5a6dd1155b7d1d294f_00000000_cab_05bee8df
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d0cb6a69-fac2-4f27-be41-f70480c34856
    Report Status: 268435460
    Hashed bucket:
      My ComputerSystem Spec

  3.    23 Jan 2018 #3

    I remembered I changed my XMP profile a few weeks ago to try to get my RAM running close to 3200, my computer was running great until a couple weeks ago. I turned off the XMP to see if that could have been the cause, but, ended up getting another BSOD last night. This one referenced fltmgr.

    But, here are the updated log files, I have not had a chance to run the memory test yet.
    KMODE EXCEPTION NOT HANDLED after clean install Attached Files
      My ComputerSystem Spec


  4. Posts : 17,735
    windows 10 professional version 1607 build 14393.969 64 bit
       23 Jan 2018 #4

    1) Open Ccleaner > scroll down to system and advanced > post an image into the thread.

    2) In the left lower corner type system > open system control panel > on the left pane click advanced system settings >view system properties

    a) under performance click settings > on performance options click the advanced tab > under virtual memory click change > post an image of the virtual memory tab into the thread

    b) under startup and recovery click settings > post an image of startup and recovery into the thread

    3) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

    4) In the left lower corner search type: services > on services scroll down to windows error reporting service > right click > left click on properties > post an image into the thread
      My ComputerSystem Spec

  5.    23 Jan 2018 #5

    Here's a new one, memory management, logs attached. Also, here are the pictures you requested. I've never run CCleaner, just used it for uninstalling programs. Thanks for the help.
    Click image for larger version. 

Name:	Capture2.PNG 
Views:	35 
Size:	15.0 KB 
ID:	173957Click image for larger version. 

Name:	Capture3.PNG 
Views:	35 
Size:	17.4 KB 
ID:	173958Click image for larger version. 

Name:	Capture.PNG 
Views:	35 
Size:	16.4 KB 
ID:	173955Click image for larger version. 

Name:	Capture1.PNG 
Views:	35 
Size:	14.1 KB 
ID:	173956
    KMODE EXCEPTION NOT HANDLED after clean install Attached Files
      My ComputerSystem Spec

  6.    23 Jan 2018 #6

    Another crash, not sure if these are useful if there was no BSOD. My main monitor stays active, but, freezes, and my 2nd monitor blacks out.
    KMODE EXCEPTION NOT HANDLED after clean install Attached Files
      My ComputerSystem Spec

  7.    23 Jan 2018 #7

    I am at wit's end, 3 crashes in the last two hours. No blue screen again, but, I am now getting this lovely window that continues to pop up no matter what I do. This time I was only on here, nothing else running. Some more logs for you.
    Click image for larger version. 

Name:	Capture4.PNG 
Views:	32 
Size:	6.6 KB 
ID:	173967
    KMODE EXCEPTION NOT HANDLED after clean install Attached Files
      My ComputerSystem Spec


  • Posts : 17,735
    windows 10 professional version 1607 build 14393.969 64 bit
       23 Jan 2018 #8

    1) For Ccleaner > un-check
    a) memory dumps
    b) windows log files
    2) For startup and recovery > un-check
    a) automatically restart
    3) For windows error reporting:
    Change startup type to automatic
    Click start > ok > reboot

    4) Before performing the dump test below please use file explorer to find C:\windows\memory.dmp > post a link into the thread.

    5) Download and install: http://www.resplendence.com/whocrashed
    6_ Above analyze click on tools > crash dump test > type: ACCEPT
    7) Click analyze > post an image of the results into the thread using one drive or drop box share link
    8) Run the log collector after the above steps and post a new zip into the thread.
      My ComputerSystem Spec

  •    23 Jan 2018 #9

    I wasn't paying attention and skipped #4, sorry, I hope I didn't screw anything up. Here are the pictures and the logs.

    Dropbox - Shared
    KMODE EXCEPTION NOT HANDLED after clean install Attached Files
      My ComputerSystem Spec


  • Posts : 17,735
    windows 10 professional version 1607 build 14393.969 64 bit
       23 Jan 2018 #10

    The last crash was the crash dump test.
    For the next crash run the log collector and post a memory dump for troubleshooting.

    Open device manager > click view > show hidden devices > expand all rows > look for any row with an icon that is a yellow triangle with a black exclamation mark > post an image into the thread

    Post an image of network adapters into the thread.
      My ComputerSystem Spec


  •  
    Page 1 of 5 123 ... LastLast

    Related Threads
    Bsod kmode exception not handled in BSOD Crashes and Debugging
    Hello all, I have just experienced a BSOD on my Windows 10 desktop, which displayed the following error code: KMODE EXCEPTION NOT HANDLED I have attached the dump file zip, created immediately after the system restarted. I have made two...
    BSOD Kmode exception not handled in BSOD Crashes and Debugging
    Hello everyone! I bought a new pc and when I did fresh install of Windows 10 on SSD, as soon as Windows loaded (after welcome screen) I got these errors: OneDriverSetup.exe cannot start WerFault.exe dllhost.exe and than BSOD with error...
    kmode exception not handled nvlddmkm.sys in BSOD Crashes and Debugging
    about a week age and completely out of the blue got message: kmode exception not handled nvlddmkm.sys! No idea why!! See attachment
    BSOD - Kmode Exception Not Handled - Netio.sys in BSOD Crashes and Debugging
    Hello, I recently have been having a few BSOD's and they all point to netio.sys. Unfortunately it happens very random with me doing different tasks. I'm unable to duplicate it. I've have run a System File checker on it and that's come back...
    Kmode exception not handled. fvevol.sys in BSOD Crashes and Debugging
    Hi, Thank you for looking at my problema! I migrated to W10pro about a week ago and I must say all went perfectly smooth and well! Nothing special until this morning. Using Bitlocker on both partitions, startup and data. I started up...
    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 23:42.
    Find Us