Solved BSOD When Computer is Idle. I never see it happen.

[irsmun]

Thank you for your help with my problem.

My system has been shutting down after its idle for a time. I never see it happen I just come to it and its off. This has happened just recently in the last few weeks. I think its a blue screen because it shows me an error report when I reboot. No major changes were made. Norton Internet Security was updated and installed. I uninstalled it and used the removal tool to see if it would change things. It did not so I reinstalled it. I have no idea how to troubleshoot the error. I am hoping to have some assistance in where to look. Other strange anomalies are happening such as printer problems and windows explorer having to restart or slow.

I have attached the zip file in accordance with the instructions and using the diagnostic tool.

 

[irsmun]

Nothing? I need to find some direction of where to look? Is it hardware, software, both???

 

[koolkat77]

Welcome to the Forum.

It is, at the moment very hard to pin point any information from the dumps.

Please follow the steps outlined for the time being.

Norton is a known cause of blue screen. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Run a System file check (SFC): http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Run Disk Check on your Hard Drive(s): http://www.sevenforums.com/tutorials/433-disk-check.html

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software: CrystalDiskInfo - Software - Crystal Dew World

http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Run a Hard Drive test: http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#post2610227

 

[irsmun]

Ok. That is a lot to check and most seems unnecessary. I don't want to take shots in the dark. I want to follow the trail. This is the craziness I have done so far.

I booted up in safe mode. It stayed up for over 24 hours. I think that rules out the "its getting too hot issue". I then started systematically deleting and removing programs that seem to, or have the ability to give me trouble. I uninstalled Norton Internet Security. No change. I rolled back my video driver. No change. I uninstalled my printer and its drivers. No change. I removed all unnecessary programs. No change. I removed a USB drive that had an error in device manager. No change. I have begun uninstalling everything. This is crazy (by the way I ordered a new computer today) How is that for a solution. I ran CCleaner between each uninstall and cleaned the drive and the registry each time.

This is frustrating. How can we be 30 years into an OS and there isn't better and more clear data when something goes wrong? No major changes took place in my machine. Something has to point to the problem. Is there any more info I can provide?

I think a huge clue is that it only does it when idle. I can be on the machine the whole day or just have music or a video playing and it will be fine. But when you leave it be for a while, you come back and its shut down. Its something that kicks in when the machine goes idle...whatever that is. I don't have screensavers or sleep modes turned on. But like the title says, I don't ever see it happening.

 

[ICIT2LOL]

Hmm irsmun I cannot see anywhere your power settings so just what have you got it set to?
Also most of this sort of problem I see are heat related ones and / or that that CMOS battery is dead or very near it. Another thing is have you updated the BIOS lately if not might be worth a try.

Try these please


http://www.bleepingcomputer.com/download/adwcleaner/
ADW downloadfrom bleepingcomputer delete any rubbish
&
Free Malware Removal Tools scroll down to the TDSS Killer and run.

My other thought is maybe the PSU is failing too so you can try this as I do not know how old the computer is
PSU- Jump Start

for a reference
PowerSupply 101: A Reference Of Specifications - Power Supplies asyou will see there is a +/- 5% variance that can make all the difference so11.4v is way too low and 12.6v way too high.

Plus remember correct bolts do not mean correct current (amps - in turn watts)

 

[carwiz]

BIOS Version/Date Hewlett-Packard 786B8 v2.10, 5/31/2006
You might see if there's a BIOS update for your system. HP says it supports APCI 2.0 but there may be updates that affect Windows 7 support for sleep and hibernation.

You're missing system event logs after Oct, 2013 but it DID show processor throttling (overheating) on all processors before the log terminated.

The last dump supplied was from the 18th of Dec. and was caused by Intuit Sync Manager in module dbtool11.dll. I would check with Intuit and see if there's an update there too.

 

[ICIT2LOL]

Yep carwiz I don't know much about the dump files but I did see a lot of refs to overheating and if that BIOS you mentioned and I asked about is indeed 2006 I am wondering if the machine needs a good clean out??

 

[carwiz]

A good cleaning and perhaps renewing the heatsink compound on the CPUs. Two to three years is about the limit on compound but SEVEN? That's pushing your luck.

 

[ICIT2LOL]

A good cleaning and perhaps renewing the heatsink compound on the CPUs. Two to three years is about the limit on compound but SEVEN? That's pushing your luck.

Hmm I reckon say 4 -5 years on a good compound but it depends I suppose what is was and how it was applied.

Just wish the OP would post back??

 

[irsmun]

Ok. Problem solved...I think. When I said I had all sleep and idle functions turned off I did. Its been running fine for months. But I checked anyway. The hibernate function was turned to NEVER, but in the advanced settings it was set to 62 minutes. Not sure why the first did not invalidate the other but apparently it did. I turned the advanced function to NEVER as well and it did not shut down overnight. For some reason This machine and the hibernate function do not like each other. Its sad because that is a most useful power saving feature.

I still get the Intuit Sync Manager shutting down but that may be unrelated.

Could the processor over throttling happen just before hibernation? If so, it would just be a coincidental happening. I certainly don't want it running hot.

 

[Slartybart]

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.

Ok. That is a lot to check and most seems unnecessary. I don't want to take shots in the dark. I want to follow the trail. This is the craziness I have done so far.
.....

 

[irsmun]

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.

 

[Arc]

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.

[COLOR=Red]BugCheck A0[/COLOR], {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, [COLOR=Red]A fatal error occured while preparing the hibernate file.[/COLOR]
Arg2: [COLOR=SeaGreen]c0000001[/COLOR], Status code
Arg3: 00000001, Mirroring phase
Arg4: 00000000
---------------------------------------------------------------------
Error code: (NTSTATUS) [COLOR=SeaGreen]0xc0000001[/COLOR] (3221225473) - {[COLOR=Red]Operation Failed[/COLOR]}  [COLOR=Red]The requested operation was unsuccessful[/COLOR].

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.

922d5c34 82f5d0ba nt![COLOR=Red]KeBugCheckEx[/COLOR]+0x1e
922d5ca4 82f5a951 nt![COLOR=Red]PopEndMirroring[/COLOR]+0x11f
922d5d1c 82f54821 nt!Mm[COLOR=Red]DuplicateMemory[/COLOR]+0x8ab
922d5d50 82e2653a nt![COLOR=Red]PopTransitionToSleep[/COLOR]+0xce
922d5d90 82cc7899 nt!PspSystemThreadStartup+0x9e
00000000 00000000 nt!KiThreadStartup+0x19

Post #3 and post #6 will help you reduce a lot of possibilities. Plus, rebuilding the hiberfile.sys may also help you.

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.

 

[Slartybart]

Koolkat and Arc are two of the most knowledable (and helpful) folks around here for reading memory dumps and resolving BSODs.

..... Plus, rebuilding the hiberfile.sys may also help you. ...

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

 

[irsmun]

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.

 

[Indianatone]

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).

 

[Slartybart]

What do you mean by "advanced sleep"?

Is this in a power scheme?

 

[carwiz]

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.

 

[irsmun]

What do you mean by "advanced sleep"?

Is this in a power scheme?

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.

 

[irsmun]

They ARE over heating.

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.