• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

First Windows 11 Patch Tuesday Makes Ryzen L3 Cache Latency Worse, AMD Puts Out Fix Dates

Nope. This has nothing to do with Intel. AMD's CCX Complex/Infinity Fabric works in a way that is very different and unrelated to how Intels big/little scheme works. Each have CPU Kernel driver code and they are mutually exclusive.

The Kernel driver code for each CPU does not and can not interfere with the code of another.
I see. I was thinking Microsoft tried to put everything under the same umbrella and somehow messed up AMD support. But if support is still separated, it's really weird they messed it up. I mean, it was already done for Win10. Then again, I'm a software developer, this isn't the weirdest thing I have seen.
 
I see. I was thinking Microsoft tried to put everything under the same umbrella and somehow messed up AMD support. But if support is still separated, it's really weird they messed it up. I mean, it was already done for Win10. Then again, I'm a software developer, this isn't the weirdest thing I have seen.

I'm sure it's security 'feature' related.

I think most of performance hits from windows these days is coming from new security features (vbs, flow control, memory randomization, blah blah). When you're babysitting how every piece of memory is being accessed/allocated this is bound to happen.
 
I'm sure it's security 'feature' related.

I think most of performance hits from windows these days is coming from new security features (vbs, flow control, memory randomization, blah blah). When you're babysitting how every piece of memory is being accessed/allocated this is bound to happen.
Until hardware is fully capable of running everything virtualized natively, we're bound for such 'hybrid' solutions where parts of the virtualization is done in software, while the rest is done in hardware.

Hopefully the day every program runs completely isolated natively, in hardware will be upon us all soon. It also begs the question what will happen when a sufficiently advanced (self-aware) AI manage to obfuscate its real goals with these neat security features?
 
Until hardware is fully capable of running everything virtualized natively, we're bound for such 'hybrid' solutions where parts of the virtualization is done in software, while the rest is done in hardware.

Hopefully the day every program runs completely isolated natively, in hardware will be upon us all soon. It also begs the question what will happen when a sufficiently advanced (self-aware) AI manage to obfuscate its real goals with these neat security features?
What does that even mean?
 
Until hardware is fully capable of running everything virtualized natively, we're bound for such 'hybrid' solutions where parts of the virtualization is done in software, while the rest is done in hardware.

Hopefully the day every program runs completely isolated natively, in hardware will be upon us all soon. It also begs the question what will happen when a sufficiently advanced (self-aware) AI manage to obfuscate its real goals with these neat security features?

Horizon Zero Dawn. :D
 
I was thinking Microsoft tried to put everything under the same umbrella and somehow messed up AMD support.
The way I understand it, there's a bit of truth there. The new scheduling schemes are a part of the base changes being made to 11, but those changes apply equally to all CPU models. Where the glitch comes in is where those processes interact with the architecture of each CPU line. Ryzen CPU's are a built in a unique way and as such, the CPU driver code has to be written to accommodate how it works.

What likely happened was microsoft give AMD the specifications of the changes they were going to make and AMD delivered back code for microsoft to integrate, then along the way something was changed and the code AMD created no longer worked properly. However, that's just a guess based on what I've been able to discover thus far.
 
  • Like
Reactions: bug
Nope. This has nothing to do with Intel. AMD's CCX Complex/Infinity Fabric works in a way that is very different and unrelated to how Intels big/little scheme works. Each have CPU Kernel driver code and they are mutually exclusive.

The Kernel driver code for each CPU does not and can not interfere with the code of another.
But the scheduler can. I have a feeling what happened is there rather than kernel.
 
Deragnement much?
The story of HZD is an ai that wraps itself in encryption that can't be broken/shut down.

Edit: totally missed it the first time :D...
 
Last edited:
Spelling much?

The story of HZD is an ai that wraps itself in encryption that can't be broken/shut down.
Ah, I did forget the quotes on 'Derangement'. And I misspelt it, too. You ought to know it's in the game's synopsis, no?
 
Patch is landing in Beta and Release Preview channels. Should probably reach General Availability at some point during next week.



1634362508147.png
 
You also didn't see them announce updated support for each gen of Ryzen nor 8th, 9th, 10th &11th gen Core series CPU's from Intel, but they did. Those updates will come in an update as per usual.


Maybe? Common sense really..
No, really. Alder lake requires windows 11.

It's two different CPU architectures in one, Win 10 would throw crysis on the low performance core and minesweeper on the big ones

The fix is live on the beta channel

1634374431472.png
 
Are you sure? Might be mistaken but I don't remember reading Alderlake being exclusive to Win11...
You might get it to work. It wont work properly.

It's like asking why hyperthreading doesnt work in DOS, because the OS isn't coded for it.

Microsoft and intel decided to make Alder lake only work properly on windows 11.
No one knows if that means a performance hit, missing cores, etc - yet.

This crap is not coming to 10:
1634375694612.png
 
You might get it to work. It wont work properly.

It's like asking why hyperthreading doesnt work in DOS, because the OS isn't coded for it.

Microsoft and intel decided to make Alder lake only work properly on windows 11.
No one knows if that means a performance hit, missing cores, etc - yet.

This crap is not coming to 10:
View attachment 221071
Ok, I see what you're getting at. Intel saying that it is "specifically designed for Windows 11" does not directly state exclusivity for that OS. It might hint at it, but until they actually make that direct statement, it's not set in stone..
 
Ok, I see what you're getting at. Intel saying that it is "specifically designed for Windows 11" does not directly state exclusivity for that OS. It might hint at it, but until they actually make that direct statement, it's not set in stone..
They repeatedly say it'll perform crap in any OS that is not specifically patched for the new big.little design
As far as any reviewer or consumer is concerned, thats an exclusive, since 11 is the only OS they (intel) have worked with.

It's like saying a 5950x is supported in DOS... sure, but it's sure as fuck not at full performance.
 
Last edited:
just disable the little cores then, nothing of value was lost anyways so
 
They repeatedly say it'll perform crap in any OS that is not specifically patched for the new big.little design
As far as any reviewer or consumer is concerned, thats an exclusive, since 11 is the only OS they've worked with.

It's like saying a 5950x is supported in DOS... sure, but it's sure as fuck not at full performance.
Not trying to ruffle your feathers. It seems like they just don't have things ironed out yet. This might be because of market adoption for Windows 11, which hasn't taken off like a shot or a number of other factors.
 
just disable the little cores then, nothing of value was lost anyways so
If I buy big and small cores, I'm gonna use all of them.
 
If I buy big and small cores, I'm gonna use all of them.
thats on you then
i would only ever buy big cores but idt there's an 8/0 SKU?
so i get unwanted useless little cores shoved down my throat, that don't even want to play nice w/ all OSes so yeah, -> disable
 
Back
Top