How do i fix this startup error

[maddox5]

 

 

[NonSequitur777]

@maddox5,

Welcome to our HP Community forum!

As far as I am able to ascertain, this combined error happens when your HP computer's security system blocks the Windows boot loader, which then causes the motherboard to completely lose track of your hard drive.

Here is exactly how to fix it step-by-step.

Step 1: Fix the Secure Boot Policy:

1. Turn off your computer completely.
2. Turn it on and immediately tap the F10 key repeatedly until the BIOS/Setup screen appears.
3. Use the arrow keys to navigate to the Security tab or the Advanced tab (this varies by model).
4. Look for Secure Boot Configuration and open it.
5. Change "Secure Boot" from Enabled to Disabled.
6. Look for Legacy Support and ensure it is also Disabled (Windows 10/11 requires UEFI, not Legacy).
7. Press F10 to Save and Exit.
8. Note: If a 4-digit code pops up on a black screen after restarting, type those numbers and press Enter to confirm the change.

Step 2: Clear the Keys (If the Red Box Persists):

If the red violation box pops up again, a corrupted Windows update likely broke the security certificates.

1. Go back into the BIOS using F10.
2. Navigate back to the Secure Boot Configuration.
3. Select Key Management or Clear Secure Boot Keys (sometimes listed as "Reset to Factory Defaults").
4. Save and exit.

Step 3: Fix the 3F0 Hard Disk Error:

Once Secure Boot stops blocking the system, we need to make sure the motherboard points back to Windows.

1. Turn on the computer and repeatedly tap F10 to enter BIOS again.
2. Navigate to the Main or File tab and select Restore Defaults, then choose Yes. (This resets the boot order paths).
3. Go to the Configuration or Advanced tab and find Boot Options.
4. Ensure OS Boot Manager is listed as the very first item in the UEFI Boot Order list.
5. Press F10 to Save and Exit.

What if it still fails?

If the 3F0 error remains after completing these steps, it means either your hard drive has physically failed, or the Windows operating system files have become completely corrupted. You can press F2 on startup to run HP Hardware Diagnostics and test the hard drive's physical health.

If you try these steps, let me know:

• Did disabling Secure Boot successfully get rid of the red error box?
• What results did you get if you ran the F2 Hard Drive Test again?
• What PC are you trying to fix?

Kind Regards,

NonSequitur777

[maddox5 · Accepted solution]

Turning off secure boot fixed everything. However, I want to be able to play certain games that require secure boot. Is there a way to fix this?

[NonSequitur777]

@maddox5,

That's actually a very useful troubleshooting result!

If disabling Secure Boot allows Windows to boot normally, then your hard drive is probably fine and Windows itself is largely intact. The real problem is that Secure Boot does not trust something in the current boot chain.

Since some modern games and anti-cheat systems require Secure Boot to be enabled, yes, I would not leave it disabled permanently if we can avoid it.

Try the following:

1. Enter BIOS Setup (F10 at startup).
2. Navigate to the Secure Boot configuration menu.
3. Look for an option such as:
   • Restore Factory Keys
   • Load HP Factory Default Keys
   • Install Default Secure Boot Keys
4. Select that option and save the changes.
5. Re-enable Secure Boot.
6. Save and restart.

If Windows boots normally afterward, the Secure Boot database was likely corrupted and has now been repaired.

If the Secure Boot Violation returns as soon as Secure Boot is re-enabled, then one of the following is likely true:

• The EFI boot files are damaged.
• The EFI boot files were modified by a third-party utility.
• The system is booting from the wrong EFI partition.
• A previous Windows update or operating system repair left invalid boot signatures behind.

At that point, I would need to know:

• Your exact HP model.
• Whether Windows 10 or Windows 11 is installed.
• Whether BitLocker is enabled.
• Whether the drive was ever cloned, replaced, or moved from another computer.

I can then determine whether the EFI boot files need to be rebuilt before Secure Boot can be turned back on.

Kind Regards,

NonSequitur777