Share via

Multiple different BSODs

Anonymous
2024-08-25T05:33:02+00:00

https://1drv.ms/f/c/8ed605c0467cc21d/Eulquo3FTs9Kg85BeuvddWQBxItT2k3QJlPIeWVOaZyfxQ?e=0qlwGU

Multiple BSODs, mostly kmode exception not handled and kernel security check failure. Only hardware that hasn't been swapped out at this point is the PSU and CPU. I am running a fresh Windows install on a spare drive, which I had to install using another computer because the installation media crashed. I've been having issues with random restarts with no error screen since purchasing a new CPU, so I think it may be the issue now that I am rarely even able to boot without blue screening, if not soon after logging in.

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 No comments

9 answers

Sort by: Most helpful
  1. DaveM121 891.1K Reputation points Independent Advisor
    2024-08-26T07:09:31+00:00

    Mostly your minidump files list generic RAM corruption, but Driver Verifier indicates it is the AMD chipset drivers causing your system to crash.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-08-25T19:28:22+00:00

    It gave the correct "DRIVER_VERIFIED_DETECTED_VIOLATION" code but didn't list a driver. Here's the new dumps:

    https://1drv.ms/f/c/8ed605c0467cc21d/Eq1tqtXIKDBGnJB6gv3wenYBIQOpYJo69whNxLGHwYcrlA?e=S9zdBP

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 891.1K Reputation points Independent Advisor
    2024-08-25T18:32:26+00:00

    The new minidump files indicate generic RAM corruption errors, there is no specific cause of the crashes listed.

    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?

    0 comments No comments
  4. Anonymous
    2024-08-25T16:14:11+00:00

    Thanks Dave, you've helped me a lot indirectly through Google searches, I'm glad to have your expertise here.

    After the chipset drivers and BIOS update, I encountered a few BSODs before reaching the login screen. But after a few of those, I can now log in and do anything that isn't resource intensive. Using much more than my browser and file explorer results in more BSODs.

    Here are my new dumps: https://1drv.ms/f/c/8ed605c0467cc21d/Ej0yN29IFr9Lt4Y7QLtwDgwB5hHTmb-7COMnfoCz-oBWwQ?e=hg5KtR

    I appreciate your help.

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 891.1K Reputation points Independent Advisor
    2024-08-25T06:19:28+00:00

    Hi, I am Dave, I will help you with this.

    Your minidump file indicates it is the storage drivers causing your PC to crash.

    Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of Chipset drivers they recommend and while there, if you do not have your drive encrypted with Bitlocker, check for any BIOS update that may need to be installed

    Was this answer helpful?

    0 comments No comments