Solved Unexpected Shutdown (with BSOD) in Sleep Mode???

[EvilOzzmess]

I started having this issue earlier last week. I leave the computer on to go do something else for a while (as I dislike shutting it down all the time as I think it’s better to just leave it ready and running) and it always stayed on as it's supposed to. However, recently when I come back the system is in the bootup screen asking me how I want to start it, and after the boot it tells me that the system has “Recovered from an Unexpected Shutdown”.

This is absolutely baffling to me. I have NEVER had a computer behave like this in my life… when any of my other computers shut down it was because of obvious factors like the power cutting out, or because it got too hot and with the OS telling it too to shut off to protect it - but I have NEVER had this happen in addition to a BSOD screen (disappears too quickly to read when the system shuts off and restarts), which displays before the system shuts off on its own and for seemingly no apparent reason at all!

The hardware seems to be in pristine working order as far as I can tell and I haven’t done anything differently to provoke this. However, I DO use BitTorrent but I don’t see how that could have instigated this problem (correct me if I’m wrong please) and I religiously check the system for viruses and other nasties and I also clean the Registry (backing it up every time beforehand) and wipe out useless clutter using CCleaner (never had a problem with using this either).

I’m leaning towards thinking that this is a hardware or drivers issue, primarily because:

1. I DO NOT use the battery, but rather the AC Adaptor 95% of the time (with the battery OUT to preserve the life and cycles of the battery - I drain it and recharge it once a month to retain it's longevity for when I DO need to use it).

and

2. Acer Updater never, ever displays any updates to drivers or anything else... so chances are my drivers are actually out of date, but I never download or install drivers on an OEM system UNLESS the manufacturer tells me too, to avoid major headaches when it goes wrong.


Please help me figure this out, very frustrating!


OS/Hardware information (as per the guidelines):

X86 (32-bit) or x64? Windows 7 Ultimate x64bit (NOT OEM)
Original installed OS on the system? Windows 7 Home Premium x64bit (OEM)

What is the age of the system (hardware)? 5 Months
What is the age of OS installation? 3 Months

 

[Jonathan_King]

There are no dumps in that report, which are our primary data source. I see you have no dumps in your Minidump folder. Make sure CCleaner is NOT set to delete memory dumps.

From some other info in the report, I can see your Atheros drivers are too old, dated June 2009. That means they are technically incompatible with Windows 7. Please update them to the latest version.

 

[EvilOzzmess]

Really? Wow... I didn't know that I'm really sorry.[FONT=&quot] However, it happened again last night, I left it on to see if this would transpire again. I disabled Sleep Mode when the lid was closed (so unless it goes into Sleep Mode when it has been on and inactive for a while, that isn’t part of the problem anymore):[/FONT]

[FONT=&quot]Windows has recovered from an unexpected shutdown[/FONT]

[FONT=&quot]Problem signature:[/FONT]
[FONT=&quot] Problem Event Name: BlueScreen[/FONT]
[FONT=&quot] OS Version: 6.1.7600.2.0.0.256.1[/FONT]
[FONT=&quot] Locale ID: 1033[/FONT]

[FONT=&quot]Additional information about the problem:[/FONT]
[FONT=&quot] BCCode: 9f[/FONT]
[FONT=&quot] BCP1: 0000000000000003[/FONT]
[FONT=&quot] BCP2: FFFFFA8003D2AE30[/FONT]
[FONT=&quot] BCP3: FFFFF80000B9C4D8[/FONT]
[FONT=&quot] BCP4: FFFFFA80091CCBC0[/FONT]
[FONT=&quot] OS Version: 6_1_7600[/FONT]
[FONT=&quot] Service Pack: 0_0[/FONT]
[FONT=&quot] Product: 256_1[/FONT]

[FONT=&quot]Files that help describe the problem:[/FONT]
[FONT=&quot] C:\Windows\Minidump\080810-20654-01.dmp[/FONT]
[FONT=&quot] C:\Users\Magnus\AppData\Local\Temp\WER-41901-0.sysdata.xml[/FONT]

I tried to open those files but Windows can’t find them (I did NOT use CCleaner so they should still be there) I'll run the apps again and attach, hopefully that will catch them...


EDIT: Updated files attached.

Also... if nothing can be found to solve this the "hard way" (i.e. manually), should I just consider a Repair Install, or a Factory Image reinstall? Would that even solve the problem at all, if it's software related rather than hardware related? I have an External and time on my hands so it would be no big deal for me to do it... but I'd prefer to do this the quick, dirty and painless way (manually).

Thanks again for the help, I really do appreciate it!

EDIT 2: I have altered the advanced power options to never allow the system to enter Sleep Mode. It was set to automatically enter that power state after 15 and 30 minutes respectively (battery only/AC Adaptor only). I'm certain that the BSODs are due to something screwing with the Sleep Mode functions, because that's when these occur, it never happens when the system is on and actually being used.

 

[ttran]

Please run it as administrator. Otherwise simply do this:

Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.

 

[EvilOzzmess]

Minidump event from last night attached below, thank you very much ttran!

EDIT again: I'm trying "sfc /scannow" in CMD as Admin... we'll see what happens.

 

[ttran]

I'm sorry but when looking the DMP, I can't find the cause either. Please check out these KB that related to the stop code that I see from the DMP.
KB 981848 "0x0000009F" Stop error message when a computer enters and resumes from hibernation in Windows 7 or Windows Server 2008 R2
KB 977186 Error message when you try to resume a Windows 7-based or a Windows Server 2008 R2-based computer from hibernation: "Stop 0x0000009F"
KB 975599 Stop error when you put a computer that is running Windows 7 or Windows Server 2008 R2 to sleep or into hibernation, or when you restart the computer: "0x9F"

Please update the Atheros drivers. Also, in my experience, I used to have similar problem when I left my computer idle and it BSODs, and the way I resolve it is to update power manager driver. Trust me, try that to see if it helps.

Stop code 9F is usually caused by Drivers, one thing you can try is to enable driver verifier:
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

It will flag bad drivers and we will go from there. Please re-setting CCleaner so that it won't wipe out minidump file. It would be better if we can have more than 1 DMP.

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.298\080810-20654-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c4c0?
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8be50
Debug session time: Sun Aug  8 10:50:58.841 2010 (UTC + 7:00)
System Uptime: 0 days 13:14:54.760
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8003d2ae30, fffff80000b9c4d8, fffffa80091ccbc0}

Probably caused by : ntkrnlmp

Followup: MachineOwner
---------

Are you using Mcafee?

Regard,

Tuan

 

[EvilOzzmess]

Sorry in advance for the double post, missed something...

From some other info in the report, I can see your Atheros drivers are too old, dated June 2009. That means they are technically incompatible with Windows 7. Please update them to the latest version.

I'm sure a few drivers are out of date... as for this Atheros, I have had some connectivity issues with my wireless internet but they've all been due to ISP failures (the router cuts out and looses the signal every day, at no fault of any of our computers).

I have checked and re-checked all drivers in the Device Manager but it says they are all the best and most up to date to use. Acer Updater never lists any updated versions either, nor on their website (all drivers are dated from 2009)... I make it a rule of thumb to never use drivers not recommended for OEM systems, as I've had pretty bad experiences doing that in the past on our old Dell Dimension 3000.

 

[EvilOzzmess]

ttran, will do, and thanks again. EDIT: I'm going to wait a few days to run the verifier, 'cause it can K.O. the computer... I've got some downloads going and haven't backed up in a while, so once those are done I'll go ahead and run it.

And no, I DETEST McCafe with a passion. It came preinstalled on here though and I let it stick around for about a month before I threw it off of here for being a pest, a resource hog and for not doing a dang thing lol. I stick with MBAM now (always solves my problem when paid programs don’t), I don’t need “real time” protection and I’m savvy enough to run a manual periodically when I know something is going on lol.

 

[ttran]

In looking through your driver, I could see that you've not completely remove Mcafee, use the instruction below to finish it (though you've done most of it):
How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

Good Luck,

Tuan

 

[EvilOzzmess]

In looking through your driver, I could see that you've not completely remove Mcafee, use the instruction below to finish it (though you've done most of it):
How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

Good Luck,

Tuan

Why those sly, rotten snakes!!! LOL I'm running it now, going good.

And as I suspected the cfs scan didn't find anything... I'll try a repair install next, before the verifier and a Factory Image Restore (if those are necessary as I don't want to unnecessarily loose data if I really don't have too).

 

[EvilOzzmess]

Okay well, it's happened again without the computer hibernating or sleeping and while I was actually on it. The plot thickens... I'm going to back up all of my data and make a list of programs etc. and then run the driver verifier, or restore the system to Factory if necessary (I really, really hope not).

Does anybody know if BitTorrent could cause this? It's been open and running every time this has happened... and the program has been acting screwy lately, freezing up and not wanting to respond or be shut down. Please let me know, or tell me how I can check into that.

Thanks!

 

[EvilOzzmess]

I tried to run Driver Verifier but it did nothing... it said I needed to restart, I told it "OK" and it didn't do anything, so I manually restarted and it just booted up as usual, without it doing anything for the driver verification. I've tried it twice now, and nothing happened either time.

What's the next step? Repair install, factory install, or?

 

[Jonathan_King]

Keep running your system normally, Verifier is almost certainly enabled. If you want to make sure, open a command prompt and enter verifier /query.

 

[EvilOzzmess]

Keep running your system normally, Verifier is almost certainly enabled. If you want to make sure, open a command prompt and enter verifier /query.

OK, I did that and it opened another CMD and displayed a fast running block of text, but disappeared. How am I supposed to know if it found bad drivers etc?

 

[EvilOzzmess]

Alright, I had a hunch it was BitTorrent and after some sniffing around on Google my suspicions have been confirmed. It's bandwidth related... the system thinks that when the bandwidth gets astronomically high, or has a high demand put on it (which shouldn't be a problem with the fastest FiOS but I digress), that the system itself is in danger and causes a "false" BSOD episode and shuts down immediately, much like when things get too hot internally. It's also tied to the RAM and CPU usage somehow... that's what ultimately causes the BSOD, as they drop off suddenly in response to the bandwidth demands and, I would imagine, make the system think it's freaking out somehow.

There isn't any information on how to correct this error out there so I'll just have to deal with it while I'm using the program and end the process immediately after I'm done with it to stop it from resulting in this BSOD, stop seeding Torrents, or just stop using Torrents altogether.

This bytes!

 

[EvilOzzmess]

Just want to update, for anyone else experiencing this problem...

I never had it resolved, however I simply use my physically connected XP Desktop to handle Torrents and it does not experience this issue with BSODs, unexpected shutdowns or anything else.

The issue only presents with wireless connections, not through physical connections however. So for those of you with mobile PC's like me experiencing this problem, hook an Ethernet cord to your wireless router, plug it in to the Notebook's port and then turn OFF the wireless signals until your Torrent is done and you WON'T experience BSODs. Then turn it back on and disconnect the Ethernet cord.

Nothing else for it than what I've said, until or unless BitTorrent etc. fixes their software for wireless users.

Hope this helped somebody!

 

[Jonathan_King]

Alright, thanks for reporting back! I'm glad you're able to work around it, at least.