BSOD "inaccessible boot device" 0xC1900101 0x30017 during 1909/1903

version 1809, 17763.1039
Trying to update win10 from 1809 to 1909, the update gets to 27% or so, then calls for a reboot, this is where the issue arises. The system has been up and running for many years, if i recall it was a clean install, on a different hdd, now on a sdd for several years. The error is "inaccessible boot device" 0xC1900101 0x30017
Bios are now using uefi, before the error was regular legacy, this made no change. I have unplugged my multifunction printer, and extra usb hub as well, no change. i used mbr2gpt, followed directions, and windows boots. there are some entries in the boot selector, that some seem to fail, not sure if that is related to the crash. There are 4 drives, 3 hdd and 1 sdd. the sdd has the win10 os, efi partition, screenshot of disk management included.

the update goes, gets to like 27-30%, then reboots, and the error comes up, tries again, same error, then rolls the update back. tried 1903 v2, and the computer shut down at the 30% mark, was strange, powered back on, continued and gave the same error. i have not tried a 1809 v2 repair upgrade yet.

i have included the log tool results. plus cbs folder and panther logs. The unallocated on Disk 2 was deleted recently trying to correct the update issue, Bios also updated to the latest, with no change.

Please let me know what the next steps are, and thank you so much for your time.
Joel

Hi JS racer,

Welcome to the BSOD forum.

The logs displayed multiple recent BSOD.
There were no collected dump files.


1) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)



2) Run setupdiag > post a share link into the thread
https://docs.microsoft.com/en-us/win...rade/setupdiag

3) Run the DM log collector and upload the results directly into the thread:
BSOD - Posting Instructions

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

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

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

18) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

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

20) List and uninstall all non-Microsoft firewall software

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

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

23) Read these links on Windows driver verifier: (learn how to use the reset and bootmode commands) (do not use the tool until it is communicated in the thread)
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

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

25) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


26) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

27) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


28) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10


29) Find two flash drives that you can format (> or = 8 GB)

30) Create a bootable Windows 10 iso 1809:

http://windowsiso.net
https://heidoc.net/joomla/technology...-download-tool
https://tb.rg-adguard.net/public.php

31) Create a bootable Windows 10 iso 1909:

https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

Hello, thank you so much for your time, below is the requested information.
I feel the error could be in the bcd/efi information. ??


System specs updated
Run setupdiag, done
DM Log collector, done
4-16) Done
17) Eventually got there, (only had a single pane)
18) Done
19) None, had kav, uninstalled, and also used their separate uninstall tool, (done w week or 2 ago, had only standard av)
20) None
21) None
24) 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 NOT FOUND
25) Run HD Tune (free version) (all drives Done on SSD
26) done on SSD
I will remove the other 3 drives, for testing purpose.
27 not done at this time
29-31, done already, also have 1909 on dvd

I am planning to pull the cables for the other 3 hdd, for testing purposes, that will leave the SSD only in the system. (I could also close the drive to a different hdd, to see if that stalls at the same point also)


Microsoft Windows [Version 10.0.17763.1039]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection could not perform the requested operation.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.1039

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.1039

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection could not perform the requested operation.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is win 7 SSD.

Stage 1: Examining basic file system structure ...
746752 file records processed.
File verification completed.
33530 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
24852 reparse records processed.
934022 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
24852 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
93636 data files processed.
CHKDSK is verifying Usn Journal...
33608016 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

124037711 KB total disk space.
90467460 KB in 445366 files.
294972 KB in 93637 indexes.
0 KB in bad sectors.
868431 KB in use by the system.
65536 KB occupied by the log file.
32406848 KB available on disk.

4096 bytes in each allocation unit.
31009427 total allocation units on disk.
8101712 allocation units available on disk.

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

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\JAS-Z77-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\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>net user

User accounts for \\JAS-Z77-PC

-------------------------------------------------------------------------------
Administrator DefaultAccount Guest
JAS second WDAGUtilityAccount
The command completed successfully.


C:\WINDOWS\system32>bcdedit /enum {badmemory}

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

C:\WINDOWS\system32>

Thank you again for your time, I very much appreciate it.
Next round of requested information completed.

1-3) Done
4-5) done, same results, Windows Resource Protection could not perform the requested operation. Ran 3 times
8) Done, completed successful
9) same results, Windows Resource Protection could not perform the requested operation.
10-15) Done
16-17) Not found

Microsoft Windows [Version 10.0.17763.1039]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.1039

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection could not perform the requested operation.

C:\WINDOWS\system32>findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

C:\WINDOWS\system32>

1) The computer has hash mismatches with windows defender.
This was a known problem with Windows 1809.


2) Read the links on Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

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

The tool will stress drivers and misbehaving drivers will produce BSOD.
After each BSOD the tool needs to be turned off using the Windows Recovery Environment (RE). (reset and bootmode commands)
Once you are back on the desktop run V2 and upload directly into the thread.
If dump files are created and collected they will be debugged.
Misbehaving drivers will be uninstalled, updated, or uninstalled and reinstalled.
The tool will be restarted to find the next misbehaving driver.

When the tool is started use the 3 customized tests in the Ten Forums link.
Increase the number of customized tests by 3 - 5 / hour up to the 19 in the Microsoft link.

Sometimes there can be performance problems and slow boot while using the tool.
If necessary the customized tests can be modified.


Plan to run the tool for 48 hours and then for an additional 36 hours after the last BSOD.
If there are no further BSOD that will conclude the use of the tool.

Do not start using the tool until it is communicated in the thread.
Plan to start the tool after posting the chkdsk / r /v report.

Code:

2020-02-20 07:00:50, Info                  CSI    00003d3a [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d3c [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d3e [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d40 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d42 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d44 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d46 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d48 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-02-20 07:00:50, Info                  CSI    00003d4a [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

tic confused here,
so the next step is to run the chkdsk / r /v report, then 3-4 days running the other tool
this will point the system to the proper drive on rebooting during the 1909 update ??
my system never blue screens when in use.
i still have not removed the 3 additional hdd. slight concern with the system not booting depending what it is looking for. possibly need to play with bcdboot or other tools after unplugging the drives.

as for the hashes, there are no fixes ?? or it is not important. ??
the goal is to update to 1909, the error after rebooting is the hang up, rolls the system back and starts fine again.

thank you again for your time.

The concern for scannow was corruption.
There was no corruption reported.
If an in place upgrade repair is successful these will disappear.
If in place upgrade repairs are not successful there should be backup plans.

Backup plans options are:
a) reset save files
b) reset remove files
c) custom install
d) clean install
All of the above require the reinstallation of drivers and applications.

These are the next steps:
a) chkdsk /r /v
b) Fix any misbehaving drivers
c) Run through a Windows upgrade checklist
d) Perform an in place upgrade repair while in clean boot Windows 1909
e) Run setupdiag > evaluate any new upgrade failure error codes

ok, ran the chkdsk on the SSD C: win10 drive,

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername -match "wininit"} | fl timecreated, message


TimeCreated : 2/21/2020 1:37:30 PM
Message :

Checking file system on C:
The type of the file system is NTFS.
Volume label is win 7 SSD.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
746752 file records processed.

File verification completed.
33515 large file records processed.

0 bad file records processed.


Stage 2: Examining file name linkage ...
24884 reparse records processed.

934098 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.

24884 reparse records processed.


Stage 3: Examining security descriptors ...
Cleaning up 871 unused index entries from index $SII of file 0x9.
Cleaning up 871 unused index entries from index $SDH of file 0x9.
Cleaning up 871 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
93674 data files processed.

CHKDSK is verifying Usn Journal...
38578656 USN bytes processed.

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
746736 files processed.

File data verification completed.

Stage 5: Looking for bad, free clusters ...
7798355 free clusters processed.

Free space verification is complete.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

124037711 KB total disk space.
91674412 KB in 459062 files.
302276 KB in 93677 indexes.
0 KB in bad sectors.
867603 KB in use by the system.
65536 KB occupied by the log file.
31193420 KB available on disk.

4096 bytes in each allocation unit.
31009427 total allocation units on disk.
7798355 allocation units available on disk.

Internal Info:
00 65 0b 00 85 6e 08 00 9e 55 0f 00 00 00 00 00 .e...n...U......
c5 04 00 00 6f 5c 00 00 00 00 00 00 00 00 00 00 ....o\..........

Windows has finished checking your disk.
Please wait while your computer restarts.

from wininit:
Checking file system on C:
The type of the file system is NTFS.
Volume label is win 7 SSD.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
746752 file records processed.
File verification completed.
33515 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
24884 reparse records processed.
934098 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
24884 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 871 unused index entries from index $SII of file 0x9.
Cleaning up 871 unused index entries from index $SDH of file 0x9.
Cleaning up 871 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
93674 data files processed.
CHKDSK is verifying Usn Journal...
38578656 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
746736 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
7798355 free clusters processed.
Free space verification is complete.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

124037711 KB total disk space.
91674412 KB in 459062 files.
302276 KB in 93677 indexes.
0 KB in bad sectors.
867603 KB in use by the system.
65536 KB occupied by the log file.
31193420 KB available on disk.

4096 bytes in each allocation unit.
31009427 total allocation units on disk.
7798355 allocation units available on disk.

Internal Info:
00 65 0b 00 85 6e 08 00 9e 55 0f 00 00 00 00 00 .e...n...U......
c5 04 00 00 6f 5c 00 00 00 00 00 00 00 00 00 00 ....o\..........

Windows has finished checking your disk.
Please wait while your computer restarts.

chkdsk /r /v C:

Code:

Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.

Windows driver verifier can be started with the 3 customized tests in the TF link once you:
a) understand how to turn off and recover from using the tool
b) have made a new restore point



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