BSOD when Updating WIN 10 1909 to version 20H2

RobertH99

RobertH99

Active member
Joined
Oct 14, 2019
Posts
37
After 4 failed updates I am asking for help

I am tying to update Windows 10 Pro version 1909 installed 1/6/2020 OS Build 18363.1474

This is a 64bit, 16.0GB RAM

Always get this Error 0xC1900101 noted as Stop Code System Thread

I have tried everything to resolve, but have not found the solution.
 

Attachments

There's basically no data we can use because it's looks like the data has been deleted, possibly by the Windows update.


Please run driver verifier using the settings specified in the link for 48 hours.

Warning: driver verifier could cause boot issues and/or performance issues. Configure a restore point prior enabling driver verifier.

Resetting driver verifier options (recommended in this order)
  1. In normal mode open an administrator command prompt and enter the below command
  2. In safe mode open an administrator command prompt and enter the below command
  3. On 3 boot failures, you'll boot automatically to the recovery options,
    • click Troubleshoot
    • go to the advanced options
    • choose command prompt
    • enter the below command
  4. Boot with the recovery media, see above 4 steps in option 3.
  5. Via the recovery options or recovery media, select a restore point prior enabling driver verifier
Code: 
verifier /reset

Crashed when running driver verifier
  1. Reset driver verifier
  2. Boot in normal mode if necessary
  3. Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs


Extra information about driver verifier
When you run driver verifier, there are two things you're looking out for
1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
2. Driver verifier will find a driver violating something and thus the system will crash.

The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.


Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.

Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.

If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt

Code: 
verifier /query

If the command gives a result similar to this, it means driver verifier is running.
1618088192434.png
 
You stated " Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.".

I would appreciate knowing the various methods to recover from it in advance of running the test, please
 
I have mentioned most of them throughout my post, under 'resetting driver verifier'
 
After enabling the Verifier as noted, I reset and immediately had a BSOD "Stop Code: DRIVER VERIFIER DETECTED VIOLATION". The SysnativeFileCollectionApp.zip is attached. Thanks for your assistance.
 

Attachments

It's due to the Realtek USB card reader driver which is quite old. I did not directly see any software installed related to this in your logs or at Dell, so if Dell doesn't have any driver updates then check Realtek.
Driver Reference Table (DRT)
Code: 
2: kd> lmvm RtsUer
Browse full module list
start             end                 module name
fffff80f`34220000 fffff80f`34285000   RtsUer   T (no symbols)           
    Loaded symbol image file: RtsUer.sys
    Image path: RtsUer.sys
    Image name: RtsUer.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed May 27 08:11:14 2015 (55656002)
    CheckSum:         0007401B
    ImageSize:        00065000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
Hi Axe0, I have removed Realtek and ran verifier, NO BSOD on restart, I am in windows and ran verifier /query so it is running. I will keep running 48 hours, unless you suggest different...Bob
 
Curiosity ?, please - How did you "remove" Realtek?

The link for an updated Realtek driver in our DRT is INOP - Driver Reference Table (DRT) | RtsUer.sys

It is possible that Realtek has not bothered to update the driver and simply removed it from the update site.

Thank you.

Regards. . .

jcgriff2




@x BlueRobot
@axe0

Very nice and quick job troubleshooting and nailing the culprit, guys. (y)



`
 
Hi again. . .

@RobertH99 - I MAY have found an update for your Realtek driver - Microsoft Update Catalog

Not sure which one, but if you wanted to try a few -

jcgriff2 said:
RtsUer.sys

Realtek SD driver - [For my info] Driver update site URL in DRT needs to be updated as the current one is INOP - Driver Reference Table (DRT) | RtsUer.sys (sysnative.com)

New - Microsoft Update Catalog - several choices so several driver updates may have to be tried/installed and tested - which update to select seems dependant upon version of W10 installed
Click to expand...


First thing to do is to create a Windows System Restore point - (2) Windows System Restore - Create a Restore Point (Windows 10, 8.1, 8, 7 & Vista) | Sysnative Forums

Doing so will make your life much easier to start anew and try a different Realtek driver update from Microsoft if the one that you have just installed does not work/causes a VERIFIER_ENABLED BSOD.

Easiest way to bring up System Restore to restore system - from a CMD prompt, type rstrui ; hit ENTER; select restore point that you just created

Regards. . .

jcgriff2
 
Hi All interested parties,

I removed the item in device manager then uninstalled the installer. This has been on my system without causing issues EXCEPT for when Updating WIN 10 1909 to version 20H2. I do not need it so will not attempt a different Realtek driver.

QUESTION: It has been almost 48 hours running Verifier. Today is update Tuesday. Should I keep verifier running during windows update just in case there is another BSOD or do verifier /reset before the updates?
 
I would disable Driver Verifier before you attempt any updates. If needs be, we can always enable it afterwards.
 
The reason I asked is that when it would BSOD no DMP files would be written and the reason I asked as it would save debugging time etc. Your thoughts now?
 
In most circumstances, it will produce a dump file; the only reason a dump file is usually not written to the disk, is when the crash occurs too early during the boot process for the system. DV will only produce dump files if it detects a driver which is breaking one of the predefined rules.
 
Ok, Verifier /Reset has been done. Now I wait for MS to offer the update so I can advise all...Thanks thus far :)
 
Ran the update assistant in lieu of waiting for MS to offer. After second reboot was at 71% then BSOD with "System Thread Exception Not Handled" . There was no DMP file generated. Now what?
 
Could you please run the Sysnative log collection tool again? Despite there might not being any new dump files, the event logs might have some useful information.
 
Check C:\$Windows.~bt\Sources\Rollback if there is a dump available.

If in the Rollback directory there is no dump then check C:\Windows\Panther\NewOS\Rollback for dump files.
 
Back
Top