Before you begin
A PC starts in stages: power, hardware checks, selection of a boot device, then Windows. A logo that stays on screen, a BIOS menu and a Windows repair loop are different symptoms. Write down the last thing you see and whether this started after a change, a delivery or an unexpected shutdown.
This guide is for a PC that powers on and shows a picture. If there are no lights or fans, use our power guide. If the monitor has no signal at any stage, start with no display. Keep any important files backed up whenever the machine starts successfully.
Do not initialise, format or erase a drive to make it appear in BIOS. Stop if a drive is clicking, disappearing repeatedly or reporting a health warning. Protecting recoverable files comes before repairing Windows.
Work through the checks
-
Remove external distractions
Shut down and unplug non-essential USB devices, external drives and memory cards. Leave a keyboard, mouse and one monitor. Restart once and note any difference. A connected USB drive can alter boot selection; an attached device can also hold up hardware checks. If the PC now starts, reconnect devices individually after Windows loads so you can identify which one changes the behaviour.
-
Identify the message
Photograph the complete screen. “No bootable device” means no usable boot entry was selected; it does not prove the SSD has failed. A manufacturer logo without progress can have several causes. Motherboard lights and two-character codes must be interpreted using that exact board’s manual. For example, a code such as A0 is not a universal drive-failure diagnosis.
-
Check whether the system drive is detected
Enter the firmware setup using the key specified by the motherboard manual. Inspect its storage information without changing settings. SATA drives and NVMe drives may appear in different menus. Record the model and capacity of every detected drive. Do not assume Disk 0, the smallest drive or the first SATA port is where Windows lives. Compare the details with your order and any previous working configuration.
-
Check the boot entry
On a typical UEFI Windows installation, look for Windows Boot Manager associated with the system drive. If a temporary USB device is selected first, use the board’s one-time boot menu to try the existing Windows entry. Photograph settings before making an agreed change. Do not toggle RAID, VMD, AHCI, CSM or Secure Boot at random: changing the storage or boot mode can prevent an otherwise intact installation from starting.
-
Choose hardware checks or recovery
If the drive is missing in firmware, Windows repair tools are unlikely to solve detection. Check our missing-drive guide and contact support before internal work. If the drive is detected and Windows begins loading but fails, use Windows recovery. Startup Repair or reversing a recent update may be appropriate before a reset.
-
Retest and record the outcome
After each change, restart once and record the result. If Windows opens, back up important files before further troubleshooting. Confirm the same drive remains detected on a later normal restart. A successful boot after moving a cable is useful evidence, but an intermittent connection still needs attention. Stop repeated power cycling if the PC shuts off unexpectedly or a damaged connector is visible.
What the results tell you
Drive missing from firmware
Possible causes include the connection, slot configuration, controller or drive itself. A failed reseat alone is not proof of a dead SSD.
Drive visible, Windows entry missing
The boot configuration or Windows installation may need repair. Keep the drive contents intact while support identifies the correct recovery method.
Windows logo appears, then a stop code
Record the code and use the blue-screen or recovery guide. This is a later startup stage than a monitor with no signal.
Common questions
Should I remove the BIOS battery?
Not as a first step. Clearing settings can change boot behaviour and lead to an encryption recovery prompt. Use the board-specific method only after documenting settings and locating your recovery key.
Can I delete a driver named in a repair log?
Do not delete system drivers from a command prompt based only on a log filename. The named file may be a symptom rather than the cause. Share the log or error with support.
Does a missing drive mean my files are gone?
Not necessarily. Detection failures have several causes. Avoid writing to the drive if the files matter, and discuss recovery before replacement or installation.
When to contact ElitePCS
Contact us if the system drive is absent, the firmware freezes, boot entries keep disappearing or recovery cannot start. Send the motherboard model, drive list, full error photograph and the last change before the fault.
Contact ElitePCS support. Include your order number, the exact symptom and the checks you have completed. Keep passwords, licence keys and recovery keys out of screenshots.
Technical references: Microsoft recovery options · ASUS startup diagnostics. Reviewed 27 September 2026.