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.
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:
Code: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 = c00000bb 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
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.
Last edited by vv75; 12 Dec 2012 at 16:20.
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.
didnt help. bsod again.
https://www.sevenforums.com/crashes-d...us-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.
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.
bsods disappeared after windows got fresh updates during this year.
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.
Quote