Valor Mortis shuts the PC down or crashes on Radeon RX 7000 cards

The four acknowledged faults map to different cards, and the right expectation — fix available, workaround available, or nothing yet — depends entirely on which one you have.

Applies to: All Radeon cards, Windows 10, Windows 11

1. Press Windows+R, enter dxdiag, open the Display tab and read the exact adapter name. Use this rather than what the box said: 'RX 7600' and 'RX 7600 XT' are different entries in the model range even though AMD's notice is written at series level.

   dxdiag

2. Match it against the acknowledged list. RX 7600 series: AMD acknowledges an intermittent system shutdown, with no workaround. RX 7000 generally: AMD acknowledges an intermittent driver timeout, with no workaround. RX 7900 XT: the developer acknowledges GPU crashes during gameplay. RX 9000: AMD's FSR Frame Generation entry applies and does have a workaround.
3. If your card is not on that list, none of these notices is about your machine, and anyone telling you AMD has acknowledged your crash is overreading the notes. Skip to the game-patch step and to 'When something else is wrong' below.

Confirmed by the vendor.

Source: AMD, AMD, One More Level (developer post on Steam)

A driver-induced shutdown and a failing power supply look identical from the chair. The event log will not name AMD, but it does tell you whether Windows got far enough to record a stop code — and that is what decides whether hardware checks are worth your time.

Applies to: Windows 10, Windows 11

1. Open Event Viewer, go to Windows Logs > System and find the Kernel-Power entry with Event ID 41 at the time the machine went down. Or list the last few from PowerShell:

   Get-WinEvent -FilterHashtable @{LogName='System'; ID=41} -MaxEvents 5 | Format-List TimeCreated, Message

2. Read the BugcheckCode in the event data. Microsoft's guidance is that it is written in decimal and has to be converted to hexadecimal before you look it up. A non-zero code means Windows did record a stop error, which gives you something specific to search for.
3. If the BugcheckCode and the PowerButtonTimestamp are both zero, Microsoft's own documentation describes this as usually a hardware or device-driver problem, and lists overclocking, memory, power-supply wattage and overheating as what to check. Note what that means here: Event 41 is consistent with the acknowledged Radeon driver bug, but it does not prove it. If you are overclocking or undervolting the card, set it back to stock before concluding anything.
4. Be honest with yourself about scope. If the machine also powers off in other games, or at the desktop, this page is not your answer — an acknowledged bug in one game does not explain a shutdown that happens outside it.

Source: Microsoft, AMD

The developer has shipped crash fixes twice since launch, and the ones it fixed are the crashes that leave your machine running.

Applies to: Valor Mortis on Steam

1. In Steam, right-click Valor Mortis > Properties > Updates and confirm the game is current, then restart Steam if an update is pending.
2. Check what you are getting: the Second Update of 21 October 2026 lists 'Fixed multiple crashes' among its bug fixes, but does not say which crashes, and does not name AMD, the RX 7600 or the system shutdown anywhere in its notes.
3. Set your expectations accordingly. Players replying to those patch notes disagree about whether the update cleared their crashes, and a reply asking specifically about RX 7600 issues was answered by pointing to support rather than with a fix. Treat this as worth doing, not as the answer to the shutdown.

Confirmed by the vendor, though some users report it does not help.

Source: One More Level (developer post on Steam)

The developer asks for current drivers, and 26.10.1 is the release AMD's Valor Mortis entries are written against, so it is the baseline any further diagnosis should start from.

Applies to: All supported Radeon cards

1. Open AMD Software: Adrenalin Edition > Home > check for updates, or download 26.10.1 from AMD directly. The developer explicitly asks players to update drivers to the latest version for both AMD and NVIDIA cards before launching the game.
2. Understand what updating does and does not buy you. Both Valor Mortis entries are listed as Known Issues in 26.10.1 itself, which means this release documents them rather than resolving them. 26.10.1 did fix a Modern Warfare 4 stuttering issue, so it is worth being on regardless — just not as a cure for this.
3. Do not roll back on spec. AMD does recommend a specific older driver for a different game in these same notes — 26.9.1 for War Thunder timeouts on RX 5000 — but it recommends nothing of the kind for Valor Mortis, and the game postdates the previous release, so there is no known-good version to go back to. If you downgrade anyway, AMD's notes say to use the AMD Cleanup Utility.

Confirmed by the vendor.

Source: AMD, One More Level (developer post on Steam)

The developer lists Anti-Lag 2 as not working properly in Valor Mortis, so leaving it on keeps a known-faulty feature in the loop while you are trying to isolate a crash.

Applies to: Radeon RX 7000 series, Cards supporting AMD Anti-Lag 2

1. In AMD Software: Adrenalin Edition, open Gaming, select Valor Mortis, and set Anti-Lag to Disabled for that title rather than globally.
2. Relaunch and retest. Note the limit of this one honestly: the developer says Anti-Lag 2 may not work properly, which is a statement that the feature is broken here — not a claim from either vendor that disabling it stops the shutdowns or the crashes.

Confirmed by the vendor.

Source: One More Level (developer post on Steam)

This is the one Radeon fault here that AMD actually publishes a workaround for, and it matches a specific trigger — the crash happening as you switch away from the game.

Applies to: Radeon RX 9000 series, In-game AMD FSR Frame Generation

1. Confirm the trigger first: the crash or hang happens when you alt-tab between applications, or when an overlay such as Xbox Game Bar opens or closes, and you have in-game AMD FSR Frame Generation enabled on an RX 9000 series card.
2. Enable V-Sync in the game's own graphics settings — AMD's recommendation is for the in-game setting, not the driver-level one.
3. If the crash happens with FSR Frame Generation off, this entry is not your problem and you should stop here. AMD lists a separate crash tied to the Adrenalin Performance Metrics Overlay being enabled while other overlays open or close; if you run that overlay, disable it temporarily and retest.

Confirmed by the vendor.

Source: AMD