Home > Event Id > The Previous System Shutdown At Was Unexpected. Server 2003

The Previous System Shutdown At Was Unexpected. Server 2003

Contents

How can I retrieve that reason now? and stopped. 0 LVL 38 Overall: Level 38 Windows Server 2003 33 Message Expert Comment by:ChiefIT ID: 211374302008-03-16 "Question: I changed the server not to reboot on failure but it If no, try these troubleshooting steps: Run system in selective startup, start services one by one until you get to the culprit. Is there any third-party service running or software conflict on this server? http://chatflow.net/event-id/the-previous-system-shutdown-was-unexpected-windows-7.html

I don't think a flood of supressed COM events will reboot the computer. Maybe also with another virusscan tool than you already have. 2. Going through the event log, what are the events that happen prior to the shutdown - anything unusual, or oddly consistent immediately before it powers itself off? How do I set this? 5 42 78d Windows Storage Server 2003 helps reduce duplicates with Single Instance Storage Article by: Derek Organizations create, modify, and maintain huge amounts of data

The Previous System Shutdown At Was Unexpected. Server 2003

Paging file is set to max 4.0 GB on C drive On Events: First sign of a problem is that you see no new events for a couple of hours then you should enable no restart option on systems or servers if you want to see the error message posted on the bsod. And read this article which listed possible reasons for event 6008: http://www.chicagotech.net/troubleshooting/eventid6008.htm Below are related KBs, also check them: You may experience an abnormal shutdown on a Windows Server 2003-based computer I can leave this one open in the rack for the time being trying to find a fan now.

And read this article which listed possible reasons for event 6008: http://www.chicagotech.net/troubleshooting/eventid6008.htm Below are related KBs, also check them: You may experience an abnormal shutdown on a Windows Server 2003-based computer I am comparing BIOS settings now to try and find a cause. I am checking the server every hour or so, waiting for it to fail, with my luck it will run for 3 weeks now without issue. 0 LVL 38 Overall: Unexpected Shutdown Event Id Server 2008 Browse other questions tagged windows-server-2003 windows-event-log or ask your own question.

Creating your account only takes a few minutes. Event Id 6008 Windows Server 2008 Unexpected Shutdown Thanks. 0 Pimiento OP Taylor9004 Jan 27, 2014 at 7:09 UTC 1st Post We are currently having this happen as well. Have you installed latest drivers and firmwares from Dell? Any suggestions? ------------------------------------  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

That said I have just flashed the BIOS and still fan speed slow. Unexpected Reboot Event Id Clutching at straws, but you never know. Thanks for all the help 0 Message Expert Comment by:AJN-IT ID: 252553252009-09-03 This is a known problem in Windows 2003. 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 Ü.......

Event Id 6008 Windows Server 2008 Unexpected Shutdown

The issue started yesterday and has rebooted about 10 times yesterday and continued to do it through today. No user logged during the time betwen the reboots. The Previous System Shutdown At Was Unexpected. Server 2003 this is under control pane> system> advanced tab> startup recovery options. Event Id 6008 Windows Server 2008 R2 Unexpected Shutdown My fans are all on max-except the CPU fan - that's a loop watercooler - on max.

Richard 0 Message Author Comment by:systemssupply ID: 211372822008-03-16 I just noticed that the Help and Support service was not running (probably a result of when SP2 was loaded, maybe this his comment is here Had another unexpected shut down tonight. The box has tripple power supplies all appear to be operating fine. It will give you more info. Event Id 6008 Windows Server 2012 Unexpected Shutdown

Question is, do we still think it is hardware? As for any other issues occuring, I have been seeing printer errors in the system log but they occur hours before the error so i doubt its the issue but its Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL http://chatflow.net/event-id/the-previous-system-shutdown-was-unexpected-6008.html How can we verify wich hardware update was done last time??

The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\Ole\EventLog. 0 LVL 38 Overall: Level 38 Windows Server 2003 33 Message Expert Event Id 6008 Windows 10 You can perform a clean boot on it to narrow down the issue as http://support.microsoft.com/kb/929135. Covered by US Patent.

If Windows updates, do you schedule routine driver updates?

You can perform a clean boot on it to narrow down the issue as http://support.microsoft.com/kb/929135. Is there an equivalent for vim's \zs in sed or perl? overclocking) as I've stablized this machine quite extensively. Ask a new question Read More Shutdown Event Id Windows 7 Related Resources Event ID 6008 Need help figuring this out.

So far no issues. Join our community for more solutions or to ask questions. Why is the first book of the Silo series called Wool? navigate here Given that this server was running hot and that the fans are acting up.

Shouldn't it be about 40 celsius. 0 Message Author Comment by:systemssupply ID: 211380902008-03-16 With my home made CPU fan we are at 44c. Then I will order the new board. 0 LVL 13 Overall: Level 13 Windows Server 2003 3 Message Expert Comment by:Richard_de_groot ID: 211434902008-03-17 So far so good indeed. I think we may be onto something. They don't conflict with eachother because spybot is an executable and housecall is a full program.

You may get a better answer to your question by starting a new discussion. I say it's the hardware. I know you are running symantec antivirus. How much Celsius is 150 F ?

Everything seems to be running fine now, but I want to know why it shutdown. Other notes, the servers are not on a USP - which is not ideal but that's the setup. http://support.microsoft.com/kb/326564 When logging off 2003 server, it asks the reason. Another thing you might think about is running Hijackthis and posting your results here.

I called tech support on it and we still don't have a solution. Of course since this was an unexpected shutdown, it does not give me much useful information. We are closed today so really there is no load at all and it is still rebooting. The hardware is a HP DL 380 G5 and I did run diagnostic tool and all looked good from hardware perspective.

However, I did run boot time mem for atleast 3 cycles and no issues were reported. On the server in question they just spin at 1600 rpm constantly.