New
#171
I can only guess that you mean to extract the driver in question from the Logitech gaming software installation package :/
I can only guess that you mean to extract the driver in question from the Logitech gaming software installation package :/
I tried updating LGBusEnum.sys from within Device Manager but I'm not sure it's been successful.
M-MAXIMUSXHERO (2018-04-09 12 24).zip
Please report the progress with the steps in post #164.
What did you do?
What still needs to be done?
I will uninstall LGBusEnum.sys and see whether the Microsoft driver allows the keyboard to work and will continue Driver Verifier.
In post #164 you say to "Download a replacement driver to the desktop." from Logitech Support + Downloads
I cannot find a LGBusEnum.sys file to download anywhere on that page. Please show me the replacement driver your referring to.
Please open the contact us link for Logitec and place a support request seeking help for a replacement of the misbehaving driver.
It appears that the driver is available from the software as compared to the website.
This is information about the current Logitech software/drivers:
Code:Logitech Gaming Virtual Bus Enumerator oem44.inf 8.85.75.0 True 20160613000000.******+***Logitech Gaming Virtual Keyboard oem42.inf 8.85.75.0 True 20160613000000.******+***Logitech Gaming Virtual Mouse oem42.inf 8.85.75.0 True 20160613000000.******+***Code:lgbusenum Logitech Gaming Virtual Bus Enumerator Driver c:\windows\system32\drivers\lgbusenum.sys Kernel Driver Yes Manual Running OK Normal No YesCode:LGBusEnum.sys Mon Jun 13 13:47:08 2016 (575EFFAC)
Code:BugCheck 1000007E, {ffffffffc0000005, fffff80173ba3901, ffffaf89d040ec78, ffffaf89d040e4c0}Code:ffffaf89`d040df60 fffff802`e66e3135Unable to load image \SystemRoot\system32\drivers\LGBusEnum.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for LGBusEnum.sys*** ERROR: Module load completed but symbols could not be loaded for LGBusEnum.sys LGBusEnum+0x3135
If I uninstall the Logitech Gaming Software perhaps that will uninstall the driver, at least then we can move on with the troubleshooting. Another option I thought of is to exclude the LGBusEnum.sys from Driver Verifier to allow the troubleshooting to continue. I can deal with the Logi driver and Logitech support inbetween. Plan?
Either of the options works.
However there will be times in which windows driver verifier is off and there can be spontaneous BSOD.
So it is best to uninstall the software and driver and use the Microsoft default driver if this is possible.