Chipset 4.08.09.2337 - all the individual drivers (PCIE, GPIO, etc.) have all the same version numbers as the last driver on my B450 board, but 4 of them have a newer date and different file size. The PCIE one was the same. Odd. Don't know about the power plan thing, I don't use it.
Yeah, I assume the power plan or some other driver my system does not use has been changed, so the overall package version changes. What I meant was that the individual drivers were the same version number, but different date and file size (so why same version?), so they did install, like a new version would.
GPIO 2.2.0.130 (same version, new date)
GPIO Promontory 3.0.0.0 (same version, new date)
SMBus 5.12.0.38 (same version, new date)
PSP 5.19.0.0 (same version, new date)
PCI 1.0.0.89 (same, did not install)
Just installed on both Win 10 and Win 11.
I have identical hardware on both Win 10 and Win 11.
I just use the Win 11 driver. As far as I can tell they are identical.
Everything is fine. On Win 10, I had to reset the "Turn Monitor off after..." back to 5 minutes.
Last edited by Ghot; 21 Nov 2022 at 17:43.
This week I'm going to be building a new system for the first time in 11 yearsGoing from a i5 2500K system to a Ryzen 5 7600X.
The motherboard is a Gigabyte B650
B650 AORUS ELITE AX (rev. 1.x) Support | Motherboard - GIGABYTE Global
The chipset driver offered on the support page is 4.06.09.215 Should I stick with the recommended version on the support page or install the very latest version listed in op?
Thanks
All B650 chipsets are identical, no reason not to go for newest one and that's from AMD's site.This week I'm going to be building a new system for the first time in 11 years
The motherboard is a Gigabyte B650
B650 AORUS ELITE AX (rev. 1.x) Support | Motherboard - GIGABYTE Global
The chipset driver offered on the support page is 4.06.09.215 Should I stick with the recommended version on the support page or install the very latest version here?
Thanks
PSA the 4.11.15.342 is #@*&ed
[PC one in specs]
I attempted that one first through Armoury Crate and directly from AMD after (yes of course, the Win10 not Win11). Same problem. And I couldn't modify or uninstall. I had to, as last time, resort to some off the beaten path workarounds... with the Programs Files (x86) AMD_Chipset_Drivers.exe to partially uninstall it (get rid of it from installed apps/programs) then manually delete the C root and x86 programs folder leftovers (and restart, of course) to attempt reinstallation.
None of AMD's recommendations work for this (as last time). Not even Revo Uninstaller will do anything (depends on the actual program uninstaller; these b@stards won't uninstall at all the typical actually specified methods with missing dependencies. Attempting to reinstall over does nothing but the same errors).
So specifically, the runaround that actually gets it done:
C:\Program Files (x86)\AMD\Chipset_Software\AMD_Chipset_Drivers.exe
Do: Next > Remove, yatta yatta... (it will not finish; manually close out after it stalls towards the end).
Manually delete:
C:\AMD
C:\Program Files (x86)\AMD
RESTART.
Retry same installer (freshly downloaded again) first if you want (but don't hold your breath). Rinse and repeat above workaround (mentioned nowhere on AMD's resolution procedures) then fallback to your MOTHERBOARD'S (as in from the DOWNLOADS section of their SUPPORT page for YOUR motherboard) older AMD Chipset driver if/when the direct from AMD is still #@*&ed.
For instance, the (and from)...
AMD Chipset driver V4.07.13.2243 For Windows 10/11 64-bit.
Version 4.07.13.2243 52.72 MB 2022/09/30
... is the winner, this time. We're averaging a totally #@*&ed AMD Chipset driver per year here, ya'll (at least I am).
OH! And, definitely kill Defender.
Now excuse me while I reminisce over the good old days when runarounds weren't necessary for Chipset drivers.
Quote
