The AMD software has detected a driver timeout.
Solvedfabul Posted messages 42069 Registration date Status Modérateur Last intervention -
14 réponses
Hello,
Try to update as many drivers as possible among the hard-to-find ones with IOBit Driver Booster Free, which only updates 15 drivers for free.
For those it lists that are easier to find elsewhere, update them through other means if it finds more than 15.
https://www.majorgeeks.com/files/details/iobit_driver_booster.html
Note: Uncheck optional offers during installation /!\
Uninstall it after use to remove its scheduled tasks at the same time.
Hello
If it's an MSI motherboard (or an MSI graphics card); you need to go to the manufacturer's website to find the correct drivers
Hello again
Yes, the BIOS is up to date, I installed the latest version of the AMD drivers (24.8.1) today and I am currently testing if the games are stable.
Good evening,
To help you better, please provide us with the model of your graphics card and the game that is causing the problem. With this information, I will be better able to guide you.
Also, which version of AMD Adrenalin do you have?
Hello,
The card is a rx6750xt, the games I have tested so far are ETS2, ATS, and Russian Fishing. The version of Adrenalin is the latest one, 24.8.1, which I just installed.
Actually, I wanted to reinstall Windows 11 and update my drivers, and that's when these problems started. Before that, I had no issues.
https://pastebin.com/Ud1UsPg7 here is the log file of ATS after a crash if that can help.
Thank you for your responses.
Okay, I will try, these last few days I have tested several versions of the drivers but always uninstalled with DDU.
But always uninstall with DDU.
Oh well don’t look for it.....you have the culprit,
You can reinstall Windows, you must not use this type of utility, it removes keys in the registry that the driver update routines do not reinstall because they depend on the system, especially DDU, it should be banned........
It should be noted that it is no longer necessary to uninstall drivers even when changing graphics cards, as long as they are of the same brand (AMD to another AMD or Nvidia to another Nvidia)
To see the temperature of the GPU in-game, download GPU-Z
https://www.techpowerup.com/download/techpowerup-gpu-z/
And check the Log To File box in the Sensors tab before starting a game.
everything was fine until a few days ago Perform a system restore and choose a date before the problem occurred.
Windows + R
Type --> rstrui.exe and hit OK.
Whether it's AMD or Intel, the ecosystems and security trigger at around 90/95 °. The 5700x is 90.
@fabul StatutModérateur, your processor has a problematic feature called Intel Thermal Velocity Boost (Intel TVB), which activates around 70/75 °, supposedly designed to improve performance when the CPU heats up; it has actually proven to be the opposite. Some BIOS allow disabling this feature, which has since been abandoned by Intel.
After that, when there are more than 8 cores to monitor, only HWmonitor can relay the temperatures on the fly; it's the hot spot that needs to be monitored for the graphics card as well.
Signature
Waiting for more responses; I attract trolls....
I will check the RAM
With Memtest86 Free USB to start.
Right here https://www.memtest86.com/download.htm
Otherwise https://forums.commentcamarche.net/forum/affich-38101152-le-logiciel-amd-a-detecte-un-depassement-de-delai-du-pilote#p38102060
Well, for now on 3 Steam games, I'm going to try an Epic game. What I don't understand is why the issue persists even after a clean reinstall of Windows and the drivers. I've been looking for a solution for over a week...
I'm trying to change the RAM tomorrow; I ran 2 passes on Memtest and it found 64 errors.
Good session of 1 hour and 30 minutes of gaming and it’s still running without crashing after replacing the RAM; however, the temperatures might be borderline for the CPU, especially in the CCD. A little undervolt could indeed help a bit, so 32GB of faulty Viper RAM, switching back to 16GB of Corsair and the problem seems to be solved, phew. I’m going to get Corsair again in 32GB, prices have become affordable again.
On the right track.
On my Givabyte Z490 to lower the vcore
Set the CPU Vcore option to "Normal" instead of "Auto"
Change the Dynamic DVID value to -100
I don't know if it's as simple on yours as it is on my Intel.
Maybe -100 mV is too low or still too high.
We can do stability tests with OCCT; when we've lowered it too much and it's no longer stable, it helps to know.
When it's no longer stable, we increase the voltage a bit.
I've gotten used to it since my Gigabyte GA EP45 UR3R and my Quad Core Q9550; while overclocking it, I lowered the vcore to a fixed 1.175V in the BIOS and
it heated up a lot less. CPU-Z didn't show me exactly the same value, but it was close.
It worked well for 10 years without touching anything, until I moved on to new hardware.
/!\ Important note /!\
If it doesn't start after lowering the vcore too much, you need to know how to do a "Clear CMOS": Often the manual indicates how.
1. Unplug the power supply
2. Remove the CR2032 battery
3. Check if you have a jumper on pins with CLR_CMOS or CLRTC written nearby
If it's there, move it to the other pins * * * > * * * for at least 10 seconds
If you don't have it, just short the two pins with a screwdriver for at least 10 seconds.
Sometimes shorting the two contacts of the battery holder can do the same thing.
4. Put the jumper back as it was before, or stop shorting
5. Reinsert the battery
6. Replug the power supply
7. Start the PC
-
Samsung j5 unable to answer
on 19 May -
Scam of the suvedene highway
on 18 May -
Minecraft restore the cursor and the bar.
on 16 May -
My ps3 keeps shutting down on its own...
on 16 May -
Samsung series 4 led tv logo display...
on 16 May -
How to enable bluetooth on a samsung tv?
on 16 May -
Ctrl key issue
on 16 May -
[metin2] sura ...
on 16 May -
Freebox tv locked step 2 or network
on 16 May -
Error 46 (brother dcp-150c) cleaning impossible
on 15 May







Thank you for your reply, I will try your solution. While searching, I also saw that disabling ULPS could help, apparently to be done in the registry or with MSI Afterburner.