Skip to content
← All errors

AMD driver "Outdated"

WARDOGS says your AMD driver is outdated when it is not

Published Data as of Season 1 · 10 Sept 2026

This one is not your machine

A false positive in the game rather than a problem with your driver. If Adrenalin says you are current, you are current, and there is nothing to do.

Check whether WARDOGS is down right now →

What you see

A warning at startup that your graphics driver version is outdated, on a machine where AMD Adrenalin reports you are already on the newest driver.

Also reported as: outdated driver warning · driver version outdated · amd adrenalin outdated

What to do instead

The cause is not on your machine, so reinstalling and verifying will not reach it. These are the things that actually help while it lasts.

  1. 01 Check Adrenalin, then ignore the warning

    Confirmed

    Open AMD Adrenalin and look at the driver version it reports. If it says you are up to date, the game is wrong and you can carry on past the warning.

  2. 02 Do not roll back, reinstall or clean-install because of this alone

    Confirmed

    It is the most common wasted evening on this list. Driver surgery has its own risks and this warning is not a reason to take them.

  3. 03 Treat a real crash as a separate problem

    Confirmed

    If the game also crashes, the driver warning is not the cause and chasing it will not help. Start from what the crash itself says instead.

Did this fix it for you?

Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.

No comments yet. Be the first to say whether this worked.

The reason this has a page is not that it is hard to fix — it is that the obvious response to it is wrong and expensive. Told your driver is outdated, most people go and reinstall their driver, and on AMD that often means a clean uninstall in safe mode and a reboot cycle for a warning that was never true.

It is the most-reacted thread in the beta support corpus, which suggests a large number of people hit it and a large number of them went looking for something to do about it. The answer is that there is nothing to do.

If the game genuinely will not start, that is a different fault wearing the same warning. Start at crashes on launch, or at the named module if the dump gives you one.

If that did not do it