-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Enabling fTPM can cause stuttering on some Ryzen systems
- Thread starter GregI
- Start date
It's a nice buzz word
Given all the vulnerabilities in Windows 10/11 outside of TPM - one of the latest in a long line for instance being CVE-2021-43890, many of which shouldn't be there in the first place, it isn't going to accomplish much anyhow in terms of protecting the end user - it does however increasingly take away control of the machine from the end user...
I find it amusing when people get their knickers in a twist over Windows 7 and security yet if anything 10/11 are in a worse place despite having security updates (outside of extended support) because of MS incompetence.
Sadly most people don't have the foresight to see why boycotting TPM would be a good idea.
Indeed, I ditched windows long ago so makes no difference to me anyway.
Problem is if TPM becomes established, companies in general are going to start to want it as a requirement for the most mundane things so eventually other OSes will either lose out or be forced to adopt it... in the longer term it shifts a huge amount of power away from the end user even over the most everyday things, sets the groundwork for wholesale control of the internet and has huge privacy implications.
Quite frankly no one sane should support the adoption of TPM but sadly it will take a long time for people to recognise that.
That's a little hyperbolic given half of this thread say they've not had any issues...
Soldato
- Joined
- 30 May 2007
- Posts
- 4,970
- Location
- Glasgow, Scotland
Why not?
News to me, I've been running a hardware tpm for months this is the first of me hearing about this...
The problem is trying to get reports of this is really difficult. What information to trust and what not to trust.
For example I've read countless people rage and being like "GOD YOU CAN'T DISABLE FTPM ON ASUS IT'S MESSED UP!!!!!". In fact you can. So if someone like that said "my physical tpm module fixed it" I'm unlikely to believe them. You then have people who might have actually installed a tpm module but not configured the BIOS to actually use it... yes that happens. Someone on the Linus forum couple days ago seemed to have their head screwed on and says it did for them so who knows.
Just didn't want people to rush out and buy a tpm module so I still stand by that statement for now.
Anyway a general update on the situation. Someone trying to farm karma or whatever on the AMD reddit posted the toms guide article (1 whole week after it got published lol) and it seems to have blown up with 1.3k upvotes. This karma farming attempt seems to have got the right people noticing.
Coincidentally ASUS released AGESA 1.2.0.6b today so maybe that has some fix in it. No reports for or against this fixing the problem but I highly doubt it does, way too soon. I'll update in a couple of days if any pertinent info is revealed.
So you discount 50% of reports then, hardly hyperbolic.
Of course it's hyperbolic. You made the absolute statement that AMD messed up its fTPM implementation. 50% of users said they're fine, so immediately indicates the situation is more complex than just "AMD broke it" like you claim, and therefore requires further investigation. An operating system is a complex piece of software, and issues can stem for absolutely anything, especially the knotted dog pile that is Windows. So you dig and dig to see what the issue is and then see how many cases of this issue are in fact down to a bugged fTPM, and perhaps even then do the bugs come from AMD's core codebase or is it actually from the motherboard vendor's implementation.
It's exactly the same deal as people like Cyber-Mav decrying the entirety of Ryzen 5000 to be broken because a higher-than-normal percentage of CPUs in the wild were duff to varying degrees. 3% or something either didn't hit stock or were outright DOA? Now that's an obscenely high percentage of CPUs that should never have made it out of the factory, but to claim "Ryzen 5000 is broken" when 97% of all CPUs are perfectly fine is hyperbolic.
So yes, until such time things are fully determined, your sweeping statement is very much hyperbole.
It's exactly the same deal as people like Cyber-Mav decrying the entirety of Ryzen 5000 to be broken because a higher-than-normal percentage of CPUs in the wild were duff to varying degrees. 3% or something either didn't hit stock or were outright DOA? Now that's an obscenely high percentage of CPUs that should never have made it out of the factory, but to claim "Ryzen 5000 is broken" when 97% of all CPUs are perfectly fine is hyperbolic.
So yes, until such time things are fully determined, your sweeping statement is very much hyperbole.
Associate
- Joined
- 4 Oct 2017
- Posts
- 1,320
I don't appear to have an option to disable fTPM. I can only select discrete fTPM module, which I'm assuming is the closest thing to disabling it?
This is on an Asus Dark Hero board.
The 5950x was my first venture into amd since the Phenom days and I'm full of regret, it's been nothing but issues.
This is on an Asus Dark Hero board.
The 5950x was my first venture into amd since the Phenom days and I'm full of regret, it's been nothing but issues.
Associate
- Joined
- 4 Oct 2017
- Posts
- 1,320
I do have stutters in games which I assumed were frame time spikes. I may try and change the setting to see if it improves anything.
From my OP.
4: There has been some massive confusion about how to disable fTPM from people saying "My ASUS BIOS doesn't allow it". This is simply not true. Every board manufacturer to my knowledge allows TPM to be disabled. For ASUS you go to Advanced > Trusted Computing > Security Device Support > Set to Disable. You do not actually have to be in the AMD fTPM configuration menu at all (which is where the confusion has arisen).
Associate
- Joined
- 4 Oct 2017
- Posts
- 1,320
Thank you, I should have read your post more thoroughly. Apologies.
I'll look into my bios for that. I was (like many) looking into the fTPM menu.
No problem. If you want to know if this is likely your issue this seems to be a decent way of knowing.
1: Open event viewer and wait for it to load fully (5 seconds or so)
2: Under the error section you should see "CertificateServicesClient-CertEnroll" and double click it
3: Verify an event id 86 was logged (most likely at system startup time).
If you don't see this event id 86 you likely have another issue.
Associate
- Joined
- 4 Oct 2017
- Posts
- 1,320
@GregI it looks like I did suffer from that error as I've just checked it.
Literally gone into the bios and disabled it so will see if it works.
Literally gone into the bios and disabled it so will see if it works.
@Jay343434 Yeah if you disabled it that error won't show up now and your issue should also be resolved.
While I have you can you check your event viewer for this specific event id related to fast startup when you switch the PC on (if you have it enabled ofcourse): https://i.imgur.com/FD5gzEI.png
No matter what I do on this Dark Hero board I always apparently fail fast startup.
While I have you can you check your event viewer for this specific event id related to fast startup when you switch the PC on (if you have it enabled ofcourse): https://i.imgur.com/FD5gzEI.png
No matter what I do on this Dark Hero board I always apparently fail fast startup.