自Windows 95(Windows 95)推出以来，可怕的BSOD或蓝屏(Blue Screen)死机(Death)就一直存在。这是一个可怕的错误屏幕，弹出的警告很少或没有警告，让您知道计算机上的事情已经偏离了方向，以至于您已经走到了路的尽头。
通常在简单的重启后问题就会消失，但间歇性或频繁的 BSOD(BSODs)可能表明从软件中的严重错误到实际计算机硬件的问题。然而，蓝屏(BSODs)死机没什么好惊慌的。您的计算机不会爆炸，您只需要分析BSOD错误的内容，然后排除潜在的解决方案。
究竟什么是Windows 10上的蓝屏死机(BSOD)？
您可能已经发现Microsoft本身并未正式将此错误称为Blue Screen Of Death。这是用户社区多年来给这个问题起的名字。此错误的正确术语是“停止错误”或“异常错误”。这两种都是致命系统错误的类型。更常见的是系统崩溃。
当计算机上运行的应用程序发生致命错误时，它通常会显示错误消息然后关闭。但是，如果导致如此严重错误的错误或问题发生在操作系统本身上怎么办？那是蓝屏(BSOD)，需要重启电脑。
如果不是因为此类停止错误，您将面临严重故障或数据丢失的风险。因此，蓝屏死机(BSODs)是保护您的计算机免受损坏的一种方法。
首先，拍照！
由于当BSOD(BSOD)发生时您的整个操作系统基本上已经停止，因此最好使用智能手机快速拍摄屏幕照片。正如您将看到的，联网的智能手机确实是您在排除BSOD(BSODs)时最好的朋友，因为在许多情况下，您可能无法在受影响的计算机上访问互联网。
承认这一事实，微软(Microsoft)实际上已经改变了 Windows 10 蓝屏的外观。您将在一分钟内了解我们的意思，但最好先看一下Windows 10 BSOD 的整体结构。
常见的蓝屏错误
有很多潜在的BSOD错误。但是，有些比其他更常见。因此，作为普通Windows(Windows)用户，您至少应该熟悉一下最常见的停止代码：
- PAGE_FAULT_IN_NON_PAGED_AREA – Windows无法在RAM的受保护部分（不是页面文件的一部分）中找到关键数据。这可能是RAM故障、Windows文件损坏或恶意应用程序写入不应出现的内存位置。
- IRQL_NOT_LESS_OR_EQUAL – 这通常是驱动程序问题。回滚(Roll)最近安装的驱动程序，重新安装当前驱动程序或安装最新驱动程序。
- NTFS_FILE_SYSTEM或FAT_FILE_SYSTEM –扫描(Scan)您的硬盘驱动器是否存在错误、驱动器可能存在的问题或驱动器上的关键数据是否损坏。
- OUT_OF_MEMORY – 测试(OUT_OF_MEMORY – Test)您的RAM，这可能表示失败。或者，它可能归结为内存管理中的故障。
- BAD_POOL_CALLER –(BAD_POOL_CALLER – Something)在没有正确权限的情况下访问了内存。很可能是一个坏司机。
- UNABLE_TO_LOAD_DEVICE_DRIVER –(UNABLE_TO_LOAD_DEVICE_DRIVER – One)您系统上的驱动程序之一坏了。安装最新版本或将系统回滚到以前的驱动程序。
- KMODE_EXCEPTION_NOT_HANDLED – 行为不端的软件强制关闭Windows。卸载(Uninstall)最新软件或将当前软件更新到最新版本。如果此错误显示 .sys 文件是罪魁祸首，您将需要运行System File Checker。
这少数常见的BSOD错误也很好地说明了BSOD错误的外观以及每个问题和解决方案的种类。最后，蓝屏死机(BSOD)实际上只有四个主要原因：
- 硬件不好
- 损坏的 Windows 安装
- 坏司机
- 流氓、有缺陷的软件应用程序
真正的诀窍是弄清楚哪个是哪个！
罕见但特定的 BSOD
常见的BSOD(BSODs)显然在网络上有大量的修复和建议。但是，有一些相对罕见的问题可能难以修复。好消息是，我们已经费尽心思为更令人震惊的指南编写指南。
系统(System)内存错误很常见，主要是因为对RAM硬件中的错误几乎没有容忍度，而且Windows本身有一种严肃的方法来处理软件以不应该的方式弄乱内存。然而，内存管理蓝屏(Memory Management BSOD)并不经常出现。查看我们的如何修复 Windows 停止代码内存管理 BSOD(How To Fix Windows Stop Code Memory Management BSOD)指南，以解决此问题的一个相当罕见的版本。
另一个相当罕见的错误是 Unexpected Store Exception Error。尽管有此错误的名称，但实际原因通常是硬件故障。您可以通过查看How to Fix Unexpected Store Exception Error In Windows 10来了解所有相关信息（以及如何修复它） 。
最后一个罕见但仍然致命的系统服务异常(System Service Exception)停止代码很棘手，因为它有很多潜在的原因。如何修复 Windows 10 中的系统服务异常停止代码(How to Fix System Service Exception Stop Code in Windows 10)将帮助您找到真正的罪魁祸首。
没人想看到的最后一个BSOD是 Critical (BSOD)Process Died错误。这个是相当不具体的，但是如果您查看如何修复停止代码关键进程死亡 BSOD(How to Fix a Stop Code Critical Process Died BSOD)，您会运气好一点。
蓝屏内存转储
有时您需要寻求专家的帮助，以确定发生BSOD(BSOD)时到底出了什么问题。幸运(Luckily)的是，在大多数情况下，当停止错误发生时， Windows会创建您内存中的内容的转储。这些通常保存为“.DMP”文件。默认情况下，您会在Windows文件夹中找到它们。
如果您设法重新启动到Windows或以其他方式访问系统驱动器，则值得将这些转储文件保存到USB闪存驱动器之类的东西中，然后保留它们以防问题再次发生。Microsoft、硬件供应商和软件开发人员可以使用这些转储来查看出现问题时发生的情况。
Windows 10 中的基本 BSOD 修复
这是很多关于我们都希望完全避免的事情的信息。特别是因为它有时会觉得BSOD(BSODs)已成为过去。毕竟这些天很少发生。尽管如此(Nonetheless)，如果您正盯着一个，那么值得考虑基本的、一般的故障排除过程来让您的计算机恢复运行：
- 用您的手机拍摄BSOD的照片，以防您需要提交或查找有关它的信息。
- 谷歌停止错误代码或(Google)BSOD中提到的任何特定文件。
- 如果您的搜索带来了特定的修复，请先关注这些修复。
- 如果错误与计算机的一般区域（例如RAM）有关，则首先将故障排除集中在此处。
- 如果您的计算机最近发生了更改，请撤消这些更改。
- (Make)使用Windows恢复选项(Windows)，例如系统还原(system restore)或系统重置(system reset)。在最坏的情况下，您可能必须完全格式化您的系统驱动器。
- 从您的计算机上拔下所有不必要的设备，看看它是否解决了问题。
- 更新与BSOD(BSOD)中的错误代码相关的任何硬件设备的软件（例如您的GPU）。
- 如果在软件方面似乎没有任何问题并且您正在运行桌面系统，请考虑检查计算机内的所有内容是否正确连接和就位。
- 如果您正在超频(overclocking)或有可能导致不稳定的BIOS设置，请将您的BIOS重置为默认设置以进行故障排除。
当一切都失败时，不要害怕寻求专业人士的帮助或求助于技术论坛。在技术支持上花一点钱通常比花费数小时的宝贵时间试图找出导致看似随机的BSOD的原因要好得多。
Blue Screen of Death Troubleshooting Guide for Windows 10
The dreaded BSOD or Blue Screen оf Death has been around since the introduction of Windows 95. It’s a dreaded еrror screen that poрs up with little or no warning, letting you know that things have gone so sideways on your computer that you’ve reached the end of the road.
Often the problem goes away for good after a simple reboot, but intermittent or frequent BSODs can indicate anything from a serious bug in software to problems with the actual computer hardware. BSODs are nothing to panic about however. Your computer won’t explode, you just need to analyze the content of the BSOD error and then troubleshoot potential solutions.
What Is a BSOD on Windows 10 Exactly?
You’ve probably figured out that Microsoft itself doesn’t officially call this error a Blue Screen Of Death. That’s the name the community of users has given the issue over the years. The correct term for this error is a “stop error” or “exception error”. Both of these are types of fatal system errors. More commonly known as a system crash.
When a fatal error happens to an application running on the computer, it usually puts up an error message and then closes. However, what if the bug or issue causing such a serious error happens to the operating system itself? That’s a BSOD, and the computer needs to be restarted.
If it weren’t for stop errors such as these, you’d risk serious malfunction or data loss. BSODs are therefore a way to protect your computer from damage.
First, Take a Photo!
Since your entire operating system has essentially stopped when a BSOD happens, it’s a good idea to snap a quick picture of the screen with your smartphone. As you’ll see, an internet-connected smartphone is really your best friend when troubleshooting BSODs, since you’re likely to have no internet access on the affected computer itself in many cases.
Microsoft has actually changed the way Windows 10 blue screens look in acknowledgement of this fact. You’ll see what we mean by that in a minute, but it’s best to look at the anatomy of a Windows 10 BSOD as a whole first.
Common BSOD Errors
There are lots of potential BSOD errors. However, some are much more common than others. So it’s worth having at least a passing familiarity with the most common stop codes you’ll see as a normal Windows user:
- PAGE_FAULT_IN_NON_PAGED_AREA – Windows can’t find critical data in the protected part of RAM that’s not part of the page file. This could be faulty RAM, Windows file corruption or a rogue application writing to memory locations it should not be.
- IRQL_NOT_LESS_OR_EQUAL – This is usually a driver problem. Roll back recently installed drivers, reinstall current ones or install the latest ones.
- NTFS_FILE_SYSTEM or FAT_FILE_SYSTEM – Scan your hard drives for errors, likely problems with the drive or damage to critical data on the drive.
- OUT_OF_MEMORY – Test your RAM, this might indicate failure. Alternatively it could be down to a glitch in memory management.
- BAD_POOL_CALLER – Something accessed memory without the right permissions. Most likely a bad driver.
- UNABLE_TO_LOAD_DEVICE_DRIVER – One of the drivers on your system is bad. Install the latest version or roll your system back to the previous driver.
- KMODE_EXCEPTION_NOT_HANDLED – Badly behaved software forced a shutdown of Windows. Uninstall recent software or update current software to the latest version. If this error shows a .sys file as being the culprit, you’ll want to run the System File Checker.
This handful of common BSOD errors also serve as a good example of what BSOD errors look like and the sorts of problems and solutions each one entails. In the end, there are really only four major causes for a BSOD:
- Bad hardware
- Damaged Windows installations
- Bad drivers
- Rogue, buggy software applications
The real trick is figuring out which is which!
Rare Yet Specific BSODs
Common BSODs obviously have plenty of fixes and advice available out on the web. However, there are a few relatively rare ones that may prove tricky to fix. The good news is that we’ve already gone to the trouble of writing guides for the more egregious ones.
System memory errors are pretty common, mainly because there’s little tolerance for errors in RAM hardware and Windows itself has a no-nonsense approach to software messing with memory in ways it’s not supposed to. The Memory Management BSOD, however, doesn’t crop up that often. Check out our How To Fix Windows Stop Code Memory Management BSOD guide to tackle a fairly rare version of this issue.
Another fairly rare error is the Unexpected Store Exception Error. Despite the name of this error, the actual cause is usually hardware failure. You can learn all about it (and how to fix it) by checking out How to Fix Unexpected Store Exception Error In Windows 10.
The last rare but still fatal System Service Exception stop code is tricky because it has so many potential causes. How to Fix System Service Exception Stop Code in Windows 10 will help you track down the real culprit.
The last BSOD no one wants to see is the Critical Process Died error. This one is fairly nonspecific, but if you check out How to Fix a Stop Code Critical Process Died BSOD you’ll figure it out with a bit of luck.
BSOD Memory Dumps
Sometimes you’ll need to call in some expert help to figure out exactly what went wrong when a BSOD happens. Luckily, in most cases Windows creates a dump of what’s in your memory when the stop error happens. These are usually saved as “.DMP” files. By default you’ll find them in your Windows folder.
If you manage to boot back into Windows or access the system drive in some other way, it’s worth saving these dump files to something like a USB flash drive and then keeping them in case the problem happens again. Microsoft, hardware vendors and software developers can use these dumps as a way to see what was happening when things went wrong.
Basic BSOD Fixes in Windows 10
That’s a lot of information about something we all hope to avoid entirely. Especially since it can sometimes feel that BSODs are a thing of the past. They happen so rarely these days after all. Nonetheless, if you’re staring at one it’s worth considering the basic, general troubleshooting process to get your computer back up and running:
- Take a photo of the BSOD with your phone in case you need to submit it or look up information about it.
- Google the stop error code or any specific files that are mentioned in the BSOD.
- If your search brings up specific fixes, follow those first.
- If the error relates to a general area of your computer (such as RAM) then focus your troubleshooting there first.
- If something has recently changed on your computer, undo those changes.
- Make use of Windows recovery options, such as system restore or system reset. In a worst-case scenario you might have to completely format your system drive.
- Unplug all unnecessary devices from your computer to see if it resolved the issue.
- Update the software of any hardware devices that are related to the error code in the BSOD (e.g. your GPU).
- If nothing seems to be wrong in terms of software and you’re running a desktop system, think about checking that everything inside the computer is properly connected and seated.
- If you’re overclocking or otherwise have BIOS settings that could cause instability, reset your BIOS to default settings for troubleshooting purposes.
When all else fails, don’t be afraid to call in the help of a professional or turn to technical forums for help. It’s often better to spend a little money on tech support than spend hours and hours of your valuable time trying to figure out what’s causing a seemingly random BSOD.
