When Windows crashes with a Blue Screen of Death (BSOD) or a sudden restart, the system usually saves a crash dump and an event log entry. This guide shows you how to find and read those logs using built-in tools, so you can identify the faulty driver or component and start fixing the problem. You’ll need a Windows PC (Windows 10 or 11) with administrative access.
What You’ll Need
- A Windows 10 or 11 PC that has experienced a crash or BSOD.
- Administrator rights (to run certain tools and view some logs).
- Patience – crash logs can be cryptic, but the key info is usually in the first few lines.
Step-by-Step
- Open Event Viewer. Press Win + R, type
eventvwr.msc, and press Enter. If prompted by User Account Control, click Yes. - Navigate to the System log. In the left pane, expand Windows Logs and click System. This log records all system-level events, including crashes.
- Find the crash event. Look for events with Error level and source BugCheck (for BSODs) or Kernel-Power (for unexpected shutdowns/restarts). The date and time should match when the crash happened. Double-click the event to see details.
- Read the BugCheck event details. In the General tab, you’ll see the stop code (e.g., 0x0000000A) and sometimes the name of the driver that caused the crash (e.g.,
ntoskrnl.exeordriver.sys). The Details tab shows raw XML with more info, including the four parameters (if any). - Check the minidump files. By default, Windows writes a minidump file to
C:\Windows\Minidumpwhen a BSOD occurs. Open File Explorer and navigate to that folder. If you see .dmp files, you can analyze them with a debugger tool (see Tips). - Use the Reliability Monitor (optional). Press Win + R, type
perfmon /rel, and press Enter. This shows a timeline of system events, including crashes, with a brief description. It’s easier to read than Event Viewer for non-technical users. - Check for kernel dump files (if minidumps are missing). If the Minidump folder is empty, Windows might be set to write a full memory dump. Go to Control Panel > System > Advanced system settings > Startup and Recovery > Settings. Under “Write debugging information,” see what is selected. If it’s “Kernel memory dump” or “Complete memory dump,” the file will be at
C:\Windows\MEMORY.DMP.
Common Mistakes
- Looking only at the most recent event. The crash might not be the latest event if other errors occurred after. Filter by date and time.
- Misreading Kernel-Power 41 as a BSOD. Kernel-Power 41 (Event ID 41) means the system rebooted without a clean shutdown – it could be a hardware issue, power failure, or a hang, not necessarily a BSOD. Check if there’s a BugCheck event immediately before it.
- Ignoring the “Details” tab. The General tab only shows the stop code. The Details tab contains the actual bugcheck parameters and the driver that was loaded at the time – often the culprit.
- Assuming the minidump folder is always present. If Windows is set to “Small memory dump (256 KB)”, the folder is created automatically. If not, no minidumps are saved.
- Not running Event Viewer as administrator. Some events require admin rights to view fully. If you see “Access Denied”, close and reopen as admin.
Tips
- Use the BlueScreenView tool (free). This third-party utility reads minidump files and presents the crash information in a simple table, including the driver that likely caused the crash. It’s much easier than parsing Event Viewer.
- Copy the stop code and search for it. For example, “0x0000000A” or “IRQL_NOT_LESS_OR_EQUAL”. Search the web for that code plus your Windows version to find common causes and fixes.
- Check for driver updates. The most common BSOD cause is a faulty or outdated driver. Once you identify the driver (e.g., a GPU driver), update it from the manufacturer’s website.
- Enable automatic memory dumps. In Startup and Recovery settings, ensure “Write debugging information” is set to “Automatic memory dump” (default). This ensures minidumps are saved when a crash occurs.
- Use the Windows Debugger (WinDbg) for deep analysis. Install the Windows SDK or use the Microsoft Store version of WinDbg, open the .dmp file, and run the command
!analyze -v. It will often point to the specific driver.
Troubleshooting
I can’t find any BugCheck events in Event Viewer. If the system crashed but no BugCheck event is logged, it might be a hardware issue (like a power supply failure) that prevented Windows from writing the log. Check if the system is overheating or if the RAM is faulty. Also, check the “Kernel-Power” events – if there’s a critical event with ID 41, it usually indicates an unexpected shutdown.
The minidump folder is empty. This could be because Windows is not set to write minidumps, or the crash was so severe that the dump couldn’t be written. Go to Startup and Recovery settings and make sure “Small memory dump (256 KB)” or “Automatic memory dump” is selected. If it’s already selected, the dump might have been saved to a different location – check C:\Windows\MEMORY.DMP.
I see the stop code but no driver name. That’s normal – the driver name is often not in the Event Viewer. You need to analyze the minidump file to get the driver. Use BlueScreenView or WinDbg as described in Tips.
Event Viewer is very slow or unresponsive. Try filtering the log to only show Error level events for the last 24 hours. Right-click on “System” and choose “Filter Current Log”. Set “Event level” to “Critical” and “Error”, and set a time range.
I can’t open Event Viewer because it says “MMC cannot open the file”. This is rare, but you can try running eventvwr.msc /a from an elevated command prompt. If that fails, restart the Windows Event Log service (in services.msc) and try again.
Frequently Asked Questions
Q: What is the difference between a BugCheck and a Kernel-Power event?
A: A BugCheck event (source: BugCheck) is logged when a BSOD occurs. A Kernel-Power event with ID 41 is logged when the system restarts without a clean shutdown – it could be a BSOD, a hardware failure, or a power loss. Always check for a BugCheck event first.
Q: How do I find the stop code (e.g., 0x0000000A) from a BSOD?
A: In Event Viewer, open the BugCheck event and look at the General tab. The stop code is the first number after “The computer has rebooted from a bugcheck.” It’s also in the Details tab under EventData – the BugcheckCode field.
Q: Can I analyze a minidump without installing any software?
A: Windows doesn’t include a built-in tool to read minidumps. You can use the Windows Debugger (WinDbg) which is free but requires installation. Alternatively, you can use online minidump analyzers that let you upload the file.
Q: Why does my PC restart without showing a BSOD?
A> This happens when Windows is set to automatically restart on system failure. To see the BSOD, go to Control Panel > System > Advanced system settings > Startup and Recovery > Settings, and uncheck “Automatically restart”.
Q: What should I do after identifying the faulty driver?
A: Update the driver from the manufacturer’s website, or roll back to a previous version if the issue started after an update. If the driver is a third-party one, consider uninstalling it and checking for a newer version.
Q: Are crash logs stored forever?
A: Event Viewer logs can grow large, but Windows overwrites old events when the log reaches its maximum size (default 20 MB). Minidumps are kept until you delete them or Windows cleans up old files.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- iOS 18 Safari Not Working? Fixes That Help
- How to Check Your Linux Kernel for Spectre
- iPhone Safe Mode: How to Enable or Disable It
- Fix Slow Internet Lag on Samsung Galaxy Note
- How to Get iOS 17 on iPhone X (Safe Methods)
- Fix Gmail IMAP Error in Outlook: Step-by-Step