New CPU added. fTPM/PSP NV is damaged and stuck, "Y" does nothing
New CPU added. fTPM/PSP NV is damaged and stuck, "Y" does nothing
Hello Guys, thank you for taking the time to read ahead!
I’m facing an unusual issue that I’ve never encountered before.
After building a new PC, I noticed the following:
The CPU was replaced and the fTPM/PSP NV files were either corrupted or their structure changed.
Pressing Y will reset the fTPM. If Bitlocker or encryption is active, the system won’t boot without a recovery key.
Pressing N keeps the previous fTPM data and lets the system boot normally. The fTPM won’t work on the new CPU; you can revert to the old one to recover related keys and data.
The main concern is that the system remains unresponsive. Pressing Y doesn’t produce any action, and pressing N or Del also yields little effect. I found a Spanish video suggesting a workaround: pressing both N and Del at the same time to enter BIOS and disable "Security Device Support," which might disable TPM.
However, this solution has drawbacks—it prevents installing Windows 11, as it requires TPM functionality.
I’ve tried resetting the CMOS and updating the BIOS, but also reset the BIOS myself.
Could this mean I have a faulty CPU or motherboard? I encountered difficulties reaching this point and had a black screen of death. I’m uncertain what caused it (perhaps re-seating RAM).
Details: B550M Aorus Elite Rev.3
5800x, 2x16 CL16, 16GB RAM, 750W PSU, 1TB Samsung SSD.
I really value your assistance! Thanks!
Checking the BIOS settings can reveal the current version installed on your motherboard.
Hi there,
I'm facing the same issue, the "Y" key doesn't respond. From what I found, it's because the BIOS is expecting a "QWERTY" keyboard. Since I have a "QWERTZ" keyboard, I had to press Z to make it work. Hope this helps. See you around!
I even attempted that, pressed z and still nothing happened... I plan to try it with a different keyboard first. Please let Simeone know right away. Thank you for your help. Just begin the setup again from scratch. This issue occurs when inserting and starting the remote drive DVD Windows 11 64bit home before installation.