Apparently, BSODs Still Exist!

ElvenshaeElvenshae Registered User regular
Okay, so, I noticed I had some Chrome and Windows updates that needed to be installed. So, I figure, during my lunch break, I'll quit out of Chrome and then restart my computer so that they can be applied. I usually let this happen automatically overnight, but was feeling all proactive and shit.

WRONG MOVE!

While attempting to restart to finish applying the Windows updates, my computer hit a BSOD with an error ("SYSTEM_THREAD_EXCEPTION_NOT_HANDLED") and failed the update. It also failed to automatically restart after it reached 100% on the "Just collecting information, we'll restart for you" page and then sat there for ~15 minutes.

After manually restarting it, it BSODs with the same error on restart.

If I manually cycle it 3 times, I can get into safe mode (with networking) (hence being able to post this here). I can attempt to remove the latest updates (apparently, there were 2: KB4549951 and KB4534132, though these were supposedly released last month / February, and I've had numerous updates since, so I'm not sure why I'm getting them now), then my computer says it needs to restart to complete removing the updates. When it attempts to restart, it BSODs again, with an error related to a driver being stopped before requests are finished (rtwlanu.sys). I believe that driver is for the TP-LINK USB WiFi adapter I've got plugged in. So I've pulled that out and gone through the whole process again.

That'll allow Windows to look like it uninstalls one of the updates, except then it BSODs again when starting up. And the updates are still appearing like they're installed. Simply shutting down or restarting results in the same BSOD that started things off.

I've run a Malwarebytes check while here in safe mode and come up empty, just in case.

I noticed that my nVidia drivers were a bit out of date, and did a clean install on them, too, since apparently that's one of the common causes of this issue. Still doesn't fix the issue.

The startup repair tool accessed through the Windows Recovery Environment provides the following helpful advice: "A recent driver installation or upgrade may be preventing the system from starting." Apart from the nVidia drivers I just updated and Malwarebytes for the above scan, the only items installed recently are Steam games, Github for Desktop, and MS Office updates. Discord seems to have an update from the future (install date of 12/14/2020), but I just started it up again and it updated like it normally does.

So, uh ... What's my next step? :D I'd prefer to not nuke things from orbit, but apparently I don't have any system restore points available (and I'm not sure why that got shut off).

omgbfz5lzi1s.png
Steam: Elvenshae // PSN: Elvenshae // WotC: Elvenshae
The Disappearance of Inigo Sharpe: Tomas à Dunsanin

Posts

  • BahamutZEROBahamutZERO Registered User regular
    A clean reinstall is pretty much the only thing you can do at this point. Select your gun, and then, select your operating system. Salvage what irreplaceable files you can onto portable media or the cloud or whatever first if you can still reach the desktop.

    BahamutZERO.gif
  • TelMarineTelMarine Registered User regular
    Is it creating a minidump memory dump? If it is and you can get into safe mode, you can analyze the dump using the Windows Debugging Tools. By using the !analyze command in the Windows Debugging Tools after opening a minidump file, it'll tell you what is probably causing the issue (like a driver file).

    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled
    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/crash-dump-files

    3ds: 4983-4935-4575
    Elvenshae
  • Bendery It Like BeckhamBendery It Like Beckham Hopeless Registered User regular
    If the BSOD still throws the RTwlanu.sys as the faulting driver after unplugging it Uninstall the TPLink Drivers via Control Panel. BSOD shows you the last faulting driver in the stack, but the crash could have been caused by something executed earlier.
    If you can find the crash dump/minidump using Telmarine's links you can see the full stack and possibly any other faulting drivers or components.

    Shadowfire
  • ShadowfireShadowfire Vermont, in the middle of nowhereRegistered User regular
    If the debugger doesn't help, you can also parse the stop code with bluescreenview. I find it does a way better job of telling me what to look for than Microsoft's debugger.

    https://www.nirsoft.net/utils/blue_screen_view.html

    WiiU: Windrunner ; Guild Wars 2: Shadowfire.3940 ; PSN: Bradcopter
    Elvenshae
  • bowenbowen How you doin'? Registered User regular
    @Elvenshae do you play Valorant by any chance?

    Their kernel level anti cheat is causing a lot of blue screens on certain drivers (ones that hacks piggyback off of because they're designed poorly). rtwlanu.sys is one of those drivers IIRC

    not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
  • ElvenshaeElvenshae Registered User regular
    TelMarine wrote: »
    Is it creating a minidump memory dump? If it is and you can get into safe mode, you can analyze the dump using the Windows Debugging Tools. By using the !analyze command in the Windows Debugging Tools after opening a minidump file, it'll tell you what is probably causing the issue (like a driver file).

    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled
    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/crash-dump-files

    Yes, it's creating the minidump. Unfortunately, I don't have the Windows debugger installed yet, and I can't get it from the MS Store because that won't work in safe mode, and the standalone installer just fails halfway through. So that's fun. :D
    If the BSOD still throws the RTwlanu.sys as the faulting driver after unplugging it Uninstall the TPLink Drivers via Control Panel. BSOD shows you the last faulting driver in the stack, but the crash could have been caused by something executed earlier.
    If you can find the crash dump/minidump using Telmarine's links you can see the full stack and possibly any other faulting drivers or components.

    That stops crashing on shut-down as soon as I just unplug it.
    Shadowfire wrote: »
    If the debugger doesn't help, you can also parse the stop code with bluescreenview. I find it does a way better job of telling me what to look for than Microsoft's debugger.

    https://www.nirsoft.net/utils/blue_screen_view.html

    This one installs, though, and points to an issue with ha20x22k.sys, which is apparently a sound card driver. I don't think I've even used it (and I don't have speakers, just my headset), so I've uninstalled that entirely. Let's see if that helps solve the issue.

    Thank you, everyone, for the assistance!

    omgbfz5lzi1s.png
    Steam: Elvenshae // PSN: Elvenshae // WotC: Elvenshae
    The Disappearance of Inigo Sharpe: Tomas à Dunsanin
  • ElvenshaeElvenshae Registered User regular
    Uninstalling ha20x22k.sys worked! I was able to shut down from safe mode cleanly, reboot into normal mode, and have my computer up-and-running!

    For about 30s.

    Then it crashed again because Windows detected the "new" soundcard, installed the drivers automatically, and CRASH.

    So now I've ripped out the hardware (which I wasn't actually using anyway), et voila, back to rock solid.

    @TelMarine @bowen @Bendery It Like Beckham @BahamutZERO

    Thank you again, everyone, for your help!

    omgbfz5lzi1s.png
    Steam: Elvenshae // PSN: Elvenshae // WotC: Elvenshae
    The Disappearance of Inigo Sharpe: Tomas à Dunsanin
    jungleroomxBendery It Like BeckhamBahamutZEROJaysonFourTelMarineDarkewolfeSynthesis3clipseZilla360
  • ElvenshaeElvenshae Registered User regular
    @Shadowfire , too! Can't believe I missed your name. :D

    omgbfz5lzi1s.png
    Steam: Elvenshae // PSN: Elvenshae // WotC: Elvenshae
    The Disappearance of Inigo Sharpe: Tomas à Dunsanin
    Shadowfire
  • Bendery It Like BeckhamBendery It Like Beckham Hopeless Registered User regular
    Glad to hear you got it sorted :)

    Elvenshae
  • BahamutZEROBahamutZERO Registered User regular
    glad my nuke it from orbit advice was wrong lol

    BahamutZERO.gif
    jungleroomxElvenshaeShadowfireZilla360
  • jungleroomxjungleroomx antifa anti american nazi socialist terrorist fascist alien warmonger Registered User regular
    glad my nuke it from orbit advice was wrong lol

    tbf it usually isn't, but I had a driver issue that persisted after a reinstall of Windows.

    When a driver gets cranked like this it can be a real pain in the ass to get it corrected.

    Make. Time.
    ElvenshaeShadowfirebowenZilla360
  • SynthesisSynthesis Honda Today! Registered User regular
    glad my nuke it from orbit advice was wrong lol

    tbf it usually isn't, but I had a driver issue that persisted after a reinstall of Windows.

    When a driver gets cranked like this it can be a real pain in the ass to get it corrected.

    I enjoy shouting "Nuke it from Orbit" as much as the next person, but I'd argue with the advent of Windows Repair Installation/Replacement Installation/whatever else they call it, a lot of problems that called for "start over from scratch" can actually be solved if they are faults within Windows 10 itself. And if so, it's remarkably good at fixing them with very little effort on the user's part. This can include certain kinds of driver conflicts.

    The catch is that you have to be able to boot into Windows 10 at least once in one mode or another. Which isn't always doable, as we know.

    Orca wrote: »
    Synthesis wrote:
    Isn't "Your sarcasm makes me wet," the highest compliment an Abh can pay a human?

    Only if said Abh is a member of the nobility.
    ElvenshaeZilla360
  • ShadowfireShadowfire Vermont, in the middle of nowhereRegistered User regular
    Synthesis wrote: »
    glad my nuke it from orbit advice was wrong lol

    tbf it usually isn't, but I had a driver issue that persisted after a reinstall of Windows.

    When a driver gets cranked like this it can be a real pain in the ass to get it corrected.

    I enjoy shouting "Nuke it from Orbit" as much as the next person, but I'd argue with the advent of Windows Repair Installation/Replacement Installation/whatever else they call it, a lot of problems that called for "start over from scratch" can actually be solved if they are faults within Windows 10 itself. And if so, it's remarkably good at fixing them with very little effort on the user's part. This can include certain kinds of driver conflicts.

    The catch is that you have to be able to boot into Windows 10 at least once in one mode or another. Which isn't always doable, as we know.

    And depending on how broken it is, downloading the media creation tool and using it to perform a repair install is pretty great.

    WiiU: Windrunner ; Guild Wars 2: Shadowfire.3940 ; PSN: Bradcopter
  • PhyphorPhyphor Building Planet Busters Tasting FruitRegistered User regular
    Heh I have also been seeing bluescreens and a lot of deadlocks. My system went from an uptime of months at a time to it can crash a minute after login a few days ago

    If memtest passes I may have to nuke it from orbit

Sign In or Register to comment.