• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Windows 11 Performance Issues on Ryzen Fixed by Updates from Microsoft and AMD

Here is my results!
 

Attachments

  • Cache & Memory Benchmark - Windows 10 & 11.jpg
    Cache & Memory Benchmark - Windows 10 & 11.jpg
    168.6 KB · Views: 120
I dont care I use intel AMD sucks.
 
LiveOrDie said:
I dont care I use intel AMD sucks.
Click to expand...
If it wasn't for AMD kicking Intel up the ass we would stiil be stuck with quad cores and the overpriced HEDT platform. About 10yrs of quads was enough.
 
Gentlemen, keep your fanboy at the thread entrance...
 
Tigger said:
You was you replied to me, Brand don't matter, just stow it if that's all you got. But no worries eh
Click to expand...
I was speaking generally in response to the AMD part. But no worries yeah.
 
fiftofar said:
Personally never had a good time with AMD drivers in general, when Windows updates are thrown in the mix it is even worse (mainly with alpha/beta/insider etc)
Especially the AMD RAID drivers and software.
Click to expand...

Pre-nvme their raid drivers were fine...their testing of nvme+hdd raid was lackluster and a pita to use.
Now in combination with windows update touching drivers they shouldn't...
Needless to say I moved that friend to storage spaces... I figure they are more likely to test compatibility with things they make.

Windows has changed driver frameworks once or twice with windows 10 and I have seen many driver issues due to that from many vendors. There is no longer windows 10 compatibility, there is a recipe of Win10build +driver.
AMD gpu drivers have been more or less unstable trying to use their screen recording capabilities, but then again shadowplay has gone through bouts of instability.

@bug, AMD having to make a new driver seems more like another framework change with the changes Intel made to the scheduler, Keep in mind Intel and MS made the scheduler for win11 together.
 
Last edited:
Patriot said:
Pre-nvme their raid drivers were fine.

Now in combination with windows update touching driers they shouldn't...
Needless to say I moved that friend to storage spaces... I figure they are more likely to test compatibility with things they make.
Click to expand...
I've used raid0 on Amd for years across builds and HDD and nvme without a single issue.

Hopefully you will continue to be wrong in the future but I'll let you know if I ever agree with that.

Now on Topic.

Good a new OS tends to have teething problems good to see prompt fixes.
 
TheoneandonlyMrK said:
I've used raid0 on Amd for years across builds and HDD and nvme without a single issue.

Hopefully you will continue to be wrong in the future but I'll let you know if I ever agree with that.

Now on Topic.

Good a new OS tends to have teething problems good to see prompt fixes.
Click to expand...
Wow toxic trash.

Windows changes driver frameworks, it causes driver issues. Thems the facts.

If you don't keep your driver in lockstep recipe it causes issues.
Windows 11 changed stuff again, and Intel helped write the scheduler hence new driver required.

AMD had issues with young Windows 10 drivers and nvme+raid. I wrote multiple bug reports and got them fixed...
Having to have 3 different drivers on install to enable hdd raid from nvme boot... is still a jank install method.

Whose fault is it? Well windows 10 has been a bit of a moving target for driver writing...
Drivers written on earlier frameworks are supposed to work on later but MS has broken support between "compatible" versions multiple times.

Windows breaks stuff with updates, and vendors are forced to find fixes and release drivers that work around MS changes.
1635020277641.png
 
Patriot said:
Wow toxic trash.

Windows changes driver frameworks, it causes driver issues. Thems the facts.

If you don't keep your driver in lockstep recipe it causes issues.
Windows 11 changed stuff again, and Intel helped write the scheduler hence new driver required.

AMD had issues with young Windows 10 drivers and nvme+raid. I wrote multiple bug reports and got them fixed...
Having to have 3 different drivers on install to enable hdd raid from nvme boot... is still a jank install method.

Whose fault is it? Well windows 10 has been a bit of a moving target for driver writing...
Drivers written on earlier frameworks are supposed to work on later but MS has broken support between "compatible" versions multiple times.

Windows breaks stuff with updates, and vendors are forced to find fixes and release drivers that work around MS changes.
View attachment 222132
Click to expand...
Yeah and yet still no problems here hmmn.
 
Patriot said:
Pre-nvme their raid drivers were fine...their testing of nvme+hdd raid was lackluster and a pita to use.
Now in combination with windows update touching drivers they shouldn't...
Needless to say I moved that friend to storage spaces... I figure they are more likely to test compatibility with things they make.

Windows has changed driver frameworks once or twice with windows 10 and I have seen many driver issues due to that from many vendors. There is no longer windows 10 compatibility, there is a recipe of Win10build +driver.
AMD gpu drivers have been more or less unstable trying to use their screen recording capabilities, but then again shadowplay has gone through bouts of instability.

@bug, AMD having to make a new driver seems more like another framework change with the changes Intel made to the scheduler, Keep in mind Intel and MS made the scheduler for win11 together.
Click to expand...
I doubt the new scheduler was MS and Intel only, AMD was most likely involved too. And let's not forget Qualcomm. The bug was linked here at some point, it's 6 months old. So it wasn't a last minute change, bat rather something both MS and AMD were ok with - they might have deemed it not critical or agreed on a timeline beforehand. Either that, or they spat about behind the curtains.
 
TheoneandonlyMrK said:
Yeah and yet still no problems here hmmn.
Click to expand...
I am glad you are enjoying the results of my bug reports, subsequent patches, and updated install directions, you are welcome.

bug said:
I doubt the new scheduler was MS and Intel only, AMD was most likely involved too. And let's not forget Qualcomm. The bug was linked here at some point, it's 6 months old. So it wasn't a last minute change, bat rather something both MS and AMD were ok with - they might have deemed it not critical or agreed on a timeline beforehand. Either that, or they spat about behind the curtains.
Click to expand...
Main point, Dev build had the fix without new AMD driver. I am sure the agreed on schedule had a Fix before RTM not after... and MS may have released earlier than originally scheduled to correspond with ADL launch. I have seen plenty of companies having a good face together and fighting behind curtains.
 
Patriot said:
Main point, Dev build had the fix without new AMD driver. I am sure the agreed on schedule had a Fix before RTM not after... and MS may have released earlier than originally scheduled to correspond with ADL launch. I have seen plenty of companies having a good face together and fighting behind curtains.
Click to expand...
Which fix is that? Because the cache latency seems to have been fixed by MS, but that preferred core was AMD's to fix.
And while I'm glad you're sure about what happened between MS and AMD, I'm not and as such I choose not to point fingers.
 
Patriot said:
I am glad you are enjoying the results of my bug reports, subsequent patches, and updated install directions, you are welcome.


Main point, Dev build had the fix without new AMD driver. I am sure the agreed on schedule had a Fix before RTM not after... and MS may have released earlier than originally scheduled to correspond with ADL launch. I have seen plenty of companies having a good face together and fighting behind curtains.
Click to expand...
Thank you lord but I did say I've been using it since FX days ,was that you fixing the issues I wasn't having back then too, praise to you bro.
 
TheoneandonlyMrK said:
Thank you lord but I did say I've been using it since FX days ,was that you fixing the issues I wasn't having back then too, praise to you bro.
Click to expand...
Reading is hard.
 
It looks like AMD Ryzen Chipset Driver 3.10.08.506 doesn't support AMD Ryzen Mobile 2000U Series with Windows 11.
 
bug said:
Which fix is that? Because the cache latency seems to have been fixed by MS, but that preferred core was AMD's to fix.
And while I'm glad you're sure about what happened between MS and AMD, I'm not and as such I choose not to point fingers.
Click to expand...
Why was it AMDs to fix? The frameworks are supposed to be backwards compatible, yet oddly often require new drivers from...everyone. (shrugs)
And I am sure they agreed on a fix, since they listed timelines on their (amd) website... Every OS before 10 had 1 framework listed... 10 has.. 10, and 11 yet another.
They are all supposed to be backwards compatible yet the windows 10 driver doesn't have preferred core working on 11, why is that?

My main point has been its the constant changing frameworks that are causing the driver headaches all around. Drivers built on older builds may work on newer or they might not... it's been pretty hit and miss on windows 10 rolling release.

I am not saying I know what is going on behind the scenes... Just saying those framework changes are not as compatible as they claim, and why would they be, they can't test everything, they are just being reckless at the speed of changes.
 
You must log in or register to reply here.
Back
Top