New
#11
How did you differ your methods during each Logitech un-installation/reinstallation?
How did you differ your methods during each Logitech un-installation/reinstallation?
I didn't change anything with the install of the drivers, still installed the latest version of the software. What I am currently running is the Logitech Gaming Software version 8.94.108. After installing the software, I booted into safe mode and disabled the Logitech Gaming Virtual Bus Enumerator driver. A google search for the driver that was causing issues, LGBusEnum.sys shows other people experiencing bsod's caused by this driver going back over a year.
The two drivers in the Logitech Gaming Virtual Bus Enumerator seem to be only LGBusEnum.sys, which according to BleepingComputer is a driver for the lcd screens on some of the older motherboards.
And LGJoyXlCore.sys, which is a driver for your Logitech joystick if you have one.
Disabling this driver therefore doesn't seem to do anything to hamper the usage of software if you don't have a lcd screen on your keyboard or a joystick. And thus far with verifier running in the background, I haven't had any crashes at all.
So given that the driver related issues seem to be solved, guess I will mark the issue as complete. Thanks for your help.
Can you please clarify:
1) how come the first time you uninstalled/re-installed it failed?
Was this luck? Or did you do something different?
This may be useful for any future failures related to this driver and/or the computer environment.
2) what did you do differently each time?
I think it is an issue with the software. It seems like the issue is recurring with the software based on this version. I wish I had some of the dump files from before I reinstalled windows to see if it was the same issue causing trouble then too.
Well I figured that all the problems were solved after I didn't receive another bsod, and then one occurred.
Was that a spontaneous bsod?
Intel driver was the misbehaving driver.
On the Asus web site enter the computer's serial or product number and download the Intel chipset or processor drivers.
intelppm.sys Intel Processor driver http://downloadcenter.intel.com/Default.aspx also at
Code:BugCheck D1, {0, ff, 0, 0}Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+23d )
It needs the .sys to make sure it is the processor driver? Otherwise it is windows? So 50/50 chance of impact?
Went to the Asus website to download the latest items to do with the chipset. Ran the Intel Management Engine Components installer and repaired the currently installed version. Also tried to download the latest Intel chipset from Asus, but the installer said it would be a downgrade from my current software. Wish I knew the best way to reproduce the issue to see if it is solved.
Earlier in the thread you had reported that you used Windows driver verifier. You could restart it to see if it finds misbehaving drivers and we could debug them.