Create an account on the HP Community to personalize your profile and ask a question
05-24-2013 05:47 AM
For about 6mnths now we have been chasing the root cause of why 12 out of 15 workstations randomly shuts down. They even usually do not restart. Just shuts down. The log has the famous Event id 6008 ("unexpected shutdown").
Since the problem affects so many workstations, it is tempting to think this is the PDU/APC Power system, but why does it then not affect all of them?
Appreciate any feedback.
I finally thought this could be due to some thermal alarm that shuts it down, but I could not find its settings in the BIOS.
I also assume these workstations do not use ASR.
05-24-2013 11:11 AM
it was not the latest version from May. I have upgraded 3 machines to the latest BIOS as well as the Intel storage drivers. But in the release notes for the BIOS, it does not mention a fix of shutdown problems, so I am a bit pessimistic...
05-24-2013 05:31 PM
My opinions are my own, and do not express those of HP.
Please click "Accept as Solution" if you problem was solved. This helps other forum readers.
05-27-2013 02:02 AM
2 machines shut down this weekend. They both had the latest BIOS 3.14. One of the machines even had its own power supply going outside of the APC PDU.
The strange thing is that they never seem to write a memory.dmp or minidump. But today I found one by coincidence from 25 April. I will look for a tool to analyze it. What is recommended that is free? The one from Microsoft? Hopefully I will find the answer through this analysis.
05-27-2013 02:41 AM
seems like the attachment is the culprit, at least in the one machine I have the minidump for.
I deduced from the minidump using a tool that the crash is caused by a Windows corrupt system file:
and it can perhaps be fixed with sfc /scannow or the file can simply be replaced.
What is recommended in this case? What is this file?
Here is a link to the use of sfc:
I verified the Windows system files (Win 7 Enterprise) integrity by: sfc (verifynow. It did find problems. I will now proceed to go ahead and fix them using the above command.
But a bit strange so many machines are affected.
Update: Sfc /scannow could not repair the files. I will now go ahead and replace this file.