BSOD when PC goes into sleep mode

[TheOnion]

Hello,

I searched and found some other threads on this, but never saw a solution. When my Windows 7 Professional 64bit PC goes into sleep mode it will not come out. If I leave it long enough it appears to turn off. Upon restart it says it recovered from a BSOD. I have attached a picture of the mini dump for help deciphering whats wrong.

 

[theog]

Take a look at this:

http://www.sevenforums.com/crashes-debugging/48955-hotfix-3-stop-errors-resuming-sleep-hiberate.html

 

[JMH]

Hello,

I searched and found some other threads on this, but never saw a solution. When my Windows 7 Professional 64bit PC goes into sleep mode it will not come out. If I leave it long enough it appears to turn off. Upon restart it says it recovered from a BSOD. I have attached a picture of the mini dump for help deciphering whats wrong.

Welcome TheOnion,
Please provide the following information -

1. How was Windows 7 installed? Was it an upgrade installation or a clean installation?

2. Please provide red error messages in the Event Log for more information:
a. Click "Start", input "eventvwr" (without quotation marks) in the Start Search bar and press Enter.
b. Go to Windows Logs - Application - note red errors.

3.To get a more definitive idea of what is happening we may also require the dmp files. Please read this link [1 - Novice] How to ask for help with a BSOD problem
Upload all of the minidump files located in C:\Windows\Minidump

If you require more help let us know.
Thanks.

Re you pic above - FYI - ntoskrnl.exe is the kernel image for the family of MicrosoftWindows NT operating systems. It is responsible for various system services such as hardware virtualization, process and memory management, etc., thus making it a fundamental part of your system.

 

[TheOnion]

Here are my mini dump files.

The Event viewer seems to show this message with the red x's that correspond with my crash times.

Activation context generation failed for "c:\program files (x86)\microsoft\search enhancement pack\search helper\sepsearchhelperie.dll".Error in manifest or policy file "c:\program files (x86)\microsoft\search enhancement pack\search helper\sepsearchhelperie.dll" on line 2. Invalid Xml syntax.

 

[YakSipper]

Hey there.

Problems are caused by L1E62x64.sys. That's your network driver.

Update that and you should be well.

 

[TheOnion]

Hey there.

Problems are caused by L1E62x64.sys. That's your network driver.

Update that and you should be well.

Thats what I thought you would say. Problem is I have updated my network driver. A bunch of times. I am on the most current driver.

 

[YakSipper]

Try visiting Atheros' website itself for the latest, instead of motherboard manufacturer etc...

Also, completely uninstall any 3rd party firewalls as a temporary test.

 

[TheOnion]

Try visiting Atheros' website itself for the latest, instead of motherboard manufacturer etc...

Also, completely uninstall any 3rd party firewalls as a temporary test.

I had already gone to Atheros' website also. I will try the firewall thing and let you know.

 

[ickymay]

I'm not convinced it's the network driver "YakSipper" ?

as debugger shows

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80043dea20, fffff80000b9c518, fffffa80071457b0}

Probably caused by : pci.sys

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80043dea20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80071457b0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc117

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f93000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c4c8 fffff800`02adf1b3 : 00000000`0000009f 00000000`00000003 fffffa80`043dea20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02a7c6a6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`02a7ba26 : fffffa80`03dab758 fffffa80`03dab758 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02a7c57e : 00000016`8de37138 fffff800`00b9cc58 00000000`0009799c fffff800`02bee608 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02a7bd97 : 00000005`494eacc7 00000005`0009799c 00000005`494eaca3 00000000`0000009c : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a78dfa : fffff800`02beae80 fffff800`02bf8c40 00000000`00000000 fffff880`0ff23ea0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_L1E62x64_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_L1E62x64_IMAGE_pci.sys
Followup: MachineOwner

and although the driver

L1E62x64.sys fffff880`03fd2000 fffff880`03fe4000 0x00012000 0x4bb00bac 29/03/2010 03:08:44

is involved I think it's more likely your antivirus or third party firewall could be blocking access and causing the DRIVER_POWER_STATE_FAILURE (9f) ?

also very importantly you need to update ASACPI.sys ?

these are all old drivers and need replacing

ASACPI.sys fffff880`03fe4000 fffff880`03fec000 0x00008000 0x42476c4c 28/03/2005 03:30:36
snapman.sys fffff880`019b0000 fffff880`019e9000 0x00039000 0x46974de0 13/07/2007 11:03:12
tifsfilt.sys fffff880`02b2d000 fffff880`02b44000 0x00017000 0x46d56889 29/08/2007 13:37:29
timntr.sys fffff880`01895000 fffff880`01945000 0x000b0000 0x46d568bf 29/08/2007 13:38:23
tdrpman.sys fffff880`01800000 fffff880`01894000 0x00094000 0x4725d229 29/10/2007 13:29:29

ASACPI.sys is known to cause BSOD's: ASACPI.sys belongs to the Asus ATK0110 ACPI Utility (14/05/2009 is latest available)
snapman.sys is from Acronis Snapshots Manager or Acronis True Image Home or Seagate DiscWizard or Acronis True Image Workstation
tifsfilt.sys = Acronis Disk Backup Software
timntr.sys = Acronis Disk Backup Software
tdrpman.sys is Acronis again

your version of speedfan is from 2006 but I haven't known that to cause a problem ?

let us know how it goes

 

[TheOnion]

I also had a problem with my network connection not functioning upon reboot and removing the driver from device manager and Scanning for hardware changes fixed that. It found an older version of the Atheros driver that didn't cause problems. However, this did not fix my sleep mode issue.

I now agree with ickymay that its my antivirus.I am running a trial of Eset smart security. It runs out in a few weeks and I will go back to Avira Antivir. Sleep mode worked fine on Avira.

Eset makes a good antivirus product but Ive had nothing but problems with it on Windows 7 64bit. Before with Nod32 4.0 and now with Smart Security 4.2.

 

[ickymay]

I also had a problem with my network connection not functioning upon reboot and removing the driver from device manager and Scanning for hardware changes fixed that. It found an older version of the Atheros driver that didn't cause problems. However, this did not fix my sleep mode issue.

I know agree with ickymay that its my antivirus. I am running a trial of Eset smart security. It runs out in a few weeks and I will go back to Avira Antivir. Sleep mode worked fine on Avira.

Eset makes a good antivirus product but Ive had nothing but problems with it on Windows 7 64bit. Before with Nod32 4.0 and now with Smart Security 4.2.

MSE is also very good and stable , don't forget

ASACPI.sys is known to cause BSOD's: ASACPI.sys belongs to the Asus ATK0110 ACPI Utility (14/05/2009 is latest available)

 

[TheOnion]

I also had a problem with my network connection not functioning upon reboot and removing the driver from device manager and Scanning for hardware changes fixed that. It found an older version of the Atheros driver that didn't cause problems. However, this did not fix my sleep mode issue.

I know agree with ickymay that its my antivirus.I am running a trial of Eset smart security. It runs out in a few weeks and I will go back to Avira Antivir. Sleep mode worked fine on Avira.

Eset makes a good antivirus product but Ive had nothing but problems with it on Windows 7 64bit. Before with Nod32 4.0 and now with Smart Security 4.2.

MSE is also very good and stable , don't forget

ASACPI.sys is known to cause BSOD's: ASACPI.sys belongs to the Asus ATK0110 ACPI Utility (14/05/2009 is latest available)

I have heard good things about it. Maximum PC gave it an 8 out of 10 in their recent Antivirus round up. That's really good for a free antivirus product.

 

[TheOnion]

Ok so the plot thickens. I removed ESET smart security and installed Microsoft Security Essentials. I then re enabled sleep mode and walked away from my PC to see if it worked. A few hours later I come back and the PC is not in sleep mode, it's off.

It blue screened again. The latest mini dump file attached.

 

[ickymay]

Ok so the plot thickens. I removed ESET smart security and installed Microsoft Security Essentials. I then re enabled sleep mode and walked away from my PC to see if it worked. A few hours later I come back and the PC is not in sleep mode, it's off.

It blue screened again. The latest mini dump file attached.

well it's the same power state failure error so we haven't found the culprit yet although I would advise you don't change too much on your system or revert from what wev'e done yet ?

the next likely candidate I mentioned before is Acronis Disk Backup Software which you need to completely unninstall as you are using an old version which was also known to cause crashes in vista

snapman.sys fffff880`01b0e000 fffff880`01b47000 0x00039000 0x46974de0 13/07/2007 11:03:12
tifsfilt.sys fffff880`050a5000 fffff880`050bc000 0x00017000 0x46d56889 29/08/2007 13:37:29
timntr.sys fffff880`01868000 fffff880`01918000 0x000b0000 0x46d568bf 29/08/2007 13:38:23
tdrpman.sys fffff880`01a6b000 fffff880`01aff000 0x00094000 0x4725d229 29/10/2007 13:29:29

as you can see these drivers are from 2007 which predates the introduction of windows 7 :huh:

do that and monitor for crashes

 

[TheOnion]

I removed Acronis True image and it still blue screens when going into Sleep mode.

 

[Capt.Jack Sparrow]

Hello !!

Delete all the Minidump from that folder and Enable Driver Verifier http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Hope this helps,
Captain

 

[TheOnion]

I setup and ran the Driver Verifier. So far nothing.

 

[ickymay]

I setup and ran the Driver Verifier. So far nothing.

post any more .dmp files so we can look for a trend and anymore clues

 

[TheOnion]

Fresh minidump file for you. I ran the driver verifier for hours and it did not blue screen. It made my system run like mud, but no blue screen. Then I put it in sleep mode because I was sleepy and it did what it always does: Monitor looses signal, backlight LEDs on keyboard go off and it will not come back from sleep. I left it alone and went to bed. In the morning the PC was off so I turned it back on. It booted though BIOS and froze on the loading windows screen. After a reboot it got to the loading windows screen and blue screened. Then it auto rebooted and loaded into windows fine,slow,but fine. I then turned off that cursed verifier and rebooted again. Windows runs like normal now.

Attached if the new mini dump file.

 

[ickymay]

Fresh minidump file for you. I ran the driver verifier for hours and it did not blue screen. It made my system run like mud, but no blue screen. Then I put it in sleep mode because I was sleepy and it did what it always does: Monitor looses signal, backlight LEDs on keyboard go off and it will not come back from sleep. I left it alone and went to bed. In the morning the PC was off so I turned it back on. It booted though BIOS and froze on the loading windows screen. After a reboot it got to the loading windows screen and blue screened. Then it auto rebooted and loaded into windows fine,slow,but fine. I then turned off that cursed verifier and rebooted again. Windows runs like normal now.

Attached if the new mini dump file.

my thoughts are you have a driver which does not support sleep state and as driver verifier didn't crash or name a driver and this last dump has failed to catch the driver that caused the crash the only thing we can work with is driver age ?

nearly all of your drivers in the crash are from july 2009 and I am confident that they are not going to be the most current ?

please fill out your system specs such as mobo and ram makes and models etc then go to your motherboard manufacturers website and check you have all the latest drivers ?

unninstall Utorrent if you have it and please post a shortlist of your software installed including any third party firewalls etc ?

Oo and for now unninstall speedfan