Thanks for that. I guess it was the APC monitor applciation that might’ve caused this as we did swap the UPS around. So far no issues. But your answer did help.

Well, it didn’t turn out like we had hoped. Had another unexpected shut down tonight. Looks like we’ll have to keep digging as well.

Event Type: Error Event Source: EventLog Event Category: None Event ID: 6008 Date: 18/08/2013 Time: 10:10:15 AM User: N/A Computer: XXXXXX Description: The previous system shutdown at 8:14:13 AM on 18/08/2013 was unexpected.

This is an issue with a program that is forcing the system to shut down. This could be as simple as using a remote tool, like logmein, to reboot the system.

Thank you for the reply! It turned out for us the previous server manager did not have dual power supplies in the server. When the single power supply failed the server shutdown with not much evidence if the cause. When we opened the cabinet and checked the server hardware and noticed there was only one power supply we knew we were on the right track. Now we have a dual power supply set up and no more shutdowns.

I’m starting to get this unexpected shutdown again. Though I’ve enabled the settings to store the complete membory dump and also to automatically restart after the system shutsdown, none of the above is actually performed.

We are currently having this happen as well. We examined the Security Audit in the Event Viewer on the server that was shutting down unexpectedly. It appears that we are having a lot of logon and logoff entries shortly before the unexpected shutdown.

We’ve received the below error log occasionally on our servers. Mostly and only on windows server 2003 SP2 Std Edition. Googling the event ID mainly points out to heat issue or some sort of memory failure but this server is on a virtualised environment (VmWare esxi 4.1) along with its companion which doesn’t have this issue.

For more information, see Help and Support Center at Microsoft Support. Data: 0000: 000807dd 00120000 000e0008 022d000d 0010: 000807dd 00110006 000e0016 022d000d

We are going to go without Spiceworks for a week or so to see how it goes. We are a small organization and do not rely on Spicworks for day to day functions.

We are suspecting that the scanning done by Spiceworks is causing the unexpected shutdown due to “overloading” of the server. Our server is running Server 2003 R2 Standard.

Since turning off Spiceworks, it seemed that we didn’t quite have this trouble and I’ve had a close watch for 2 months now and all seems working. It’s worth keeping an eye on your hardware too like have you tried running a memory test?