Windows 10: Blue screen when installing device drivers after October 2019 update, Haswell platform

Hi there,


This is the second question I've asked pertaining to this issue as I had previously thought it resolved after the November 2019 update, but it has since returned and I have more symptoms to report. I'll start with my specs:

MSI Z97A Gaming 7 Motherboard Z97 platform with USB 3.1 support

Intel Core i5 4690k

Kingston HyperX Savage 2x8GB DDR3 1866

MSI Radeon R9 390 Gaming 8G

Samsung SSD 840 Pro 256GB Boot drive

Seagate Barracuda 7200RPM 2TB drive the latest one with 256MB cache I believe; whatever model is currently on Amazon UK

Corsair RM750x power supply


After installing the October 2019 update, my machine would sometimes freeze a few seconds after logging on, which could be remedied with a reboot. With some brief investigation I found AppXSvc to be the culprit and have disabled it. Then I went to update my drivers for my AMD R9 390 graphics card and got the same issue, and around this time the utility software for other devices stopped working, giving bad image errors code 0xc000012f pertaining to various DLLs. Reinstalling these proved to cause the same crash as the graphics drivers. After a failed system restore to try and remedy a failed driver install, the OS became unrecoverable and I repaired the installation with a recovery drive of the October 2019 build. Alas, my woes persisted, so I have again disabled AppXSvc and had to use device manager to install my graphics drivers, which only worked once; I now can't update them. After the November update, my peripheral drivers briefly worked again, although graphics drivers did not, and they have all since relapsed. All installations will occasionally blue screen shortly after freezing with a MACHINE CHECK EXCEPTION, except for my chipset drivers, which will promisingly get most of the way through before throwing a CLOCK WATCHDOG EXCEPTION. Both of these are pretty serious and initially led me to believe my hardware was dying, but I have run rigorous tests on my RAM, CPU and disks to verify they're operating correctly even swapping my RAM modules over to the other channel, and my machine runs games very stably with the expected performance. It also doesn't explain why the issues only started after a Windows update. After seeing the CLOCK WATCHDOG EXCEPTION for the first time yesterday, I tried disabling HPET in the BIOS even though the OS isn't using it. Interestingly it almost made things worse, with the system refusing to boot about 1 in 3 times. I'm at my wit's end trying to solve this problem, and I really want it over and done with as I got a Logitech G29 wheel for Christmas and I can't even use it since I can't install the relevant version of Logitech Gaming Software. I have version 5 installed for my old Driving Force GT; older and less complex driver utilities seem to work fine. Even if sticking with pre-October 2019 build for the rest of time was an acceptable solution, I can't as I reinstalled the OS with that build and thus lost the ability to roll back.


I have a couple more leads as to the ultimate culprit:

After a failed install, the LCore component of Logitech Gaming Software protested that there was an issue loading the Qt framework. After using the echo %PATH% command in cmd prompt I found that most of the programs referenced in the PATH list were the ones giving me trouble.

I checked Event Logs and found the occasional error with event code 35 under Kernel-Processor-Power, which indicates an incompatibility with motherboard or chipset firmware. I have the latest BIOS, and would love to update the chipset drivers, but as established they themselves chuck a hissy fit when I try.

Shortly after my OS reinstall, I tried to play Dota 2 and upon entering a match was met with a blue screen that referenced a DLL in my Killer Ethernet drivers, which was never seen again after reinstalling those. I've had problems with this driver causing memory leaks in the past and generally being a pain, so perhaps Realtek's incompetence knows no end and has once again ruined my day.


I'd be very grateful if someone can help me investigate this, even if the conclusion is that I'd better start saving for a new machine. Merry Christmas and a happy new year to all!

:)

 

Blue Screen

Hi,





Blue screens could be caused by problems with your computer’s hardware or with its driver. Still, we
would like to know more about the issue. Please clarify the following:

• Did you get a STOP code?
• Did you install any hardware or driver recently?

For basic troubleshooting steps to resolve blue screen errors, we suggest checking out this
article and simply follow the steps.



Feel free to contact us if you need further help.

 

blue screen and "device stuck in thread driver error

Hi William,

Thank you for posting in Microsoft Community and being a part of Windows 10.

I understand your concern about getting blue screen error on your device. We will help you with this issue.

Do let us know the following to assist you better with this issue:

• What is the make and model of your device?
• What is the complete error message/ error code of this issue?
• Have you made any changes to the operating system prior to this issue?
• Is this issue specific while performing any particular action of your computer?

I would like to inform that this usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. Frequently, this is the result of a bad video card or a bad display driver.

Try few of the below troubleshooting steps and check if it helps.

Step 1: I suggest you to scan for the hardware changes
in the Device Manager and check if it helps.

Press Windows + X keys from the keyboard, click on Device Manage, click on Scan for hardware changes icon
in the Tools bar.

Step 2: I recommend you to install all the pending updates on your device and check if it helps.

Steps:

• Connect to the internet.
• Press Windows key and type updates.
• Click on Check for updates.
• Under Windows Updates, click on Check for updates.
• Try to install the updates being shown.

Also, refer to the article: Updating a driver. and check if it helps.

Hope it helps. Get back to us with the required information and updated status of this issue for further assistance.

 

The October update of Microsoft created WDF violation in my HP PC.

The Microsoft updates released on October 9th, are not the source of the 0x10D WDF_VIOLATION bugchecks on RS4 or RS5. They do not contain or update the driver in question. Instead, affected devices, primarily HP business desktop, are installing a keyboard
driver update in close proximity, if not the same reboot cycle to the October 9th, 2018 updates.

Owners of devices in reboot pending state should follow the guidance in:

• KB
  4468304: HP Devices may experience blue screen error WDF_VIOLATION after installing HP Keyboard driver (11.0.3.1)

Devices currently experiencing the WDF_VIOLATION Bugcheck should follow the guidance in:

• KB
  4468372: HP devices may experience blue screen error WDF_VIOLATION after installing HP keyboard driver (version 11.0.3.