System shut down unexpectedly

[Allen Drake]

This is the first time any Win7 system of mine has just shut down
unexpectedly. Can anyone decipher this event log report?

A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service.


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="49152">7011</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2011-11-24T11:29:47.531200100Z" />
<EventRecordID>82067</EventRecordID>
<Correlation />
<Execution ProcessID="796" ThreadID="1244" />
<Channel>System</Channel>
<Computer>Al'sDesktop</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">30000</Data>
<Data Name="param2">ShellHWDetection</Data>
</EventData>
</Event>

I was simply reading something online after having system up for a
few hours doing some research.


I have searched for this problem but nothing seems to fit.

Thanks for any clues.

Al.

 

[Ed Cryer]

This is the first time any Win7 system of mine has just shut down
unexpectedly. Can anyone decipher this event log report?

A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service.


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="49152">7011</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2011-11-24T11:29:47.531200100Z" />
<EventRecordID>82067</EventRecordID>
<Correlation />
<Execution ProcessID="796" ThreadID="1244" />
<Channel>System</Channel>
<Computer>Al'sDesktop</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">30000</Data>
<Data Name="param2">ShellHWDetection</Data>
</EventData>
</Event>

I was simply reading something online after having system up for a
few hours doing some research.


I have searched for this problem but nothing seems to fit.

Thanks for any clues.

Al.

There are a few instances of this through Google, but, as you say,
nothing definitive.

You'll have to do some detective work. Here's a guide.
1. Have you tried it again? How long does it stay up?
2. Windows logs in Event Viewer (Admin Tools); especially application &
system ones.
3. Disk scans, memory tests.
4. And then, of course, full AV scan.

Let us know.

Ed

 

[Paul]

This is the first time any Win7 system of mine has just shut down
unexpectedly. Can anyone decipher this event log report?

A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service.


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="49152">7011</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2011-11-24T11:29:47.531200100Z" />
<EventRecordID>82067</EventRecordID>
<Correlation />
<Execution ProcessID="796" ThreadID="1244" />
<Channel>System</Channel>
<Computer>Al'sDesktop</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">30000</Data>
<Data Name="param2">ShellHWDetection</Data>
</EventData>
</Event>

I was simply reading something online after having system up for a
few hours doing some research.


I have searched for this problem but nothing seems to fit.

Thanks for any clues.

Al.

Another possibility, is this Event, is a side effect of
something else happening, which didn't get logged.

Maybe, something else is dying in process land, and
preventing ShellHWDetection from completing it's
check, and that caused the event to be logged. But then,
soon afterward, whatever is really happening, causes
the shutdown ?

In the past, Windows would shutdown, if some critical
security service was compromised. But then, there'd probably
be some sort of log entry if that happened.

In terms of hardware, there is THERMTRIP, but it takes
no prisoners, and there is no time for any log entries of
any sort to be made. It's just "lights out". I doubt that is it.
This sounds like more of a software problem.

Paul

 

[Peter Foldes]

This is the first time any Win7 system of mine has just shut down
unexpectedly. Can anyone decipher this event log report?

Did you check for overheating especially the Power Supply

--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/protect

 

[Robert Sudbury]

When you say `Shutdown' do you mean to say that Windows performed a shutdown
process, gracefully exiting all programs, saving and logging your profile
off, then powering down the system?

Shutdown is a specific process of events occuring in a specific order to
achieve a non-powered state.

Or do you mean to say that your system spontaneously powered off, going from
full operation to a hard off instantly, like a light bulb switch or a pulled
electrical plug?

Or did something else entirely different occur?

This is the first time any Win7 system of mine has just shut down
unexpectedly. Can anyone decipher this event log report?

A timeout (30000 milliseconds) was reached while waiting for a
transaction response from the ShellHWDetection service.


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service
Control Manager" />
<EventID Qualifiers="49152">7011</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2011-11-24T11:29:47.531200100Z" />
<EventRecordID>82067</EventRecordID>
<Correlation />
<Execution ProcessID="796" ThreadID="1244" />
<Channel>System</Channel>
<Computer>Al'sDesktop</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">30000</Data>
<Data Name="param2">ShellHWDetection</Data>
</EventData>
</Event>

I was simply reading something online after having system up for a
few hours doing some research.


I have searched for this problem but nothing seems to fit.

Thanks for any clues.

Al.

__________ Information from ESET NOD32 Antivirus, version of virus
signature database 6657 (20111124) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

--
[Robert]


__________ Information from ESET NOD32 Antivirus, version of virus signature database 6657 (20111124) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[Allen Drake]

There are a few instances of this through Google, but, as you say,
nothing definitive.

You'll have to do some detective work. Here's a guide.
1. Have you tried it again? How long does it stay up?

I am not sure if I understand this question. I started the system as
soon as it shut down and it said it was continuing with system restore
or something like that. The system was up for several hours before it
shut down. It has not happened again. I guess I should not have
panicked as I did and waited to see if it reoccurred.

2. Windows logs in Event Viewer (Admin Tools); especially application &
system ones.

Nothing that has anything near that time stamp or actually mean
anything significant.

3. Disk scans, memory tests.

No bad reports.

4. And then, of course, full AV scan.

Let us know.

Ed

I guess it was a fluke and hopefully goes away.

Al.

 

[Allen Drake]

Another possibility, is this Event, is a side effect of
something else happening, which didn't get logged.

Maybe, something else is dying in process land, and
preventing ShellHWDetection from completing it's
check, and that caused the event to be logged. But then,
soon afterward, whatever is really happening, causes
the shutdown ?

In the past, Windows would shutdown, if some critical
security service was compromised. But then, there'd probably
be some sort of log entry if that happened.

In terms of hardware, there is THERMTRIP, but it takes
no prisoners, and there is no time for any log entries of
any sort to be made. It's just "lights out". I doubt that is it.
This sounds like more of a software problem.

Paul

I guess I may never know unless things get really bad. I don't use
this system for anything intensive. Mostly reading and posting here
and some email. Other systems are reserved for CAD and heavy
applications and never any problems so far.

Thanks.

Al.

 

[Allen Drake]

Did you check for overheating especially the Power Supply

I did not but it is a very old power supply. I was planning on
ordering a few back up units so I guess that is what I will be doing
this morning. One of my next projects will be the customizing of the
wiring harnesses for shorting them as indicated in another post.

Thanks.

Al.

 

[Allen Drake]

When you say `Shutdown' do you mean to say that Windows performed a shutdown
process, gracefully exiting all programs, saving and logging your profile
off, then powering down the system?

Shutdown is a specific process of events occuring in a specific order to
achieve a non-powered state.

Or do you mean to say that your system spontaneously powered off, going from
full operation to a hard off instantly, like a light bulb switch or a pulled
electrical plug?

Or did something else entirely different occur?

I could say it crashed which would be a better term. It wasn't
instantaneous as the screen went black. I looked at the case and the
inside lights were still on for several seconds then it was off. As I
pressed the start button it came with a message that it was continuing
with system restore or something to that effect. I didn't have much
time to read it but everything seemed normal after that. I remember
thinking about "System Restore" application but was puzzled because it
was nothing like that process other then that one message.

 

[G. Morgan]

I was simply reading something online after having system up for a
few hours doing some research.


I have searched for this problem but nothing seems to fit.

Thanks for any clues.

See if this applies:
http://beecherbowers.com/2009/04/30/eventid-7011-timeout-waiting-for-shellhwdetection-service/

"I tried stopping services, but the problem persisted. Seeing the
original ShellHWDetection error, I started investigating the hardware
and found several forums with users mentioning virtualCD drivers causing
problems. I knew I didn’t have virtualCD drivers loaded, but I did
discover one piece of hardware that was new. With the latest version of
Dameware, a mirror driver had been installed. The mirror driver emulates
a second monitor (with a mirror of the first monitor’s output) and pipes
it over the network. Tracking back over the eventlogs, I was able to
determine it was installed about the time the 7011 errors began.
Removing the mirror driver instantly fixed the problem. "


Is it possible you have automatic updates on and you missed a shutdown
notice?

Also, check if 'ShellHWDetection' is set to 'auto' in the services
console.

%windir%\system32\services.msc

--

"I don't like to discriminate against terrorists based on nationality.
If you declare war on the United States and you want to kill us,
We're going to kill you first, period."

October 19, 2011 - Ali Soufan (Colbert Report)

 

[Allen Drake]

See if this applies:
http://beecherbowers.com/2009/04/30/eventid-7011-timeout-waiting-for-shellhwdetection-service/

"I tried stopping services, but the problem persisted. Seeing the
original ShellHWDetection error, I started investigating the hardware
and found several forums with users mentioning virtualCD drivers causing
problems. I knew I didn’t have virtualCD drivers loaded, but I did
discover one piece of hardware that was new. With the latest version of
Dameware, a mirror driver had been installed. The mirror driver emulates
a second monitor (with a mirror of the first monitor’s output) and pipes
it over the network. Tracking back over the eventlogs, I was able to
determine it was installed about the time the 7011 errors began.
Removing the mirror driver instantly fixed the problem. "


Is it possible you have automatic updates on and you missed a shutdown
notice?

Also, check if 'ShellHWDetection' is set to 'auto' in the services
console.

%windir%\system32\services.msc

Thanks Mr Morgan for your response. While the posts do seem similar
with the error report I have only experienced this occurrence one
time. I have not added or installed anything and have configured Auto
Updates for every day at 3:am so as far as I can tell at the time of
my problem it would have been several hours past that time. I am
pretty sure I did not miss any notification of pending shutdown.

ShellHWDetection is set to auto.

I, of coarse will be waiting for this to happen again and will try to
pay closer attention to everything going on. This is a rather old
system so anything would be expected at this point.

Thanks again.

Al.

 

[G. Morgan]

Thanks Mr Morgan for your response. While the posts do seem similar
with the error report I have only experienced this occurrence one
time. I have not added or installed anything and have configured Auto
Updates for every day at 3:am so as far as I can tell at the time of
my problem it would have been several hours past that time. I am
pretty sure I did not miss any notification of pending shutdown.

ShellHWDetection is set to auto.

I, of coarse will be waiting for this to happen again and will try to
pay closer attention to everything going on. This is a rather old
system so anything would be expected at this point.

Let's see if it happens again and maybe you'll notice a pattern. My
next guess would be an overheat condition causing the CPU safety
shutdown to kick-in. Have you taken the cover off yet and checked for
dirty fans (especially the CPU fan)? It may just need a good blast of
compressed air to unclog the heatsink and fans. Use a program like SIW,
http://www.gtopala.com/download/siw_portable.zip to view the system
temps. its under "hardware >> sensors".

--

"I don't like to discriminate against terrorists based on nationality.
If you declare war on the United States and you want to kill us,
We're going to kill you first, period."

October 19, 2011 - Ali Soufan (Colbert Report)

 

[Allen Drake]

Let's see if it happens again and maybe you'll notice a pattern. My
next guess would be an overheat condition causing the CPU safety
shutdown to kick-in. Have you taken the cover off yet and checked for
dirty fans (especially the CPU fan)? It may just need a good blast of
compressed air to unclog the heatsink and fans. Use a program like SIW,
http://www.gtopala.com/download/siw_portable.zip to view the system
temps. its under "hardware >> sensors".

I just took a look and as I usually find a very clean system. I am
always fanned up and have a well vented side panel. No dust anywhere
to be found and nothing using the canned air. Everything is cool to
the touch except the Nvidia GeForce 260 witch is slightly warm(50C).
The CPU sensors report a constant 40C. All wires neatly tucked and
plenty of room for air flow. What is surprising is the SSD is 35C
while the HDD is 34C.

I don't know what else to check so I guess I am fine for now.

Thanks for the link and fine application that I swill be using
continually.

Al.

 

[G. Morgan]

I don't know what else to check so I guess I am fine for now.

Thanks for the link and fine application that I swill be using
continually.

Okay, just post back here if it happens again. Good luck!

--

"I don't like to discriminate against terrorists based on nationality.
If you declare war on the United States and you want to kill us,
We're going to kill you first, period."

October 19, 2011 - Ali Soufan (Colbert Report)

 

[blank]

I did not but it is a very old power supply. I was planning on
ordering a few back up units so I guess that is what I will be doing
this morning. One of my next projects will be the customizing of the
wiring harnesses for shorting them as indicated in another post.

Thanks.

Al.

***shorting them***?! Did you mean to say that?

 

[Allen Drake]

***shorting them***?! Did you mean to say that?

Yes.

 

[Paul]

Yes.

You means "shortening" don't you ?

http://www.cooksinfo.com/edible.nsf/images/shortening/$file/shortening.jpg

(and shortening some wires...)

http://forums.bit-tech.net/showthread.php?t=148887

Paul

 

[Allen Drake]

You means "shortening" don't you ?

http://www.cooksinfo.com/edible.nsf/images/shortening/$file/shortening.jpg

(and shortening some wires...)

http://forums.bit-tech.net/showthread.php?t=148887

Paul

Ya, I'm from New England so I want to make them shotta.

 

[blank]

'Shorting' means short circuiting, means bridging the output leads together,
destroying them for most power supplies (those that do not have overload
protection)! It certainly does mean disabling them, either temporarily or
permanently (and sometimes very dangerously!)

 

[Allen Drake]

'Shorting' means short circuiting, means bridging the output leads together,
destroying them for most power supplies (those that do not have overload
protection)! It certainly does mean disabling them, either temporarily or
permanently (and sometimes very dangerously!)

ya, I know. My bad. I meant to have it say "shorten".