Bluescreen 0x0000003B during DownloadFileAsync?

Question

Hello again,

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.

Answer 1

Update your network card drivers.

Answer 2

There's probably something wrong with your network drivers. Try reinstalling the network drivers.

Answer 3

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.

Answer 4

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

1. Run a tool like Memtest86+ to check the system memory for any possible problems.

2. 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.

Answer 5

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.