Discussion Locked

Event ID 6008

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My server crashed overnight. The last event was 6008, an unexpected shutdown occurred. As usual Microsoft Technet wasn't very helpful. All I could find there was SP4 fixed this problem. I'm running SP6a.If anyone has any suggestions about what may have caused this please let me hear from you.
rturner@powertechnology.com

5 replies

by jason.barnett

Hi,

Event ID 6008 can be expected whenever NT4 stops unexpectedly for whatever reason from having the power reset to any Blue Screen of Death type crash. So unfortunately this Event ID does not provide any clues for a successful diagnosis.

Look at events leading up to the ID 6008 and also check to see if any other machines crashed at the same time (power problems). You'll probably find that it was a random blue screen, but keep checking the event log every morning for a while in case itis happening every night and is caused by say back-up software or anti-virus scans / updates.

Best Wishes,

JB.

by rturner

Thanks, but I was hoping that someone had a more definitive solution. I really appreciate you for answering.

by jason.barnett

I'm not sure that you are going to find a definitive solution to an unexpected / unexplained shutdown.

A definition of 6008 follows:

Dirty Shutdown Event ID: 6008
Event Log Service records a dirty shutdown event whenever the operating systemis shut down via a mechanism other than a clean shutdown. The most common cause is when the system is power-cycled, i.e., NT is stopped by powering off the system. The event is recorded upon the subsequent system reboot. While Windows NT Server is running, the system periodically writes a time stamp to the registry, which always overwrites the "last alive" time stamp from the previous interval. When the "last alive" time stamp is written, it's also flushed to disk. A normal clean shutdown is also flagged in the registry. If the clean shutdown flag isn't found on disk when an SP4 system reboots, a dirty shutdown event is recorded. The description part of the event contains the "last alive" time stamp. The "last alive" time stamp is written to the registry at a default interval of 5 minutes to HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability\LastAliveStamp. Adding the registry DWORD value TimeStampInterval can change the interval. This value is in units of minutes. Setting it to zero prevents any "last alive" time stamp logging, only the boot and normal shutdown stamps will be written in that case.

This discussion is closed to new replies.