Windows Vista Beta | WinVistaBeta.com - Message | Can I trace VS2005 startup?

December 03, 2008  
Subject: Can I trace VS2005 startup?
Group: microsoft.public.vstudio.general
Date: 7/24/2008 8:11:16 AM
From: "Steve Barnett" [Email Address Protection]

I have a problem with VS 2005. After a spyware scan or a virus scan (or any
disk intensive activity), if I start VS 2005, I get the splash screen and
then PC reboots. It's a bit irritating.

On reboot, Windows reports a blue screen error and blames a "device error".
Strange thing is, this ONLY happens when starting VS 2005, so I'm
unconvinced about the cause. To be fair, the error reporting used to blame
my anti-virus program, so I replaced it with a different one. It now blames
the device error.

What I was wondering was, is it possible to trace the start up of VS 2005 so
I can see what it was doing before it crashed? If I can get a few traces
together, maybe I can spot something going on when the PC reboots and maybe
I can do something to fix the problem.

Thanks
Steve



Back
Subject: Re: Can I trace VS2005 startup?
Group: microsoft.public.vstudio.general
Date: 7/24/2008 9:59:02 AM
From: "Igor Solodovnikov" [Email Address Protection]

Execute it with /log parameter.
http://msdn.microsoft.com/en-us/library/ms241272.aspx

On Thu, 24 Jul 2008 18:11:16 +0300, Steve Barnett <noname@nodomain.com>
wrote:

> I have a problem with VS 2005. After a spyware scan or a virus scan (or
> any
> disk intensive activity), if I start VS 2005, I get the splash screen and
> then PC reboots. It's a bit irritating.
>
> On reboot, Windows reports a blue screen error and blames a "device
> error".
> Strange thing is, this ONLY happens when starting VS 2005, so I'm
> unconvinced about the cause. To be fair, the error reporting used to
> blame
> my anti-virus program, so I replaced it with a different one. It now
> blames
> the device error.
>
> What I was wondering was, is it possible to trace the start up of VS
> 2005 so
> I can see what it was doing before it crashed? If I can get a few traces
> together, maybe I can spot something going on when the PC reboots and
> maybe
> I can do something to fix the problem.
>
> Thanks
> Steve
>
>


Back
Subject: Re: Can I trace VS2005 startup?
Group: microsoft.public.vstudio.general
Date: 7/24/2008 11:01:06 AM
From: "John Saunders" [Email Address Protection]

Maybe you have a device error. Did you look in the event log to see if your
disk has been reporting errors?

Visual Studio is purely user-mode code. It is completely impossible for it
to cause a BSOD. On the other hand, some piece of kernel code could be
watching what VS is doing and in the process, could be crashing your system.

Without naming the name of the a company that has been very helpful in
resolving my BSOD issue, I have to say that I know of one case of a popular
piece of kernel-mode software that is being notified when each DLL is being
loaded on the system. Sometimes, when it does this, it screws up and the
system crashes. The problem appears related to Visual Studio simply because
Visual Studio is composed of a large number of DLL files.

--
John Saunders | MVP - Connected System Developer

"Steve Barnett" <noname@nodomain.com> wrote in message
news:#QniI#Z7IHA.4536@TK2MSFTNGP04.phx.gbl...
> I have a problem with VS 2005. After a spyware scan or a virus scan (or
> any disk intensive activity), if I start VS 2005, I get the splash screen
> and then PC reboots. It's a bit irritating.
>
> On reboot, Windows reports a blue screen error and blames a "device
> error". Strange thing is, this ONLY happens when starting VS 2005, so I'm
> unconvinced about the cause. To be fair, the error reporting used to blame
> my anti-virus program, so I replaced it with a different one. It now
> blames the device error.
>
> What I was wondering was, is it possible to trace the start up of VS 2005
> so I can see what it was doing before it crashed? If I can get a few
> traces together, maybe I can spot something going on when the PC reboots
> and maybe I can do something to fix the problem.
>
> Thanks
> Steve
>

Back