DownloadFileAsync 期间蓝屏 0x0000003B？
我在使用 C#/.NET 开发的应用程序时遇到了问题。我无法追踪这个问题，因为它会导致我的系统崩溃并出现 BSOD。这是小型转储：
060310-27066-01.dmp 03.06.2010 19:47:39 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000c0000005 fffff8000306d4d0 fffff8800b107640 0000000000000000 ntoskrnl.exe ntoskrnl.exe+ 70600 NT 内核与系统 Microsoft® Windows® 操作系统 Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\060310-27066-01.dmp 4 15 7600
它与 DownloadFileAsync 无关。 System.Net 程序集类中与 HTTP 下载相关的其他方法也会导致我的系统崩溃。我真的希望有人能帮助我解决这个问题。
仅供参考：下载文件的其他应用程序（浏览器等）非常有用。
如果您需要更多信息，请随时询问！
谢谢！
// 更新 06.06.2010 - 02:58: 仅供参考：几天前我运行 memtest86+ 来检查我的内存模块。安装所有四个 2GB 模块时出现一些错误。我删除了其中的3个，并一一检查了所有4个模块，没有任何错误。仅当我的应用程序在调试器中运行并从网络下载某些内容时，才会发生 BSOD。
// 更新 04.06.2010 - 18'53： 在测试了几件事后，我发现每当我在 Visual Studio 2010 调试器中运行自己的应用程序并开始下载时，就会出现 BSOD。在没有附加调试器的情况下运行应用程序不会导致 BSOD。
我认为 BSOD 在某种程度上与调试器有关。
I've run into a problem with an application I'm developing in C#/.NET. A problem I can't trace down because it causes my system to crash with a BSOD. Here's the minidump:
060310-27066-01.dmp 03.06.2010 19:47:39 SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000c0000005 fffff8000306d4d0 fffff8800b107640 0000000000000000 ntoskrnl.exe ntoskrnl.exe+70600 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16539 (win7_gdr.100226-1909) x64 C:\Windows\Minidump\060310-27066-01.dmp 4 15 7600
It's not related specifically to DownloadFileAsync. Other methods of the System.Net assembly classes related to HTTP download also make my system crash. I really hope someone can help me with this.
Just for info: other apps (browsers etc.) that download files work like a charm.
If you need further information don't hesitate to ask!
Thanks!
// Update 06.06.2010 - 02:58: Just for info: I ran memtest86+ to check my memory modules a few days ago. There were some errors when all four 2GB modules were installed. I removed 3 of them and checked all 4 modules again one by one without any errors. The BSOD occurs solely when my app is run in the debugger and downloads something from the web.
// Update 04.06.2010 - 18'53: I figured out after testing several things that the BSOD occurs whenever I run my own application inside the Visual Studio 2010 debugger and start a download. Running the app with no debugger attached to it isn't causing the BSOD.
I suppose that the BSOD is somehow related to the debugger.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
更新您的网卡驱动程序。
Update your network card drivers.
您的网络驱动程序可能有问题。尝试重新安装网络驱动程序。
There's probably something wrong with your network drivers. Try reinstalling the network drivers.
检查是否有适用于您的主板 BIOS 和芯片组的更新。调试会执行许多与核心操作系统线程调度程序相同的任务切换逻辑，以保存进程状态/CPU 状态，但时序与线程调度程序有很大不同。
检查制造商的网站，不要仅仅依赖 Windows 更新。
查看您的显卡和其他硬件是否也有更新也没什么坏处。
Check to see if there are any updates available for your mobo BIOS and chipset. Debugging exercises much of the same task-switching logic as the core OS thread scheduler to save the state of the process / state of the CPU, but the timing is very different from the thread scheduler.
Check the manufacturer's web site, don't rely solely on Windows Update.
It wouldn't hurt to see if there are updates for your graphics card and other hardware, too.
不幸的是，没有从小型转储中收集到任何具体原因，至少我看不到太多（可能其他人会更清楚）。
如果您查看 Windows 文件夹，您应该会找到一个 memory.dmp 文件。这会更大，但希望包含一些可用于识别问题可能根源的信息。
您可以同时尝试一些事情
运行 Memtest86+ 等工具来检查系统 问题
检查 Windows 事件日志中是否有与硬盘相关的任何错误消息，也许您正在看到 HDD 丢失的第一个迹象，并且问题就出现在此处。您还可以运行 chkdsk。
Unfortuantely no specific cause can be gleened from the mini dump, at least there is not much I could see (possibly others would know better).
If you look in your windows folder you should find a memory.dmp file. That will be larger, but hopefully contain some piece of information that can be used to idntify the possible source of the problem.
Some things you can try in the meantime
Run a tool like Memtest86+ to check the system memory for any possible problems.
Check the windows eventlog for any error messages relating to the harddisk, maybe you are seeing the first signs of HDD loss and the problem is presenting here. You can also run a chkdsk.
打开管理控制台，然后执行“sfc /scannow”。这可能会修复 Windows 安装中任何损坏的文件。
有关详细信息，请参阅 http://support.microsoft.com/kb/310747。
Open an admin console, then execute 'sfc /scannow'. This will possibly fix any corrupted files in your Windows install.
See http://support.microsoft.com/kb/310747 for more details.
好吧，只是为了结束这个问题......现在，在我问这个问题两年后，我不再遇到这个问题了。显然，问题已经解决了，因为我同时重新安装了操作系统几次。不幸的是，我一直不明白为什么会发生这个 BSOD。
Alright, just to close this question... Now, two years after I had asked this question, I'm not experiencing this anymore. The problem has dissolved, apparently, because I've reinstalled my operating system several times in the meantime. Unfortunately, I've never figured out why this BSOD occurred.