[Firmware Bug]: Failed to parse event in TPM Final Events Log

Help
1

Today I’ve noticed a
[Firmware Bug]: Failed to parse event in TPM Final Events Log

on my NixOS startup. I shrugged and ignored it. However Windows when booting got a BSOD on TPM.sys. I was able to boot Windows using UEFI’s Windows menu entry – only the entry on systemd-boot got that error.

I also had no generations showed on the systemd-boot. At last I decided to ask Google’s Gemini and got the generations listing back with

sudo /run/current-system/bin/switch-to-configuration boot

So, the problem is fixed. After generations appeared again and even selecting the latest one, the error does not appear again on NixOS start and Windows now boots successfully using NixOS menu.

But the process through which I got into the initial state is not clear to me.

Any tips on why I got into that mess and why the latest entry now does not trigger the issue?

1 Like
2

I mean, it literally says:

Hard to know what triggered this; the TPM is stateful, and clearly something tickled it in such a way as to send invalid events. Could be anything from something overheating to an actual firmware bug that you accidentally fixed by writing a new boot entry.

Consider updating your firmware, but there’s not much else you can do.

1 Like