当 PC 脱离底座时，WPF/WCF 应用程序会导致蓝屏
我正在尝试解决蓝屏问题。
我们有一个 .Net 4.0 WPF PRISM 应用程序。该应用程序的一个特别之处是它托管一个 WCF 服务，我们用它来与客户端（Thinkpad PC、Windows XP）进行通信。
重现问题的步骤如下：
- 打开应用程序
- 关闭应用程序
- 断开 PC 的连接
蓝屏消息类似于“检查驱动器上是否有空间”。
上述步骤每次都“有效”，已在多台 PC 上进行了测试。任何人都知道这可能是什么原因造成的？
如果我从 Visual Studio 运行该应用程序，则不会收到此错误。我仅在运行已安装的应用程序时收到错误消息。
I am trying to solve a blue screen problem.
We have a .Net 4.0 WPF PRISM application. One special thing about this application is that it hosts a WCF Service, which we use to communicate with the client (Thinkpad PC, Windows XP).
The steps to recreate the problem are:
- Open the application
- Close the application
- Undock the PC
The blue screen message is something like "check that there is space on your drive".
The above steps "work" every time, have tested on several PC's. Anyone have any idea what could be causing this?
If I run the app from Visual Studio I do not get this error. I only get the error when I run the installed application.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
调查蓝屏源的典型步骤：
打开内存转储设置。在 Win XP 中，位于系统属性 - 高级 - 启动和恢复 - 设置中。至少选择内核内存转储。默认情况下，内存转储保存在%SystemRoot%\MEMORY.DMP。重新启动计算机。
再现蓝屏。等待内存转储完全写入。重新启动计算机。
压缩 %SystemRoot%\MEMORY.DMP 文件并转到此页面：http:// /www.osronline.com/page.cfm?name=analyze。单击浏览并选择压缩的内存转储文件。单击上传转储。
粉碎转储分析结果显示在 WEB 浏览器中。最重要的信息是导致蓝屏的驱动程序的名称。
有了WinDbg，就可以在WinDbg 中打开memory.dmp（打开故障转储）并输入！analyze -v（而不是3,4）。
如果这是第三方驱动程序，我认为您唯一能做的就是将故障转储分析（可能还有转储文件本身）发布给驱动程序供应商。
Typical steps to investigate a blue screen source:
Open memory dump settings. In Win XP this is in System Properties - Advanced - Startup and Recovery - Settings. Select at least Kernel memory dump. By default, memory dump is saved at %SystemRoot%\MEMORY.DMP. Reboot computer.
Reproduce blue screen. Wait while memory dump is completely written. Reboot computer.
Zip %SystemRoot%\MEMORY.DMP file and go to this page: http://www.osronline.com/page.cfm?name=analyze. Click Browse and select zipped memory dump file. Click Upload Dump.
Result of crush dump analysis are displayed in the WEB browser. The most important information is the name of the driver which caused blue screen.
Having WinDbg, it is possible to open memory.dmp in WinDbg (open crash dump) and type !analyze -v (instead of 3,4).
If this is third-party driver, I think the only thing you can do is to post crash dump analysis (and possibly dump file itself) to the driver vendor.