Bsod : Kmode_exception_not_handled

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 13,957
    Windows 10 Pro X64 21H1 19043.1503
       #11

    Everything looked good except for this:

    Attachment 284218

    Definitely need to keep an eye on the drive. CRC errors can cause problems like inpage data errors when paging.

    Let's see what Driver Verifier shows.

    Good work so far.
      My Computers


  2. Posts : 10
    Windows 10
    Thread Starter
       #12

    Hmmm,

    Using Driver Verifier on all non microsoft drivers as per instructions puts me into a boot loop. I get to the login screen and then once i input my pin/password it tries to get into windows and restarts the PC.

    Only way to fix is boot into safe mode and turn off Driver Verifier.

    Before i turned off Driver Verifier in safe mode i checked for minidumps and memory.dmp and found nothing unfortunately.

    Ran the log generator just incase.

    DESKTOP-AFL1NRM-(2020-06-20_13-21-39).zip - Google Drive

    Also test Driver Verifier with just Nvidia drivers and i could boot into Windows.
    So now i am going to systematically add drivers to test to see if it's a specific driver causing the boot loop!

    - - - Updated - - -

    Edit:

    So apparently it was multiple drivers causing the reboot issue.

    So i tried the settings in the second link (Less test cases i know)

    But trying out these tests on all non Microsoft drivers to see if we get anything

    I/O Verification
    Force pending I/O requests
    IRP logging
      My Computer


  3. Posts : 13,957
    Windows 10 Pro X64 21H1 19043.1503
       #13

    Okay, good luck.
      My Computers


  4. Posts : 10
    Windows 10
    Thread Starter
       #14

    Ztruker said:
    Okay, good luck.
    Well it finally happened haha!

    Here are the logs: DESKTOP-AFL1NRM-(2020-06-21_19-38-57).zip - Google Drive

    And the memory.dmp : MEMORY.zip - Google Drive

    Thanks so much for all the help!
      My Computer


  5. Posts : 13,957
    Windows 10 Pro X64 21H1 19043.1503
       #15

    Dumps are not Verifier generated, just IRQL_NOT_LESS_OR_EQUAL. No useful info in them unfortunately.

    Continue to add drivers.
      My Computers


  6. Posts : 10
    Windows 10
    Thread Starter
       #16

    Ztruker said:
    Dumps are not Verifier generated, just IRQL_NOT_LESS_OR_EQUAL. No useful info in them unfortunately.

    Continue to add drivers.
    Urgh! And here i was hoping to give you something tangible!

    I also see that i am getting loads of access violations suddenly with my RTX Voice application from Nvidia, so i think i'm going to do a nice DDU and see if that helps anything
      My Computer


  7. Posts : 13,957
    Windows 10 Pro X64 21H1 19043.1503
       #17

    Worth a try.
      My Computers


  8. Posts : 10
    Windows 10
    Thread Starter
       #18

    Ztruker said:
    Worth a try.
    Didn't work either.

    I'm at the point now where i am just going to do a completely fresh install again and hope for the best.

    Any advice other than media creation tool?

    - - - Updated - - -

    See you guys on the other side!

    Fingers crossed!

    - - - Updated - - -

    So far so good! Haven't had a blue screen and no app crashes yet!

    I'll give it another day or so and then close this thread!

    Thanks so much for all the help ztrucker!
      My Computer


  9. Posts : 13,957
    Windows 10 Pro X64 21H1 19043.1503
       #19

    I'm still here though I miss a day every now and then. Good luck.
      My Computers


  10. Posts : 10
    Windows 10
    Thread Starter
       #20

    Ztruker said:
    I'm still here though I miss a day every now and then. Good luck.
    So, I was still getting the same BSOD issue now and then...
    Decided to use my snooping skills to try out WinDbg and i found something in one of the minidumps...

    DeviceId : USB\VID_04E8&PID_6860\ce071717282f772d017e

    On googling this i see it is a driver associated with SAMSUNG Mobile USB Composite Device.

    Now come to think of it, and i could be hellishly wrong but, each time i've connected my Samsung device to my PC a few hours later i would get the BSOD. So what i am going to try out, is completely removing said driver as i don't need to connect my phone to my PC.

    For interest sake, My driver version is 1.16.14.0 and i see on the windows update catalog that that specific version is for Windows 8.1 Drivers, Windows 7, Windows 8

    while the next version for Windows 10, version 1809 and later, Servicing Drivers is version 2.16.12.0

    http://www.catalog.update.microsoft....mposite+Device

    So maybe a compatibility issue is causing the BSOD issues i have been having but lets see
      My Computer


 

  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 08:06.
Find Us




Windows 10 Forums