BSOD when Updating WIN 10 1909 to version 20H2

It can be easy to miss the important data.

The logs may report what had happened and report a malfunctioning driver.

Another thread had a crash during an upgrade:

Code: 
crash information in rollback log:
BugCheck Code: 0x0000007E
Driver: RtsPer.sys
SetupPhase: FirstBoot,Start

Code: 
2021-04-18 17:58:44, Info                  SP     Found driver store entry C:\WINDOWS\System32\DriverStore\FileRepository\rtsper.inf_amd64_d1a95bad1f2cc83b
2021-04-18 17:58:44, Info                  SP     Matching INF entry found: C:\WINDOWS\Inf\oem154.inf
2021-04-18 17:58:44, Info                  SP     Crash 0x0000007E detected
2021-04-18 17:58:44, Info                  SP       Parameter 1  : 0xFFFFFFFFC0000005
2021-04-18 17:58:44, Info                  SP       Parameter 2  : 0xFFFFF8061C0F277D
2021-04-18 17:58:44, Info                  SP       Parameter 3  : 0xFFFFF88FDB82F638
2021-04-18 17:58:44, Info                  SP       Parameter 4  : 0xFFFFF88FDB82EE70
2021-04-18 17:58:44, Info                  SP       Param module name: RtsPer.sys
2021-04-18 17:58:44, Info                  SP               INF name : rtsper.inf
2021-04-18 17:58:44, Info                  SP             Class GUID : {4d36e970-e325-11ce-bfc1-08002be10318}
2021-04-18 17:58:44, Info                  SP             Class Name : MTD
2021-04-18 17:58:44, Info                  SP               Provider : Realtek Semiconductor Corp.
2021-04-18 17:58:44, Info                  SP                Version : 06/08/2020,10.0.18363.21333


If you post these logs they can be scanned:
C:\$Windows.~BT\Sources\Rollback
C:\$Windows.~BT\Sources\Panther
 
Last edited by a moderator:
Hi, Please help me with the names of the specific logs you are asking for in each:
C:\$Windows.~BT\Sources\Rollback
C:\$Windows.~BT\Sources\Panther
 
For the other thread this was a portion of the setupmem.dmp


Code: 
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\aaaaaaaa\AppData\Local\Temp\Temp2_RollbackFiles.zip\RB2\Rollback\setupmem.dmp]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`0f000000 PsLoadedModuleList = 0xfffff806`0fc2a3d0
Debug session time: Sun Apr 18 19:57:58.215 2021 (UTC - 5:00)
System Uptime: 0 days 0:00:39.408
Loading Kernel Symbols
...............................................................
................................................................
...........Page 1001a8a not present in the dump file. Type ".hh dbgerr004" for details
.....................................................
................................................................
.........
Loading User Symbols

Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff8061c0f277d, fffff88fdb82f638, fffff88fdb82ee70}

*** ERROR: Module load completed but symbols could not be loaded for RtsPer.sys
Probably caused by : RtsPer.sys ( RtsPer+e277d )

Followup:     MachineOwner
---------

6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8061c0f277d, The address that the exception occurred at
Arg3: fffff88fdb82f638, Exception Record Address
Arg4: fffff88fdb82ee70, Context Record Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  19041.1.amd64fre.vb_release.191206-1406

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  20QNCTO1WW

SYSTEM_SKU:  LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53

SYSTEM_VERSION:  ThinkPad P53

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  N2NET43W (1.28 )

BIOS_DATE:  01/13/2021

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  20QNCTO1WW

BASEBOARD_VERSION:  SDK0J40697 WIN

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8061c0f277d

BUGCHECK_P3: fffff88fdb82f638

BUGCHECK_P4: fffff88fdb82ee70

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
RtsPer+e277d
fffff806`1c0f277d 418b460c        mov     eax,dword ptr [r14+0Ch]

EXCEPTION_RECORD:  fffff88fdb82f638 -- (.exr 0xfffff88fdb82f638)
ExceptionAddress: fffff8061c0f277d (RtsPer+0x00000000000e277d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffff8601b55ad00c
Attempt to read from address ffff8601b55ad00c

CONTEXT:  fffff88fdb82ee70 -- (.cxr 0xfffff88fdb82ee70)
rax=ffff8601b55ad000 rbx=fffff8061c145a00 rcx=2f0ff816fc800000
rdx=ffffd4ea753a9000 rsi=ffffb002a4a401a0 rdi=ffffb002a4a40500
rip=fffff8061c0f277d rsp=fffff88fdb82f870 rbp=0000000000000000
r8=0000007ffffffff8  r9=ffffd4ea61806d50 r10=0000000000000001
r11=ffffd4ea753a9000 r12=346dc5d63886594b r13=0000000000000000
r14=ffff8601b55ad000 r15=ffffb002a4a40100
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
RtsPer+0xe277d:
Page f0000 not present in the dump file. Type ".hh dbgerr004" for details
fffff806`1c0f277d 418b460c        mov     eax,dword ptr [r14+0Ch] ds:002b:ffff8601`b55ad00c=????????
Resetting default scope

CPU_COUNT: c

CPU_MHZ: a20

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: d

CPU_MICROCODE: 6,9e,d,0 (F,M,S,R)  SIG: DE'00000000 (cache) DE'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

FOLLOWUP_IP:
RtsPer+e277d
fffff806`1c0f277d 418b460c        mov     eax,dword ptr [r14+0Ch]

BUGCHECK_STR:  AV

READ_ADDRESS: Unable to get offset of nt!_MI_VISIBLE_STATE.SpecialPool
Unable to get value of nt!_MI_VISIBLE_STATE.SessionSpecialPool
ffff8601b55ad00c

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffff8601b55ad00c

ANALYSIS_SESSION_HOST:  DESKTOP-9HEBUKS

ANALYSIS_SESSION_TIME:  04-20-2021 22:16:30.0045

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8061c111f9e to fffff8061c0f277d

STACK_TEXT:
fffff88f`db82f870 fffff806`1c111f9e : fffff806`1c145a40 fffff806`1c145906 00000000`00000004 ffffffff`80001854 : RtsPer+0xe277d
fffff88f`db82f910 fffff806`1c0f76cc : 00000000`00000001 ffffb002`a4a40050 ffffb002`00000004 ffffb002`00000000 : RtsPer+0x101f9e
fffff88f`db82f9a0 fffff806`0f35a4c5 : ffffb002`a63f5400 ffffb002`a4a40050 ffffb002`928ef040 fffff806`1b698490 : RtsPer+0xe76cc
fffff88f`db82fa00 fffff806`0f225975 : ffffb002`a39430c0 ffffb002`a39430c0 fffff806`0f35a390 ffffb002`00000000 : nt!IopProcessWorkItem+0x135
fffff88f`db82fa70 fffff806`0f317e85 : ffffb002`a39430c0 00000000`00000080 ffffb002`9269a040 000fa56f`b19bbfff : nt!ExpWorkerThread+0x105
fffff88f`db82fb10 fffff806`0f3fd498 : fffff806`0c719180 ffffb002`a39430c0 fffff806`0f317e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff88f`db82fb60 00000000`00000000 : fffff88f`db830000 fffff88f`db829000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


THREAD_SHA1_HASH_MOD_FUNC:  ae444904fa043cc4301491973aca3661d53eb7a6

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  bcf6c41e3e8b2d806aaaaa5abf7345ddaa914663

THREAD_SHA1_HASH_MOD:  b31cbcc5afa7ab6f46c900f79e5f69329ea587cd

FAULT_INSTR_CODE:  c468b41

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  RtsPer+e277d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RtsPer

IMAGE_NAME:  RtsPer.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5e9919bb

STACK_COMMAND:  .cxr 0xfffff88fdb82ee70 ; kb

BUCKET_ID_FUNC_OFFSET:  e277d

FAILURE_BUCKET_ID:  AV_RtsPer!unknown_function

BUCKET_ID:  AV_RtsPer!unknown_function

PRIMARY_PROBLEM_CLASS:  AV_RtsPer!unknown_function

TARGET_TIME:  2021-04-19T00:57:58.000Z

OSBUILD:  19041

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  1977-10-11 02:04:26

BUILDDATESTAMP_STR:  191206-1406

BUILDLAB_STR:  vb_release

BUILDOSVER_STR:  10.0.19041.1.amd64fre.vb_release.191206-1406

ANALYSIS_SESSION_ELAPSED_TIME:  a4c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_rtsper!unknown_function

FAILURE_ID_HASH:  {5972166a-a6f4-1eee-ba85-d5534a099133}

Followup:     MachineOwner




(The collected logs should report whether there was or was not a setupmem.dmp)


Use: voidtools

These folders can be zipped > post multiple share links using one drive, drop box, or google drive (please keep each share link < 2 GB)

C:\$Windows.~BT\Sources\Rollback
C:\$Windows.~BT\Sources\Panther

also search for: (folders and files)

C:\Windows\inf\setupapi.dev.log
C:\Windows\Logs\CBS
C:\Windows\memory.dmp
Setupmem.dmp

Run these administrative command prompt commands > find new text files on the desktop > post share links
sfc /scannow
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
findstr /c:"conx" C:\$Windows.~BT\Sources\Panther\setupact.log >"%userprofile%\Desktop\Setupactdetails.txt"
 
Last edited by a moderator:
The edit is not working.


The logs confirmed your setupmem.dmp search results.

There was no reported upgrade crash and no setupmem.dmp.

The logs displayed:
Code: 
2021-04-19 16:11:11, Info                  SP     No crash detected. Try to get the binary info of last crash dump.

OS Version:                10.0.18363 N/A Build 18363
Upgrade failure: 0xC1900101, 0x40017

Windows 10 upgrade failed after the second reboot.



Open administrative command prompt and copy and paste:

wmic recoveros set autoreboot = false
wmic recoveros set debuginfotype = 7
wmic recoveros get autoreboot
wmic recoveros get debuginfotype
wmic computersystem where name="%computername%" set automaticmanagedpagefile=true
wmic computersystem where name="%computername%" get automaticmanagedpagefile

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread



There was a Windows Driver Verifier BSOD on 4/11/2021
There were 3 spontaneous BSOD on 4/19/2021 displaying: Crash dump initialization failed!


Create a new restore point.
Restart Windows Driver Verifier with these settings:
Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista | Sysnative Forums


For any BSOD > post new Sysnative log collector results



Installation Failure: Windows failed to install the following update with error 0x8024200D: Feature update to Windows 10, version 20H2.
Installation Failure: Windows failed to install the following update with error 0xC1900101: Feature update to Windows 10, version 20H2.


For the next attempted upgrade:
1) uninstall any these non-Microsoft software:
a) antivirus
b) firewall
c) drive encryption

2) place the computer in clean boot:
How to perform a clean boot in Windows (microsoft.com)

3) uninstall non-signed drivers:
Quick fixes - Windows IT Pro - Windows Deployment | Microsoft Docs
 
Last edited by a moderator:
Microsoft Windows [Version 10.0.18363.1500]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\HOMEPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>mic recoveros set debuginfotype = 7
'mic' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>mic recoveros get debuginfotype
'mic' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>wmic computersystem where name="%computername%" set automaticmanagedpagefile=true
Updating property(s) of '\\HOMEPC\ROOT\CIMV2:Win32_ComputerSystem.Name="HOMEPC"'
Property(s) update successful.

C:\WINDOWS\system32>mic computersystem where name="%computername%" get automaticmanagedpagefile

PLEASE SEE: #6,7,8 for the Driver Verifier previous findings.
I do have Veracrypt on this PC as an FYI. See attached.
I will standby for the next steps.
 

Attachments

Last edited:
RobertH99 said:
Microsoft Windows [Version 10.0.18363.1500]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\HOMEPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>mic recoveros set debuginfotype = 7
'mic' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>mic recoveros get debuginfotype
'mic' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>wmic computersystem where name="%computername%" set automaticmanagedpagefile=true
Updating property(s) of '\\HOMEPC\ROOT\CIMV2:Win32_ComputerSystem.Name="HOMEPC"'
Property(s) update successful.

C:\WINDOWS\system32>mic computersystem where name="%computername%" get automaticmanagedpagefile

PLEASE SEE: #6,7,8 for the Driver Verifier previous findings.
I do have Veracrypt on this PC as an FYI. See attached.
I will standby for the next steps.
Click to expand...


There were several commands that were copied and pasted incompletely: (missing the first letter)

mic recoveros set debuginfotype = 7

should have been:

wmic recoveros set debuginfotype = 7



mic recoveros get debuginfotype

should have been:

wmic recoveros get debuginfotype



mic computersystem where name="%computername%" get automaticmanagedpagefile

should have been:

wmic computersystem where name="%computername%" get automaticmanagedpagefile



Rerun the commands making sure that all characters are copied and pasted > post images into the thread


After running the commands > make a new restore point > start WDV > post new Sysnative log collector results for any BSOD
https://www.sysnative.com/forums/threads/driver-verifier-bsod-related-windows-10-8-1-8-7-vista.29/
https://www.sysnative.com/forums/pages/bsodcollectionapp/




This driver displayed unsigned: smbdrv.ini Unknown None Not Signed N/A

Code: 
SmbDrvI      SmbDrvI                SmbDrvI                Kernel        Manual     Running    OK         TRUE        FALSE        0                 20,480      0          8/25/2017 7:59:25 PM   C:\WINDOWS\system32\DRIVERS\Smb_driver_Intel.sys 4,096

Code: 
Module Name:       SmbDrvI
Display Name:      SmbDrvI
Driver Type:       Kernel
Link Date:         8/25/2017 7:59:25 PM


The closest match in the Sysnative database is:
Smb_driver.sysSynaptics SMBus Driverhttp://www.synaptics.com/resources/drivers

The source displayed:
OOPS. SOMETHING WENT
WRONG.

See if you can find a signed driver on the Dell website.

An alternate option may be Intel: from Intel: C:\WINDOWS\system32\DRIVERS\Smb_driver_Intel.sys
https://downloadcenter.intel.com/download/28425/Intel-Driver-Support-Assistant



For the upgrade failure 0xC1900101, 0x40017
This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers.


Plan to uninstall Veracrypt to improve the likelihood of a successful upgrade.
 
I did not copy/paste each command separately. SORRY!

Microsoft Windows [Version 10.0.18363.1500]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\HOMEPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set debuginfotype = 7
Updating property(s) of '\\HOMEPC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get debuginfotype
DebugInfoType
7


C:\WINDOWS\system32>wmic computersystem where name="%computername%" set automaticmanagedpagefile=true
Updating property(s) of '\\HOMEPC\ROOT\CIMV2:Win32_ComputerSystem.Name="HOMEPC"'
Property(s) update successful.

C:\WINDOWS\system32>wmic computersystem where name="%computername%" get automaticmanagedpagefile
AutomaticManagedPagefile
TRUE


C:\WINDOWS\system32>
 
AS an FYI and a Question. I am running Verifier and confirmed w Query
Why can't I just delete the folder C:\WINDOWS\System32\DriverStore\FileRepository\smbdrv.inf_amd64_6f8f396ef8f62fde which contains the smb related files as I do not see this is being used?
 
Open administrative command prompt (ACP) and type or copy and paste:
Code: 
verifier /querysettings 
Dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"
findstr /c:"CONX" C:\$Windows.~BT\Sources\Panther\setupact.log  >"%userprofile%\Desktop\Setupactdetails.txt"

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


Find the new text file(s) on the desktop > post share link(s) into this thread.
 
Last edited by a moderator:
For WDV one of the Sysnative link customized tests was missed during the latest run:
Power framework delay fuzzing

Please turn off the tool and restart with these customized settings: (run for 24 hours)

[ ] 0x00000010 I/O verification
[ ] 0x00000080 DMA checking
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.


For any BSOD run the Sysnative log collector:
https://www.sysnative.com/apps/SysnativeBSODCollectionApp.exe


The logs displayed: Av with display name "Microsoft Security Essentials" (stripped name is "Microsoft Security Essentials") has no upgrade exe dir.

If appears as a prior Windows 7 instillation.

After WDV testing and before the next upgrade attempt:
1) Decrypt any Veracrypt files
2) Uninstall Veracrypt using control panel
3) Uninstall Pace Anti-Piracy using control panel
4) Run: Dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"
5) If the results indicate that Veracrypt and Pace drivers were uninstalled then plan an in place upgrade repair while in clean boot
 
Why those settings, they can heavily impact system performance.
 
TEST ABORTED

I set up verifier as requested. I selected ALL NON microsoft drivers. Rebooted and just after the Dell logo screen the system hung. I let it hang for 5 minutes. My normal reboot is 30 seconds.

I had to run verifier /reset to notify you that the test had to be aborted.

Now what?
 
Each customized test can cause performance problems or very slow boot.

The computer performance and boot were without reported problems for 7 simultaneous customized tests.

Select 2 - 4 of the 14 remaining customized tests and test each group for approximately 3 - 4 hours.
 
Many driver verifier options do not heavily impact performance, nothing noticeable anyway. There are a few that seriously impact performance up to the point where the computer could start freezing, like Systematic low resources simulation that emulates an environment for drivers where drivers run with very little resources compared to the real environment. If a driver isn't developed to handle situations with little resources, it can impact performance significantly, even cause Windows to freeze, which is why it's an additional option. Additional options are originially designed to be used for specific drivers, not for a whole bunch of drivers. Sysnative lists some additional options as a default configuration for good reason, because they are used to find common problems in the drivers.

You can't and should not just list a random configuration for driver verifier and instruct the user to run them without knowing what they do, that doesn't help anyone.


@RobertH99, I would advise against following Zbook's suggestion for driver verifier using those options. Not only is there a significant chance of unneeded performance problems, but it's also prone to false positives. Also please answer x BlueRobot's question.
 
RobertH99 said:
Actually it was the RtsUer.sys which was uninstalled via IOBit uninstaller. I believe the name was Realtek USB Card Reader
Click to expand...
They're very likely part of the same package. I would suggest removing the driver via device manager if you're able to, it may be worthwhile running Revo uninstaller as well. I don't trust IOBit and their software.

Interestingly, there is a thread on the Microsoft forums from user which reported having upgrade problems due to the Realtek Card Reader driver as well - Uninstall Realtek Card Reader to upgrade to Windows 10
 
x BlueRobot said:
They're very likely part of the same package. I would suggest removing the driver via device manager if you're able to, it may be worthwhile running Revo uninstaller as well. I don't trust IOBit and their software.

Interestingly, there is a thread on the Microsoft forums from user which reported having upgrade problems due to the Realtek Card Reader driver as well - Uninstall Realtek Card Reader to upgrade to Windows 10
Click to expand...
I first removed the driver in device manager w/uninstall it and delete software, rebooted to verify it did not reinstall. I then uninstalled the software and rebooted. I feel it is removed unless in the repository or registry. It must have been there from windows 7.
 
Back
Top