Solved Windows 7 shuts down during sleep

[1metalguru]

HI guys

My computer recently started some odd behaviour. I normally rarely shut down the system, I just use the Start menu Sleep button when I leave it, and just click the mouse or keyboard when I return. This has been working fine for years, and yes, I occasionally reboot the system.

Recently, (last couple of weeks) it has started to shut itself off after several hours in sleep mode. I have to use the power button to turn the system back on, and when it comes up I get the "Windows was not shut down properly" screen. I usually just select "Start Windows Normally".

It does not seem to shut down after short periods in Sleep mode, usually only if left overnight or at least several hours. I have noticed some stuff in the logs that seems to indicate that there is something causing a BSOD in sleep mode. I have had one odd BSOD while using the machine but I don't recall what the error message was. It does not seem to affect anything while the machine is on and I am working with it. Only had the one crash in a couple of weeks.

I have checked all the power settings, etc, but I have not changed any settings for months. I did install a couple of games recently but uninstalled them when the problem started, to no avail. Other than that, I have not installed any new software for some time. It seems it might have started after a recent Windows Update, but not 100% sure.

I have attached the requested log information file.


Thanks.

 

[1metalguru]

Come on guys, 222 views and no one has any hint of a solution?

 

[1metalguru]

Update
Tried some software called Passmark Sleeper, supposed to test sleep mode. As soon as computer entered sleep, it shut down with BugCheck error as follows:


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa800fbfcab0, 0xfffff80000b9c568, 0xfffffa800d276ca0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072618-36114-01.


MG

 

[1metalguru]

More info from "windows encountered a problem" Splash screen on bootup



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800FBC2CD0
BCP3: FFFFF80000B9C568
BCP4: FFFFFA801881C010
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\072718-46332-01.dmp
D:\Users\Metalguru\AppData\Local\Temp\WER-16314069-0.sysdata.xml
^^^Note: this last file does not actually exist for some reason.


MG

 

[philc43]

Hello MG,

Thanks for your patience. I normally work on the W10 forums but have been called over here to help.

The crash dumps report a DRIVER_POWER_STATE_FAILURE (9f).
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800fe4e920, Physical Device Object of the stack
Arg3: fffff80000b9c568, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8010385010, The blocked IRP

The analysis shows:

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa800e34fa30

IMAGE_NAME:  asmthub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4eb203d0

MODULE_NAME: asmthub3

FAULTING_MODULE: fffff88006ccb000 asmthub3

We can look at the blocked IRP:

0: kd> !irp fffffa8010385010
Irp is active with 8 stacks 6 is current (= 0xfffffa8010385248)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
[COLOR="Red"]>[/COLOR][IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 fffffa800fe4e920 00000000 00000000-00000000    pending
	       [COLOR="red"]\Driver\asmthub3
[/COLOR]			Args: 00016600 00000001 04c840c0 00000005
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa800fc11d60 00000000 00000000-00000000    pending
	       \Driver\Serenum
			Args: 00016600 00000001 04c840c0 00000005
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-fffffa800cf018a0    

			Args: 00000000 00000000 00000000 00000000

The module is asmthub3.sys from the ASMedia USB 3.0 Hub driver. This is the driver that you need to update.


The current driver on your system has a time stamp of: Wed Nov 2 19:00:32 2011


See if you can find an update for it.

 

[1metalguru]

Hello MG,

Thanks for your patience. I normally work on the W10 forums but have been called over here to help.

The module is asmthub3.sys from the ASMedia USB 3.0 Hub driver. This is the driver that you need to update.

The current driver on your system has a time stamp of: Wed Nov 2 19:00:32 2011

See if you can find an update for it.

Hey Phil:


Thanks for the reply. Apologize for the rant earlier, it's just so frustrating to have a computer that you rely on daily to start acting up. I know you guys do this for free and have no reason to help anyone other than altruism, but I hope that a warm thank you is enough to keep you doing it.


Anyway, as to the problem, I tried using the Device Manager/Device/Driver Update method to update this driver, and it said it was up to date, even though it was obviously not. So I tried Driver Easy and managed to get it updated, along with a few others that were out of date.


I have yet to test this out since it seems to require a night of sleep (the computer, not me) to get the problem to occur. I will post back in a day or two with the results.


Thanks again for your service.


MG

 

[philc43]

You are welcome!

As a rule I do not recommend using any 3rd party driver update package. It runs the risk of introducing unwanted programs and possibly bad drivers. Always use the manufacturers website for updates. If you suspect any problems rollback the drivers that were updated and do them again via the websites, e.g. http://www.asmedia.com.tw/eng/e_products_list.php?item=83&cate_index=0. Sorry for not giving you this link in the first place.

 

[1metalguru]

Phil:


I tried the link you sent, but all it is is a hardware description of the chips, I could not find any driver software on that site. I don't know which chip/driver is applicable to my system either, there are several to choose from. I can do a Google search for the driver, but how do I tell which one I need?

I put the system to sleep last night after updating the drivers, it was still dead this morning, so updating the driver didn't seem to work.

The new system BSOD message, I think is the same. I will verify that later, I forgot to copy it to paste in here. Let me know if you need more info.


Thanks.

 

[1metalguru]

Latest BSOD message (its a bit different):


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800E77F990
BCP3: FFFFF80000B9C568
BCP4: FFFFFA8013762600
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\072918-29109-01.dmp
D:\Users\Metalguru\AppData\Local\Temp\WER-59592-0.sysdata.xml


Both these files are attached Update, I tried to upload the files, but it kept telling me they were invalid. Added them to a .zip

 

[1metalguru]

Jeez this thing is a pain. Only lets you add one file to a message. Here is the dump

 

[philc43]

Even though it's a new driver the asmthub3 is still being called out as the problem. You may have to consider removing or replacing the device if that is possible.

0: kd> !irp fffffa8010d29700
Irp is active with 8 stacks 6 is current (= 0xfffffa8010d29938)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa800e7d8c70 00000000 fffff88004bd1b70-00000000 Success Error Cancel pending
	       [COLOR="Red"]\Driver\asmthub3[/COLOR]	serenum!Serenum_FDOPowerComplete
			Args: 00014400 00000001 00000000 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa80105b8d60 00000000 00000000-00000000    pending
	       \Driver\Serenum
			Args: 00014400 00000001 00000000 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-fffffa8010d87160    

			Args: 00000000 00000000 00000000 00000000

 

[1metalguru]

Phil:


Not possible. The device is soldered onto the motherboard.


That's the only suggestion? How come it only started doing this a couple of weeks ago, nothing else has changed? The USB 3 ports still work fine.


MG

 

[philc43]

Something may have changed with the way the power to these devices is managed. Are there any device power management settings in Device Manager that you can experiment with for this device?

Finding the right driver may require that you go back to an older driver provided the MB manufacturer.

 

[1metalguru]

Update:


Downloaded and installed the latest driver from the MB manufacturers site.


Still no joy


What now? Buy a new motherboard?


MG

 

[1metalguru]

Another update:


I did go into the device properties and unchecked "allow the computer to turn off this device to save power"


I'll see if that has any effect...


MG

 

[philc43]

Another update:


I did go into the device properties and unchecked "allow the computer to turn off this device to save power"


I'll see if that has any effect...


MG

That's what I'd hoped you would try

 

[1metalguru]

Yeah, it didn't work though...

 

[philc43]

Try googling the terms: asmthub3 +W7 +Driver_Power_State_Failure

Hopefully you will find others with the same problem and you might be able to find a solution.

 

[1metalguru]

I think I may have gotten it.
I found a Bios update for the motherboard, installed it, and the problem seems to have been fixed.
I want to wait a few days to see how it goes before I close out this thread, but it looks promising.
Thanks for your help!


MG

 

[philc43]

Still fixed?