Can I trace VS2005 startup?   

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

date: Thu, 24 Jul 2008 16:11:16 +0100   author:   Steve Barnett

Re: Can I trace VS2005 startup?   

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

date: Thu, 24 Jul 2008 19:59:02 +0300   author:   Igor Solodovnikov

Re: Can I trace VS2005 startup?   

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"  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
>

date: Thu, 24 Jul 2008 14:01:06 -0400   author:   John Saunders

Re: Can I trace VS2005 startup?   

I've checked out the hard disk as best I can and it appears to be fine - it 
passed the tests I've run. If it were failing, I would have expected crashes 
when I started other apps or when I did my spyware/virus scans since they're 
rather disk intensive. Fact is, only VS reboots the system.

Until recently, I also had VS 2003 installed and that didn't have a problem. 
I would have thought it was as likely to crash as VS 2003.

I was wondering whether one of the scans is corrupting a file or leaving it 
open or in a strange state and VS isn't handling it properly, which is why I 
wanted to see if a trace would highlight something. I'm quite prepared to 
accept that VS is suffering the consequences of another apps actions, but I 
need a way to track down what that 'other app' might be.

I'll try the log parameter as suggested by Igor.

Thanks
Steve



"John Saunders"  wrote in message 
news:epG2lcb7IHA.1192@TK2MSFTNGP05.phx.gbl...
> 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"  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
>>

date: Fri, 25 Jul 2008 08:31:02 +0100   author:   Steve Barnett