Attempted switch from DPC in Win 11 (during games, voice chat)

Dromanthis · Dec 7, 2022

I'm getting a BSOD about once a week. The most common error code is ATTEMPTED_SWITCH_FROM_DPC. Often, the bluescreen happens too quickly for me to check.

It seems to occur most often during gaming, and while on voice chat (Discord). It could be related to graphics or audio.

I've got no overclocking, have updated drivers relentlessly, and temperatures seem fine. I've even reinstalled Win 11 twice with PC resets. This problem keeps coming back.

Link to full crash logs: WARFORGED-(2022-11-19_00-27-01).zip

Any help would be appreciated.

evo9pl · Dec 20, 2022

hello, did you manage to fix the problem. I also reinstalled Windows 11 and still have this BSOD ;(

Dromanthis · Dec 24, 2022

evo9pl said:
hello, did you manage to fix the problem. I also reinstalled Windows 11 and still have this BSOD ;(

I wish.

Had another BSOD with "MULTIPLE IRP COMPLETE REQUESTS" just last night.

The same attempted solutions as always: drivers, disk checks, memory checks. But nothing ever seems to fix it.

evo9pl · Dec 24, 2022

Hello Bro, reinstalling the graphics drivers helped me. must be removed by DDU. completely removed

Dromanthis · Dec 28, 2022

Damn. I gave DDU a try and cleaned everything completely, but still got a BSOD last night (Multiple IRP complete requests).

Thank you though.

Hoping someone out there can help. WinDbg gave me this report:

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffcf8b7c867010, Address of the IRP
Arg2: 00000000000012b1
Arg3: 0000000000000000
Arg4: 0000000000000000

.Dmp file attached for any experts out there.

zbook · Dec 30, 2022

This thread was started on 12/7/2022.

How come the V2 share link posted in the opening post was dated 11/19?

Why not post a new V2 share link?

Dromanthis · Dec 30, 2022

zbook said:
This thread was started on 12/7/2022.

How come the V2 share link posted in the opening post was dated 11/19?

Why not post a new V2 share link?

Here's a new zip file from today: WARFORGED-(2022-12-30_19-08-50).zip

zbook · Dec 30, 2022

1) Run:

https://www.elevenforum.com/attachments/tuneup_plus_log-bat.36285/

Post a share link into this thread using one drive, drop box, or google drive.

2) Uninstall: Driver Booster 10

3 Turn off Windows fast startup:

Turn On or Off Fast Startup in Windows 11 Tutorial

This tutorial will show you how to turn on or off fast startup in Windows 11. There are three startup modes in Windows: Cold (traditional) Wake-from-hibernation Fast Starting with Windows 8.x, the default shutdown and restart scenario has been updated and named fast startup. Fast startup...

www.elevenforum.com

4) Make a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

5) Read this link on Windows Driver Verifier:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Learn the methods to recover from using the tool by booting into safe mode and typing one or more of these commands:
verifier /reset
verifier /bootmode resetonbootfail

If there is no immediate BSOD then open administrative command prompt and type or copy and paste:
verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

Plan to run the tool for 48 hours with various customized test settings and an additional 24 hours after the last BSOD.

For any new BSOD post a new V2 share link into the newest post.

Dromanthis · Dec 30, 2022

zbook said:
1) Run:

https://www.elevenforum.com/attachments/tuneup_plus_log-bat.36285/

Post a share link into this thread using one drive, drop box, or google drive.

Thanks for the help - I appreciate it.

Here's Tuneup.log from step 1: Tuneup.log

I've completed steps 1-4 in order successfully.

Step 5 is of course a longer process so I'll report back later when possible.

Thanks again.

zbook · Dec 30, 2022

Tuneup plus results were good.

For WDV:

Test all non-Microsoft drivers.
Test no Microsoft drivers.
Start testing with the 3 customized tests in the TF link.

Plan to run the tool for 48 hours with various customized test settings.
And plan to run WDV for an additional 24 hours after the last BSOD.

Dromanthis · Dec 31, 2022

zbook said:
Test all non-Microsoft drivers.

zbook said:
For any new BSOD post a new V2 share link into the newest post.

Feels like this is getting somewhere, because I get an immediate BSOD using Driver Verifier while testing all non-Microsoft drivers.

Here's the new V2 link from those immediate BSODs: WARFORGED-(2022-12-31_17-51-46).zip

zbook · Dec 31, 2022

The misbehaving drivers causing the latest BSOD were:

lgvirhid64.sys
lgbusenum64.sys

lgvirhid Logitech Gamepanel Virtual HID Device Driver (64-bit) c:\windows\system32\drivers\lgvirhid64.sys

lgbusenum Logitech Gaming Virtual Bus Enumerator Driver (64-bit) c:\windows\system32\drivers\lgbusenum64.sys

1) Detach all non-essential Logitech hardware and uninstall all non-essential Logitech software.

2) Make a new restore point

3) Restart WDV with the same customized test settings

If there is no immediate BSOD then post a verifier /querysettings result share link into the newest post.

For any BSOD post a new V2 share link into the newest post.

4) After the troubleshooting has completed Logitech hardware and software can be reattached and reinstalled respectively

Dromanthis · Dec 31, 2022

zbook said:
The misbehaving drivers causing the latest BSOD were:

lgvirhid64.sys
lgbusenum64.sys

lgvirhid Logitech Gamepanel Virtual HID Device Driver (64-bit) c:\windows\system32\drivers\lgvirhid64.sys

lgbusenum Logitech Gaming Virtual Bus Enumerator Driver (64-bit) c:\windows\system32\drivers\lgbusenum64.sys

1) Detach all non-essential Logitech hardware and uninstall all non-essential Logitech software.

2) Make a new restore point

3) Restart WDV with the same customized test settings

If there is no immediate BSOD then post a verifier /querysettings result share link into the newest post.

For any BSOD post a new V2 share link into the newest post.

4) After the troubleshooting has completed Logitech hardware and software can be reattached and reinstalled respectively

Ok, this is good. My Logitech stuff is just mouse and webcam. This really narrows it down. I'm starting to guess that it's the mouse, since that gets used a lot more than the webcam.

I've unplugged them and uninstalled anything Logitech. There is no longer any immediate BSOD using WDV.

Results of verifier /querysettings here: verifier querysettings result.txt

Thanks for your help. Please let me know if I should do anything else.

zbook · Dec 31, 2022

Restart WDV with these customized test settings:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.

If there is no immediate BSOD then post a new querysettings share link.

For any BSOD post a new V2 share link.

Make sure that all non-Microsoft drivers are tested.

zbook · Dec 31, 2022

(its 2:28 AM here. I've got to go to bed and will catch up much later today.)

If there are no performance problems or very slow boot with the customized tests in the prior post and no BSOD then modify the WDV customized tests.

Run all customized tests except [ ] 0x00000004 Randomized low resources simulation. for 24 hours.

Post a querysettings before the end of the 24 hour period.
And post a new V2 share link after turning off WDV.

If there are no further BSOD then this will complete the troubleshooting.

Dromanthis · Jan 1, 2023

zbook said:
Restart WDV with these customized test settings:

If there is no immediate BSOD then post a new querysettings share link.

No BSOD on this test. Querysettings here: verifier querysettings result 2.txt

zbook said:
(its 2:28 AM here. I've got to go to bed and will catch up much later today.)

I hope my problem didn't contribute to this

zbook said:
If there are no performance problems or very slow boot with the customized tests in the prior post and no BSOD then modify the WDV customized tests.

Run all customized tests except [ ] 0x00000004 Randomized low resources simulation. for 24 hours.

Post a querysettings before the end of the 24 hour period.

For this test I definitely noticed things running slowly, but no BSOD.
Querysettings here: verifier querysettings result 3.txt

I didn't quite make 24 hours; closer to 13-15 since I needed to use the computer at a decent speed today. But I can run another 20+ hour test this week if it's still needed.

zbook said:
And post a new V2 share link after turning off WDV.

If there are no further BSOD then this will complete the troubleshooting.

Here's the V2 report (although there was no BSOD): WARFORGED-(2023-01-01_16-17-31).zip

While running these tests, I googled Logitech GHUB BSODs and found quite a few threads that matched my situation. If we've found the culprit with GHUB, then I don't know how to thank you. What an enormous weight it will be off my shoulders if this is solved.

zbook · Jan 1, 2023

There was a residual Logitech driver displayed in the V2 collected files.

Logitech USB Composite Device C922 Pro Stream Webcam

If you want to uninstall or uninstall and reinstall this driver then open administrative command prompt and copy and paste:

pnputil /delete-driver oem36.inf /uninstall /force

Reboot as needed.

The driver can be reinstalled as needed.

The WDV results look good.
There were no new BSOD.

That will complete the troubleshooting.

You're welcome.

Glad to help.

Happy New Year. :party:

Dromanthis · Jan 1, 2023

zbook said:
There was a residual Logitech driver displayed in the V2 collected files.

Logitech USB Composite Device C922 Pro Stream Webcam

If you want to uninstall or uninstall and reinstall this driver then open administrative command prompt and copy and paste:

pnputil /delete-driver oem36.inf /uninstall /force

Reboot as needed.

The driver can be reinstalled as needed.

The WDV results look good.
There were no new BSOD.

That will complete the troubleshooting.

You're welcome.

Glad to help.

Happy New Year.

Done.

Thank you for the brilliant help. I thought I'd never get this fixed. Happy new year

zbook · Jan 1, 2023

That's terrific.

You're welcome.

Dromanthis · Jan 6, 2023

It pains me to say that I've had 2 more BSODs since uninstalling Logitech.

3 Jan: WARFORGED-(2023-01-03_18-37-17).zip
6 Jan: WARFORGED-(2023-01-06_23-14-56).zip

At a loss again.