Stopping debugging session while waiting for PingReply causes BSOD - by leppie

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


17
0
Sign in
to vote
ID 691615 Comments
Status Closed Workarounds
Type Bug Repros 15
Opened 9/29/2011 4:31:13 AM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

When stopping your debugging session in Visual Studio when Ping.Send is waiting for a reply, causes the PC to get a BSOD. (PROCESS HAS LOCKED PAGES)

After setting TraceLockedPages to 1, the BSOD points to tcpip.sys as the faulty driver.

Another report: http://www.codeguru.com/forum/archive/index.php/t-509623.html
Sign in to post a comment.
Posted by SteveGG on 8/19/2014 at 10:30 AM
Just started experiencing this. I'm running Win 7 x64, targeting .NET 4.5. I am shocked this is still an issue almost 3 years later. What work-arounds are people using?
Posted by Mr SiB on 1/6/2012 at 3:14 AM
I am also experiencing this exact same problem.
Has anyone found a better work around than using .net 2.0?
Posted by leppie on 11/18/2011 at 2:23 AM
Can you provide a link where this bug can be tracked now?
Posted by Microsoft on 11/18/2011 at 2:16 AM
Thank you for your bug submission. The issue you reported appears to be on a released Windows Product. If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance. For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.
Other Support links - http://support.microsoft.com/ph/14019#tab13
Posted by JF2015 on 11/17/2011 at 1:49 AM
Hi,

I can also reproduce this issue. Minidump was uploaded.
Would be nice to hear of a solution.
Posted by leppie on 10/13/2011 at 6:13 AM
I dont understand that last response. Can you clarify what you mean?
Posted by Microsoft on 10/11/2011 at 11:34 PM
Thank you for your bug submission. The issue you reported appears to be on a released Windows Product. If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance. For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.
Other Support links - http://support.microsoft.com/ph/14019#tab13
Posted by Microsoft on 10/11/2011 at 2:43 AM
Thank you for attaching the dump file. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by schalli on 10/6/2011 at 5:51 AM
I just discovered, that .NET 2.0 is never crashing, while .NET 4.0 does give me the BSOD as described.

Some decompiling revealed, that the Ping class in .NET 4.0 is relying on the function "IcmpCreateFile" from the iphlpapi.dll, while .NET 2.0 is using the same function from the icmp.dll.

Maybe the implementation in iphlpapi.dll is broken?
Posted by schalli on 10/6/2011 at 4:25 AM
Hi,

since I am experiencing the same issue, I have just uploaded my most recent minidump.

Please let me know when this is fixed, I am working on a university research project which relies on .NET and the Ping utility.


Best regards,

Daniel
Posted by MS-Moderator08 [Feedback Moderator] on 9/30/2011 at 2:21 AM
Thank you for reporting this issue. Could you please provide a dump with the following steps:
1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.
2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".
3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.
4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.

If the Blue Screen appears again, please refer to the following steps to collect memory dump files:

1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.
2. Go to your Desktop, right-click on it and create a new folder named "Dump".
3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.
4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".
5. Please send the ZIP file to us.

You can upload your dump to the workspace:
https://sftasia.one.microsoft.com/choosetransfer.aspx?key=64b8c383-9225-4638-9247-8fe73b6f6790
Password:zDyRp0LOnmJU5

Please use "FeedbackID-691615" as the file name.

Thanks!
Posted by leppie on 9/29/2011 at 11:36 PM
Did some further testing.

1. Can replicate on different hardware (both OS was Win7 x64).
2. Only happens with .NET 4 or above using VS2010. Cannot replicate in VS2008 targeting .NET 2.
Posted by MS-Moderator01 on 9/29/2011 at 4:42 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)