您的计算机每隔一段时间就会死机，尤其是在您运行Microsoft Windows 10/11或旧版Windows时。所有计算机崩溃都由您的操作系统记录，这可以帮助您了解需要修复的内容。但是，关键是要知道在哪里可以找到这些记录。
在Windows上，您会注意到您的计算机屏幕在崩溃之前会先变蓝片刻。臭名昭著的“蓝屏死机”（BSOD）是一个确定的信号，表明您的计算机上需要修复某些东西。
但是，在某些情况下，蓝屏会很快消失(blue screen disappears very quickly)。您将无法记录错误代码以进行故障排除，但您仍然可以找到有关导致崩溃的原因的详细信息。这正是我们在本指南中讨论的内容。
计算机(Computer)崩溃或冻结(Froze)的潜在原因(Reasons)
- 故障或 RAM 或硬盘
- 过热
- 病毒或恶意软件
- 错误、错误、过时或损坏的设备驱动程序
- 供电不足或波动
- 有时，第三方软件
既然您知道了可能导致系统崩溃的原因，那么我们来谈谈如何确定导致Windows 10的原因。只有确定原因后，您才能修复Windows并防止其在未来崩溃。
在可靠性监视器(Reliability Monitor)中查找关键事件
Windows 从Windows 7(Windows 7)开始引入了可靠性监视器(Reliability Monitor)，它从此成为查找系统和应用程序崩溃的最快、最用户友好的方式。
但是，请注意，可靠性监视器(Reliability Monitor)没有明确说明导致崩溃的原因。查看在崩溃之前或周围发生的事件更有帮助，因此您可以尝试缩小潜在原因的范围。
您可以通过在开始菜单(Start Menu)中搜索来打开可靠性监视器(Reliability Monitor)。在开始菜单(Start Menu)搜索栏中键入可靠性(reliability)，然后选择在 Windows 10 或 11 上查看可靠性历史记录。(View reliability history)
可靠性监视器(Reliability Monitor)打开后，您将能够查看最右侧的当前日期以及每一天的事件的按日列。您还可以通过从左上角选择周来选择每周视图。(Weeks)
冻结(Freezes)和崩溃由红色圆圈中的 X 表示。它们是您在试图找出导致崩溃问题的原因时在可靠性监视器中寻找的关键事件。(Reliability Monitor)
您还将在底部看到列出的关键事件——双击事件以获取有关导致它的原因的更多信息。例如，在以下情况下，事件日志显示Windows由于OneDrive而停止响应。
您还可以查看事件查看器(Event Viewer)来检查您的计算机崩溃的原因。但是，您将在Event Viewer上获得与Reliability Monitor相同的信息。
在事件查看器中查看崩溃日志
您可以使用事件查看器检查在(Event)Windows 10崩溃之前生成的错误、警告和系统消息。事件查看器(Event Viewer)将事件分类如下：
- 信息性：(Informational: )成功执行流程的正常事件属于此类别。
- 警告：(Warning: )此类别下的事件可能会在未来导致问题，尽管它们目前没有导致任何错误。
- 错误：(Error: )这是您会发现进程失败和崩溃的类别。
要在Windows 10和 11上访问事件查看(Event Viewer)器，请在开始菜单(Start Menu)搜索框中键入事件查看器，然后按(event viewer)Enter选择最佳匹配。
启动事件查看器(Event Viewer)后，您将在左侧边栏中看到一个列表。您将在Windows 日志(Windows Logs)>系统(System )部分中找到BSOD事件或您的 PC 因任何其他原因而崩溃的崩溃日志。
您现在将看到列出的所有事件，但如果您不想筛选数百个事件，只需选择第一列顶部的级别(Level)标签，它会将所有关键事件置于顶部。
或者，您可以创建自定义视图来过滤和查找关键事件。您可以通过从事件查看器(Event Viewer)的右侧栏中选择创建自定义视图(Create Custom View)来执行此操作。您会看到弹出一个新窗口。
从Logged(Logged)选项旁边的下拉列表中选择基于崩溃事件发生时间的相关持续时间。选中事件级别(Event level)选项中的错误(Error )框，然后从按日志(By log)选项旁边的下拉菜单中选择系统(System)。
完成后，选择OK。
如果您愿意，可以为视图命名并添加描述。再次选择确定(OK )以创建视图。
您现在将在事件查看器(Event Viewer)中看到过滤后的事件。查找围绕蓝屏错误或 PC 崩溃的事件，以查看导致问题的原因。
使用 PowerShell 查看错误日志
您还可以选择使用PowerShell在(PowerShell)Windows上提取错误日志。在开始菜单(Start Menu)中搜索powershell并启动Windows PowerShell。
将以下命令复制并粘贴到PowerShell中：
Get-EventLog -Log system | where {$_.entryType -match “Error”}
该命令将检索整个事件日志。但是，如果您只想保留 30 个条目，请使用以下命令：
Get-EventLog -LogName System -Newest 15 -EntryType 错误(Get-EventLog -LogName System -Newest 15 -EntryType Error)
这两个命令都将获取在事件查看器(Event Viewer)中被归类为错误的系统事件。
如何修复Windows 10或 11上的崩溃(Crashing)问题？
崩溃问题的修复取决于原因。使用上述方法之一确定原因后，选择相关修复程序来修复计算机上的崩溃问题：
- 重新启动：(Reboot:) 关闭(Shut)您的 PC，稍等片刻，然后再次按下电源按钮。通常(Often)，您只需要重新启动即可解决问题。
- 更新驱动程序：(Update drivers: )如果您的 BSOD 错误显示为“ Driver Overran Stack Buffer ”或“ Driver Power State Failure ”，则更新驱动程序可能会有所帮助。
- 禁用 CPU 超频：(Disable CPU Overclock: )如果您的计算机因CPU 过热而崩溃，请从(overheating CPU)BIOS中将其解锁，或使用第三方工具进行过热保护。
- 卸载防病毒软件：(Uninstall antivirus: )在某些情况下，您的防病毒软件可能是罪魁祸首。尝试卸载它以查看是否可以解决问题。
- SFC：如果Windows崩溃是因为您的 PC 中缺少系统文件，您可以在提升的命令提示符中(Command Prompt)使用系统文件检查器(use the System File Checker)( SFC ) 命令来修复它：sfc /scannow.
- Chkdsk：Chkdsk是一个内置的命令行实用程序，可检查您的硬盘驱动器是否存在文件系统错误和坏扇区。要修复由文件系统错误或坏扇区引起的崩溃，请在“开始”菜单中键入(Start Menu)cmd，右键单击“命令提示符(Command Prompt)”，然后选择“以管理员身份运行”(Run as administrator)。然后，运行以下命令：chkdsk D: /f /r /x
- 系统还原：(System Restore: )如果您的 PC 有还原点，您可以使用系统还原功能将您的 PC 还原到之前的工作状态。(restore your PC to its previous working condition using)
但是，如果您根本无法启动到Windows或崩溃发生在启动时，您需要先启动到安全模式(boot into Safe Mode)。
我应该担心崩溃(Crash)吗？
一次性崩溃不是您应该太担心的事情。新的Windows更新中的错误或有故障的驱动程序可能会导致崩溃(faulty driver can cause a crash)，但这主要是（尽管并非总是）孤立事件。但是，如果您的计算机反复崩溃，您可能需要戴上故障排除的帽子。
当您的计算机死机(your computer freezes)或崩溃时应用通用修复程序会浪费您大量的时间，而且通常在修复问题方面没有任何重大进展。本指南中讨论的工具将帮助您总结可能的原因，因此您至少可以尝试找到适当的修复方法。
How to Find Out Why My Windows 11/10 Computer Crashed
Your computer will freeze every once in a while, especially if you’re rυnning Microsoft Windows 10/11 or an older version of Windows. All cоmputer crasheѕ are recorded by your operating system, which can help you understand what nеeds to be fixed. However, thе key is to know where to look for these records.
On Windows, you’ll notice your computer screen go blue for a moment before it crashes. The infamous “blue screen of death” (BSOD) is a surefire sign that something needs to be fixed on your computer.
In some cases, though, the blue screen disappears very quickly. You won’t be able to record the error code for troubleshooting, but you can still find details about what caused the crash. That’s exactly what we discuss in this guide.
Potential Reasons Why Your Computer Crashed or Froze
- Failure or RAM or hard disk
- Overheating
- Virus or malware
- Wrong, buggy, outdated, or corrupt device drivers
- Weak or fluctuating power supply
- Occasionally, a third-party software
Now that you know the possible reasons that can cause system crashes, let’s talk about how to determine what caused the Windows 10. Only once you determine the cause will you be able to fix Windows and keep it from crashing in the future.
Look for Critical Events in the Reliability Monitor
Windows introduced the Reliability Monitor starting with Windows 7, and it has since been the quickest, most user-friendly way to find system and app crashes.
However, note that the Reliability Monitor doesn’t state explicitly what caused the crash. It’s more helpful in looking at the events that occurred before or surrounding the crash so you can try and narrow down on a potential cause.
You can open the Reliability Monitor by searching for it in the Start Menu. Type reliability in the Start Menu search bar and select View reliability history on Windows 10 or 11.
Once the Reliability Monitor is open, you’ll be able to see day-wise columns with the current date at the extreme right and the events on each of those days. You also have the option to choose a weekly view by selecting Weeks from the top-left.
Freezes and crashes are represented by an X in a red circle. They’re the critical events you’re looking for in the Reliability Monitor while trying to figure out what caused the crashing issue.
You’ll also see critical events listed at the bottom—double-click on an event to get more information about what caused it. For instance, in the following case, the event log says that Windows stopped responding because of OneDrive.
You can view the Event Viewer to check why your computer crashed as well. However, you’ll get the same information on the Event Viewer as the Reliability Monitor.
View Crash Logs in Event Viewer
You can use Event viewer to check for errors, warnings, and system messages generated right before the Windows 10 crash. Event Viewer categorizes events as follows:
- Informational: Normal events where a process was executed successfully fall under this category.
- Warning: Events under this category can potentially lead to a problem in the future, though they haven’t resulted in any errors currently.
- Error: This is the category under which you’ll find process failures and crashes.
To access Event Viewer on both Windows 10 and 11, type event viewer in the Start Menu search box and press Enter to select the Best Match.
Upon launching the Event Viewer, you’ll see a list in the left sidebar. You’ll find crash logs for a BSOD event or your PC crashing for any other reasons in the Windows Logs > System section.
You’ll now see all events listed, but if you don’t want to sift through hundreds of events, just select the Level label at the top of the first column, and it will bring all critical events at the top.
Alternatively, you can create a custom view to filter and find critical events. You can do this by selecting Create Custom View from the right sidebar on the Event Viewer. You’ll see a new window pop up.
Select the relevant duration based on when the crash event occurred from the drop-down next to the Logged option. Check the Error box in the Event level options and select System from the drop-down menu next to the By log option.
Once you’re done, select OK.
Name the view and add a description if you prefer. Select OK again to create the view.
You’ll now see the filtered events in the Event Viewer. Look for events surrounding the blue screen error or the PC crash to look at what caused the problem.
View Error Logs Using PowerShell
You also have the option to extract error logs on Windows using PowerShell. Search for powershell in the Start Menu and launch Windows PowerShell.
Copy and paste the following command into the PowerShell:
Get-EventLog -Log system | where {$_.entryType -match “Error”}
The command will retrieve the entire event log. However, if you only want to last 30 entries, use the following command:
Get-EventLog -LogName System -Newest 15 -EntryType Error
Both commands will fetch system events that were categorized as an Error in the Event Viewer.
How to Fix a Crashing Issue on Windows 10 or 11?
The fix for the crashing issue depends on the cause. Once you’ve determined the cause using one of the above-mentioned methods, choose a relevant fix to repair the crashing issue on your computer:
- Reboot: Shut down your PC, give it a minute, and press the power button again. Often, a reboot is all you need to fix an issue.
- Update drivers: If your BSOD error reads “Driver Overran Stack Buffer” or “Driver Power State Failure”, updating the drivers might help.
- Disable CPU Overclock: If your computer is crashing because of an overheating CPU, unlock it from the BIOS, or use a third-party tool for overheat protection.
- Uninstall antivirus: In some cases, your antivirus might be the culprit. Try uninstalling it to see if it fixes the issue.
- SFC: If Windows is crashing because a system file is missing from your PC, you can use the System File Checker (SFC) command in an elevated Command Prompt to fix it: sfc /scannow.
- Chkdsk: Chkdsk is a built-in command-line utility that checks your hard drive for filesystem errors and bad sectors. To fix crashes caused by filesystem errors or bad sectors, type cmd in the Start Menu, right-click on Command Prompt, and select Run as administrator. Then, run the following command: chkdsk D: /f /r /x
- System Restore: If your PC has a restore point, you can restore your PC to its previous working condition using the System Restore feature.
However, if you can’t boot into Windows at all or the crash happens right at the startup, you’ll need to boot into Safe Mode first.
Should I Be Worried About the Crash?
A one-off crash isn’t something you should be too worried about. A bug in the new Windows update or a faulty driver can cause a crash, but it’s mostly, though not always, an isolated incident. If your computer is repeatedly crashing, though, you might want to put on your troubleshooting hat.
Applying generic fixes when your computer freezes or crashes will waste plenty of your time, often without any significant progress towards fixing an issue. The tools discussed in this guide will help you boil down the possible causes, so you can at least try and find an appropriate fix.
