When Windows fails to boot, missing the C drive in BIOS or encountering NVIDIA driver conflicts, start by verifying hardware detection in the UEFI firmware before running chkdsk /r from the recovery environment. This approach ensures you address physical connectivity and storage controller issues first, preventing data corruption during file system repairs and avoiding driver installation loops caused by unstable storage subsystems.
Verifying Drive Detection in BIOS/UEFI
A common symptom of severe boot failure is the complete absence of the primary hard drive or SSD in the BIOS menu. Before attempting software fixes, you must confirm that the motherboard can physically see the storage device. If the drive does not appear in the boot order or storage list, no amount of command-line repair will restore access to the operating system files. First, restart your computer and enter the setup utility by pressing the designated key, typically Delete or F2. Navigate to the Storage or Boot configuration section. Look for your specific drive model in the SATA or NVMe port list. If it is missing, check the physical connections inside the case. For desktop PCs, reseat the SATA data cable and power connector. For laptops or M.2 drives, remove and reinstall the module to ensure proper contact with the slot. If the drive appears in BIOS but shows an incorrect capacity or "Unknown" status, refer to our guide on Fixing Unknown Status Drive Not Select Error After Making Registry Changes. This issue often stems from corrupted partition tables or controller mode settings rather than physical failure. Switching the SATA operation mode from RAID to AHCI (or vice versa) in the BIOS can sometimes resolve recognition issues, though this may require a clean Windows installation if the OS was installed under a different mode.Running chkdsk /r from Recovery Environment
Once the drive is visible in the BIOS, you can attempt to repair file system errors using the Check Disk utility. The standardchkdsk command only scans for logical errors, while chkdsk /r locates bad sectors and recovers readable information. This process is time-consuming but essential for fixing corrupted boot files or damaged system directories.
Access the Windows Recovery Environment (WinRE) by forcing three consecutive hard shutdowns during the boot logo, or by using a Windows installation USB drive. Select Troubleshoot > Advanced options > Command Prompt. In the command window, identify your Windows partition. It may not be assigned the letter C: in this environment. Use diskpart followed by list volume to find the volume containing your Windows folder.
Execute the repair command using the correct drive letter. For example, if your Windows partition is D:, run chkdsk D: /f /r. The system will scan for integrity issues and attempt to fix them. After completion, type exit and restart the computer. To verify the results, consult our article on Where to Find Chkdsk Disk Scan Report After System Restart in Windows 10, which explains how to review the Event Viewer logs for detailed error codes and success messages.
Resolving NVIDIA Driver Installation Conflicts
Sometimes, boot loops are triggered not by disk errors, but by graphics driver failures during the startup sequence. An incompatible or corrupted NVIDIA driver can cause the display to black out or crash just as Windows loads, making it impossible to proceed to the desktop. This is distinct from GPU detection issues, so if your card is recognized but drivers fail, check our troubleshooting steps at Troubleshooting: Windows Could Not Find NVIDIA GPU for deeper hardware diagnostics. To isolate driver-related boot failures, boot into Safe Mode. This loads Windows with minimal drivers, bypassing the problematic NVIDIA kernel-mode driver. If the system boots successfully in Safe Mode, the issue is likely software-related. Uninstall the current graphics driver using Device Manager or a dedicated cleanup tool like DDU (Display Driver Uninstaller) to remove residual registry keys. After cleaning the driver files, download the latest stable version from the NVIDIA website. Avoid beta drivers unless necessary for specific new hardware. Install the driver and reboot normally. If the boot issue persists, consider rolling back to a previous version known to work with your specific Windows build. Ensure that Windows Update is not automatically overriding your manual driver installation by checking the advanced update settings in the Device Manager properties.Final Verification and Stability Checks
After resolving the immediate boot and driver issues, perform a stability check to ensure the system is fully operational. Run a quick stress test to monitor temperatures and prevent crashes, keeping in mind that sudden shutdowns during testing can indicate underlying hardware faults. See our advice on PC Crashes: Game Closes Unexpectedly During Stress Tests on Windows to interpret diagnostic results correctly. Regular maintenance of your storage health is crucial for long-term reliability. Schedule periodicchkdsk scans if you experience frequent unexpected shutdowns. Keep your BIOS updated to the latest version provided by your motherboard manufacturer to improve compatibility with newer storage controllers and GPUs. By addressing hardware detection first, then file system integrity, and finally driver conflicts, you create a robust foundation for a stable Windows installation.
Frequently Asked Questions
Why does my drive disappear from BIOS after a power outage?
Power surges can corrupt the firmware on some SSDs or damage the SATA controller ports temporarily. Always use a surge protector to prevent electrical damage to your storage components. If the drive remains invisible after reseating cables, it may have suffered permanent hardware failure requiring replacement.Can I run chkdsk on the active Windows partition without recovery mode?
No, you cannot runchkdsk /r on the drive currently hosting the operating system while Windows is running. The system locks critical files to maintain consistency, which would result in an error message stating the volume is in use. You must boot from external media or the recovery environment to access and repair the active system drive.