Page 2 of 4 FirstFirst 1234 LastLast
  1.    15 Jul 2017 #11
    Join Date : Apr 2017
    Posts : 8,584
    windows 10 professional version 1607 build 14393.969 64 bit

    How did you differ your methods during each Logitech un-installation/reinstallation?
      My ComputerSystem Spec
  2.    15 Jul 2017 #12
    Join Date : Jul 2017
    Posts : 15
    Win 10 64bit
    Thread Starter

    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.
      My ComputerSystem Spec
  3.    15 Jul 2017 #13
    Join Date : Apr 2017
    Posts : 8,584
    windows 10 professional version 1607 build 14393.969 64 bit

    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?
      My ComputerSystem Spec
  4.    15 Jul 2017 #14
    Join Date : Jul 2017
    Posts : 15
    Win 10 64bit
    Thread Starter

    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.
      My ComputerSystem Spec
  5.    17 Jul 2017 #15
    Join Date : Jul 2017
    Posts : 15
    Win 10 64bit
    Thread Starter

    Well I figured that all the problems were solved after I didn't receive another bsod, and then one occurred.
      My ComputerSystem Spec
  6.    17 Jul 2017 #16
    Join Date : Apr 2017
    Posts : 8,584
    windows 10 professional version 1607 build 14393.969 64 bit

    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.



    Code:
    BugCheck D1, {0, ff, 0, 0}Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+23d )
      My ComputerSystem Spec
  7.    17 Jul 2017 #17
    Join Date : Jun 2015
    Posts : 12,854
    Windows 10 Pro

    I don't see the processor driver flagged?
      My ComputersSystem Spec
  8.    17 Jul 2017 #18
    Join Date : Apr 2017
    Posts : 8,584
    windows 10 professional version 1607 build 14393.969 64 bit

    It needs the .sys to make sure it is the processor driver? Otherwise it is windows? So 50/50 chance of impact?
      My ComputerSystem Spec
  9.    17 Jul 2017 #19
    Join Date : Jul 2017
    Posts : 15
    Win 10 64bit
    Thread Starter

    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.
      My ComputerSystem Spec
  10.    17 Jul 2017 #20
    Join Date : Apr 2017
    Posts : 8,584
    windows 10 professional version 1607 build 14393.969 64 bit

    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.
      My ComputerSystem Spec

 
Page 2 of 4 FirstFirst 1234 LastLast


Similar Threads
Thread Forum
BSOD on fresh install
Just did a fresh install a couple days ago, and still getting multiple BSOD`s. I have basicly just let the rig sit there with the power on to see if it was stable. It was not.... I have not installed any drivers or anything myself. Just...
BSOD Crashes and Debugging
Fresh Install, All New Hardware, Persistant BSOD on install
I was experiencing a BSOD during Windows 10 Pro x64 installation on a freshly built computer, the installation would get to 80% 100% and BSOD with a variety of errors, mostly IRQL_NOT_LESS_OR_EQUAL After about 10 attempts with different...
BSOD Crashes and Debugging
Various BSOD after fresh win 10 install
Hello everyone, I am having a huge problem since 4 days with my desktop PC. I had windows 8.1 running and had lots of different BSODs. I then decided to format my SSD (128GB) and install fresh windows 10. At the beginning (first hours) everything...
BSOD Crashes and Debugging
BSOD loop on boot from fresh Win 10 upgrade over fresh Win 7 install
This is on an old eMachines M6805 laptop that originally came with XP 32-bit. I put a fresh install of Windows 7 32-bit on it which ran fine. I then upgraded that to Windows 10 32-bit. The first time it booted up I was able to log in but got a...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:06.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums