Solved Unusual BSOD Error when plugging in Wireless Mouse Connector Stop 0x48

[Richiebro72]

Today my laptop crashed when I was waiting for a game for Dota 2. While I was waiting for a game, I plugged in a Belkin Mouse connector for my Belkin wireless mouse which I have not used for some time. It didn't come on quickly the first time i inserted it so i removed the connector and put it into another usb port. Windows then said it was installing driver software then the screen went fuzzy and crashed. A blue screen appeared with The CANCEL_STATE_IN_COMPLETED_IRP bug check which has a value of 0x00000048 that came up. Apparently this bug check is rare. I have attached the dump files. I really appreciate it if you can have a look to see if it was in fact the mouse driver which completed the IRP (I/o request packet) and then attempted to cancel it, causing a crash or if the crash was caused by two drivers each trying to access the same IRP in an improper way? Any help would be greatly appreciated.

 

[Arc]

The BSOD took place when drvinst.exe was in operation, that means the driver was being installed.

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

CANCEL_STATE_IN_COMPLETED_IRP (48)
This bugcheck indicates that an I/O Request Packet (IRP) that is to be
cancelled, has a cancel routine specified in it -- meaning that the packet
is in a state in which the packet can be cancelled -- however, the packet
no longer belongs to a driver, as it has entered I/O completion.  This is
either a driver bug, or more than one driver is accessing the same packet,
which is not likely and much more difficult to find. The cancel routine
parameter will provide a clue as to which driver or stack is the culprit.
Arguments:
Arg1: fffffa8009e7a198, Pointer to the IRP
Arg2: 05351bcf08000000, Cancel routine set by the driver.
Arg3: 0000000000000000
Arg4: 0000000000000000

This issue occurs because of a race condition between a thread of the Redirected Driver Buffering SubSystem (Rdbss.sys) driver and a thread of the I/O Manager.

When this race condition occurs, an I/O request packet (IRP) is processed by a thread while another thread cancels this IRP. Therefore, the Stop error occurs.​

It appears that the driver is not installed at all. The I/O operation to install the driver is cancelled by the cancel routine.

Dont put any type of load to the computer. Dont run any other programs etc. Keep the computer totally idle. Then attach the mouse. Hopefully it will configure the driver.

When the driver is configured, then you may use the mouse (plug in) anytime.

BTW, how old the mouse is?

 

[Richiebro72]

Thank you for your time and detailed explanation. I inserted the mouse connector while the computer was in idle and it runs fine. The mouse is about 4 years old. I will mark this thread as solved.

 

[Arc]

Good news