Question
209 views

Windows 8.1 BSOD (Multiple IRP Complete Requests)

AndyEnglish asked on

There are several threads for this error but it seems each instance is unique, so I'm linking my Minidump info here. I'm running Windows 8.1 on an Aspire V5-552G-X414. (Quad Core A10, 6GB of RAM). The crashes occur seemingly at random so I have no idea what specifically is malfunctioning.

Minidump:

DMP

1 person had this question

Abuse history


The answered status icon Answer
Patrick Barker replied on

Thank you very much!

The attached DMP file is of the MULTIPLE_IRP_COMPLETE_REQUESTS (44) bug check.

This indicates that a driver has tried to request an IRP be completed that is already complete.

3: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffd000`20847518 fffff800`b6ba5b4b : 00000000`00000044 ffffe000`040cd490 00000000`00000f8a 00000000`00000000 : nt!KeBugCheckEx
ffffd000`20847520 fffff800`01a0d389 : ffffffff`ffffffff ffffe000`021ab000 ffffe000`021ac0e0 ffffe000`70627375 : nt! ?? ::FNODOBFM::`string'+0x2a9ab
ffffd000`20847630 fffff800`01a0c91d : fffff780`00000302 ffffe000`01c8ba0c ffffe000`021ac0e0 ffffe000`021ab1a0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x979
ffffd000`208477d0 fffff800`01a0c3b8 : ffffe000`01c8bb44 ffffe000`021ac178 ffffe000`021ab1a0 00001ded`00001e00 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x21d
ffffd000`20847830 fffff800`01a0c12e : 00000000`00001000 ffffe000`021ab050 ffffd000`20847a02 00000973`3da83755 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x238
ffffd000`208478a0 fffff800`b6a77d10 : ffffd000`20847a20 fffff800`b6a1d000 ffffd000`20847ad0 00000000`00000f44 : USBPORT!USBPORT_Xdpc_Worker_IocDpc+0x1fe
ffffd000`20847920 fffff800`b6a779f0 : ffffe000`00000000 00001f80`00000001 ffff4497`4bc5e969 00000000`00000002 : nt!KiExecuteAllDpcs+0x1b0
ffffd000`20847a70 fffff800`b6b6e7ea : ffffd000`207dc180 ffffd000`207dc180 00000000`00000000 ffffd000`207e8240 : nt!KiRetireDpcList+0xd0
ffffd000`20847be0 00000000`00000000 : ffffd000`20848000 ffffd000`20841000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

^^ Pretty interesting call stack! As we move up, we can see that it calls to retire the DPC list, and then it makes a call to execute all DPCs. We then call into the USBPORT driver and have a few worker routines going on, which inevitably call into the bug check. I have seen many threads like this, so I assume it's a bug with perhaps a new Windows Update KB, or an issue when updating from 8.1 > latest Service Pack (update).

-- FAILURE_BUCKET_ID:  0x44_IMAGE_ACPI

We can see that by default, WinDbg notes that the cause of the crash was the Advanced Configuration and Power Interface (ACPI). Essentially, in its simplest terms, it brings power management under the control of the operating system, as opposed to the previous BIOS-central system which relied on platform-specific firmware to determine power management and configuration policy.

-- ADDITIONAL_DEBUG_TEXT:  USB\VID_0489&PID_E04E

^^ WinDbg provides us with a Vendor/Product ID, which we can sift through a database to find out which device this specifically is. 0CF3 regarding a Vendor ID falls under Foxconn / Hon Hai. Specifically, regarding its Product ID, E04E is not listed, however the others are related to Bluetooth, so this may be similar.

---------------------

BugCheck 44, {ffffe000040cd490, f8a, 0, 0}

3: kd> !irp ffffe000040cd490 1
Irp is active with 8 stacks 7 is current (= 0xffffe000040cd710)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = ffffe000040cd4b0
ThreadListEntry.Blink = ffffe000040cd4b0
IoStatus.Status = c0000001
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 = ffffe000040cd508
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 00000000
Tail.Overlay.ListEntry.Blink = 00000000
Tail.Overlay.CurrentStackLocation = ffffe000040cd710
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
 [  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
 [  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
*** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
>[  f, 0]   0 e1 ffffe000023ee050 00000000 fffff8000344f460-ffffe000003bf180 Success Error Cancel pending
           \Driver\usbohci    btfilter
            Args: ffffe00002f63dd0 00000000 00220003 00000000
 [  f, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: ffffe00002f63dd0 00000000 00220003 00000000

^^ Bingo! btfilter.sys is the Atheros Bluetooth driver.

3: kd> !devstack ffffe000023ee050
  !DevObj   !DrvObj            !DevExt   ObjectName
  ffffe0000244e2e0 *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
 \Driver\usbfilter  ffffe0000244e430  
  ffffe0000245d050  \Driver\usbhub     ffffe0000245d1a0  00000030
  ffffe0000244ebf0  \Driver\usbfilter  ffffe0000244ed40  
  ffffe0000244e040  \Driver\ACPI       ffffe000003d44f0  
> ffffe000023ee050  \Driver\usbohci    ffffe000023ee1a0  USBPDO-3
!DevNode ffffe0000244e8e0 :
  DeviceInst is "USB\ROOT_HUB\4&312d70b8&0"
  ServiceName is "usbhub"

^^ Here's where we can see mention of ACPI, and other USB related drivers (even the root hub of USB).

---------------------

1. Ensure all of your USB drivers are up to date via the manufacturers website (so in your case as you appear to have an Acer system, you'd go here http://us.acer.com/ac/en/US/content/drivers).

2. Ensure all of your Bluetooth drivers (Atheros specifically) are up to date as well via Acer's website.

Regards,

Patrick

Debugger/Reverse Engineer.
1 person found this helpful

Abuse history


progress