BIOS / UEFI practice questions

The SSD is not getting power

Why wrong: The drive is detected, so power is fine.

Secure Boot is blocking the Windows bootloader

Why wrong: Windows bootloader is signed and works with Secure Boot; this is not the primary issue.

The CMOS battery is dead

Why wrong: A dead battery would lose settings but not prevent boot if drive is detected.

The hard drive is failing

Why wrong: A failing drive would cause different errors like bad sectors or boot failure, not a CMOS checksum error.

The RAM module is faulty

Why wrong: Faulty RAM typically causes random crashes or beep codes, not checksum errors.

The UEFI firmware is corrupted

Why wrong: Corrupted firmware would cause a different error and likely prevent boot entirely.

The hard drive has failed due to the update

Why wrong: The drive is still detected in UEFI, so it is likely functional.

Secure Boot is blocking the bootloader

Why wrong: Secure Boot would give a different error and typically only affects non-Windows bootloaders.

The CMOS battery needs replacement

Why wrong: A dead CMOS battery would lose settings but not cause a boot device error immediately after a firmware update.

Enable Secure Boot

Why wrong: Secure Boot is for boot integrity, not virtualization support.

Enable Execute Disable Bit (XD/NX)

Why wrong: This is a security feature to prevent buffer overflow attacks, not virtualization.

Set SATA mode to AHCI

Why wrong: AHCI is for storage performance, not virtualization.

Disable Secure Boot

Why wrong: Secure Boot does not affect video output.

Enable CSM (Compatibility Support Module)

Why wrong: CSM helps with legacy boot, not video output priority.

Update the UEFI firmware to the latest version

Why wrong: While sometimes helpful, this is not the first step; the issue is likely a setting.

Enable Secure Boot and set it to Windows UEFI mode

Why wrong: Secure Boot is required but the error specifically mentions TPM, not Secure Boot.

Disable CSM and set boot mode to UEFI only

Why wrong: This is good practice but does not address the TPM requirement.

Update the UEFI firmware to the latest version

Why wrong: While updating firmware can help, the error indicates TPM is disabled, not that it's missing.

The power supply unit is failing

Why wrong: A failing PSU would cause shutdowns or instability, not just time/date loss.

The motherboard clock crystal is defective

Why wrong: A defective crystal would cause time drift while running, not reset to a specific year.

The UEFI firmware has a bug

Why wrong: A firmware bug would be consistent and not tied to power-off duration.

Enable Fast Boot

Why wrong: Fast Boot speeds up boot by skipping some checks but does not block USB boot.

Set SATA mode to RAID

Why wrong: SATA mode affects storage, not boot device selection.

Disable the TPM

Why wrong: TPM is for encryption and does not control boot devices.

Enable Legacy Boot (CSM)

Why wrong: CSM allows booting unsigned legacy OSes, which violates the policy.

Enable TPM

Why wrong: TPM provides encryption and attestation but does not control boot signature verification.

Set boot order to network first

Why wrong: Boot order does not enforce signature requirements.

Enable Secure Boot

Why wrong: Secure Boot prevents unauthorized operating systems from loading; it does not affect drive detection.

Disable the TPM chip

Why wrong: TPM is for encryption keys and security, not storage detection.

Change boot order to list the SSD first

Why wrong: Boot order only affects which device the system tries to boot from; it does not make an undetected drive appear.

Enter the UEFI setup and change the boot order permanently.

Why wrong: While this works, it is less efficient because it permanently changes the boot order, requiring another change later.

Disable Secure Boot in the UEFI settings.

Why wrong: Secure Boot prevents unauthorized OS from booting but does not affect boot order; it's unrelated to selecting a boot device.

Remove all other bootable drives from the system.

Why wrong: Physically removing drives is impractical and unnecessary when a boot menu option exists.

Update the UEFI firmware to the latest version.

Why wrong: Updating firmware is unnecessary since the drive is already detected in UEFI; the issue is at the OS level.

Change the SATA mode from AHCI to IDE in UEFI.

Why wrong: M.2 NVMe drives use PCIe lanes, not SATA; changing SATA mode has no effect on NVMe detection.

Reseat the M.2 drive in the slot.

Why wrong: Reseating is a hardware check, but since the drive appears in UEFI, it is properly connected; the issue is software-side.

Enable Legacy BIOS mode in the UEFI to support MBR.

Why wrong: Enabling Legacy BIOS would allow MBR but would not meet Windows 11's UEFI requirement, potentially causing other compatibility issues.

Disable Secure Boot in the UEFI settings.

Why wrong: Disabling Secure Boot does not change the partition table type; the drive still uses MBR, which is not supported for UEFI boot.

Update the UEFI firmware to the latest version.

Why wrong: Firmware updates do not change the partition table of the drive; the drive itself needs to be converted to GPT.

Update the UEFI firmware to the latest version from the manufacturer.

Why wrong: Firmware updates may add TPM support but do not enable it; the setting must still be changed in the UEFI.

Disable the integrated graphics to free up resources for TPM.

Why wrong: TPM is a separate hardware component or firmware module; disabling graphics has no effect on TPM availability.

Set the SATA controller to RAID mode.

Why wrong: SATA mode does not affect TPM; it only changes how storage drives are managed.

The RAID array was not properly initialized in the UEFI RAID utility.

Why wrong: If the array were not initialized, it would not appear in the RAID utility; the technician confirmed it was configured there.

The UEFI boot mode is set to Legacy, which does not support RAID.

Why wrong: Legacy BIOS can support RAID as long as the SATA mode is set to RAID; UEFI mode is not a requirement for RAID functionality.

The discrete GPU is not seated properly.

Why wrong: Video-related beep codes are usually one long followed by two or three short beeps, not three repeated beeps.

The CPU has failed or is overheating.

Why wrong: CPU errors often produce a different beep pattern (e.g., continuous short beeps) or no beeps at all, depending on the BIOS manufacturer.

The BIOS battery is dead.

Why wrong: A dead CMOS battery usually causes a checksum error or date/time reset, not a beep code indicating a hardware failure.

The BIOS has a power-on password enabled.

Why wrong: A power-on password would prevent booting entirely, not cause shutdowns after 30 minutes.

The BIOS is set to the wrong CPU multiplier.

Why wrong: An incorrect CPU multiplier could cause instability but wouldn't produce a consistent 30-minute shutdown followed by a cooldown period.

The UEFI boot order is set to network boot first.

Why wrong: Boot order affects which device the system boots from, not system runtime behavior.

The UEFI firmware has become corrupted and needs reflashing.

Why wrong: Firmware corruption would typically prevent booting or cause more severe errors, not just a checksum warning with date/time loss.

The power supply unit is not providing enough standby power.

Why wrong: While a failing PSU can cause issues, the CMOS battery is a separate, dedicated power source for the BIOS settings; the PSU's +5VSB rail is not used for this purpose.

The hard drive is failing and corrupting the boot sector.

Why wrong: A failing hard drive would cause boot or data errors, not CMOS checksum errors or date/time resets.

Enable Secure Boot and set a UEFI administrator password.

Why wrong: Secure Boot ensures only signed OS boot loaders run, but it does not prevent booting from USB drives if they are in the boot order; a password alone doesn't restrict boot devices.

Set the boot mode to Legacy BIOS and disable USB support.

Why wrong: Legacy BIOS may still allow booting from USB depending on configuration; disabling USB support entirely would also disable keyboard/mouse, making the kiosk unusable.

Enable the TPM and set a power-on password.

Why wrong: TPM is for encryption and attestation, not boot control; a power-on password prevents unauthorized access but does not restrict boot devices.

Set the boot mode to Legacy BIOS instead of UEFI.

Why wrong: Legacy BIOS has a 4 GB address space limitation for memory; UEFI is required for memory remapping and full RAM support.

Disable the integrated graphics in the UEFI.

Why wrong: Disabling integrated graphics may free some memory but does not enable the system to address RAM above 4 GB; it's not the primary solution.

Change the SATA mode from AHCI to RAID.

Why wrong: SATA mode affects storage controllers, not memory addressing; it has no impact on RAM capacity recognition.