I updated to Windows 8.1 a few weeks ago and beginning this morning my laptop has been showing me a BSOD with the message MULTIPLE_IRP_COMPLETE_REQUEST before restarting. The only solutions I have been able to find involve a bug related to LogMeIn Hamachi,
a program that is not and has never been installed on my computer. Please help.
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
It did, thanks very much! This is actually a very interesting issue we have here as it appears to be widespread, so your post is actually the first analysis I am doing of it. I will blog about it later.
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.
^^ 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_0CF3&PID_3004
^^ 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
Atheros Communications, Inc. Specifically, regarding its Product ID, 3004 is not listed, but 3000, 30002, and 3005 are all related to Bluetooth (from Atheros).
Interestingly enough, in the crash dump itself, this is mentioned -- OVERLAPPED_MODULE: Address regions for 'bthport' and 'bthport.sys' overlap
bthport.sys is the Bluetooth Bus driver.
Right, so the summary so far is that we appear to possibly be having a Bluetooth related driver (appearing to be from Atheros) causing issues. Let's look forward more to confirm or deny this: