Hallett0789

updated

22 days ago

H

Hallett0789

1 Rookie

•

1 Message

•

4 Points

0

117

October 24th, 2026 15:45

Area-51 R7, BIOS, TPM Attestation Failure

Alienware Area-51 R7 — TPM Attestation Failure / BIOS Update Required

I’m experiencing a TPM attestation failure preventing me from playing Call of Duty multiplayer.

My specifications are:

  • Alienware Area-51 Threadripper Edition R7
  • AMD Ryzen Threadripper 2950X
  • BIOS version 1.0.1
  • AMD fTPM firmware version 3.5.0.2
  • Windows 11

TPM 2.0 and Secure Boot are both enabled and functioning correctly.

 

However, Call of Duty reports “BIOS Firmware: Update Required” and “Failed Attestation Status”.

 

Activision confirms that AMD TPM firmware versions matching 3..0. require an update.

I’ve checked Dell’s driver downloads, but BIOS 1.0.1 appears to be the latest available for my system.

 

I’ve seen discussions about Dell providing special I-REV BIOS updates for the Alienware Aurora R10 under Knowledge Base article 000387773.

 

Does an equivalent I-REV BIOS or AMD fTPM firmware update exist for the Alienware Area-51 R7?

 

Could a Dell community manager escalate this to the BIOS engineering team?

 

Any assistance would be greatly appreciated.

(edited)

  • DELL-ChrisM2

    Community Manager

    •

    1987 Posts

    •

    9967 Points

    7

    0

    Posted October 24th, 2026 21:35

    The 2018 Area-51 R7 (or any other end of life model released 2018 and earlier) is not going to receive an I-REV BIOS for COD TPM attestation.

     

    The Dell article states that only these Ryzen systems would receive a specially built BIOS to address the issue =

    2019 Aurora R10 Ryzen I-REV BIOS

    2021 Aurora R14 Ryzen released BIOS

    2021 m15 R5 Ryzen released BIOS

    2021 G15 5515 Ryzen released BIOS

     

    #IWork4Dell

  • noahmitchell

    1 Rookie

    •

    24 Posts

    •

    66 Points

    7

    0

    Posted October 24th, 2026 18:02

    Since 1.0.1 is the latest public release for your machine, I would not try to force a build meant for a different model — those special builds are tied to that specific board, and the wrong one can leave you with a worse problem than the one you started with. First, double-check that the firmware TPM is still set as the active TPM device and that Secure Boot is actually in its enabled, deployed mode, not just switched on, because that check is picky about both. It is also worth clearing the TPM from the operating system, then rebooting and letting it re-provision before you launch the game again, since a stale attestation can stick even after the settings look right. If that still fails, the most useful next step is to get this escalated through support with your service tag sent privately, and specifically ask whether an equivalent special build exists for your model rather than waiting for the public page to change. In the meantime, do not turn the TPM or Secure Boot off just to get in, as that will only trip the same check in a different way.