Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / November 2005

Tip: Looking for answers? Try searching our database.

2005 RTM Blue Screen of Death BSOD when saving

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Wayne Brantley - 01 Nov 2005 02:55 GMT
_sometimes_ when I save a file in the IDE, I get a blue screen of death.
It _seems_ to happen most often when saving web user controls.

this also happened in the RC build.   The blue screen says:

"a thread tried to release a resource it did not own"

MS Docs say it is a driver problem, but it ONLY happens in VS.NET 2005 (not
2003 or any other software I have) and only happens when I save a file.
Also, their have not been any recent driver changes.

Any help or should I call PSS as this makes it hard to develop.
"Gary Chang[MSFT]" - 01 Nov 2005 09:26 GMT
Hi Wayne,

I noticed you posted this problem in our Bug Report web site a few days
before, currently this issue has already been logged into our internal
database, and the corresponding VS2005 product team will work on it, it may
need some time to research and work around it.

>Any help or should I call PSS as this makes it hard to develop.

Since the PSS will not support an RC product, I suggest you may test our
VS2005 RTM product first, if that problem still exists, then you can
contact PSS for the further support. This may need you submit a support
incident in Microsoft PSS (Product Support Service). As a MSDN subscriber,
you have two free support incidents.

By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.

For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-(800)936-5800 or by
choosing one of the options listed at
http://support.microsoft.com/common/international.aspx?rdpath=gp;en-us;offer
prophone

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary Chang[MSFT]" - 01 Nov 2005 09:45 GMT
Hi Wayne,

I noticed you posted this problem in our Bug Report web site a few days
before, currently this issue has already been logged into our internal
database, and the corresponding VS2005 product team will work on it, it may
need some time to research and work around it.

>Any help or should I call PSS as this makes it hard to develop.

If you have a big concern on this problem, it is better to contact PSS for
the urgent support. This may need you submit a support incident in
Microsoft PSS (Product Support Service). As a MSDN subscriber, you have two
free support incidents.

By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.

For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-(800)936-5800 or by
choosing one of the options listed at
http://support.microsoft.com/common/international.aspx?rdpath=gp;en-us;offer
prophone

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Wayne Brantley - 01 Nov 2005 16:50 GMT
Yes, I did post it there, that was for RC1 - tried to modify it the other
day and could not for some reason.
Wanted to say it seemed to happen 'more' in user controls.

Also, tried to post it as a bug for RTM, but RTM is not a choice on the drop
down list (yet).

If they cannot reproduce it, I am guessing they will contact me and I can
check on the status of it through that bug website?

> Hi Wayne,
>
[quoted text clipped - 41 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
"Gary Chang[MSFT]" - 02 Nov 2005 04:24 GMT
Hi

>If they cannot reproduce it, I am guessing they will contact
>me and I can check on the status of it through that bug website?

yes, currently it appears the product team cannot repro this error, I think
you may upload a self-contain sample project to that correspnding bug
website just as they suggested:)

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Cowboy (Gregory A. Beamer) - 03 Nov 2005 16:09 GMT
There are two possibilities here:

1. Visual Studio has a bug.
2. Visual Studio exposed a bug in someone else's driver or in Windows.

While, for you, it is only in Visual Studio, it is possible that others
experience it in some other software. Most BSODs are driver problems and a
great majority of them deal with display drivers.

My first plan of action would be making sure all drivers for all hardware
are up to date. The manufacturer's site is the best place to start that
query. I would then contact PSS after you do that (if the problem persists).

The BSOD should have created a dump file which should have the offending
piece of software (driver, etc.).

Signature

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***********************************************
Think Outside the Box!
***********************************************

> _sometimes_ when I save a file in the IDE, I get a blue screen of death.
> It _seems_ to happen most often when saving web user controls.
[quoted text clipped - 8 lines]
>
> Any help or should I call PSS as this makes it hard to develop.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.