Question BSOD from Logitech G Hub?

[mr blasto]

Background: I just built two identical PCs and both are getting BSODS, and it seems highly likely the issue is related.

Motherboard: ASRock B450M Pro4 with the latest BIOS (P3.60)

Processor: AMD Ryzen 3 2200g

Windows 10 Home no updates available as of writing this.

When I first started getting the BSOD, I used BlueScreenView to view the Minidump files. The common issue that kept popping up seemed to be a problem with ntoskrl.exe.

So I ran the extended Windows Memory Diagnostics and no problems were discovered.

I used Driver Booster 7 to quickly update all of my drivers.

Then I ran Windows Driver Verifier, and was not having any problems on one PC. On the other PC, it was getting a BSOD shortly after logging into windows. Sometimes it would get stuck before then. But it never seemed to last more than a minute after logging into windows before BSOD. I turned off the Driver Verifier, and the problem seemed to be logi_joy_vir_hid.sys and HIDCLASS.SYS.

This PC that would crash very quickly had logitech g hub set to start on start-up and the LED colors on the G502 Hero mouse indicated it was running.

On the PC that wasn't crashing, the LED colors (also on a G502 Hero mouse) were the default ones, which made me wonder what would happen if I turned G Hub on on that PC. The result was a BSOD as ghub was launching (again Driver Verifier is still running on this PC, but it is far more stable because g hub wouldn't launch on start up).

The obvious answer is, don't use G hub, which would kind of suck, because I want to be able to control the LEDs, mouse buttons, dpi, and other mouse settings easily.

However, without running Driver Verifier, we were both getting BSODs at a much lower rate while running G Hub.

Not sure how to get these things as stable as possible as soon as possible, but that's what I'm after. On both PCs, the device manager indicates the driver for the mouse was published by Microsoft in 2006 (10.0.18362.1), so it doesn't look like they are using anything from logitech.

Here are the minidumps from the PC that was running g hub on startup: https://1drv.ms/u/s!AlIE3vqqC9biq3pCfXCLlHfoHpVR?e=aLI5J9

Here are the minidumps from the other pc: https://1drv.ms/u/s!AlIE3vqqC9biq35VnMmKO5w_mUVM?e=vNtazV

First post on here, so my apologies if I did something wrong.

 

[mr blasto]

In case anyone finds this, here's an update:

I messaged Logitech and they suggested I uninstall G Hub and reinstall as admin. Uninstall turned out to be fairly cumbersome. If I fired up G Hub, BSOD. I tried to use the Windows 10 uninstaller, but nothing would happen. I resorted to using Revo uninstaller, but it didn't get everything. After trying to track down and delete left over Windows Registry entries related to G Hub, I finally used ccleaner as a shortcut to clean that up. After all that, some drivers still remained. Trying to delete the drivers didn't work, so I manually changed the file extensions on them from .sys to .bup, which seemed to take care of everything.

I kept Windows Driver Verifier running while leaving my PC alone over Thanksgiving weekend and was pleasantly surprised that it stayed up an running that whole time without any BSODs. Of course, only a few programs were running but I wasn't using it over that time. That being said, similar circumstances resulted in BSOD previously, so I was pretty thrilled.

Logitech support suggested I reinstall G Hub as an administrator, but I'm hesitant. I've read that Logitech Gaming Software seems to give people fewer problems, so I'm tempted to try that, but still worried. I'll probably give it a try out of morbid curiosity.

 

[mr blasto]

Upon running Logitech Gaming Software and Windows Driver Verifier, I immediately got BSOD during the boot process. Fortunately, Windows was able to fix the issue and when it finally booted up, LGS was no longer on the computer and verifier was not running. I'm assuming it used a restore point I created right before installing LGS.

Looks like I'm stuck with the G502 Hero mouse cycling through random colors because the logitech software to control is seems to be creating problems for me. Pretty frustrating. If anyone has run into this and found a work around, I'd love to hear what you did.