The suggestions by Koolkat are all valid and would provide additional information or rule out some possible causes. None of the suggestions are unnecessary if you want members to help solve the issue.
Without following the advice given by members, all you will have are "shots in the dark" because there is no trail to follow.
Please complete post #3 and provide feedback as requested.
Thank you Slartybart. Though I may not be a computer genius I have been around them, building them, and configuring them for almost 20 years. I am good at troubleshooting and I think I can recognize when one is "shooting in the dark" because there seems to be nothing to go on. They were all very generic and wide scoped suggestions. I did not say they were invalid. They would be perfectly valid if I had nothing to start with. However, I provided the required information and was able to give a huge clue that the incident was only happening when idle. Which, as it turns out, was the a key to the problem.
Thank you all for your help. My main issue was that I could not troubleshoot the dump logs nor was I confident I could read them properly. That's when I came here. The event viewer did not offer any evidence of the solution. I have checked my processor temps and they are fine, running about 60 degrees C.
I will look into the other suggestions (such as BIOS updates) for the causes of the other anomalies. Thank you again.
All the suggestions are supplied based on the dump data.
May be you are not satisfied as dumps are not explained. We usually dont do it, as those are klingon to most.
The BSODs are INTERNAL_POWER_ERROR, BugCheck A0.
I hope now it is clear that the preparation of the hibernate file (hiberfile.sys) is failed. Why, that is not very clearly stated in the dump. But, it is occurred during the power transition to sleep.Code:BugCheck A0, {9, c0000001, 1, 0} Probably caused by : ntkrnlmp.exe ( nt!PopEndMirroring+11f ) ------------------------------------------------------------------ INTERNAL_POWER_ERROR (a0) The power policy manager experienced a fatal error. Arguments: Arg1: 00000009, A fatal error occured while preparing the hibernate file. Arg2: c0000001, Status code Arg3: 00000001, Mirroring phase Arg4: 00000000 --------------------------------------------------------------------- Error code: (NTSTATUS) 0xc0000001 (3221225473) - {Operation Failed} The requested operation was unsuccessful.
Post #3 and post #6 will help you reduce a lot of possibilities. Plus, rebuilding the hiberfile.sys may also help you.Code:922d5c34 82f5d0ba nt!KeBugCheckEx+0x1e 922d5ca4 82f5a951 nt!PopEndMirroring+0x11f 922d5d1c 82f54821 nt!MmDuplicateMemory+0x8ab 922d5d50 82e2653a nt!PopTransitionToSleep+0xce 922d5d90 82cc7899 nt!PspSystemThreadStartup+0x9e 00000000 00000000 nt!KiThreadStartup+0x19
Some drivers may also cause it, despite of being pointed by the crash dump. Let us see. Upload the list of all the third party drivers Using NirSoft DriverView :
- Download and execute Driverview
- View > Hide Microsoft Drivers
- Edit > Select all
- File > Save Selected Items
- In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
- Zip the .txt file and upload it.
Well, let us know about your advancement through the troubleshooting.
Koolkat and Arc are two of the most knowledable (and helpful) folks around here for reading memory dumps and resolving BSODs.
Launch an elevated Command Prompt (right click, run as adminstrator)
powercfg -H off
exit
Restart your machine - there should not be a hiberfile.sys on your machine. It is a hidden / system file so you'd have to change the folder view to see it.
Once your machine is stable, you can turn hibernation back on if you want.
Launch an elevated Command Prompt (right click, run as adminstrator)
powercfg -H on
exit
I meant no disrespect in any of my replies. Maybe it was the simplistic approach and not providing "why's". I do like to learn.
Since I purchased this machine I have never gotten the hibernate to work. When I first got it, I formatted the drive and did a fresh install of Win 7. I think it had XP before. I tried to update everything but whenever I tried to make it hibernate it would shut off...which is what made me search the advanced sleep sections as this seemed to be what its doing. I don't clutter my machine with software as I use it and want to keep it stable and fast. This is why these are anomalies to me. I have not done any significant changes or added any hardware or software, yet these occurrences began happening in the last month. Some software updated I'm sure as well Windows updates. I read somewhere that hibernate doesn't like some video cards. As you know this is not a new machine.
You answered my question already Slartybart. I was wondering how to rebuild the hibernate file. I will give this a shot. Thanks everyone.
I would replace the heatsink compound as 60C is a little warm for a CPU's at idle. Currently mine are around 16C to 25C idle depending on cooling (fans or water cooled).
As already mentioned, look for a BIOS update. That may fix the hibernation problem.
I don't know what the ISM does but it may not play well with the stop states. Again, update the BIOS.
The processors don't over-throttle, it's more under throttle or a stop state. Throttling is a function the processor goes through when it over heats. It turns itself off for short periods in an attempt to save itself from catastrophic failure. This is a built in feature of the Intel processors. The OS and user have no control over it. When it occurs, it's an indication that the processor(s) have reached a critical temperature. If the throttling is allowed to continue, permanent damage to the CPU could occur. Your log indicated that both CPUs and both cores on each entered throttling states. They ARE over heating.
Yes. I set a custom scheme when I was playing with trying to get the hibernate feature to work. When it didn't, I set the main hibernate option to "never" but left the one in the advanced menu to 62 minutes. At some point the last few weeks it started working off that advanced menu setting by itself.
This does concern me. I have looked all over for "normal" temps for Xeon processors. Apparently I am not the only one who has them running high. I can't find exact numbers for normal operation but Intel says 79 C is max temp. One suggestion keeps coming up that the software tools reading the temps can be wrong and by a significant factor. There is no way to really know without putting an actually temp reader on the processor. This is a server class machine and I thought that the Xeon processors run a little hotter than most. I really don't know. I do know that the machine puts out a lot of heat. Its no big deal now, but in the Texas summers it makes a huge difference.
I will see if there is a BIOS update available.
Quote