没有不可怕的BSOD （蓝屏(BSOD)死机）(Blue Screen)错误(Death)。尽管如此，“关键结构损坏”必须是我们所知道的听起来最可怕的错误之一。
不要恐慌！虽然这个致命错误可能表明存在严重问题，但这并不是说您的计算机会突然起火。深呼吸，并通过以下各种故障排除选项进行工作。
什么是致命错误 (BSOD)？
如果这是您第一次与可怕的蓝屏(Blue Screen)死机(Death)（官方称为“致命错误”）纠缠不清，那么它值得一个简短的解释。这些是Windows无法纠正的错误，如果放任不管，将导致数据损坏和其他严重的系统损坏或不稳定。
因此，一方面，蓝屏死机(BSOD)是一件好事，因为您的计算机正试图帮助您主动保护系统。另一方面，这意味着有些事情是错误的。这个问题可能微不足道或难以解决，但确实需要注意。
此特定BSOD的许多修复与其他致命错误的修复重叠。因此，绝对值得查看我们的通用BSOD 故障排除指南(BSOD troubleshooting guide)。
是什么导致关键结构损坏 BSOD(Structure Corruption BSOD)？
目前尚不完全清楚导致此错误的原因。但是，它肯定与某种硬件故障有关，或者不太严重，与驱动程序问题有关。在任何一种情况下，都会对触发致命错误的Windows 10 内核(kernel)的结构进行恶意更改。
这是一种特定的影响，潜在的原因范围很广。不过，我们应该通过以下基本步骤找到一种方法来缩小范围。
1. 记下最近的变化
虽然完全有可能由于后台硬件出错而发生致命错误，但它更有可能是由您的系统最近的更改引起的。
因此，值得列出您知道的最近更改，并从这些更改开始您的故障排除之旅。通过回滚它们或使用它们来缩小问题的可能根源。需要注意的事项包括：
- 新(New)硬件或新硬件驱动程序。
- 新的应用程序安装。
- 最近的 Windows 更新。
相关性并不意味着因果关系，但紧随其中一种类型的变化出现蓝屏错误就足以值得一看。
2.启动进入安全模式
如果您想确定驱动程序或其他启动应用程序是否导致此错误，它可以帮助将Windows 10启动到安全模式(Mode)。在安全模式下(Mode)，仅加载一组通用驱动程序，并且我们大多数人在一段时间后建立的自定义启动程序都不会加载到内存中。
如果您在安全模式下仍然遇到(Safe Mode)关键结构损坏(Critical Structure Corruption)错误，则更有可能是您的问题背后有硬件原因。如果您不知道如何启动到安全模式(Safe Mode)，请查看如何以安全模式重新启动 Windows。
3.执行干净启动
安全模式将(Mode)Windows剥离到最基本的功能，以确保您获得稳定的故障排除环境。但是，有一种不同的启动模式假定Windows本身不是问题。相反，干净启动会使Windows单独运行，并禁用所有第三方启动应用程序和其他自定义项。这是确定BSOD是由Windows本身的问题还是由第三方应用程序引起的好方法。
执行干净启动比安全模式(Mode)稍微复杂一些。因此，如果您想亲自尝试，请查看在 Windows 7/8/10 中执行干净启动以获取详细说明。
4. 拔下 USB 设备
在对此类错误进行故障排除时，从方程中删除尽可能多的变量总是一个好主意。因此，请拔下您并非绝对需要的所有USB设备。(USB)
通常这意味着除了键盘和鼠标之外的所有东西。如果BSOD停止，请一一添加设备，直到它再次发生。这应该提供有关哪些设备可能负责的线索。
5.卸载行为不端的(Misbehaving)应用程序
似乎有某个应用程序子集已知会导致关键结构损坏错误。他们并不为每个人都这样做，而且他们可能大部分时间都工作得很好。
哪些应用？我们已经看到有关应用程序的轶事报告，例如酒精 120(Alcohol 120) % 和守护程序工具(Daemon Tools)导致此BSOD。因此，如果您安装了这些应用程序或具有类似系统访问或功能级别的应用程序，请尝试卸载它们。
6.罪魁祸首(Common Culprit)：显示驱动程序
根据我们在互联网上看到的这种BSOD的各种案例，似乎有故障的显示驱动程序通常是原因。这意味着一种可能的解决方法是卸载当前的显示驱动程序并重新安装最新的驱动程序。
当我们说“卸载”时，我们真的是认真的。显示(Display)驱动程序因未正确从系统中删除而臭名昭著，这实际上是它们一开始就引起问题的原因之一。这就是您应该使用DDU（显示驱动程序卸载程序(Display Driver Uninstaller)）的原因。最好的办法是在安全模式下卸载驱动程序，然后将新驱动程序作为新软件安装。
7.撤销超频
对于 PC 上发生的任何致命错误，我们建议使用此步骤。如果您的任何组件（例如GPU、CPU 或 RAM(GPU, CPU, or RAM)）的运行超出其额定规格，请先将它们切换回库存设置，然后再进行任何其他故障排除。
8. 硬件测试
硬件(Hardware)故障几乎可以成为任何BSOD的根源，关键结构损坏(Critical Structure Corruption)也不例外。因此，值得运行一些硬件诊断程序以确保它不是故障组件。
首先(Start)在每个驱动器上运行Windows磁盘检查器。如果有坏扇区或SMART报告系统指示未决故障，您会通过这种方式找到答案。
虽然RAM可能不是问题，但不时运行Windows 内存诊断程序是个好主意。
9.检查系统文件
Windows中的系统文件检查器(System File Checker)( SFC )是最好的通用故障排除步骤之一，只要Windows本身看起来很不稳定，您就可以采取。它所做的是交叉检查所有系统文件，以确保它们没有损坏或不正确。如果发现损坏的文件，SFC将用新副本替换它。
要使用 SFC，您只需：
- 右键单击开始按钮(Start Button)
- 选择Windows Powershell（管理员）(Windows Powershell (Admin))
- 键入 sfc /scannow 并按Enter
如果该过程完成且没有错误，那么您就知道它不是损坏的系统文件。
严重失败？
我们希望在尝试这些故障排除技巧后，您的关键结构错误已经消失。但是，如果它回来了，或者您根本找不到它发生的原因，那么总是有核选项。
前往 3 种擦除和重新安装 Windows 10 的方法(Head over to 3 Ways to Wipe & Reinstall Windows 10)，了解如何为自己重新开始。
9 Fixes for Critical Structure Corruption BSOD Error in Windows 10
There is no such thing as a BSOD (Βlue Screen of Death) error that isn’t scary. Still, “critical structure corruption” has to be one of the most scary-sounding errors we know of.
Don’t panic! While this fatal error can indicate a serious problem, it’s not as if your computer is going to suddenly go up in flames. Take a deep breath and work through the various troubleshooting options below.
What Is a Fatal Error (BSOD)?
If this is your first tangle with the dreaded Blue Screen of Death (officially a “fatal error”) then it deserves a brief explanation. These are errors that Windows can’t correct and, if left alone, will lead to data corruption and other serious system damage or instability.
So, on the one hand, a BSOD is a good thing because your computer is trying to help you be proactive in protecting the system. On the other hand, it means that something is wrong. That problem can be trivial or difficult to fix, but it does need attention.
Many of the fixes for this particular BSOD overlap with those for other fatal errors. So it’s definitely worth checking out our general BSOD troubleshooting guide.
What Causes the Critical Structure Corruption BSOD?
It’s not entirely clear what causes this error. However, it’s certainly either related to hardware failure of some sort or, less seriously, a problem with a driver. In either case, rogue changes are being made to the structure of the Windows 10 kernel which triggers the fatal error.
That’s a specific effect with a vague and wide range of potential causes. Still, we should find a way to narrow it down with the basic steps below.
1. Make a Note of Recent Changes
While it’s entirely possible that fatal errors can happen because of hardware going wrong in the background, it’s more likely it’s being caused by a recent change in your system.
So it’s worth making a list of recent changes that you’re aware of and starting your troubleshooting journey with those changes. Either by rolling them back or using them as a way to narrow down the likely origin of the issue. Things to look out for include:
- New hardware or new hardware drivers.
- New applications installations.
- Recent Windows updates.
Correlation does not mean causation, but a blue screen error closely following one of these types of changes is enough to warrant a look.
2. Boot Into Safe Mode
If you want to figure out whether a driver or other startup application is responsible for this error, it can help to boot Windows 10 into Safe Mode. In Safe Mode only a generic set of drivers is loaded and none of the custom startup crud that most of us have built up after a while loads into memory.
If you still get the Critical Structure Corruption error despite being in Safe Mode, it’s more likely that there’s a hardware cause behind your woes. If you don’t know how to boot into Safe Mode check out How to Restart Windows in Safe Mode.
3. Perform a Clean Boot
Safe Mode strips Windows down to the barest essentials, to make sure you get a stable environment for troubleshooting. However, there’s a different boot mode that assumes Windows itself isn’t the issue. Instead, a clean boot leaves Windows alone and disables all third-party startup apps and other customizations. This is a good way to figure out if the BSOD is being caused by something in Windows itself or by a third-party app.
Performing a clean boot is slightly more complicated than Safe Mode. So if you want to try it for yourself, check out Perform a Clean Boot in Windows 7/8/10 for detailed instructions.
4. Unplug USB Devices
When troubleshooting errors such as these, it’s always a good idea to remove as many variables as possible from the equation. So unplug every USB device you don’t absolutely need.
Usually that means everything except for your keyboard and mouse. If the BSOD stops, add devices back one by one until it happens again. This should provide a clue as to which devices might be responsible.
5. Uninstall Misbehaving Applications
There seem to be a certain subset of applications that are known to cause the critical structure corruption error. They don’t do this for everyone and they probably work just fine most of the time.
Which applications? We’ve seen anecdotal reports of applications such as Alcohol 120% and Daemon Tools causing this BSOD. So if you have these applications installed or ones that have a similar level of system access or functionality, try uninstalling them.
6. The Common Culprit: Display Drivers
Based on the various cases we’ve seen with this BSOD on the internet, it seems that faulty display drivers are often the cause. Which means that one potential fix is to uninstall your current display driver and reinstall the latest one.
When we say “uninstall” we really mean it though. Display drivers are notorious for not properly removing themselves from your system, which is actually one of the reasons they cause problems to begin with. This is why you should use DDU (Display Driver Uninstaller). It’s best thing to do is to uninstall the driver in safe mode and then install your new driver as new software.
7. Undo Overclocking
This is a step we recommend for just about any fatal error that happens on a PC. If any of your components such as the GPU, CPU, or RAM are running beyond their rated specifications, switch them back to stock settings first before doing any other troubleshooting.
8. Hardware Testing
Hardware failure can be a source for almost any BSOD, and Critical Structure Corruption is no different. So it’s worth running a few hardware diagnostics to make sure it’s not a failing component.
Start by running the Windows disk checker on each of your drives. If there are bad sectors or the SMART reporting system indicates a pending failure, you’ll find out this way.
While it’s probably not a problem with RAM, it’s a good idea to run the Windows Memory Diagnostic from time to time anyway.
9. Check System Files
The System File Checker (SFC) in Windows is one of the best general-purpose troubleshooting steps you can take whenever it seems that Windows itself is wonky. What it does is cross-checks all of your system files to make sure they aren’t corrupt or incorrect. If a broken file is found, SFC will replace it with a fresh copy.
To use SFC, all you need to do is:
- Right-click on the Start Button
- Select Windows Powershell (Admin)
- Type sfc /scannow and press Enter
If the process completes with no errors, then you know it wasn’t a corrupt system file.
Critical Fail?
We hope that after trying these troubleshooting tips your critical structure error has disappeared. However, if it comes back or you simply can’t find the reason it’s happening, there’s always the nuclear option.
Head over to 3 Ways to Wipe & Reinstall Windows 10 and learn out how to make a fresh start for yourself.
