First, analyze the bug check code and parameters from Event ID 1001 using tools like BlueScreenView or WinDbg to identify the crash cause, as specific codes like 0x0000007E or 0x000000D1 point to system thread exceptions or driver issues. 2. Update or roll back problematic drivers, especially graphics, network, or storage drivers, by checking Device Manager and using minidump analysis to identify the faulty driver. 3. Run system diagnostics including Windows Memory Diagnostic for RAM issues, chkdsk /f /r for disk errors, and CrystalDiskInfo for drive health, followed by sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair corrupted system files. 4. Monitor for overheating using tools like HWMonitor, clean internal components, and test hardware such as RAM with MemTest86 and PSU if possible. 5. Disable automatic restart in System Properties under Startup and Recovery settings to view the actual BSOD error during crashes. 6. Install pending Windows updates to resolve known issues or uninstall recent updates if crashes began immediately after installation. The error indicates a past BSOD event, and resolving it requires checking the minidump, updating drivers, and ruling out hardware problems, which fixes the issue in most cases.

The "The computer has rebooted from a bugcheck" error in Windows Event Viewer means your system experienced a Blue Screen of Death (BSOD) and automatically restarted. The error is logged under Event ID 1001 in the System log and often includes a bug check code (like 0x0000007E, 0x000000D1, etc.). Here’s how to fix it step by step.

1. Check the Bug Check Code and Parameters

Open Event Viewer → Go to Windows Logs > System → Find the event with Source: BugCheck or Event ID 1001.

Look for:

• BugCheckCode (e.g., 0x0000003B, 0x0000007E)
• BugCheckParameters (four values listed)

These codes tell you what went wrong. For example:

• 0x0000007E: System thread exception
• 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL (often driver issue)
• 0x0000003B: Kernel mode exception in user mode callback

? Use tools like Windows Debugger (WinDbg) or upload the minidump file (C:\Windows\Minidump\*.dmp) to a tool like BlueScreenView (NirSoft) to analyze the crash dump.

2. Update or Roll Back Drivers

Most bug checks are caused by faulty or outdated drivers.

Steps:

• Press Win X → Device Manager
• Look for devices with warnings (yellow icon)
• Focus on:
  • Graphics drivers (NVIDIA/AMD/Intel)
  • Network adapters
  • Storage controllers
  • Any recently updated drivers

Update:

• Right-click device → Update driver → Search automatically
• Or download the latest driver from the manufacturer’s website

Roll back (if problem started recently):

• Right-click device → Properties → Driver tab → Roll Back Driver

? Tip: If you’re not sure which driver is causing the issue, check the minidump analysis — it usually points to a specific driver (e.g., dxgkrnl.sys, nvlddmkm.sys).

3. Run System Diagnostics

a. Check for Memory Issues

Use Windows Memory Diagnostic:

• Press Win R, type mdsched.exe, press Enter
• Choose Restart now and check for problems
• After reboot, check results in Event Viewer:
  Windows Logs > System → Find source MemoryDiagnostics-Results

b. Check Disk Health

Open Command Prompt as admin:

chkdsk /f /r

(Requires reboot — say Yes if prompted)

Also check SSD/HDD health using tools like CrystalDiskInfo.

c. Run SFC and DISM

Fix corrupted system files:

sfc /scannow

Then:

DISM /Online /Cleanup-Image /RestoreHealth

4. Check for Overheating or Hardware Issues

• Monitor CPU/GPU temps using HWMonitor or Core Temp
• Clean dust from fans and heatsinks
• Ensure proper airflow
• Faulty RAM, PSU, or motherboard can also cause BSODs — test with:
  • MemTest86 for RAM
  • Power supply tester (if possible)

5. Disable Automatic Restart (So You Can See the BSOD)

By default, Windows hides the blue screen and reboots — this makes diagnosis hard.

Turn off auto-restart:

• Go to Control Panel > System > Advanced system settings
• Under Startup and Recovery, click Settings
• Uncheck Automatically restart
• Click OK and reboot

Now, if a BSOD occurs, you’ll see the error screen with more details.

6. Check for Windows Updates

Sometimes Microsoft releases fixes for known driver or kernel issues:

• Go to Settings > Update & Security > Windows Update
• Install all pending updates

Also consider uninstalling recent updates if crashes started right after one.

Summary: What to Do First

• ? Analyze the minidump file for the actual crash cause
• ? Update or roll back suspicious drivers (especially GPU)
• ? Run sfc /scannow and DISM
• ? Test RAM and disk health
• ? Disable auto-restart to catch the BSOD screen

Most of the time, this error comes from driver conflicts or hardware issues — not Windows itself. Focus on what changed recently: new hardware, driver update, or software install.

Basically, check the dump file, update drivers, and rule out hardware problems. That’ll fix it in 90% of cases.

The above is the detailed content of how to fix 'the computer has rebooted from a bugcheck' in win event viewer. For more information, please follow other related articles on the PHP Chinese website!