The NTFS partition works on the system drive but fails to boot.
The NTFS partition works on the system drive but fails to boot.
TL;DR: My second system drive is slightly problematic. Files can still be accessed, and the partition details are accurate, but it fails to boot past Windows. The only issue is in the SRTTrail.txt logs under Startup repair. I have two SSD drives with Windows 10, both new and functional in terms of checks. The main problem appears to be in the SRTTrail.txt startup logs. I recently got two SSD drives, one 2TB and one 1TB, both installed with Windows 10. The C drive is new and working well, while the D drive has been in my PC for a year. It passed chkdsk and HD Tune tests.
I tried to install the system on the new C drive, copy necessary files from D over a few days, and then format D. However, something went wrong during the process. After installing basic software (VcRedist, Notepad++, VSCode, Adobe programs, etc.) and updates, I received a notification to restart the computer for chkdsk to scan for errors. I rebooted, but a BSOD appeared upon startup with the message "NTFS_FILE_SYSTEM". It restarted, but the BSOD repeated. I went into BIOS and booted from D, which worked fine, but I couldn't access C from This PC.
I suspected a recent Windows update might have corrupted the C file system and switched back to booting from C. Then I started chkdsk during startup, waited a bit, and stopped it by turning off the PC with the power button—this was a mistake. I switched back to booting from D, but the same BSOD appeared again. I checked the registry for BootExecute and found it set to run autocheck and autochk, suggesting chkdsk was likely running at that time.
After another switch to C drive, Startup Repair appeared and reported disk errors. It took over an hour but finished quickly (just 9 seconds). I then booted from C again, which resolved the issue. Now I'm back on the new C drive, but D still shows the same BSOD.
I attempted to force Startup Repair on D, hoping it would fix the problem, and it worked—no more BSOD.
The D drive went through Windows loading repeatedly, ending in a black screen, and I left it running for the entire night without success. It was visible as an NTFS partition but inaccessible from This PC.
I removed quality and feature updates, ran DISM, SFC, and chkdsk, but nothing resolved the issue. The operation completed without errors.
The drive shows 2TB of space, with 882420056 KB across 1941907 files. There are 3354503 KB in use, 0 bad sectors, and 89387956 KB available. The system is stable overall, but the persistent BSOD remains a concern.
I tried uninstalling updates and ran chkdsk, but it didn’t help. The logs in Startup Repair are crucial for understanding the root cause.
The main problem seems to be a corrupted boot binary from a recently serviced system, which triggered the repair steps. I’m still unsure how to fully resolve it without further investigation.
why did you set up VcRedist?
are all the apps genuine?
what is your system specification?
did you run a memory test?
1. For games.
2. Yep.
3. Included in OP post.
4. No memory errors found.
I proceeded to change the name of the `LCU` folder manually to test if the repair process would continue, but it failed more quickly with a different message.
Spoiler
Startup Repair diagnosis and repair log
But when it operated in read-only mode, it verified there were no issues. To confirm further, I reran it with the fix flag:
Code:
C:\Windows\system32>chkdsk /F d:
The file system type is NTFS.
...
Windows examined the file system and detected no problems.
No additional steps are needed.
Some games might need manual VcRedist installation to function properly.
I just discovered something odd. In the details section of the SrtLog.txt file, the date appears to be a half day ahead.
It seems your drive has probably started relying on boot files and system files located in the boot folder. However, if the new Windows version has "Fast Startup" activated, it may be locking the partitions on your C: drive. This is just a hypothesis; "Fast Startup" is typically enabled by default on Windows 10 and 11. On Windows 10, navigate to "Settings>System>Power & Sleep" and click the link for "Additional Power Settings." From there, select the option for the Control Applet, then choose the settings for the power buttons. Click on "Change Settings that are Currently Unavailable" and remove the checkmark next to "Fast Startup." Restart your computer for the changes to apply. Keep in mind that with multiple bootable Windows partitions on one machine, the booting system can overwrite files on another partition. This is why Linux is often recommended for troubleshooting and system management. Good luck with your problem, feel free to reach out if you encounter further issues or have more questions.
I turned off Fast Startup prior to this, so it doesn't solve the issue here. But thank you for your feedback ❤️