of course i did not install 3690 after fresh install, and never will
KB5003690 BSOD
Not so fast! On installing this update.
Installed KB5003690 (tried) on five rigs. Three no issue, one refused to install, and worst of all one started BSOD constantly after installing. Removed from that rig and all was fine and returned to normal. Reinstalled KB5003690 to verify this was the issue and yes, the BSOD issues returned, again uninstalled and all returned normal again. I'm satisfied in saying that KB5003690 is / was the issue.
Heidi-Ann
Scientific Frontline
Rig with issue
Edition Windows 10 Home
Version 20H2
Installed on 10/21/2020
OS build 19042.1055
Experience Windows Feature Experience Pack 120.2212.2020.0
Processor AMD FX(tm)-8320 Eight-Core Processor 3.50 GHz
Installed RAM 8.00 GB
System type 64-bit operating system, x64-based processor
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
93 answers
Sort by: Oldest
-
Anonymous
2021-07-02T22:44:46+00:00 -
Anonymous
2021-07-03T12:19:58+00:00 Bit of an interesting part is, that we dont share hardware similarities, I'm on an intel based system, 16GB of RAM, windows 10 PRO (not home).
The intel part means we dont share motherboard series either, do you have a Creative Sound Blaster Audigy (PCI) sound card by any chance?
And as with you, it worked flawlessly on other comps I own. But this is my "main" rig so to speak, so bit of a headache.
-
Anonymous
2021-07-03T13:38:10+00:00 Just adding a couple of data points for those here. No sound blaster installed (on board sound only) and I didn’t have to uninstall the stack update to fix the problem. This is an old i7 intel system with win10 home.
-
Anonymous
2021-07-03T18:11:53+00:00 Just adding another reply in general for information, been 26+ hours without a single BSOD after uninstalling the update in question.
Gone from a BSOD every 30-60 minutes-ish, to none in 26 hours.
-
Anonymous
2021-07-03T18:52:29+00:00 I'm really glad this worked for you, it didn't for me. A few hours after work reinstalling from absolute scratch did the trick of course.
P. S. I'm on a 2017 Alienware 13