Unsolved
This post is more than 5 years old
1 Rookie
•
39 Posts
0
113303
November 29th, 2012 16:00
Event Id 6008 Windows Server 2003 Server Reboot
Windows 2003 x86 SP2 installed on Dell Poweredge 6850. Server rebooted the other day with event id 6008;
Event Type: Error
Event Source: EventLog
Event Category: None
Event ID: 6008
Date: 29/11/2012
Time: 12:15:48 PM
User: N/A
Computer: Server1
Description:
The previous system shutdown at 12:11:59 PM on 29/11/2012 was unexpected.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: dc 07 0b 00 04 00 1d 00 Ü.......
0008: 0c 00 0b 00 3b 00 2e 00 ....;...
0010: dc 07 0b 00 04 00 1d 00 Ü.......
0018: 01 00 0b 00 3b 00 2e 00 ....;...
Why did the server reboot? What can I make out of this event log?
No Events found!
Daniel My
12 Elder
•
6.2K Posts
0
November 29th, 2012 17:00
Hello callumd
The error doesn't tell us any more than what is stated. There was an unexpected shutdown. The operating system shut down without someone choosing the shutdown or restart option, or with a program initiating a restart. I would check the hardware logs to see if there are any errors around the time that the system shut down. If there are no hardware errors then the operating system likely locked up. If that is the case then I would recommend reviewing the system event log to see what was happening when the lockup occurred. Reviewing mini dump files can be very useful for troubleshooting lockups/crashes. If you don't have a mini dump file then I would recommend enabling mini dumps.
http://support.microsoft.com/kb/307973
Thanks
Daniel My
12 Elder
•
6.2K Posts
0
November 29th, 2012 17:00
If there was nothing in the hardware logs then it was not likely a hardware issue. Do you know if power was lost to the server around the time of the shutdown? You will typically get voltages errors in the event of a power loss, but it is possible to not receive an error.
If there was not a power loss then it is likely an OS problem. You should go into the OS and review the system even log and application log. Look through the log during the time frame of the unexpected shutdown. The time stamp for the unexpected shutdown is going to be when the server comes back on, not when it was shut down. Scroll back from that error to the point before everything started up during boot. Find the time when the server actually shut down and find out what happened right before that. Check what was going on at that time in the application log as well.
If you have a mini dump file then use the KB article I linked to review the dump file. The debugger will tell you what file it suspects caused the crash. If you don't have minidumps enabled, and you don't see anything in the logs to point to the problem then I would enable minidumps and wait to see if the issue occurs again. If it does then review the minidump file.
Thanks
CallumD
1 Rookie
•
39 Posts
0
November 29th, 2012 17:00
checked hardware logs, alert logs & command logs, didnt find anything that can lead me to the reason.
What are my options?
CallumD
1 Rookie
•
39 Posts
0
November 29th, 2012 17:00
Thanks Daniel, how can I check hardware logs?