Event Id 6008 Windows Server 2008 R2 Unexpected Shutdown
Anyways I am sharing below useful info. Is it a security vulnerability if the addresses of university students are exposed? UPDATE: Here are the relevant portions of the iLO2 log: 305 04/15/2011 23:42:00 Server reset. 306 04/15/2011 23:42:00 Server power removed. 307 04/15/2011 23:42:00 iLO 2 network link down. 308 04/15/2011 I witnessed it, the shutdown and restart was perfectly clean. Check This Out
If you have installed a non-HP(retail) copy of server 2008 OS, then boot system to install and run repair startup. share|improve this answer answered May 3 '11 at 19:46 DanBig 10.6k12050 Dang. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. share|improve this answer answered May 3 '11 at 21:29 Holocryptic 5,22522034 That looks promising.
Event Id 6008 Windows Server 2008 R2 Unexpected Shutdown
Keep in touch with Experts ExchangeTech news and trends delivered to your inbox every month Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource It's an HP Proliant ML330 G6 Series server. However, I did run boot time mem for atleast 3 cycles and no issues were reported. I also found a similar discussion here: http://www.eventid.net/display.asp?eventid=41&eventno=10602&source=Kernel-Power&phase=1(different event ID, but I read where it solved the problem you describe) 0 LVL 53 Overall: Level 53 Windows 7 24 Windows
Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... Then please don't answer to avoid discussions. 0 Comment Question by:McKnife Facebook Twitter LinkedIn https://www.experts-exchange.com/questions/28219906/2008-R2-Servers-sometimes-log-unexpected-shutdown-although-shutdown-was-clean.htmlcopy LVL 53 Active today Best Solution byMcKnife I am able to close it: It seems to Will try safe mode for diagnosis. Event Id 6008 Windows Server 2003 It seems, as though it happens in the process of restarting after windows updates are installed.
We have a clean windows 8 pro x64 system and it does this even with not a single software installed. All goes well for a very long time. Perhaps run a stress test tool, like Intel Burn Test to make sure the server isn't faulty first. If you find dump file analyze it with the help ofwin bebugtoolto know root cause of server shutdown.steps to analyse a dmp file:http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx#3476888 Win Debugging tools:for dump file analysis download windebuger
Back to top ↑ Resolution Stop the BlackBerry Controller Service prior to initiating a Shut Down. The Previous System Shutdown At Was Unexpected. Server 2003 We have a problem here on all 2008 R2 servers and on as far as I can see all win7 clients. do you see event id 57 in your system log? –tony roth Apr 19 '11 at 2:11 @tony: Sorry, still not following. It will depth in Network and Internet, Hardware and Sound, etc.
Event Id 6008 Windows Server 2012 R2
windows server 2008 reboot automatically Rahi Padariya asked Sep 23, 2011 | Replies (4) hello all, We are currantly facing problem of server restarting problem, we have HP Proliant DL180 G6 You need to look there too because spontaneous shutdowns might be related to a hardware issue that you won't be able to see info about anywhere else. Event Id 6008 Windows Server 2008 R2 Unexpected Shutdown It's unfortunate there's nothing useful in the HP logs. The Previous System Shutdown Was Unexpected 6008 If it doesn't show anything I still suspect the ASR process.
It's worth keeping an eye on your hardware too like have you tried running a memory test? 0 Pimiento OP Taylor9004 Apr 8, 2014 at 1:09 UTC Thank his comment is here From time to time (maybe every 3rd time, some server every time) they log event 6008 ("the previous shutdown was unexpected") although the shutdown was perfectly clean and expected. Clutching at straws, but you never know. Will carry on isolating the problem. 0 LVL 59 Overall: Level 59 Windows 7 20 Windows Server 2008 2 Message Active today Expert Comment by:LeeTutor ID: 395824272013-10-17 I've requested that The Previous System Shutdown Was Unexpected Server 2008 R2
windows-server-2008-r2 share|improve this question edited May 20 '11 at 18:19 asked Apr 18 '11 at 20:42 boot13 135118 dang do you have ASR enabled? –tony roth Apr 18 '11 We are a small organization and do not rely on Spicworks for day to day functions. 1 Poblano OP bg_vignesh Jan 29, 2014 at 4:01 UTC Hi Taylor, Probably What's the male version of "hottie"? this contact form Please be advised that contacting phone support will be a charged call.
It turns out that the Xeon 5000 series CPUS, which your machine does use, have an issue with 2008 R2 and Hyper-V role. Event Id 41 Windows Server 2008 R2 Although the server is configured to write a kernel dump and restart, there is no memory dump and the system did not restart. mjkisic Saturday, December 29, 2012 9:50 PM Reply | Quote 0 Sign in to vote Hi Mohammed, If you don't have a mini dump file then I would recommend enabling mini
I'll keep that one in mind in case the firmware and driver updates don't fix it. –boot13 May 3 '11 at 22:24 add a comment| up vote 1 down vote I'm
There are no blue screens/minidumps but only clean reported as unclean. share|improve this answer answered Apr 18 '11 at 23:40 icky3000 3,6971314 @icky: Okay, I looked at the System Management Home Page and the logs therein: System Management Homepage Log, How about tracing the power back - dual power supplies? Windows 10 Event Id 6008 It could still be the server's power supply, though. –boot13 Apr 19 '11 at 21:10 | show 1 more comment up vote 1 down vote I had this EXACT issue happening
UPDATE: I increased the size of the paging file to allow for full kernel dumps, so if it's really a Windows crash, I'll be able to see what happened - the Brand new server, fans all running fine, temps all nominal. –boot13 Apr 18 '11 at 21:52 1 Hmm. Source. This is a bug.
Looks like we'll have to keep digging as well. 0 Poblano OP bg_vignesh Apr 8, 2014 at 12:36 UTC Hi Taylor, Since turning off Spiceworks, it seemed that There were no programs that was installed recently that might cause this We have no monitoring tools except Spice works :) We use Vipre Business Premium AV on our network There 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 By ASR do you mean the HP 'Automatic Server Recovery'?
There are no other events or errors that are logged in the event log just before the 6008 event. share|improve this answer answered Oct 17 '12 at 15:04 Massimo 47.8k29137251 Power does seem to have been the issue, but since the UPS didn't report anything unusual, I'm going Causes: ===== Hardware going bad Hardware firmware or driver is misbehaving Mini filter drivers (i.e. The most recent occurrence was at 11:41pm a few days ago.
The absence of such an event log and of a subsequent reboot means the shutdown was caused by an external event (power missing, hardware fault...). When you refer to the 'integrated log management' do you mean the 'Integrated Management Log' in the System Management Homepage?