XPS 8940 BIOS 2.17.1 Intel PTT Firmware Remote Attestation Failure in Call of
Duty
I am reporting a firmware signature mismatch issue on a Dell XPS 8940 desktop running the latest official BIOS version 2.17.1.
Inside Windows 11, my hardware security layers are perfectly healthy, active, and fully compliant:
Secure Boot State: ON (Verified via msinfo32) [1.4.x]
BIOS Mode: UEFI PCR7 Configuration: Binding Possible
My Motherboard Product Code is: 0427JK A00
My TPM Manufacturer Version (tpm.msc) is: INTC 500.14.75.2420 Ver 2.0
While Activision's standalone Secure Attestation Wizard passes with two green checkmarks, the live Call of Duty game client applies a "Failed Attestation Status" restriction to my account. This blocks access to Ranked Play and locks my matchmaking exclusively to casual public lobbies.
Testing suggests that Call of Duty's anti-cheat framework (RICOCHET) uses a secure remote verification process that is rejecting the specific Intel PTT sub-firmware string compiled into Dell's 2.17.1 BIOS update. Because out-of-warranty users cannot submit individual repair tickets to Dell without a paywall, I am posting this here so Dell engineering can coordinate a signature whitelist update with Microsoft and Activision for this motherboard platform.
Activision Support has formally reviewed my account and stated that because the system is passing their standalone software check, the live block is a firmware communication issue that must be addressed directly by Dell.
Technical Support stance is correct. I will try to clear up the confusion.
Dell never released an I-rev BIOS for the 2020 released XPS 8940 or any XPS desktop to address TPM Attestation/RICOCHET.
Dell internal article 000387773 never mentions any Intel CPU. Only AMD CPU (Ryzen). The article also never mentions any XPS desktops. It only mentions the following applicable models =
Thanks for this. But following up with Dell and quoting this I-Rev Bios they advise that is only for Alienware not XPS. Do you have any thoughts on their comment? They are now advising me to kick it back to Activision to resolve.
I'm experiencing what appears to be the same Call of Duty attestation failure on my Dell XPS 8940, despite meeting all the security requirements.
My system:
Dell XPS 8940, motherboard 0K3CM7, revision A00
Intel Core i9-11900K
Dell BIOS 2.27.1
Intel PTT TPM 2.0, firmware 500.14.75.2420
Windows 11, UEFI boot, Secure Boot enabled
SHA-256 TPM PCR bank active
The Call of Duty Secure Attestation Wizard passes all nine checks, including Secure Boot, TPM, TCG log and EFI measurements.
However, the game still displays:
"You are under Failed Attestation Status. This playlist is currently unavailable."
Activision's account enforcement check confirms No Ban Detected.
I've completed extensive troubleshooting, including updating the BIOS, clearing and reprovisioning the TPM, restoring BIOS defaults, updating Secure Boot certificates, and changing the TPM PCR bank to SHA-256. None of these procedures resolved the problem.
I have also identified a reproducible TPM measured-boot discrepancy.
Windows TPM-WMI Event ID 1041 consistently reports:
The official Activision diagnostic tool generated a ZIP archive, which I have submitted to Activision.
I've also seen references to Dell support article 000387773, concerning TPM attestation failures, and to special I-REV BIOS firmware provided for certain Dell systems.
Could Dell confirm the following?
Is this a known Intel PTT or measured-boot firmware issue affecting the XPS 8940?
Does Dell article 000387773 apply to the XPS 8940?
Is an I-REV or other corrective BIOS available for this model?
Can Dell firmware engineering investigate the PCR 0 mismatch on BIOS 2.27.1?
My system is out of warranty, but this appears to be a firmware-level compatibility issue rather than a conventional hardware failure.
I would appreciate any guidance from Dell engineering or anyone who has successfully resolved this issue on an XPS 8940.
Thank you for clarifying that the I-REV BIOS does not apply to the XPS 8940.
I'm experiencing the same Call of Duty attestation failure on my XPS 8940, running BIOS 2.27.1 with Intel PTT firmware 500.14.75.2420.
The official Call of Duty Secure Attestation Wizard passes all nine checks, but the game reports Failed Attestation Status.
During troubleshooting, I identified a reproducible TPM measured-boot discrepancy.
Windows TPM-WMI Event ID 1041 reports:
PcrsMatchTcgLog = false
BitMaskOfPcrMismatches = 1
HealthStatus = Possibly attestable
The tpmtool comparepcr sha256 command independently confirms that PCR 0 does not match the TCG measured-boot event log.
This persists after updating the BIOS, clearing and reprovisioning the TPM, and switching the active PCR bank to SHA-256.
My question is specifically about the firmware measurement discrepancy:
Is Dell aware of any PCR 0 / TCG measured-boot inconsistencies involving Intel Boot Guard or Intel PTT on the XPS 8940?
Is this something Dell firmware engineering could investigate, even though the I-REV BIOS solution does not apply to this model?
I understand that Activision must investigate the game's attestation rejection, and I've already submitted their diagnostic ZIP. However, the PCR 0 mismatch is independently reproducible in Windows, regardless of whether Call of Duty is running.
UPDATE — October 23, 2026: Identical attestation failure confirmed on a second Dell XPS 8940
I have now confirmed this issue on a second, independently configured Dell XPS 8940. Both computers are unable to access Call of Duty: Modern Warfare 4 multiplayer or DMZ on the game's official release date.
Both display the identical error:
"You are under Failed Attestation Status. This playlist is currently unavailable."
Hardware and firmware — identical on both systems:
Dell XPS 8940
Intel Core i9-11900K
Dell BIOS 2.27.1
Intel PTT TPM 2.0
Intel PTT firmware 500.14.75.2420
Secure Boot enabled
Diagnostic findings — identical on both systems:
TPM present, enabled, activated, and ready
TPM reports ready and capable for attestation
Activision Secure Attestation Wizard passes all nine checks
AIK certificate enrollment succeeds
Windows TPM-WMI Event ID 1041 reports:
HealthStatus: Possibly attestable
PcrsMatchTcgLog: false
BitMaskOfPcrMismatches: 1
tpmtool comparepcr independently confirms a mismatch between the physical TPM PCR 0 measurement and the value reconstructed from the TCG measured-boot event log.
Importantly, the first computer exhibits the mismatch using the SHA-256 PCR bank, while the second exhibits the same mismatch using SHA-1.
The second computer has not undergone the extensive TPM and BIOS troubleshooting performed on the first. This demonstrates that the discrepancy is reproducible on another independently configured system.
Why this requires engineering investigation
Both computers pass Activision's security diagnostic wizard, yet both are rejected by the game's attestation enforcement.
The consistent PCR 0 mismatch raises the possibility of an issue involving Dell's BIOS, Intel Boot Guard/PTT measured-boot implementation, or the generation or interpretation of the TCG event log.
We recognize that the PCR mismatch has not yet been conclusively established as the cause of the game's rejection. Nevertheless, it is a reproducible firmware-level measurement discrepancy deserving investigation.
Request to Dell
Could Dell please escalate this to the XPS 8940 BIOS/firmware engineering team and investigate:
Whether BIOS 2.27.1 has a known issue involving PCR 0 measurements or TCG event-log generation.
Whether Intel Boot Guard measured-boot events are being recorded and replayed correctly.
Whether Dell can reproduce this PCR 0 discrepancy on an XPS 8940 with BIOS 2.27.1.
Whether a BIOS or firmware correction is available or planned.
Whether Dell can coordinate with Intel, Microsoft, or Activision to identify the incompatibility.
Both computers are now unable to access the multiplayer functionality for which the game was purchased, including on its official release date.
We have collected Windows attestation event logs, TPM PCR comparisons, TCG boot logs, and Activision diagnostic packages from both systems and can provide them privately to Dell engineering.
We would appreciate an engineering-level response rather than another recommendation to clear the TPM, reset BIOS settings, or reinstall Windows, as those troubleshooting approaches have already been extensively investigated.
@jame.hodge did you ever find a solution to this issue? I want to play the game but i cannot because of the attestation issue, I also have a XPS 8940.
@seaguss Sorry no. In an emailed response from tech support Dell advise - "In the screenshots you kindly provided, the official COD Secure Attestation Scanner app explicitly passed and shows your system is fully compliant. In genuine hardware/firmware failures investigated by our teams, this scanner fails immediately. Because your PC passes the official scanner completely, your Dell motherboard, TPM 2.0, UEFI, and Secure Boot are verified compliant with Activision’s standards." They then go on to kick it back to Activision by saying - " We completely share your desire to have your game working normally again. Since your hardware has officially passed the Call of Duty Scanner test, we strongly encourage reporting this result via Activision's TPM report form linked above so their software engineering team can address this false-positive trigger on your account/client."
Adding a third XPS 8940 with the same PCR 0 measured-boot mismatch. My data shows it isn't new to BIOS 2.27.1 and isn't tied to one PCR bank.
System
- XPS 8940, board 0427JK A00, Core i7-11700
- BIOS 2.27.1 (updated from 2.10.0 on Oct 20, 2026)
- Intel PTT TPM 2.0, firmware 500.14.75.2420
- Windows 11 25H2 (build 26200), UEFI, Secure Boot on
- Secure Boot certificates current: KEK and db contain the Microsoft 2023 CAs, Windows reports the Secure Boot CA/key update as done (TPM-WMI event 1808), and the boot log shows the boot manager was authorized by Windows UEFI CA 2023
- CODSecureAttestationWizard 1.3.0 passes every check, but MW4 multiplayer still gives me "Failed Attestation Status"
What I found
1. Windows' own pre-attestation check (TPM-WMI event 1041, saved in C:\Windows\Logs\MeasuredBoot\*.json) has never once found the boot log matching the TPM on this PC. Of the checks still on disk:
- BIOS 2.10.0: 95 of 95 boots, Jan 10 to Oct 20, 2026, show "PcrsMatchTcgLog": false, "BitMaskOfPcrMismatches": 1 (PCR 0 only)
- BIOS 2.27.1: 11 of 11 completed checks show the same PCR 0-only mismatch (2 more boots couldn't run the comparison because the TPM wasn't ready right after a driver install)
HealthStatus is "Possibly attestable" on every boot except a few right after the TPM was cleared or reinstalled, which show "Cannot be attested" until Windows re-enrolls the attestation certificate.
2. I replayed the TCG event log myself. PCRs 1-15 match the TPM exactly; only PCR 0 does not:
- Firmware log is SHA-1 legacy format (jame.hodge sees the same mismatch on SHA-256 on another 8940, so the bank doesn't matter)
- PCR 0 events in the log: StartupLocality (locality 3), "Boot Guard Measured S-CRTM", S-CRTM version, POST code, separator
- Replayed PCR 0 (starting from locality 3): d857a7dd2ff2add0112bbdbdad9922c6e95d3731
- Actual TPM PCR 0 (SHA-1): 499c45706169000bac4a7dd48e7db434d55bf61b
So the TPM's PCR 0 contains a measurement the firmware didn't log correctly, most likely in the Intel Boot Guard / S-CRTM step. A remote attestation service that checks the log against a TPM quote (CoD reportedly uses Microsoft Azure Attestation) would reject that.
3. Already tried, with no change:
- BIOS 2.10.0 -> 2.27.1
- Restore BIOS defaults
- PTT Clear (Windows logged the clear, re-provisioned the TPM, and re-enrolled its attestation certificate)
- Latest Intel Management Engine Components package from SupportAssist
- There's no SHA-256 option on this board's PTT Security page (only PTT On / Clear / PPI Bypass for Clear Commands)
About the Dell email David quoted above: the Activision wizard's checks confirm that a TPM 2.0, Secure Boot and a boot log are present. None of them compare the boot log with the TPM's PCR values. That comparison is the one Windows says fails, so passing the wizard doesn't show the firmware is fine.
This now reproduces on three XPS 8940s, two board revisions (0427JK and 0K3CM7), two CPUs, both PCR banks and two BIOS versions. Could it go to the XPS 8940 BIOS team to check whether the Boot Guard PCR 0 measurement is being logged correctly? I can share the Windows health-check files, the raw TCG logs and the Activision diagnostic ZIP privately with Dell engineering.
DELL-ChrisM2
Community Manager
•
1993 Posts
•
10000 Points
31
0
Posted October 19th, 2026 14:44
Technical Support stance is correct. I will try to clear up the confusion.
Dell never released an I-rev BIOS for the 2020 released XPS 8940 or any XPS desktop to address TPM Attestation/RICOCHET.
Dell internal article 000387773 never mentions any Intel CPU. Only AMD CPU (Ryzen). The article also never mentions any XPS desktops. It only mentions the following applicable models =
Aurora R10 Ryzen desktop
Aurora R14 Ryzen desktop
m15 R5 Ryzen laptop
G15 5515 Ryzen laptop
#IWork4Dell
