Solved bsod when going to sleep/hibernate on asus k53e

[vv75]

i have bsods when the laptop is going to sleep or hibernate. from what i've analyzed the crashdumps myself with windbg, there's some driver that hangs at handling an IRP. i don't have symbol files on this system, so windbg didnt tell me what driver is that.

attached are my minidumps. can someone have a quick look at the most recent ones and tell me what driver(s) causes the problem?

 

[Arc]

Hello vv75.

It is caused by Atheros network adapter driver.

!irp fffffa800bb2dc10
Irp is active with 5 stacks 3 is current (= 0xfffffa800bb2dd70)
 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 fffffa800a898050 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
*** WARNING: Unable to verify timestamp for ndis.sys
*** ERROR: Module load completed but symbols could not be loaded for ndis.sys
 \Driver\athr
            Args: 00014400 00000000 00000004 00000002

Which is an old one.

lmvm athrx
start             end                 module name
fffff880`05480000 fffff880`0572a000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
   [COLOR=Red] Image name: athrx.sys
    Timestamp:        Tue Oct 04 12:19:29 2011 [/COLOR](4E8AAC79)
    CheckSum:         002B1FA7
    ImageSize:        002AA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from ATHEROS drivers for Microsoft Windows (Atheros?????)

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Uninstall the programs:

Start Menu\Programs\ASUS    Public:Start Menu\Programs\ASUS    Public
Start Menu\Programs\ASUS Utility    Public:Start Menu\Programs\ASUS Utility    Public

Let us know the results.

 

[vv75]

thank you. yes, athrx.sys is the atheros wifi card driver. and it's the freshest available from asus k53e downloads.
i tried the link you provided, thank you very much again, the driver from there installed fine (also seems to reflect that atheros was bought by qualcomm).
results... we need time to see the results, the problem does not reproduce at my will.

 

[Arc]

Wait and see how it goes, let us know the results. OK?

 

[vv75]

nah. same shit. new minidump attached.

 

[Arc]

Do it again ... first uninstall the driver using |MG| Driver Fusion (Driver Sweeper) 1.2.0 Download.

If its wireless (Atheros AR9002WB-1NG Wireless Network Adapter), match your device from here:

• ATHEROS Wireless drivers for Windows

If its not a wireless (Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20)), match your device from here:

• ATHEROS Network drivers for Windows

Also, disable USB selective suspense. http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html

Uninstall Avast using Avast Uninstall Utility.
Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download and install those, and then run full system scans with both of them, one by one.

Let us know the results.

 

[vv75]

yes, it's wireless. the ethernet driver doesn't involve athrx.sys. iuninstalled the driver repeatedly, checking the box "also delete driver from system" until windows said it doesn't have any driver for this device. then installed the driver from atheros.cz again.
again, time is needed to see if it's solved...

 

[vv75]

no luck. new minidump.
and i'm not surprised, atheros is in fact the stupidest brand of all wifi world, even the cheapest ralink is of much better quality.

 

[vv75]

it seems that i found an even newer driver for this f*ing atheros, Qualcomm Atheros AR9000 Series Wireless LAN Driver for Microsoft Windows | HP® Support
(.200, the existing one is .75)

 

[Arc]

Last crash was also the same .... what is the situation after applying the newer driver?

 

[vv75]

same shit. i just wanted to post, i had it again about 5 minutes ago. i suspect that Atheros is simply illiterate when it comes to drivers. their purpose was just to make some fuzz, then sell the company, and that is precisely what they did. they never cared about making WORKING products.

 

[Vir Gnarus]

Yeah, so far it's looking like the wifi driver is just being stupid. The hung IRP is held up because of a c00000bb error, which means that the request given is not supported. Most likely it's because the driver is bickering about the remove device power IRP that's been thrown at it.

I think two things you may try to do as a workaround is first to go into Device Manager and go to the Atheros wifi properties and see if there is a Power Management tab you can mess with, as well as any possibly related settings in the Advanced tab. Second thing you can do is go into your Power Options and then configure the advanced settings for it pertaining to your wifi device if present.

TBH, this system looks like it's a desktop PC and not a laptop. Is it? If so, why put it in sleep or hibernate?

Printout of latest crashdump's hung IRP, with switch to show extra info:

0: kd> !irp fffffa800d6a7760 1
Irp is active with 5 stacks 3 is current (= 0xfffffa800d6a78c0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800d6a7780
ThreadListEntry.Blink = fffffa800d6a7780
IoStatus.Status = [COLOR=Red]c00000bb[/COLOR]
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800d6a77d8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa8006e270b8
Tail.Overlay.ListEntry.Blink = fffff80003641b00
Tail.Overlay.CurrentStackLocation = fffffa800d6a78c0
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     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 fffffa800a87b050 00000000 00000000-00000000    
           \Driver\athr
            Args: 00014400 00000000 00000004 00000002
 [ 16, 2]   0 e1 fffffa800a8a8e10 00000000 fffff800036de200-fffffa800c913570 Success Error Cancel pending
           \Driver\vwifibus    nt!PopSystemIrpCompletion
            Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800c913570    

            Args: 00000000 00000000 00000000 00000000

 

[vv75]

no, it's a laptop, an asus k53e. what makes you think it looks like a desktop? it's my workhorse, and it probably has some software usually found on desktops?
following your advice, i now disabled the only power-related checkbox that there is in the Power Management tab of the problematic device driver. i disabled usb selective power-off when you advised earlier, but had the last bsod since then.

 

[Vir Gnarus]

If you haven't already, you may also wanna go ahead and update BIOS and drivers for your chipset, audio and NIC, since either of those can impede (audio shares resources with network devices). Other than that, I don't know what to tell you. I suppose I could look at a kernel dump (MEMORY.DMP in Windows dir) and I can try scrutinizing over that.

 

[vv75]

didnt help. bsod again.

 

[Arc]

http://www.sevenforums.com/crashes-debugging/268343-bsod-when-going-sleep-hibernate-asus-k53e-2.html

Option two, point 4. Download the registry and merge it. At the next crash, it will be written in the memory dump. Then upload it, Vir will take a look, as he said in hil last post.

 

[vv75]

if i free the startup, i cannot work on this laptop as usual. and i cannot just sit and sleep+resume it in cycle, hoping that a crash will occur. it's a floating bug and it happens when it wants, not when i want.

it's obvious that atheros simply lacks literate driver development, our dances will not fix anything. the most that i can afford is disable the atheros wifi alltogether, plug in a cheap chinese thumb usb wifi adapter that i have in my collection, live without problems for, say, a week, then draw conclusions.

 

[vv75]

bsods disappeared after windows got fresh updates during this year.

 

[Arc]

Good to know.

 

[Vir Gnarus]

Did the Windows updates include device drivers for your wifi? Usually those show up as optional or sometimes recommended updates, and perhaps a new driver version fixed the problem. I just want to ensure that this is either a new wifi device driver that fixed it or a Windows patch that did.