Share via

KMODE EXCEPTION NOT HANDLED BSOD after reinstalling windows 10

Anonymous
2023-07-21T09:05:25+00:00

Hi

I have an old desktop that needed to be refreshed one last time before I save up for a new one. I attempted a clean install of Windows 10 and have been suffering the Kmode exception BSOD ever since. This can occur during installation, boot-up, after 5 seconds or half an hour but it always happens with no apparent trigger. As there is no additional information to the error code and because it occurs during installation I presume it is a hardware issue? I have tried most of the common fault finding operations for this error detailed below. The system specs are an ASUS P8P67 Pro, (Bios 0402), with an i5-2500K, 16Gb of Ram and a GTX 970, 'running' Windows 10 Home 64-bit (10.0, Build 19045)Things I've tried already:

  • Disabled Fast Startup
  • Installed all the drivers suggested by Snappy Driver installer
  • Run the memory diagnostic tool
  • Removed and swapped the memory slots over
  • Unplugged all cables and re-assembled
  • Installed windows on various hard drives (SSD and HDD)

I'm at a bit of a loss what to try next, I was thinking of trying to install Windows 7 next as this machine was upgraded from this and I don't recall doing a fresh install of Windows 10 before. This link contains some of the latest minidump files https://1drv.ms/f/s!AsiuUPHi9ybOhUPvjgcvDN6xlUos?e=M80O6e

Any help or direction you can give me so that I can nurse this machine through 1 more year would be greatly appreciated.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-07-24T13:17:49+00:00

    Hi Dave

    Have you had a chance to look at the new minidump files.

    Thanks

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-07-21T20:21:41+00:00

    I was able to run verifier and let it crash after doing a fresh install and not updating the missing drivers, hopefully that helps identify the cause still.

    The files are in the same shared folder above.

    Thanks

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. DaveM121 876.9K Reputation points Independent Advisor
    2023-07-21T15:57:43+00:00

    Are there any new minidump files created that you can upload?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. DaveM121 876.9K Reputation points Independent Advisor
    2023-07-21T09:40:44+00:00

    Hi Richers,

    I am Dave, I will help you with this.

    Your minidump files just indicate memory (RAM) corruption no specific driver is listed

    System crashes should not survive a clean install of Windows, that usually indicates a hardware fault, but I see you are using a driver updating utility to install your drivers and that may be the cause, those utilities install corrupt and incompatible drivers.

    To try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    Before you run Driver Verifier, please create a new System Restore Point

    https://answers.microsoft.com/en-us/windows/for...

    Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Open Command Prompt as Administrator and run these two commands, then restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2023-07-21T15:56:27+00:00

    Hi Thanks for your reply,

    With verifier on it wont boot, I rolled back to the restore point and after it crashed I got a new BSOD - bad system config info. This BSOD stopped me from booting and the restore point did not help so I have now had to re-install windows again. Should I go through the process of updating all the drivers again? or try verifier again?

    Was this answer helpful?

    0 comments