Sorry for my absence - I think I forgot to turn notifications on, and then I was traveling and totally forgot about checking
Please remove the Game Panel software as kemical suggests. It's driver dates from 2009, so it may have troubles coping with W10.
After the removal, if the BSOD's still occur (and presuming that the xusb22.sys driver remains uninstalled), then try Driver Verifier again.
Also, ensure that the Microsoft wireless XBox controller software is removed also - as the xusb22.sys driver was in this memory dump.
Once those 2 are removed, if the BSOD's continue, please run Driver Verifier. Even if it was run before, removing the xusb22.sys driver and the Logitech GamePanel drivers will give it a fresh look at the system - and will hopefully force the system to give up the name of the actual offending driver.
Here's the scenario that I think is happening:
- a driver/drivers writes to memory space owned by another driver.
- then the offending driver exits
- then, after a while, the other driver checks that memory space, sees unexpected data, freaks out and crashes to a BSOD.
As the offending driver has exited, there's no way to tell what caused it - so the debugger points to the driver that it occurred in.
Beyond that, I think it's a good idea to start the Hardware Stripdown also.
I can't recall if you've tested your memory either - but MemTest86 or MemTest86+ along with Prime95 would be advised to help rule out memory issues. (my list of diagnostics is here: Hardware Diagnostics
Also, there was a video driver (actually DirectX) in the raw stack text - so trying the video tests would be a good idea also.