Liste des Groupes | Revenir à col advocacy |
Andrzej Matuch <andrzej@matu.ch> wrote:On 2025-01-02 14:00, Frank Slootweg wrote:Andrzej Matuch <andrzej@matu.ch> wrote:>
[...]
>The bug that finally caused me to stop bothering with them isn't>
Microsoft's fault, but I do fault them for continuing to demand TPM when
the requirement was causing stuttering with anyone who owned an AMD
processor. [...]
I didn't follow this 'stuttering' problem before, but as I have an AMD
processor and - like you - in a laptop [1], can you tell me how/where I
would experience said stuttering? So far everything seems to be running
fine.
>
[...]
>
[1] HP Pavilion 15-eh2560nd laptop, AMD Ryzen 5 5625U 2.3Ghz 6 Cores,
Windows 11 24H2.
An example:
>
<https://www.youtube.com/watch?v=TYnRL-x6DVI>
Thankss!
I've never experienced any noticeable video/display stuttering, but
then I don't play games and watch few, but some, videos. OTOH, the
author says "Regardless of what programs I was running.". I assume he
means "Regardless of what *other* programs I was running."
I got my laptop in end of July 2022. Most references are older than
that. Perhaps my laptop was already fixed by HP/AMD.
The video and its notes talk about 'fTPM' ('firmware TPM'). When I run
'tpm.msc' as mentioned in the notes, the 'Trusted Platform Module
Management' plugin only mentions 'TPM', not 'fTPM' anywhere, so perhaps
I *do* have a discrete TPM module.
Anyway, the only specific information reported is:
"TPM Manufacturer Information
Manufacturer Name: AMD
Manufacturer Version: 3.91.2.5
Specification Version: 2.0"
An acknowledgement from AMD:
>
<https://videocardz.com/newz/amd-acknowledges-ftpm-stuttering-issues-promises-a-bios-fix-in-may>
>
I doubt that you never experienced it. However, you might have had it
fixed if you use a desktop and the manufacturer of your motherboard
issued an update for the problem.
Thanks again! I thought I didn't download/install any BIOS firmware
update, but on checking my notes, I remembered/saw that there was a
*forced* BIOS upgrade as part of the 12SEP2023 monthly Windows Update
cycle, so perhaps the problem (which I never encountered/noticed) was
fixed at that time.
AFAIC, case closed. But feel free to comment. Thanks.
Les messages affichés proviennent d'usenet.