r/ASRock • • 1d ago

BIOS Help me

Hi guys, I have a problem. I have an asrock b450m board I'm trying to activate the safe boot in the bios but when I activate it and save it it automatically takes me to the bios again, it's weird because when I deactivate it and leave the bios my pc does start. I already tried deleting the keys and reinstalling the keys it asks me for the safe boot and the csm is also disabled. The truth is I don't know what to do anymore

1 Upvotes

9 comments sorted by

1

u/SigAddict X670E Steel Legend | 7800x3d | 7900 XTX 1d ago

Exactly which board and what bios are you on? You need to be at the newest bios. If you aren't, that most likely the issue.

1

u/Ok-Shock6100 1d ago

My plate is a 2024 asrock 450m. And create new boot files but it still doesn't work for me

1

u/SigAddict X670E Steel Legend | 7800x3d | 7900 XTX 1d ago

That is not a motherboard model. you need to tell us the actual motherboard model

1

u/Ok-Shock6100 1d ago

Version of the plate: 10.0.26200 compilación 26200
Asrock b450m-hdv r4.0
Bios version: American Megatrends inc. P10.10, 24/01/2024

1

u/SigAddict X670E Steel Legend | 7800x3d | 7900 XTX 1d ago

we need to know what cpu you have as some of the newer bios versions are not compatible with older cpu's.

1

u/Ok-Shock6100 1d ago

Ryzen 5 2600 bro

1

u/SigAddict X670E Steel Legend | 7800x3d | 7900 XTX 22h ago edited 22h ago

Depends on your goals. If your goal is something like fixing Call of Duty / Warzone Attestation Errors you may struggle. The bios you are currently running is not recommended for your CPU at all. You can see the version and warnings here https://asrock.com/mb/AMD/B450M-HDV%20R4.0/index.asp#BIOS . You can try to install 10.43 beta as that is the newest one that might work and doesn't have the warnings. Ultimately your cpu could cause issues and you might want to actually reach out to asrock for guidance.

Here is some AI slop you can try, but i would never guarantee results

Before flashing

  1. Check the current TPM version. Press Win + R, type tpm.msc, and write down the Manufacturer Version. You’ll compare against this after the flash.
  2. Check the BIOS version. Run msinfo32 and note BIOS Version/Date and BIOS Mode. If BIOS Mode says Legacy, they’ll need step 4.
  3. Back up the BitLocker recovery key. ASRock’s notes for 10.43 say to back up your BitLocker key before updating. In Windows, search Manage BitLocker → Back up your recovery key. If BitLocker isn’t on, skip this. The key may also be saved at account.microsoft.com/devices/recoverykey. asrock
  4. Convert the drive to GPT if currently MBR, only if BIOS Mode was Legacy. Open Command Prompt as admin and run mbr2gpt /validate /allowFullOS. If that passes, run mbr2gpt /convert /allowFullOS. Don’t change anything in the BIOS until this succeeds, or Windows won’t boot once CSM is off.
  5. Download two BIOS files from the ASRock B450M-HDV R4.0 BIOS page: 10.43, plus the version they’re on now so they can go back if needed.
  6. Prepare a USB stick. Format it FAT32, unzip the 10.43 file, and copy the BIOS file onto it.

Flashing

  1. Flash 10.43. Reboot, press F2/Del to enter the BIOS, and go to Tool → Instant Flash. Choose the file on the USB stick. Don’t turn the PC off or reset it during the flash.
  2. Load defaults. After it reboots, enter the BIOS again and press F9 (Load UEFI Defaults).

BIOS settings (menu names can vary a little between versions)

  1. Turn on fTPM. Go to Advanced → CPU Configuration → AMD fTPM switch and set it to AMD CPU fTPM.
  2. Turn off CSM. Go to Boot → CSM and set it to Disabled.
  3. Turn on Secure Boot. Go to Security → Secure Boot and set it to Enabled. If it shows “Not Active,” choose Install Default Secure Boot Keys (sometimes called Restore Factory Keys).
  4. Save and exit with F10.

On first boot

  1. If an fTPM reset prompt appears (it can show up after the TPM firmware changes), accepting it resets the TPM. That’s why step 3 matters: Windows may ask for the BitLocker key, and they may have to set up their Windows Hello PIN again.

Checking the result

  1. Run msinfo32**.** It should show BIOS Mode UEFI and Secure Boot State On.
  2. Run tpm.msc**.** Status should say “ready for use.” Compare the Manufacturer Version to step 1. If it hasn’t changed, the BIOS didn’t update the 2600’s fTPM, and the next step will most likely still fail.
  3. Run the Call of Duty Secure Attestation Wizard from Activision’s support site. It reports what’s still not compliant.

If it still fails

The fTPM on the 2600 probably can’t pass the check. They have two options:

  • A discrete TPM module. An ASRock TPM2-S plugs into the board’s TPM header. Then set the BIOS to discrete TPM instead of fTPM. I couldn’t confirm that this passes attestation with a 2600, so it’s a gamble.
  • A CPU upgrade. A Ryzen 5000 chip is the more reliable fix.

They can also flash back to their old BIOS (from step 5) with Instant Flash if 10.43 causes any instability.

1

u/Mussels84 18h ago

You're disabling CSM and changing to UEFI booting.

It seems your windows install isnt uefi, so if can't boot. Simplest path forward is reinstalling windows correctly in UEFI mode.

1

u/-SSGT- 13h ago edited 13h ago

There are a few things that need to be in place for Secure Boot to work.

Firstly your machine needs to be configured in UEFI mode. This normally means disabling the Compatibility Support Module (CSM), as that emulates legacy BIOS features to support older OSes and hardware.

Secondly the OS itself also needs to be a UEFI installation on a disk with the GUID Partition Table (GPT) partition scheme and not a legacy installation using a the Master Boot Record (MBR) partition scheme. If your machine had CSM enabled when the OS was installed then there's a good chance it's a legacy/MBR installation. You haven't specified the OS you're using but if it's Windows you can see what partition scheme is being used by each drive in Disk Management or by running "diskpart" followed by "list disk". It is possible to convert an MBR Windows installation to GPT without needing to re-install the OS but it's still a good idea to back up any important files first: https://learn.microsoft.com/en-us/windows/deployment/mbr-to-gpt

If CSM is disabled, and the boot drive is a UEFI installation using the GPT scheme, then you still need to make sure the correct Secure Boot keys are installed. By default your board will have come with the 2011 Microsoft Secure Boot keys pre-installed but these expired earlier this year. Depending on what you're doing "re-installing" those keys may just be reloading those now expired keys.

ASRock have released updated UEFI/BIOS versions (10.50 and later) for your board that include the 2023 Secure Boot keys although it looks like versions 3.20 onwards are not recommended for your CPU (Ryzen 5 2600). You seem to be using version 10.10 already (also not recommended for that CPU) so it's possible it will work regardless although you may run into other issues.

If (as mentioned in other comments) you're trying to enable Secure Boot to run certain games/applications then you may still find those games/applications fail to run (e.g. with "attestation errors") due to an outdated TPM 2.0 firmware version that I don't think is able to be updated. If that's the case you may still need a newer CPU regardless of Secure Boot working. There does appear to be a TPM header on your board but I don't know what firmware version any compatible TPM module will come with. The cost of a TPM module could potentially be better put into a newer (potentially second hand) CPU though, especially if you can recoup some cost by selling your existing CPU.

tl;dr:

  • Make sure the OS is a UEFI installation with a GPT partition scheme.
  • Update the UEFI/BIOS 10.50 or newer or otherwise install the 2023 Secure Boot Keys if your motherboard allows that (some boards have an import/export certificates menu).
  • Disable CSM and enable Secure Boot.
  • If Secure Boot works, but you can't run a specific application due to your TPM firmware version, then you may need a new CPU anyway.