blocks|key|4017754|text|当计算机蓝屏时，它很可能会创建内存的转储。当系统崩溃时，内存中的内容被写入Pagefile。它使用Pagefile作为数据占位符，因为尝试在磁盘上创建新文件太危险了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4017755|当机器再次启动时，它将检测转储，并将数据移动到一个单独的转储文件中(通常是C:\Windows\Memory.dmp或C:\Windows\Minidumps*.dmp)。|4017756|安装WinDbg并打开.dmp文件。点击！分析链接。现在，它将向您展示杀死Windows的线程中的堆栈，并向您展示所涉及的文件。通常，WinDbg将直接指向特定的驱动程序文件。您可以找到分步指令这里.|offset|length|4017757|我可以推荐你阅读马克·鲁西诺维奇的博客和书籍。你可以从微软下载WinDbg。|4017758|因此，用户的问题是：“你能把你的转储文件电邮给我吗？”|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/1321103/171846|1|http://blogs.technet.com/markrussinovich|2|http://www.microsoft.com/whdc/DevTools/Debugging/^0|0|0|2P|2|0|0|8|B|1|Q|B|2|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$F|Z|G|10|1|11]]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@$F|13|G|14|1|15]|$F|16|G|17|1|18]]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]|U|$5|N|O|P|A|$Q|V]]]]

When the computer bluescreens it'll most likely create a dump of the memory. The content from memory is written to the Pagefile as the system is going down. It uses the Pagefile as placeholder for the data since it is too dangerous to try to create a new file on disk.

When the machine starts up again it'll detect the dump, and move the data into a separate dump file (typically C:\Windows\Memory.dmp or C:\Windows\Minidumps*.dmp).

Install WinDbg and open the .dmp file. Click the !Analyze link. Now it'll show you the stack from the thread that killed Windows, and show you which files that were involved. Often WinDbg will point you directly at a specific driver file. You can find step-by-step instructions <a href="https://stackoverflow.com/a/1321103/171846">here</a>.

I can recommend reading <a href="http://blogs.technet.com/markrussinovich" rel="nofollow noreferrer">Mark Russinovich's blog</a> and books.
You can <a href="http://www.microsoft.com/whdc/DevTools/Debugging/" rel="nofollow noreferrer">download WinDbg from Microsoft</a>.

So the question to the user is: "Can you e-mail me your dump file?"

blocks|key|278677|text|Mark+(+SysInternals著名的)有一个很好的博客条目，他描述了如何使用调试工具来跟踪模块名，甚至是蓝屏幕出现的堆栈帧(即函数调用)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|278678|它有插图，写得很好，并且在我开始学习如何调试蓝屏消息时，它帮助我摆脱困境。|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.technet.com/markrussinovich/archive/2008/12/30/3174871.aspx^0|T|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@$A|N|B|O|1|P]]|C|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]]]

Mark Russinovich (of SysInternals fame) has an excellent <a href="http://blogs.technet.com/markrussinovich/archive/2008/12/30/3174871.aspx" rel="noreferrer">blog entry</a> where he describes how one can use the debugging tools to track down the module name and even the stack frame (i.e. function call) during which the blue screen occurred.

It's illustrated, well written, and has helped me get my feet under me when I started learning how to debug Blue Screen messages.

blocks|key|278454|text|左上角的错误代码。通过谷歌搜索，你可以把它缩小到是硬件问题还是软件问题。从那里开始(谷歌的结果)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

The error code in the top left. By googling that, you can often narrow it down to whether it's a hardware or software issue. Proceed from there (the Google results).

blocks|key|278470|text|如果蓝屏仍然打开:顶部附近的实际消息(即IRQL_DRIVER_LESS_OR_EQUAL)和底部的错误代码(0+x.)使用崩溃的模块(即nvdishi4.dll)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|278471|这里有一些常见的方法，但在我的示例中，这是一个由nVidia图形驱动程序引起的蓝屏。如果您分析了几个蓝屏，就会有一些常见的消息、代码和模块经常弹出，因此经过一段时间之后，您应该能够通过经验更容易地缩小问题范围。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

If they have the Bluescreen still open: The Actual Message near the top (i.e. IRQL_DRIVER_LESS_OR_EQUAL) and the Error Code at the Bottom (0x.......) with the module that crashed (i.e. nvdisp4.dll).

There are some common approaches here, but in my example, it's a Bluescreen caused by the nVidia Graphics Driver. If you analyze a few bluescreens, there are some common messages, codes and modules that regularly pop up, so after some time you should be able to narrow down issues more easily simply through experience.

blocks|key|4017674|text|这些是我从1开始寻找的东西。)蓝屏的电脑，通常是我的互联网连接。2.)对像我这样有经验的用户来说，蓝屏的闪存速度太快了。所以我在很大程度上依赖问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4017675|首先，你最近有没有换过任何硬件？|ordered-list-item|4017676|你安装了什么新软件吗？|4017677|重要的是，你能通过安全模式进入吗？|4017678|毫无疑问，如果上面三个答案是肯定的，那么撤销上面的一个和两个中的任何一个都是肯定的。如果其中一个和两个都是肯定的，那么先执行一个步骤，然后在执行另一个之前进行测试。|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|M|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|N|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]]|K|$]]

These are the things I look for since 1.) the PC that bluescreens, is normally my internet connection. 2.) bluescreens flash by too fast for even an experienced user like myself. So I rely heavily on questions.

<ol>
<li>First, have you changed any hardware lately?</li>
<li>Have you installed any new software?</li>
<li>Importantly, can you get in via safe mode?</li>
</ol>

It goes without saying that if the answer to three above is yes then undo which ever of one and two above is yes. If both one and two are yes, handle the undo stepwise by doing one then testing before you do the other.

blocks|key|4017782|text|试着检查事件查看器，如果您没有看到任何显而易见的东西(不会让我感到惊讶)，试着尝试一下MS调试工具：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4017783|http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx|offset|length|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1P|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@$D|N|E|O|1|P]]|A|$]]]|F|$G|$5|H|I|J|A|$K|C]]]]

Try checking the event viewer, if you don't see anything obvious there (wouldn't surprise me) try giving the MS debugging tools a try: 

<a href="http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx" rel="nofollow noreferrer">http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx</a>

blocks|key|4017795|text|尝试运行内存测试-间歇的BSOD通常是错误的RAM。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Try running a memory test - intermittent BSODs are often faulty RAM

Sometimes I have to answer support calls responding to PC crashes with blue screens. How can I effectively narrow down the problem giving the information on that screen? What are the most important questions I have to ask the user?

Edit: By "diagnose" I mean, how can I interpret the information on the blue screen in order to narrow down the cause of the problem?

How to diagnose a Windows blue screen?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

有时，我必须回答支持电话回应电脑崩溃的蓝色屏幕。如何有效地缩小在屏幕上提供信息的问题？我要问用户的最重要的问题是什么？编辑:我的意思是“诊断”，我如何解释蓝色屏幕上的信息，以缩小问题的原因？

问如何诊断Windows蓝屏？
EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何诊断Windows蓝屏？EN

回答 7

Server Fault用户

Server Fault用户

Server Fault用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何诊断Windows蓝屏？
EN