BSOD on laptop lid close


  1. josh08
    Posts : 4
    Windows 7 Home Premium 64bit
       New #1

    BSOD on laptop lid close


    I have a relatively new ASUS laptop running Win7 64bit which has developed a problem with crashing when the lid is closed. When I open the lid, it wakes up normally maybe only 20% of the time. The rest of the time either the screen remains black and the computer wakes up or I get a blue screen which says something like 'driver power state failure'. I've tried updating all of the drivers posted on ASUS's website for this model but it has not helped.

    Attached is the output from the SF diagnostic tool.

    Thanks in advance,
    Josh
      My Computer
    Quote Quote

  3. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #2

    Welcome to SevenForums.

    Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATHEROS (Restart the system) Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper

    If its wireless, match your device from here:

    If its not a wireless, match your device from here:

    System File Checker:
    • 1. Click on the
      2. Type CMD on Search
      3. Left click and Run as Administrator
      4. Type SFC /scannow

    Full tutorial here:

    Disk Check:

    Free up start-up:

    Daemon Tools

    Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

    As an alternative, many people recommend the use of Total Mounter or Magic ISO

    Postback results.
      My Computer
    Quote Quote

  4. josh08
    Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       New #3

    Thanks for the reply.

    I uninstalled all of the atheros (wireless card) drivers and reinstalled from the link you provided, ran all of the checks you recommended, and uninstalled daemon tools / sptd.sys.

    Unfortunately, I am still getting BSODs and black screens on lid close/suspend. The BSODs are still DRIVER_POWER_STATE_FAILURE and when it goes to a black screen the power light remains lit and the hard drive light flickers until I hold the power button down for 4 seconds to turn the machine off.
      My Computer
    Quote Quote

  6. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #4

    Please upload all latest files.
      My Computer
    Quote Quote

  7. josh08
    Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       New #5

    Ok, latest files are attached.
      My Computer
    Quote Quote

  8. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #6

    It crashes on the same atheros stuff and I suspect a hardware problem here.

    To eliminate that possibility.

    Perform a clean install of windows following this tutorial:

    Avoid the Factory Bloatware that comes with the laptop:

    If a clean install does not fix these issues you may have to take it to the retailer and see what they have to say.

    Post back results.
      My Computer
    Quote Quote

  10. josh08
    Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       New #7

    Ok, I'll try that. Should I try re-seating the chip first? It is easily accessible right next to the ram slots under a cover on the bottom of the laptop.

    Can you point me to exactly where in the logs you are seeing the crash? I just want to have something more to say to ASUS than "some guy on a forum said it was a hardware problem"

    Thanks so much for your help.
    -Josh
      My Computer
    Quote Quote

  11. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #8

    Should I try re-seating the chip first? It is easily accessible right next to the ram slots under a cover on the bottom of the laptop.
    Yup
    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8005c73a10, fffff80004de13d8, fffffa800c8f1560}

Probably caused by : pci.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8005c73a10, Physical Device Object of the stack
Arg3: fffff80004de13d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800c8f1560, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88001000000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80004DE7FB0

STACK_TEXT:  
fffff800`04de1388 fffff800`033476d2 : 00000000`0000009f 00000000`00000003 fffffa80`05c73a10 fffff800`04de13d8 : nt!KeBugCheckEx
fffff800`04de1390 fffff800`032e7c3c : fffff800`04de14c0 fffff800`04de14c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`04de1430 fffff800`032e7ad6 : fffff800`03484f20 00000000`00127780 00000000`00000000 fffffa80`08e6b1c4 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04de14a0 fffff800`032e79be : 0000002b`f5485b49 fffff800`04de1b18 00000000`00127780 fffff800`03453288 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04de1af0 fffff800`032e77a7 : 0000000a`b53602c1 0000000a`00127780 0000000a`b53602e9 00000000`00000080 : nt!KiTimerExpiration+0x1be
fffff800`04de1b90 fffff800`032d4cca : fffff800`0344fe80 fffff800`0345dcc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04de1c40 00000000`00000000 : fffff800`04de2000 fffff800`04ddc000 fffff800`04de1c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_athrx_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_athrx_IMAGE_pci.sys

Followup: MachineOwner
---------
    Code:
    !irp fffffa800c8f1560
Irp is active with 5 stacks 3 is current (= 0xfffffa800c8f16c0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0  0 fffffa8008bb0050 00000000 00000000-00000000    
	      Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 \Driver\athr
			Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 fffffa800879f970 00000000 fffff80003521200-fffffa800b966600 Success Error Cancel pending
	       \Driver\vwifibus	nt!PopSystemIrpCompletion
			Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800b966600    

			Args: 00000000 00000000 00000000 00000000
    Also check how the computer acts when closing the lid with the chip disconnected.

    Enabling/Disabling USB selective suspense may help as well:
      My Computer
    Quote Quote

 

  Related Discussions
BSOD when i close my laptop lid
in BSOD Help and Support

When i close my laptop lid, it goes to sleep, but im having this blue screen for quite a few days... though not constantly. Can you please take a look at it and tell me the problem? Thanks!
BSOD on laptop lid close.
in BSOD Help and Support

For the past 3 days I have been getting the BSOD when I shut my laptop lid. I have uploaded the dump files here. Can anybody help me? I don't know how to read them :( https://www.dropbox.com/s/r5uvnw55i151y52/dump%20files.zip
Good Evening Ladies and Gentlemen, Recently I have been having issues with my computer dropping my WiFi signal at home despite still being able to access the internet via my phone, xbox, and also my roommates using it as well. On top of this I also noticed that I get the BSOD when I close my...
Several BAD_POOL_CALLER errors. Alienware laptop running Windows 7 Pro 64-bit on an Intel Core i7 chipset. The error is replicable basically every time the computer comes out of sleep. Tried updating the drivers for Realtek Audio, etc. as those are often implicated in these problems, based on...
BSOD When I close laptop lid
in BSOD Help and Support

Hi I have an Intel Spring Peak laptop running Windows 7 Professional 32 bit. Whenever I close the lid, and leave it to sleep for ~3+ minutes, I get a BSOD when I open up my computer again. Its really sad. I would attach the dump file but I forgot where I could find those.... Any solutions? and...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 01:48.
Find Us