• 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.

Ryzen 7000 and 9000 see massive gains from Windows 11 24H2. Mostly.

Thought Recall had been removed from current builds, it’s the horrendous feature that records everything you do and uses “AI” to apply context and make it searchable.
 
fTPM stuttering has been fixed in newer BIOSes on AM4 according to AMD (AGESA 1.2.0.7 and later).

Recently my Desktop isn't as silky smooth as it used to be, minimizing windows to the task bar sometimes has a bit of judder, i don't know what it is, no changes to my hardware, reinstalled windows..... i did update the BIOS to F17 recently, thinking about rolling it back to F16c.

 
Last edited:
Recently my Desktop isn't as silky smooth as it used to be, minimizing windows to the task bar sometimes has a bit of judder, i don't know what it is, no changes to my hardware, reinstalled windows..... i did update the BIOS to F17 recently, thinking about rolling it back to F16c.

I doubt that's due to fTPM stutter. I am very familiar with that stutter, it is a huge stutter that occurs at random intervals where everything goes into slow motion and the sound becomes distorted.

I was pulling my hair out because it could happen as rarely as once a month or as frequently as once an hour and I thought there was some weird fault with my hardware, but I didn't realise that it wasn't a hardware issue at all until AMD owned up.

Here's a video showing what it's like:
 
Last edited:
I doubt that's due to fTPM stutter. I am very familiar with that stutter, it is a huge stutter that occurs at random intervals where everything goes into slow motion and the sound becomes distorted.

I was pulling my hair out because it could happen as rarely as once a month or as frequently as once an hour and I thought there was some weird fault with my hardware, but I didn't realise that it wasn't a hardware issue at all until AMD owned up.

Here's a video showing what it's like:

Oof.... ouch.

En****itification of Windows by M$
 
Last edited:
The fTPM stuttering on AM4 was supposedly fixed from AGESA version 1.2.0.7 and later.
I actually didnt hear about this so maybe I will enable it again.. think my current BIOS is the first AGESA 1.2.0.7 release but theres another BIOS update just came out, but the naming gets confusing.

Currently have BIOS with AGESA ComboAm4v2PI 1.2.0.A.
Latest BIOS is AGESA ComboAm4v2PI 1.2.0.Ca.

Why dont they just stick with numbers lol

I'm dual booting Win 10 and Win 11 at the moment (trying to do a slow transition but I'm not liking 11 right now :( ) and in Win 11 Core Isolation does not even show up in search so I'm guessing fTPM disabled is causing this?

Not sure what the newer AGESA update brings but the only other fix in the description is some 'Fixed CVE-2024-36877 security issue' which applies to..

Intel 300, Intel 400, Intel 500, Intel 600, Intel 700, AMD 300, AMD 400, AMD 500, AMD 600 and AMD 700..

but this is one of those where somebody needs to physically be at your PC from what I've read.
 
Last edited:
I actually didnt hear about this so maybe I will enable it again.. think my current BIOS is the first AGESA 1.2.0.7 release but theres another BIOS update just came out, but the naming gets confusing.

Currently have BIOS with AGESA ComboAm4v2PI 1.2.0.A.
Latest BIOS is AGESA ComboAm4v2PI 1.2.0.Ca.

Why dont they just stick with numbers lol

I'm dual booting Win 10 and Win 11 at the moment (trying to do a slow transition but I'm not liking 11 right now :( ) and in Win 11 Core Isolation does not even show up in search so I'm guessing fTPM disabled is causing this?

Not sure what the newer AGESA update brings but the only other fix in the description is some 'Fixed CVE-2024-36877 security issue' which applies to..

Intel 300, Intel 400, Intel 500, Intel 600, Intel 700, AMD 300, AMD 400, AMD 500, AMD 600 and AMD 700..

but this is one of those where somebody needs to physically be at your PC from what I've read.
I think it doesn't show up if virtualisation is disabled in the BIOS (SVM on AMD). The A and C are hexadecimal numbers by the way with A being 10 and C being 12.

That particular CVE is MSI specific and the likelihood of it being exploited is high according to this (it doesn't sound like the attacker requires physical access, but I'm not an expert):

 
Last edited:
I think it doesn't show up if virtualisation is disabled in the BIOS (SVM on AMD). The A and C are hexadecimal numbers by the way with A being 10 and C being 12.

That particular CVE is MSI specific and the likelihood of it being exploited is high according to this (it doesn't sound like the attacker requires physical access, but I'm not an expert):

Yes you're correct, I just tested some different settings in BIOS and it is SVM :)

As for the BIOS update, damn I hate doing these, the scariest thing to do for a PC when you only have a single BIOS Motherboard :eek:

Will do it in the daytime as my luck will be getting a power cut at this time of night.

Cheers.
 
Recently my Desktop isn't as silky smooth as it used to be, minimizing windows to the task bar sometimes has a bit of judder, i don't know what it is, no changes to my hardware, reinstalled windows..... i did update the BIOS to F17 recently, thinking about rolling it back to F16c.


I figured it out, not having this enabled was the problem.

RqAuSsy.jpeg
 

Right so his original Zen 5 benchmark result was under performing due to "A bad Windows install" He even admits he was seeing inconsistent results with that build but ignored it, in his last podcast he said others who got better results than him are just plain wrong, even citing LTT.

Its never him who gets it wrong, its everyone else, its other reviewers, its Windows, its AMD. This is not the first time he got it wrong and blamed everyone but him self.
 
One more thing, he gave his reasoning for ignoring the problem was that Intel was getting consistent results, so he just put it down to AMD, which speaks volumes in its self about his mind set, no wonder its so easy for him to publish results that are wrong and make a click bait video out of it raging at AMD.... but here's the point, when he published the 30% 9700X gains for 24H2 vs his original review he said Intel also gained 20%. :rolleyes:

You know what he was doing, he was just using that same drive with that same windows install for all his reviews, just plugging it in to Intel motherboards and then AMD for reviews..... Who does that????? No wonder it was broken.
 
Last edited:
Right so his original Zen 5 benchmark result was under performing due to "A bad Windows install" He even admits he was seeing inconsistent results with that build but ignored it, in his last podcast he said others who got better results than him are just plain wrong, even citing LTT.

Its never him who gets it wrong, its everyone else, its other reviewers, its Windows, its AMD. This is not the first time he got it wrong and blamed everyone but him self.
In his next video he will say sorry to AMD for calling the Zen 5 launch the worst CPU launch in the history of x86 and to be sure to call microsoft for answers as to why (since Intel have been struggling to keep the performance crown at any cost) recent Windows cripples AMD processors.

Seems to me a bit like Nvidia - TWIMTBP. Dodgy stuff
 
Back
Top Bottom