System drive NTFS partition is good but just won't boot

TL;DR: My second system drive is 'a little' corrupt: files can be accessed, partition's taken/used space information is correct, sectors are good but it just won't boot past Windows loading. Chkdsk, sfc etc. all good. The only error is seen in SRTTrail.txt (Startup repair) logs.
I now have 2 SSD system drives with Windows 10.

Drive C: (2TB) is new.
Drive D: (1TB) 1 year.
They are both good in terms of chkdsk and HD Tune (test for bad sectors).

# Background:
My idea was to install system on the new C, review and copy data I needed from D in the span of few days, and then format D.

But what happened is:
1. I installed the system on C along with the basic software that I need (Notepad++, VSCode etc., nothing 'sketchy') and Windows Updates.
2. Suddenly, can't give an exact timeframe or which action triggered it, but a notification popped up that computer should be restarted so that chkdsk could scan the drive for errors, and so I rebooted it.
3. As soon as POST went by, a BSOD appeared "NTFS_FILE_SYSTEM" - image.
4. It restarted itself and again the same BSOD appeared, so I went into bios and booted into the D drive.
5. It booted just fine, but I of course couldn't access the C drive from This PC. (I didn't investigate it further from the system level at that time)
6. I figured it might be an issue with the last Windows Update (?) and it could have corrupted the C file system. I switch the boot to C again.
7. It started doing chkdsk during startup, I waited a little and then cancelled the process by turning off PC with power button (fatal mistake).
8. I again switched to boot from D drive and... the SAME BSOD APPEARED - NTFS_FILE_SYSTEM.
so I thought: Did I just toast my old drive by canceling chkdsk? Why would it? Was it checking the D drive also? (instead of focusing SOLELY on C). I checked the registry for 'BootExecute' and it had the following command:

Code:

autocheck autochk *

So chkdsk most likely was indeed fixing the D drive at the time, unlucky.

8. I switched again to boot from C drive, and Startup Repair showed up with "repairing disk errors. This might take over an hour to complete". It lasted only 9 seconds (!) after which PC booted just fine...
9. So now I'm yet again on the new C drive (which is now good) but with the D drive showing the same NTFS BSOD.
10. I tried forcing the Startup Repair on the D drive in hopes it will fix it too and it kinda did! It no longer shows the BSOD but instead...

# Background end
The D drive goes through this Windows loading and just gets stuck on the next Windows loading black screen - image. I left it running on that for the whole night but to no avail. So the D drive can't be booted but can be both seen (NTFS partition and its properties) and accessed (files can be copied).

Showcase images:
This PC

Disk management

I tried uninstalling quality and feature updates but both failed. I did also run DISM & sfc & chkdsk which found nothing wrong (watch out, long):

Code:

D:\>DISM /ImageD:\ /cleanup-image /checkhealth
...
No component store corruption detected.
The operation completed successfully.

D:\>SFC /scannow /OFFWINDIR=D:\Windows /OFFBOOTDIR=D:\
Beginning system scan.  This process will take some time.
Windows Resource Protection did not find any integrity violations.

D:\>chkdsk /f d: 
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  3216640 file records processed.
File verification completed.
 Phase duration (File record verification): 19.45 seconds.
  11447 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.62 milliseconds.

Stage 2: Examining file name linkage ...
  8466 reparse records processed.
  3927610 index entries processed.
Index verification completed.
 Phase duration (Index verification): 1.57 minutes.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 56.94 seconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.25 milliseconds.
  8466 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 22.26 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 10.50 milliseconds.
  355486 data files processed.
 Phase duration (Data attribute verification): 0.20 milliseconds.
CHKDSK is verifying Usn Journal...
  39977824 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 186.41 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

 976098127 KB total disk space.
 882420056 KB in 1941907 files.
    935612 KB in 355487 indexes.
         0 KB in bad sectors.
   3354503 KB in use by the system.
     65536 KB occupied by the log file.
  89387956 KB available on disk.
      4096 bytes in each allocation unit.
 244024531 total allocation units on disk.
  22346989 allocation units available on disk.
Total duration: 2.85 minutes (171255 ms).

The only place where I managed to find any indication of an error is... Startup Repair. It fails every time. SRTTrail.txt logs:

Code:

Root cause found:
A recently serviced boot binary is corrupt.
Repair action: Uninstall latest LCU Result: Failed.
Error code =  0x905
Time taken = 4766 ms

and doing

Code:

dir D:\Windows\servicing\LCU

shows:

Code:

Directory of D:\Windows\servicing\LCU
16.09.2023  00:18    <DIR>          .
16.09.2023  00:18    <DIR>          ..
10.05.2023  12:17    <DIR>          Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.2965.1.8
               0 File(s)              0 bytes
               3 Dir(s)  87 091 617 792 bytes free

This message led me to this topic which suggested recreating the Win 10 EFI bootloader. I did that but nothing has changed. It's still stuck on the Windows loading screen.
So I renamed the LCU folder to see if Startup repair can succeed now, but it just ends up with another error:

Code:

Root cause found:
---------------------------
A hard disk could not be found. If a hard disk is installed, it is not responding.

So my question is: How can I check logs of the Windows Loading black screen? It would be nice to know where it is stuck and why, and then go from there.

I'm also almost 100% certain that I could easily recover all of my files just now (because again, the main partition looks to be healthy and is accessible through C but I would rather try to recover the whole system, especially that it just seems easily repairable.
Secure boot is disabled.


Disk C - Kingston kc3000 2TB
Disk D - Crucial MX500 1TB
Windows 10 Pro 64bit,
AMD ryzen 3600x
RTX 3060 Ti
16 GB Ram

Hi, I would never try to have 2 separately installed O/S's on disks in the same PC or install an O/S on another disk with one already on another disk, unless I was specifically configuring them as dual boot.

Indeed some recommend only having the system disk in place when installing Win 10. (That shouldn't really be necessary, but sometimes people end up with partitions for the O/S spread across more than one disk).

If I wasn't aiming to clone the original system disk, as you apparently don't wish to do (is there something wrong with the installation on the original disk?) here's how I might have done what you're seeking to do:

a. I would already have a disk image of my installed O/S. I would make sure that was current.
b. I would remove that system disk, insert the new one.
c. I would install Win 10
d. I would start imaging the new O/S as early as possible
e. I would mount the image of the old O/S and copy what I wanted from that

Note: some data can only be readily acquired when the O/S is in use - e.g. browser-related, email client-related data.

Of course, there's more than one possible approach..

Does c boot if you pull the power on d? Is d an image of c as it may cause a disk collision