Share via

Computer BSOD with different Bugcheck codes every time

Anonymous
2024-06-19T09:45:26+00:00

At first I thought my windows was corrupted so i formatted my SSD and reinstalled windows, I ran CrystalDiskRunner and got a 100% disk health, I also ran Windows Memory Diagnostics and found no errors. Still, I'm facing 1 BSOD on average per day. I suspect that this is a hardware issue but I don't know which part is causing the problem, I don't want to waste unnecessary money so I hope someone can help me here.

Below is the latest BSOD report, BugcheckCode 80:

Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 6/19/2024 11:01:46 AM Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: WC-Desktop Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 41 9 1 63 0 0x8000400000000002 2373 System WC-Desktop 80 0xffffe60ec7ef82d8 0x0 0xffff97c09c832670 0x2 0 0 0 0 true 0 1 false 0 1 false false 0 0 3

attached are are the minidump files of all the crashes I have had since reformatting my drive and reinstalling windows: https://drive.google.com/drive/folders/1s1P7bVPa7v7ldk46o0Xlj1ZBUZxSuZ51?usp=sharing

Windows for home | Windows 11 | 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 882.3K Reputation points Independent Advisor
    2024-06-20T10:38:40+00:00

    There is nothing specific indicated in that new minidump file as the cause of that crash, to try to force Windows 11 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
  2. Anonymous
    2024-06-20T10:10:36+00:00

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 882.3K Reputation points Independent Advisor
    2024-06-20T09:49:57+00:00

    Please try this method to upload your new minidump file.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Open that minidump folder

    Select any file in there and press Ctrl + C to copy the file.

    On your Desktop, press Ctrl + V to paste a copy of the file.

    Can you upload that copy from your Desktop?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-06-20T09:46:35+00:00

    After reinstalling my network drivers, I didn't have any problems until today I got another BSOD with Bug Check Code 10, I don't know why google drive wont let me upload my latest minidump file, it says that the file is unreadable

    Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 6/20/2024 5:39:08 PM Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: WC-Desktop Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: http://schemas.microsoft.com/win/2004/08/events/event"> 41 9 1 63 0 0x8000400000000002 3053 System WC-Desktop 10 0x8b9534e8 0x2 0x0 0xfffff80207ed114e 0 0 0 0 false 0 0 false 0 0 false false 0 0 3

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 882.3K Reputation points Independent Advisor
    2024-06-19T10:20:37+00:00

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

    Your minidump files indicate it is the network drivers causing your PC to crash.

    Go to the support page for your PC on the manufacturers website, then from there, download and re-install the version of network drivers they provide.

    Was this answer helpful?

    0 comments No comments