The company says users need to install cumulative updates

Mar 24, 2022 20:48 GMT  ·  By

Microsoft has recently confirmed that its most recent cumulative updates resolve a Windows 10 bug causing BSODs on the impacted devices.

The company explained that in some cases, accessing devices that are connected to a Windows 10 computer via Bluetooth could lead to such errors, in some cases causing a fatal crash on the PC.

The issue was first confirmed by Microsoft earlier this month, with the company explaining a previous cumulative update was the one to blame for the whole thing.

“After installing KB5009596 or later updates, some organizations which have Windows devices paired to Bluetooth devices might receive an error message "Your device ran into a problem and needs to restart." with a blue screen and "Stop code: IRQ NOT LESS OR EQUAL". The error logged on affected devices will be in the System log in Event Viewer and will be logged as "Microsoft-Windows-WER-SystemErrorRe event 1001" with text "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a ". This issue is observed when certain Configuration service provider (CSP) policies are in place which affect the Bluetooth A2dp profile,” Microsoft said.

Patches already available

Microsoft explains that the latest optional cumulative updates available for Windows 10 come to resolve the glitch, with the company explaining that users who install the March 22 patches no longer need to do anything.

“This issue was resolved in updates released March 22, 2022 ( KB5011543) and later. We recommend you install the latest security update for your device. It contains important improvements and issues resolutions, including this one. If you install an update released March 22, 2022 ( KB5011543) or later, you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue. If you are using an update released before March 22, 2022, you can resolve this issue using KIR. This KIR will not propagate to devices automatically,” it says.

Additional information on how to deal with the bug is available here.