nerdexam
CompTIA

220-801 · Question #392

A technician is not able to boot to Windows OS. A "Non-bootable device found" message appears on the screen when the computer restarts. Which of the following is the MOST possible cause of the error…

The correct answer is D. A bootable HDD is not recognized in the BIOS. A 'Non-bootable device found' error means the BIOS cannot locate a valid bootable device in the configured boot order, most commonly because the hard drive is not detected by the BIOS.

Hardware and network troubleshooting

Question

A technician is not able to boot to Windows OS. A "Non-bootable device found" message appears on the screen when the computer restarts. Which of the following is the MOST possible cause of the error message?

Options

  • AMBR is corrupt on the HDD.
  • BHDD is set to Cable Select.
  • CThe operating system is corrupt.
  • DA bootable HDD is not recognized in the BIOS.

How the community answered

(43 responses)
  • A
    9% (4)
  • B
    2% (1)
  • C
    12% (5)
  • D
    77% (33)

Why each option

A 'Non-bootable device found' error means the BIOS cannot locate a valid bootable device in the configured boot order, most commonly because the hard drive is not detected by the BIOS.

AMBR is corrupt on the HDD.

A corrupt MBR would typically produce a different error such as 'Invalid partition table' or 'Missing operating system,' not a non-bootable device message, because the BIOS would still detect the drive.

BHDD is set to Cable Select.

Cable Select is a jumper setting for older IDE drives and does not cause a non-bootable device error on modern SATA systems.

CThe operating system is corrupt.

A corrupt OS would be discovered after the BIOS hands off to the boot loader, producing OS-level errors, not a BIOS-level non-bootable device message.

DA bootable HDD is not recognized in the BIOS.Correct

When the BIOS cannot detect the HDD in its device list or boot order, it cannot attempt to load any boot sector or OS, resulting in a 'non-bootable device' or 'no boot device' error. This can occur due to a loose SATA/power cable, a failed drive, or incorrect BIOS boot order settings. Unlike a corrupt MBR or OS, this error manifests before any partition or filesystem is even examined.

Concept tested: BIOS boot device detection and boot order

Source: https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/windows-boot-issues-troubleshooting

Topics

#boot failure#BIOS HDD detection#non-bootable device#POST

Community Discussion

No community discussion yet for this question.

Full 220-801 Practice