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

**THE OFFICIAL AMD CHIPSET DRIVERS THREAD**

McCarthy said:
I’ve done this just to get me back to where I was.

What’s concerning me though is that I can’t install even the latest chipset anymore as it keeps failing so I have restored a couple of times.

Something very strange.

@LtMatt have you encountered this before?
Click to expand...
Not really. What error message? There should two a couple of install logs you can check.

You can also try using Revi Uninstaller free version to force full removal of the old drivers including any reg entries.
 
LtMatt said:
Not really. What error message? There should two a couple of install logs you can check.

You can also try using Revi Uninstaller free version to force full removal of the old drivers including any reg entries.
Click to expand...
Yeah I always use Revi to remove everything, but just kept getting the failed over and over.

Don’t think it was the drivers because a full fresh install of windows and it worked first time. I tried system restore first but was still the same so thought stuff it, time to nuke.

I think it may have been the Microwin I installed, or a Windows update that was the culprit.
 
Anyone had a crash since installing these? I did mine a few days ago and received my first ever crash on Win11. PC was idle, only thing running was Spotify. Heard the music stop, came back to no signal on monitor and fans on full (I use Fan Control). Restarted via button on case. No dice. Powered off and on. No dice. Ended up having to pull the plug on PSU for 5 minutes and it came back. Checked mini dump via WinDbg.
  • DRIVER_POWER_STATE_FAILURE (9f)
    • A driver has failed to complete a power IRP within a specific time.
  • ADDITIONAL_DEBUG_TEXT: DXG Power IRP timeout.
  • IMAGE_NAME: pci.sys
  • MODULE_NAME: pci
  • FAULTING_MODULE: fffff80760000000 pci
CoPilot suggests:

1. GPU driver hung during a power transition​

  • NVIDIA/AMD/Intel drivers sometimes fail to complete a Dxgk power IRP.
  • Happens during sleep, hibernate, display-off, or low-power PCIe state changes.

2. PCIe power‑management conflict​

  • ASPM (Active State Power Management) or L1 Substates can cause hangs.
  • Motherboard BIOS or chipset drivers may be outdated.
Given the GPU drivers haven't changed, I'm going with #2 as the root cause.

Doing the usual SFC and DISM checks just in case and a reinstall of the chipset drivers. :(
 
And it looks like it has goosed something either on the board or with my memory. Can't get EXPO 6000 to work at all. Everything is set but boot into windows and it just says CAS40 2400Mhz. :mad:

I've tried loading BIOS defaults and then re-applying the settings fresh. Makes no difference.

Last step is pull the battery for a bit and see if it is just a glitch!
 
Removing bios battery didn't help. Still stuck at 2400Mhz with EXPO 6000 selected. :( Well I'm certainly not going to buy new memory! I might have to look at a new board, good excuse to move to an X870E. If the memory still doesn't do EXPO then I'll just wait it out. I doubt you can RMA RAM for not achieving EXPO even though it has been fine up until recently. Sorry. Going slightly off topic with my ramblings!
 
How long have you had your AM5 setup?

If it's been ok up till you installed the new chipset drivers then get in touch with AMD and see if they will help you out.
 
Aye cheers, sorry for taking thread off topic. I've got some further troubleshooting to try tomorrow. Single DIMM in slot B2 and then test default > Expo and anywhere in-between. Repeat for second DIMM. Trying to ascertain if it is a failing DIMM (apparently common on Corsair after 12-24 months) or if it is IMC / Memory controller or board issue. :) It could be just coincidental that the driver was done on/near to the time of the crash. Ta.
 
Yep was coincidental. The crash was a red herring. My issue with EXPO appears to have been since going to 4.10 BIOS and I hadn't noticed. The crash just lead me to it accidentally. Today I tested each DIMM individually with manual timings. Both DIMMS work at CAS30 6000Mhz. Installed them back as a pair. Therefore, I can only assume since moving to the latest BIOS there's been some change with AGESA and that has impacted DRAM Performance Mode (I've been using "Aggressive" up until now). Testing and knowing each DIMM is OK, I've gone ahead and left that on "AGESA Default". I've manually pinned the timings, the RAM speed, and the voltage at 1.4v. And we're up and running. :)
 
Firegod said:
Yep was coincidental. The crash was a red herring. My issue with EXPO appears to have been since going to 4.10 BIOS and I hadn't noticed. The crash just lead me to it accidentally. Today I tested each DIMM individually with manual timings. Both DIMMS work at CAS30 6000Mhz. Installed them back as a pair. Therefore, I can only assume since moving to the latest BIOS there's been some change with AGESA and that has impacted DRAM Performance Mode (I've been using "Aggressive" up until now). Testing and knowing each DIMM is OK, I've gone ahead and left that on "AGESA Default". I've manually pinned the timings, the RAM speed, and the voltage at 1.4v. And we're up and running. :)
Click to expand...

ASRock board I take it ? I had problems running Aggressive mode as well so left that option at default and works as normal.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom