Windows 10 upgrade from 1809 to 1909 stuck at 92 percent

There were no event logs prior to 2/17 2020.
(What was done on this date?)

There were three recent BSOD.

Please perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

13) Make sure that there is no over clocking while troubleshooting

14) Sometimes there are problems in the bios that produce BSOD.

The BIOS: V4.11, 2/16/2016

15) Check to see if this is the most up to date non-beta version

16) To ensure that there are no improper bios settings please reset the bios:

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)


17) List and uninstall all non-Microsoft antivirus software
(This includes always on and manual software.)
(This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely uninstalled)

18) List and uninstall all non-Microsoft firewall software

19) List all Microsoft and non-Microsoft drive encryption software.
Uninstall all non-Microsoft disk encryption software

20) List any software used to clean files similar to Ccleaner or Glary utilities

21) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

22) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

23) Read these links on Windows driver verifier: (learn how to use the windows recovery reset an bootmode commnds) (do not use the tool until communicated in the thread)

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

24) Make a new restore point:
Create System Restore Point in Windows 10

25) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

I cleared out my log files on the 2-17-2020 since they went back for awhile. I found no BSOD Also my Windows file is now in Caps for some reason. Is that bad?

What was used to clean the files?

The computer is having BSOD and currently is not producing dump files.

Windows file?

Code:

Event[870]:
  Log Name: System
  Source: volmgr
  Date: 2020-02-26T21:41:18.890
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gabe-Gaming-PC
  Description: 
Crash dump initialization failed!

Code:

Event[778]:
  Log Name: System
  Source: volmgr
  Date: 2020-02-26T19:59:29.999
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gabe-Gaming-PC
  Description: 
Crash dump initialization failed!

Code:

Event[613]:
  Log Name: System
  Source: volmgr
  Date: 2020-02-26T15:40:42.874
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Gabe-Gaming-PC
  Description: 
Crash dump initialization failed!

On c drive the window s folder is in caps. I think something got messed up. So after work I'm gonna use macrium reflect to restore my image before I did this.

After the restoration:

1) Indicate the date it was restored to

2) Place the computer in clean boot:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

3) Perform an in place upgrade repair while in clean boot

4) If it upgrades that will complete the troubleshooting.

5) If it fails run setupdiag and perform the steps in post #21

zbook said:

Code:

0xC1900101-0x4001E

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

Please help me with this hard stuck with Black Screen after it displays the Intel logo with a 92 at the bottom right of the screen....

Microsoft Windows [Version 10.0.14393]


X:\windows\system32>net user

User accounts for \\

-------------------------------------------------------------------------------
Administrator DefaultAccount Guest
The command completed with one or more errors.


X:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection could not perform the requested operation.

X:\windows\system32>
X:\windows\system32>
X:\windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.0


Error: 50

DISM does not support servicing Windows PE with the /Online option.

The DISM log file can be found at X:\windows\Logs\DISM\dism.log

X:\windows\system32>chkdsk /scan
The type of the file system is NTFS.
The shadow copy provider had an unexpected error while trying to process the specified operation.

A snapshot error occured while scanning this drive. You can try again, but if this problem persists, run an offline scan and fix.
Failed to transfer logged messages to the event log with status 50.

X:\windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\MININT-VVBI7DB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="|X:\\windows|"'
Property(s) update successful.

X:\windows\system32>wmic recoveros set debuginfotype=7
Updating property(s) of '\\MININT-VVBI7DB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="|X:\\windows|"'
Property(s) update successful.

X:\windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


X:\windows\system32>wmic recoveros get debuginfotype
DebugInfoType
7


X:\windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

X:\windows\system32>

@Bakayuka

14393 is Windows 1607.

This is an old thread.

Please open a new thread.