Works fine here, C8E, Geekbench is consistent with before

 

The chipset driver 4.03.03.431 from AMD made my system act weird. Ghost Recon Breakpoint wouldn't start. Windows Event Log stopped working. Terminal commands like "sfc /scannow" or "DISM /Online /Cleanup-Image /RestoreHealth" got stuck and never ran through. Had to use a system restore point from yesterday evening and now everything is running fine again und sfc couldn't find any integrity violations.

 

How long did you let it run for? After reading your post I gave sfc /scannow a try and thought it was stuck at times but it eventually finished without any errors reported. It took like ten times longer than normal though so something definitely changed.

 

I gave up pretty fast tbh. Other users reported to me they got stuck at 31% and 72% but it eventually finished. Mine probably would have finished as well, if I had had the patience.

 

Does anyone lose performance with chipset driver. I lost 10 fps in a CPU bound game. Gained it back after removing it.

 

I found some tweaks in power plan in previous version. They certainly DO work, however on my rather old system they increased kernel response times. I guess they went bit further with them, but there might be consequences performance-wise.

 

AMD is constantly taming boost as it's too optimistic by default, but the difference is very small from previous drivers like nothing to be bothered about

 

I didn't notice any changes after installing this driver, but I'm not using AMD's power plans (using a 5800X on Windows 10, so they don't install anyway) and I do not install the "AMD PCI device driver" due to potential security concerns (I use a pre-Ryzen dummy driver that has no .sys file attached, version 1.0.0.12).

 

This is so OEMs and manufacturers can meet the energy star compliance rating on these chipsets. It doesnt affect Linux. Once again Windows overriding what users want to force power management settings that will screw things up because of the law of unintended consequences

 

Subbed to read more potential issues.

 

This is pretty ridiculous. All those "known issues" are fixable issues. Now they introduce system critical bugs like ruining sfc scans? AMD still didn't overhaul their software department.

 

Could be the latest Spectre V2 mitigations are already in place, it is said to affect file transfer the most and sfc is endless amount of small files

 

Has anyone who is experiencing these hanging issues installed the latest realtek win 11 LAN Driver as well?

 

Yes, I am always on latest drivers.

And I use the Realtek drivers and 2.5Gbps port over the 1Gbps Intel port which I have disabled from the BIOS after switching. The 2.5Gbps port updated with the drivers has better latency and is much more responsive on the web compared with Intel.

 

Funny thing is, after I've rolled back my system because of the chipset drivers, I've reinstalled the latest Realtek Ethernet Controller Driver 11.5.0112.2022 (03142022) and upon a reboot my troubles returned, even though the chipset drivers were still the old ones.

Now I've discovered that the issues remanifest themselves upon every reboot, even with old drivers.

 

I went back to the previous chipset driver and just done both:

1. DISM.exe /Online /Cleanup-image /Restorehealth
2. sfc /scannow

They took:

~20 seconds and
~1 minute.

So back to normal for me, even with the latest Realtek Ethernet Driver.

Realtek PCIe FE / GBE / 2.5G / 5G Ethernet Family Controller Software - REALTEK

www.realtek.com

Using --> Win11 Auto Installation Program (NetAdapterCx) --> 2022/03/14

EDIT: Issue resolved. Chipset driver is good.

 

I had already installed the latest bios (4204, for TUF Gaming x570, with 3900x). Chipset driver installed quickly, and with no issues. SFC/scannow and DISM run normally - no slowdown and no errors. Cinebench is essentially unchanged (+1%). I was already using the latest GBE driver. A puzzlement.

 

I think those with issues are running Defender like I am because if you have these aforementioned issues, disabling Defender or temporarily switching to another AV will solve them.

 

i can confirm that turning to avast /disabling Defender, made my pc like before..

 

This makes sense to me. I have been using BitDefender and Malwarebytes.

 

How can we confirm Defender is disabled? And how do we disable it...

 

Haven't had any issues running sfc after installing these drivers, via the conventional installer, either.



Windows Defender should disable itself automatically if you install a compatible 3rd-party AV. You can check the status under "Virus and Threat Protection".

If you have an Education or Enterprise license, you can still disable Windows Defender without needing to replace it with anything else. This used to be possible with other versions, but no longer is, at least not without breaking things.

 

Oh look, AMD release a software update for their hardware and it's a total mess.

This company can't tell its head from its arse when it comes to software/BIOS.

 

The issues I described returned even with a system restore point from before the driver update. I think that there is a correlation between the chipset driver release and some issues on Microsoft's side which leads people to believe the chipset drivers are the cause.

Other people have reported to me that they've completely reinstalled Windows because they thought the driver update had corrupted their Windows installation, yet even without installing the latest chipset driver, the issues returned directly after running Windows update.

 

hello everyone, and sorry for my bad english
I show you how I updated the chipset without having errors.
I started the installation, after the check I canceled, saving the files in C: \ AMD \ Chipset_Software in another folder.
Then I manually updated all the SMBus GPIO drivers etc., then I restarted win 10 and installed the Chipset




=== Logging stopped: 16/03/2022 22:15:59 ===
MSI (c) (98:9C) [22:15:59:675]: Note: 1: 1707
MSI (c) (98:9C) [22:15:59:675]: Product: AMD_Chipset_Drivers -- Installation operation completed successfully.

MSI (c) (98:9C) [22:15:59:675]: Windows Installer installed the product. Product Name: AMD_Chipset_Drivers. Product Version: 4.03.03.431. Product Language: 1033. Manufacturer: Advanced Micro Devices, Inc.. Installation success or error status: 0.

MSI (c) (98:9C) [22:15:59:676]: Grabbed execution mutex.
MSI (c) (98:9C) [22:15:59:676]: Cleaning up uninstalled install packages, if any exist
MSI (c) (98:9C) [22:15:59:677]: MainEngineThread is returning 0
=== Verbose logging stopped: 16/03/2022 22:15:59 ===

For now everything is ok.

 

could the drivers on the first installation, alter/program some security code/part of the processor? (like a bios/epprom programming) that is resilient afterwards?

 

Depends on the level of protection ring access, granted to the driver.
Usually hardware drivers have ring 0 access, which mean direct kernel access, which mean being able to access the bios.
Bitlocker can access to the bios security features, AMD GPU drivers have direct access to the bios PBO settings, you can reboot directly into the bios from windows.

These changes can be made resilient, but ultimately it depends on what kind of task the driver performs.

 

For me, sfc / scannow normally works 1min. scan , last chipset drivers, Bios last AGESA 1.2.0.6b , CPU 5700G and last AMD software for RX 5700XT.

 

Working fine here after updating Windows. Prior to that my SFC Scannow took 15 minutes or longer.

 

Anyone else having issues with the AMD Processor Power Management Support 7.0.4.4 not installing? The chipset installer says it finished successfully, but if I open the summary it has a Fail message for it.
It's supposed to install "AMD Ryzen™ Power Provisioning Package (required for UEFI CPPC2 support with "Zen 3" and later in Windows® 11)", but it doesn't. And if I run the chipset installer again it says it's not installed.
So I ended up adding the provisioning package manually and then running the provided settings file for it. I noticed it does something to the default windows balanced power profile. I'm guessing it's the chipset side fix for Ryzen 5000 series on Windows 11.

 

this new chipset messes up my razer mouse profile....
it also introduces some windows lag.
please do not use this version

i am still on window 10!

 

Haven't had any such issues. No Windows lag, razer mouse profile intact, and I am on Windows 11 Pro 22000.588

 

I report also a loss in performance with the latest chipset driver in comparison with the ones offered by MSI (B550 Gaming Edge Wifi, 5900X) in windows 10. Less single-threaded boost with the balanced power plan. Checked with Octane 2.0 in Chrome: 75xxx-76xxx with newest drivers, 78xxx-79xxx with old ones.

Greetings