Question incessant LDqdUSB WDF call failure

Inservio Letum

Distinguished
Feb 13, 2016
10
0
18,510
Morning everyone!
Having an infuriating issue with my MX Ergo trackball. While I'm in windows, everything works swimmingly. The minute I go to a fullscreen game, however, windows starts spamming me with device connection & disconnection noises. Checked the log, turns out something is clearly hinky :



Can someone help me work out what on EARTH is going on and why my mouse keeps turning on and off?
So far the only solution has been to keep a wired mouse handy JUST for Factorio, but having paid this much for a trackball, I'd kind of like it to just work.
 
Look in Task Manager > Startup and also Task Scheduler.

Do you see any apps, utilities, etc. that are game and/or mouse related?

Overall, my immediate suggestion would be to manually download the trackball drivers directly from the manufacturer's website. No third party tools or installers.

Reinstall and reconfigure as applicable.
 
I did that, and while there are rather a LOT of things related to peripherals and corresponding software, this problem concerns Unifying SetPoint. At least... the trackball is paired to a Unifying receiver, and the file the event viewer mentioned, is part of SetPoint. I did that specifically so I can pull the dongle and swap it to different machines in the knowledge that my trackball will just always work without hassle. I want to use SetPoint rather than Options+ because having to log in every time I open my laptop is driving me bonkers.

The LE thing makes me wonder... can this is a power issue? I have all powersaving options turned off, never use sleep or hybrid, but somehow when I'm on Win10 my wireless peripherals eventually all seem to go into some kind of sleep mode that they can then not be awoken from. I literally have to unplug the peripheral in question and plug it back in.
 
Another way to look at what may be happening is to use Process Explorer (Microsoft, free).

https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

Run the tool and watch for a bit to gain some sense of what all is happening.

Minimize the window or, even better if possible, use a second monitor to watch.

Then work, game, etc. and pay attention to what changes when the spamming and so forth begin.

= = = =

As for power problems:

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s)? Make, model, capacity, how full?
 
Oh wow... The PSU is going to be hard to describe, as this is a laptop. Lenovo's Legion 5.
Here's what Speccy spat out :
CPU
AMD Ryzen 7 5800H78 °C
Cezanne 7nm Technology
RAM
32.0GB Dual-Channel DDR4 @ 1596MHz (22-22-22-52)
Motherboard
LENOVO LNVNB161216 (FP6)
Graphics
Generic PnP Monitor (2560x1600@165Hz)
4095MB NVIDIA GeForce RTX 3070 Laptop GPU (Lenovo)68 °C
Storage
953GB SKHynix_HFS001TDE9X084N (264Gb free)
 
What other wireless peripherals are in use?

And just how do you go about moving wireless peripherals about?

Simply unplugging an replugging a dongle/device may not correctly present the peripheral to the hosting device. And the last host could be still "looking for" the device which is now gone.

You should certainly be able to move the trackball between devices. But you may need a couple more "steps" to do so.

Before "pulling the plug" try going through the USB removal/disconnect options.
 
Aaaaaah, see now THAT I didn't keep track of. I normally have the computer off by the time I unplug, which might mean windows looks for the device when powering on. Never realised that could happen.

Bit of a design oversight though, don't you think? In any case I'll disconnect the peripherals before shutting down, see if that problem still occurs. Thanks for the warning! :)