You're in the middle of an important project when your Windows 11 PC suddenly crashes, then reboots with a cryptic message: "The computer has rebooted from a bugcheck." This guide explains what this error means and provides step-by-step solutions to fix the error. We'll also cover data recovery tool if any files were lost.
Computer Has Rebooted from Bugcheck
Hi, my computer has had crashes for a couple of weeks. Yesterday I tried fixing the corrupted files trough command prompt, which seemed to work, but today it's starting over again, even though, when I checked, there were no corrupted files anymore. It used to happen after quickly opening or closing a game, but now it happens in the middle of a game aswell. It usually starts with this error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffffbe0742bc5460, 0xfffff80664dead40, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\WINDOWS\MEMORY.DMP. I don't get any blue screens, usually it freezes for a few seconds and then restarts. Thanks in advance!
- Question from Anonymous
"The computer has rebooted from a bugcheck" is a Windows error message that appears after a system crash caused by a critical error, commonly known as a Blue Screen of Death (BSOD). When this error occurs, your PC will automatically restart to prevent further system damage. This unexpected crash not only interrupts your workflow but also raises concerns about system stability.
It is worth noting that the BugCheck message is not the actual cause of the crash. Instead, it is a log entry indicating that Windows detected a critical system error severe enough to stop the operating system and generate a memory dump for troubleshooting. A typical BugCheck event contains information similar to the following:
The bugcheck is a mechanism that Windows uses to detect and report these critical errors, allowing users and technicians to diagnose and fix the underlying issue. After encountering a bule screen crash, you can launch "Event Viewer" (press "Win" + "X" and choose "Event Viewer") to check the bugcheck code for further inspection. The bugcheck code often points to the underlying problem. For example:
| Bugcheck Code | Stop Error Name | Possible Cause |
|---|---|---|
| 0x00000116 | VIDEO_TDR_FAILURE | Graphics driver corruption, GPU instability, overheating graphics card, or insufficient power supply. |
| 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL | Outdated or incompatible device drivers, especially network, graphics, or storage drivers. |
| 0x0000007F | UNEXPECTED_KERNEL_MODE_TRAP | Faulty RAM, CPU errors, BIOS configuration problems, overheating, or hardware overclocking. |
| 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA | Corrupted RAM, damaged system files, faulty storage devices, antivirus conflicts, or problematic drivers. |
| 0x0000001A | MEMORY_MANAGEMENT | Memory corruption caused by defective RAM, driver conflicts, disk errors, or file system corruption. |
Above are the common error codes and their potential triggers. The next section will walk you through multiple effective fixes for this issue. Identify the root cause of your error first, then pick the most suitable solution based on your actual situation.
Now that you have identified the BugCheck code, it's time to address the root cause behind the crashes. Follow the solutions below in order until the issue is resolved.
Device drivers act as intermediaries between hardware and the operating system. When they're outdated or incompatible, they can cause communication failures that lead to system crashes. If you recently updated a driver before the errors started, rolling it back may resolve "the computer has rebooted from a bugcheck" issue on Windows.
Step 1. Press "Win" + "X" and select "Device Manager" to open it.
Step 2. Expand "Display adapters" or "Network adapters" and look for devices with yellow exclamation marks (indicating driver issues).
Step 3. Right-click the device and select "Properties".
Step 4. Go to the "Driver" tab. If you recently updated the driver, click "Roll Back Driver" to revert to the previous version.
Step 5. If rolling back isn't an option or doesn't work, click "Uninstall device", check "Delete the driver software for this device" if offered, and restart the PC. Download and install the latest driver directly from NVIDIA, AMD, or Intel, then restart again.
Step 6. Repeat this process for all devices with driver issues. After rolling back or reinstalling drivers, restart your computer and monitor for bugcheck errors. If the issue persists, proceed to the next solution.
Incompatibility between Windows Updates and device drivers can also trigger unexpected system crashes. If updating your drivers fails to resolve the issue, checking Windows Updates is another reliable troubleshooting step. Additionally, Windows Updates occasionally contain bugs that conflict with certain hardware setups. You may inspect or uninstall problematic Windows Updates as needed.
Step 1. Go to "Settings" > "Update & Security" > "Windows Update".
Step 2. Click "Check for update".
Step 3. If your Windows started malfunctioning right after a recent update, you can try uninstalling the latest Windows updates to eliminate these errors. Click "View update history" > "Uninstall updates".
Step 4. In the list of installed updates, look for updates installed around the time the bugcheck errors started. Right-click the update and select "Uninstall".
step 5. After uninstalling the problematic update, check if the bugcheck errors have stopped.
Corrupted hard drive sectors or file system errors can cause the system to crash unexpectedly. Running the check disk utility — CHKDSK can scan the hard drive for both logical errors (file system issue) and physical errors (bad sectors) to repair these issues. It can fix logical errors and mark bad sectors so the system avoids using them.
Step 1. Press "Win" + "X" and select "Command Prompt", right click on it and choose "Run as administrator".
Step 2. Type the following command and press "Enter": chkdsk C: /f /r. Replace "C:" with the drive letter of your system drive if it's different.
Step 3. When prompted to schedule the scan for the next restart, type "Y" and press "Enter". Restart your computer. CHKDSK will run during startup.
Step 4. Wait for the scan to complete. This may take some time depending on the size and condition of your drive. After CHKDSK finishes, check if "the computer has rebooted from a bugcheck" persist.
Corrupted system files can cause a variety of issues, including bugcheck errors. Using the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools can repair these corrupted files. SFC scans for and repairs corrupted system files. If SFC finds errors it cannot fix, DISM repairs the Windows image itself, which provides a clean source for SFC to use.
Step 1. Press "Win" + "X" and select "Command Prompt (Admin)".
Step 2. Enter the following commands one by one:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Step 3. Wait for the scan to complete. After repairing system files, restart your computer and check if the bugcheck errors have been resolved.
Memory errors can corrupt data being processed by the system, leading to unexpected crashes and a wide range of bugcheck codes, including 0x0000001A, 0x00000050, and sometimes even graphics-related crashes. By running a memory diagnostic, you can check the system memory outside of Windows and reports whether memory errors are detected during startup.
Step 1. Press "Win" + "R", type "mdsched.exe" in the Run dialog, and press "Enter".
Step 2. Select "Restart now and check for problems (recommended)". Your computer will restart and run the memory diagnostic.
Step 3. After the test completes, open "Event Viewer" > "Windows Logs" > System", then search for "MemoryDiagnostics-Results". If the memory diagnostic finds errors, you may need to replace the faulty RAM module.
Windows creates minidump files when a bugcheck occurs, which contain valuable information about the crash. When the previous fixes do not identify the cause, the minidump file provides the most direct evidence of which driver or component triggered the crash. This can provide precise information for troubleshooting.
Step 1. Navigate to C:\Windows\Minidump in File Explorer.
Step 3. Look for .dmp files with timestamps that match your bugcheck errors.
Step 4. Download and install the WinDbg Preview from the Microsoft Store.
Step 5. Open it and load the minidump file and run the command "!analyze -v" to get a detailed analysis of the crash.
Step 6. The analysis will show which driver or process was responsible for the crash. Look for the line Probably caused by:. If it names a driver such as nvlddmkm.sys or amdkmdag.sys, focus on reinstalling or replacing the related graphics driver or hardware.
Unstable CPU, GPU, or memory overclocks can pass light workloads but fail during gaming, causing freezes followed by automatic restarts without a visible blue screen. By reverting all performance settings to motherboard default settings, you can help stabilize the system.
Step 1. Restart your computer and press the BIOS key (usually Del, F2, or F10) during startup.
Step 2. Locate the memory profile setting (XMP, EXPO, or DOCP) and set it to Disabled.
Step 3. Remove any CPU or GPU overclock settings and choose Load Optimized Defaults if available.
Step 4. Save changes and exit the BIOS.
After disabling overclocking, monitor your system for bugcheck errors.
If the system remains unstable after driver, disk, memory, and overclocking checks, a BIOS update may resolve compatibility problems with the CPU, memory controller, or PCIe devices. BIOS updates are especially important for newer Intel and AMD platforms that have received stability-related firmware fixes.
Step 1. Press "Win" + "R", type "msinfo32" in the Run dialog, and note the BIOS Version/Date and motherboard model.
Step 2. Visit the motherboard manufacturer's website and download the latest BIOS update for your exact model.
Step 3. Follow the manufacturer's instructions to update the BIOS (this usually involves creating a bootable USB drive).
Step 4. Restart your computer after the BIOS update completes.
In most cases, a BugCheck itself doesn't delete your files. However, the events that follow a BSOD often do. Your computer may restart while you're repairing the system with CHKDSK or SFC. This can result in accidentally deleted files, inaccessible folders, or even data loss from a damaged partition. If you discover that important files are missing after fixing "The computer has rebooted from a bugcheck" in Windows 11, stop writing new data to the affected drive as soon as possible.
This is where MyRecover can help. It is a professional Windows data recovery tool designed to recover files lost due to BSOD crashes, accidental deletion, formatting, partition loss, and more over 500 data loss scenarios. MyRecover scans the drive for recoverable data and allows you preview files before restoring them, making it suitable for both everyday users and IT professionals.
Step 1. Download and install MyRecover on your Windows 11 PC from Microsoft Store.
Step 2. Launch the application, select the drive to scan, and click "Scan" to search for recoverable files.
Step 3. After scanning, filter and preview the found files, select the data you need, and click "Recover".
Step 4. Save the recovered files to an external drive or different partition to avoid overwriting existing data.
Once the process is completed, you can check the recovered files by clicking on destination folder path or the "Browse" button.
"The computer has rebooted from a bugcheck" is a frustrating error that can disrupt your work and potentially cause data loss. By following the solutions in this guide, you can identify the root cause of the bugcheck errors and resolve them easily.
However, unexpected crashes, repair operations, or system recovery attempts may sometimes lead to missing or inaccessible files. If you lose important data after a BugCheck crash, using a professional recovery tool like MyRecover can help scan your drive and recover lost files before they are overwritten.
Q1: What is a bugcheck in Windows?
A bugcheck is a critical system error that causes Windows to stop running to prevent further damage. It usually triggers a BSOD and creates a memory dump file containing diagnostic information. The bugcheck code helps identify possible causes, such as faulty drivers, hardware problems, or corrupted system files.
Q2: How can I fix Windows 11 stuck in a boot loop?
To fix a Windows 11 boot loop, try entering Safe Mode, uninstalling recent updates or drivers, running Startup Repair, and repairing system files with SFC and DISM commands. If the issue continues, check hardware components like RAM and storage drives for possible failures.
Q3: Why does my computer reboot from a bugcheck 0x0000001E?
Bugcheck 0x0000001E (KMODE_EXCEPTION_NOT_HANDLED) usually occurs due to faulty drivers, incompatible software, corrupted system files, BIOS issues, or hardware problems. Updating or reinstalling drivers, checking system files, and testing hardware can help identify and resolve the cause.
Q4: What is event ID 1001 the computer has rebooted from a bugcheck?
Event ID 1001 records that Windows restarted after a system crash caused by a bugcheck. It does not indicate the exact cause of the BSOD. You need to check the bugcheck code, memory dump file, and related system logs to determine the faulty driver or hardware component.
Q5: How to fix PC randomly rebooting?
To fix random reboots, check recent driver or Windows updates, repair corrupted system files, scan for disk errors, test RAM, and disable overclocking settings. If the problem continues, analyze crash dump files or update BIOS to identify deeper hardware or compatibility issues.
Q6: Can outdated drivers cause computer has rebooted from bugcheck?
Yes. Outdated, corrupted, or incompatible drivers are common causes of BugCheck errors because they can create conflicts between Windows and hardware components. Updating, rolling back, or reinstalling drivers, especially graphics, network, and storage drivers can often resolve repeated crashes.