Wow that sounds exactly like the problem we had with a DL380G6 about a year ago. HP shipped us a new mainboard before they figured it out. Check your version of the ilo firmware. If it's late 1.6x or early 1.7x there were a lot of problems with random reboots exactly as you describe. We updated the firmware to 1.8x and it's been fine since then. Turning off ASR in HP system management helped but didn't eliminate the problem altogether. If you look in your event log and see duplicate messages about the temperature and fan sensors you have a likely culprit.
Good luck with it. I had a second G6 server with similar problems that ended up being an actual bad system board (acted like someone was yanking both power cords at the same time) so I'd definitely open a case with HP if you have warranty on it and have not done so already. Paul The disclaimer below does not necessarily reflect my views but is automagically generated by company elves. -----Original Message----- From: Maglinger, Paul [mailto:pmaglin...@scvl.com] Sent: Wednesday, March 30, 2011 9:40 AM To: NT System Admin Issues Subject: RE: Win2008 R2 not writing crash dump file I'd start with the simple stuff. Power cord in tight? Is the server in a clean server room? If not (or even if it is), check the fans and heat sinks for dust and clean it out. Speaking of fans, are all of them running? Air vents not blocked? -Paul -----Original Message----- From: Mike Leone [mailto:oozerd...@gmail.com] Sent: Wednesday, March 30, 2011 7:38 AM To: NT System Admin Issues Subject: Win2008 R2 not writing crash dump file I've got a Win2008 R2 server that has decided that it is a yo-yo, and is rebooting daily (at different times), sometimes twice within like 20 minutes. In Control Panel, I have "Kernel memory dump" chosen under "Write debugging information", with the value "%SystemRoot%\MEMORY.DMP (and checked off "Overwrite any existing file"). But I never get any dump file - there are no files *.DMP anywhere on the server. And I don't know why it's not writing one. I want to run one through the WinDbg debugger, hopefully yo have it point at the problem (bad device driver, I'm guessing). The event log only says the previous shutdown was unexpected - never lists any bugcheck values or anything. So I'm sort of flying blind at this point. What would cause the DMP file to never be written? How can I get a DMP to analyze? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
