旧的 .Net 应用程序崩溃了。此事件日志信息是什么意思？
在我们的系统之一中 24/7 运行的 .NET 应用程序突然崩溃，没有记录任何错误。
我们能够检索到的唯一错误信息位于 Windows 事件日志中，其中包含以下代码：
faulting module msvcr80.dll,
version 8.0.50727.3053,
stamp 4889d619,
debug? 0,
fault address 0x000144dc.
以前有人遇到过这样的问题吗？有谁知道 MS 库中的位置是什么或者在哪里可以找到此类信息？我可以从哪里开始尝试解决这个问题？
编辑：应用程序最近没有更改，每个错误都应该被捕获和记录，所以行为看起来很奇怪。我真正想知道的是哪个函数位于给定的偏移量处，这样也许我们可以找出崩溃发生的位置。
A .NET application running in one of our systems 24/7 suddenly crashed without logging any errors.
The only error information we were able to retrieve is in the windows events log, with this codes:
faulting module msvcr80.dll,
version 8.0.50727.3053,
stamp 4889d619,
debug? 0,
fault address 0x000144dc.
Has anyone experienced an issue like this before? Does anybody have an idea of what the location in the ms library is about or where to find such information? Where can I start in trying to resolve this issue?
Edit: the application wasn't changed recently and every error should be trapped and logged, so the behavior seems really strange. What I really wanted to know is what function is located at the given offset, so that maybe we can figure out where the crash happened.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
那是 C++ 运行时库（我认为是 2005 年开始的）。
它可以被标记为许多事情的原因，从恶意软件攻击到 C++ 代码失去对数据库的访问权限，再到实际的程序错误。一般是在不处理异常的情况下。
但这里的要点是，如果一切都运行正常并且突然被标记，那么我会查看用于导致崩溃的系统上发生了什么变化。
只有让这种情况再次发生，您才能找出真正导致崩溃的代码。
编辑
检查最近安装到计算机上的任何软件的任何更新。不仅仅是你的，还有微软、防病毒软件等。有可能其中之一就是罪魁祸首。我认识一个人，他一直非常愉快地使用 Office 2000，直到最近的 AVG 更新覆盖了 C 运行时 dll，他无法再打印任何内容或接收电子邮件。
我知道这并不理想，但您可能必须将其传递给 Microsoft，因为它隐藏在他们的 DLL 中。
That's the C++ runtime library (from 2005 I think).
It can be flagged as being the cause for many things, from malware attacks to C++ code losing access to databases to actual program bugs. Generally when exceptions are not handled.
The main point here though is that if all has been running okay and it has suddenly been flagged then I would look to see what changed on the system on which it is used to cause the crash.
Only by making it occur again will you be able to track down what code actually caused the crash.
edit
Check for any updates put onto the machine recently for any of the software. Not just yours, but Microsoft, antivirus, etc. It is possible thta one of these is the culprit. I know someone who had been using Office 2000 quite happily until a recent update for AVG overwrote the C runtime dll and he could no longer print anything or receive emails.
I know that its not ideal but you will probably have to pass this onto Microsoft as it is buried within their DLL.
乍一看，它似乎与防病毒或更新相关，但它实际上可能只是侥幸，或者是硬件故障的迹象。我将设置进程监视器并详细记录应用程序在再次发生时正在执行的操作。如果这是一次性事件，我不会太担心。
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
At first glance it seems like it's anti-virus or update related, but it really could just be just a fluke, or a sign of failing hardware. I would setup process monitor and log in detail what the application's doing if it happens again. If this is a onetime occurrence I wouldn't worry about it much.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
如果它24/7并且突然崩溃；我会询问最近对系统进行的更改/更新。
文件
msvcr80.dll是一个 Visual Studio 2005 VC++ 运行时库；对于挖掘确切原因没有多大帮助。此讨论可能帮助。
If its 24/7 and suddenly crashed; I would ask about changes/updates in the system that were made in the recent past.
The file
msvcr80.dllis a Visual Studio 2005 VC++ Runtime library; doesn't help much in digging the exact cause.This discussion might help.