Skip to content
TroubleGrid

Assassin's Creed Black Flag Resynced crashes with DX12 error 0x887A0006

Last verified October 2026Tested against Assassin's Creed Black Flag Resynced on Windows (released 9 July 2026), AMD Software: Adrenalin Edition 26.9.2 (29 September 2026) - the driver AMD lists the known issue against, Radeon RX 7000 series (AMD lists the RX 7900, 7800, 7700, 7650 and 7600 series) - the range AMD names, Also reported on NVIDIA GeForce RTX 2080 Ti, RTX 4080 and RTX 5080Good evidence

0x887A0006 is DXGI_ERROR_DEVICE_HUNG - the graphics device stopped responding and Windows reset it, so the game was torn down. AMD lists an intermittent crash or driver timeout in this game on Radeon RX 7000 cards as a known issue in Adrenalin 26.9.2 and offers no workaround for it. But players report the same error on GeForce cards too, so the AMD driver is not the whole story. The settings change players most often report helping, on both vendors, is turning ray tracing off; disabling FSR upscaling, or dropping from FSR 4 to FSR 3, is the next most reported. Neither is a fix from Ubisoft or AMD, and some players still crash after both.

This page is about one specific crash signature in Assassin's Creed Black Flag Resynced: the game runs for a while, freezes, and closes with a DirectX 12 error whose code is 0x887A0006. It is worth separating what is documented from what is merely reported, because for this crash those are two quite different lists, and most of what circulates belongs to the second. One thing worth fixing in your head first: the game has been out since 9 July 2026, so this is not launch-week turbulence. The AMD known issue appeared months later, against a driver released on 29 September 2026.

Symptoms

  • The game freezes for a moment and then closes, showing a DirectX 12 error with code 0x887A0006
  • It happens during play rather than at launch - commonly five to thirty minutes in, and for some players roughly once an hour
  • It happens on high and low presets alike, and at reduced resolution
  • You are on a Radeon RX 7000 card and recently installed AMD Software: Adrenalin Edition 26.9.2
  • Or you are on a GeForce card and hit the same error anyway
  • The crash has no consistent in-game trigger - some players only see it during long unattended sequences

Why this happens

The GPU stopped responding and Windows reset it

0x887A0006 is the DXGI error DXGI_ERROR_DEVICE_HUNG. Microsoft's own description is blunt: "The application's device failed due to badly formed commands sent by the application. This is a design-time issue that should be investigated and fixed." In practice it means the graphics device stopped making progress on the work the game submitted, Windows' timeout detection and recovery stepped in and reset the device, and every Direct3D resource the game held became invalid - so the game cannot continue and closes. Note what the error does and does not tell you: it identifies the failure mode, not the culprit. The same code appears whether the stall originated in the game's command stream, in the display driver, or in a combination of the two that only occurs with certain features switched on.

Confirm it is 0x887A0006, and work out which situation you are in · Turn ray tracing off · Turn FSR upscaling off, or drop from FSR 4 to FSR 3

On Radeon RX 7000, AMD has acknowledged a driver-side problem in this game

AMD's release notes for Adrenalin Edition 26.9.2, dated 29 September 2026, list under Known Issues: "Intermittent application crash or driver timeout may be observed while playing Assassin's Creed Black Flag Resynced on Radeon RX 7000 series graphics products." That is as far as AMD goes - the entry carries no workaround, in contrast to the War Thunder entry on the same page, which tells affected RX 5000 owners to install 26.9.1 instead. The same notes show AMD fixing driver timeouts in two other games in this release, which is a reminder that "driver timeout" is a recurring class of problem in this driver branch rather than something unique to this title.

Confirm it is 0x887A0006, and work out which situation you are in · Radeon RX 7000 only: move off Adrenalin 26.9.2

It is not only an AMD problem, which limits how much a driver change can do

In the Steam discussion threads the same 0x887A0006 crash is reported on GeForce hardware - an RTX 2080 Ti, an RTX 4080 and an RTX 5080 among them - alongside the Radeon reports. AMD's known-issue entry covers RX 7000 cards and nothing else, and no equivalent entry exists on the NVIDIA side. If the crash were purely a Radeon driver regression it should not be appearing on GeForce cards at all. The honest reading is that something in the game's DirectX 12 workload can hang a GPU, that the current Radeon driver makes it worse or more frequent on RX 7000 parts, and that changing driver alone is unlikely to be a complete answer for anyone.

Turn ray tracing off · Turn FSR upscaling off, or drop from FSR 4 to FSR 3

Fixes

Confirm it is 0x887A0006, and work out which situation you are in

about 5 min

Three different crashes get called "the DX12 crash" in this game's forums. The code on the dialog tells you which one you have, and your GPU tells you whether AMD has acknowledged anything for you.

Applies to: Windows 10, Windows 11

  1. Read the error code off the crash dialog. This page is about 0x887A0006 only. If you see 0x887A0005 that is DXGI_ERROR_DEVICE_REMOVED, which Microsoft describes as the video card having been removed or a driver upgrade having occurred - a different situation. 0x80070057 does not appear anywhere in Microsoft's DXGI error list, so whatever it is, it is not part of this family and is not what this page is about.
  2. Note your graphics card. AMD's acknowledgement covers Radeon RX 7000 series parts — AMD's own compatibility list for this driver branch names the RX 7900, 7800, 7700, 7650 and 7600 series.
  3. Check which AMD driver you have, under Settings then System in AMD Software: Adrenalin Edition. AMD's known-issue entry is written against 26.9.2, released 29 September 2026.
  4. Decide which case applies to you. RX 7000 card on 26.9.2: AMD has acknowledged a problem in this game, with no workaround published. Any other Radeon, or a GeForce card: nothing is acknowledged for your hardware, and the settings changes below are all that is on offer.
  5. Check the timing too. This crash happens during play. If the game never reaches the main menu, or closes in the first few seconds, you are looking at a different problem and nothing on this page will help.

Confirmed by the vendor.

Source: Microsoft, AMD, AMD

Turn ray tracing off

about 5 min

This is the change players most often report stopping the crash, and it is reported on both AMD and NVIDIA cards. It costs you nothing but image quality and is reversible in a menu.

Applies to: Radeon RX 7000 series, GeForce RTX cards, Windows 10, Windows 11

  1. Open the game's graphics settings and set every ray tracing option to off. If the game exposes tiers rather than a switch, step it down to the lowest before turning it off entirely - some players report the crash becoming less frequent at a lower tier rather than needing it off.
  2. Play for noticeably longer than your usual time-to-crash before concluding anything. If you were crashing once an hour, an hour of play without a crash is not yet evidence; two or three sessions is.
  3. If it holds, you can try turning ray tracing back on one option at a time to find out which one your machine dislikes. That is optional - it is a diagnostic exercise, not a repair.

Reported to work by 3 users; not confirmed by the vendor. 2 report it did not help.

Source: Steam Community, Steam Community

Turn FSR upscaling off, or drop from FSR 4 to FSR 3

about 5 min

The second most reported change. Upscaling and frame generation add passes to every frame, and players report the crash easing when those come out of the pipeline.

Applies to: Radeon RX 7000 series, Windows 10, Windows 11

  1. In the game's graphics settings, set upscaling to off or native. If you also have frame generation enabled, turn that off in the same pass - several reports describe the crash arriving with upscaling and frame generation running together.
  2. If you would rather keep upscaling, players report that running FSR 3 in place of FSR 4 also helps. Note that doing this through a third-party substitution tool is not something Ubisoft or AMD supports, and it is not needed if the game offers both versions in its own menu - check there first.
  3. Test over a longer session, as above, before deciding it worked.

Reported to work by 2 users; not confirmed by the vendor. 1 report it did not help.

Source: Steam Community

Radeon RX 7000 only: move off Adrenalin 26.9.2

Check before applyingabout 30 min

AMD's known-issue entry names 26.9.2 specifically. Its predecessor, 26.9.1, carries no entry for this game. That is a reason to try it, not a promise - a missing line in a release note is not the same as a tested fix.

Applies to: Radeon RX 7000 series, Windows 10, Windows 11

Before you do this

Changing graphics drivers leaves the machine briefly without one. Do this when you can tolerate a reboot or two, not mid-session, and download the installer you are moving to before removing the one you have.

First:

  • Download the AMD Software: Adrenalin Edition 26.9.1 installer before you start
  • Know your exact Radeon model so you install the right package
  1. This step is for Radeon RX 7000 cards only. On any other card there is nothing acknowledged to move away from, and changing driver is unlikely to achieve anything.
  2. Be clear about what you are relying on. AMD publishes no workaround for this known issue. 26.9.1, dated 3 September 2026, simply does not list the problem - which may mean it is absent there, or may only mean nobody had reported it when those notes were written.
  3. Download the 26.9.1 installer from AMD's own previous-drivers page before uninstalling anything, so you are not left without a driver if the download fails.
  4. AMD's release notes state that when downgrading to a previous version of AMD Software: Adrenalin Edition, it is recommended to use the AMD Cleanup Utility. Use it rather than uninstalling by hand - a half-removed driver stack causes worse problems than the one you started with. Expect the screen to flicker and the resolution to drop while no driver is loaded.
    AMD Cleanup Utility (from AMD's support site) → reboot → install 26.9.1
  5. Worth knowing before you spend half an hour on this: the only driver-related success we found in these threads goes the other way — one player reports the crash stopping after updating to the latest AMD driver, not after rolling back. Nobody reports the downgrade working. That is why this step sits last.
  6. If 26.9.1 does not help, go back to 26.9.2 rather than staying on the older driver indefinitely. 26.9.2 fixes driver timeouts in other games and sitting on an older release to dodge one unconfirmed problem is a poor trade.
  7. Pause driver updates for a short while afterwards if Adrenalin offers to upgrade you straight back.

Confirmed by the vendor.

Source: AMD, AMD, Steam Community

Known issues

  • AMD lists "Intermittent application crash or driver timeout may be observed while playing Assassin's Creed Black Flag Resynced on Radeon RX 7000 series graphics products" under Known Issues in the Adrenalin Edition 26.9.2 release notes of 29 September 2026. No workaround is given and no fix has shipped. The entry does not appear in the 26.9.1 notes of 3 September 2026.

    Affects AMD Software: Adrenalin Edition 26.9.2, Radeon RX 7000 series · Status: open

  • Every settings change on this page comes from players, not from Ubisoft or AMD. Players in the same threads report continuing to crash after trying them, so treat them as things worth trying rather than a repair. Checked 4 October 2026.

    Affects Assassin's Creed Black Flag Resynced on Windows · Status: workaround only

  • One widely linked Steam thread proposes pinning the Radeon core clock to a narrow range to stop this crash. We are not recommending it: another player in that same thread disputes the reasoning, and nobody in the thread reports it working. Underclocking to mask a crash also hides whatever is actually wrong.

    Affects Radeon RX 7000 series · Status: unknown

If none of this worked

If your error code is not 0x887A0006, stop here - this page will not help. A crash in the first seconds after launch, before the game draws anything, is a different problem, as is a crash confined to one specific mission or cutscene. If you get 0x887A0006 in several different DirectX 12 games rather than only this one, the common factor is your machine rather than the game: that pattern points at an unstable GPU overclock or undervolt, including a factory profile you never set yourself, or at power delivery and thermals. Reset any tuning profile to stock and see whether the pattern changes before blaming a driver or a patch.

Common questions

Does a -dx11 launch option work?
A player suggests it in one of the Steam threads, but nobody in that thread reports trying it successfully, and we found nothing from Ubisoft saying the game ships a DirectX 11 renderer at all. A launch option for a renderer that does not exist is simply ignored, so this is unlikely to be the answer. We have left it off the fix list rather than repeat it.
Is this the same bug as the Assassin's Creed Shadows crash on NVIDIA drivers?
No, and they should not be conflated. The Shadows crash is an open issue in NVIDIA's own driver release notes, tied to a specific driver branch and to crashing after extended play. This one is a DirectX 12 device hang that AMD has acknowledged on Radeon RX 7000 and that players also hit on GeForce. Different vendor, different documentation, different signature - although the fact that two Assassin's Creed titles are producing GPU-level crashes in the same period is worth noticing.
Should I increase my page file or run the game as administrator?
Neither has anything to do with a GPU hang. DXGI_ERROR_DEVICE_HUNG is raised when the graphics device stops responding and Windows resets it; virtual memory size and process elevation do not participate in that path. This advice is common on aggregator sites and we found no source behind it.
Will waiting for a driver fix my game?
Possibly, if you are on a Radeon RX 7000 card - the issue is on AMD's open known-issues list, which is where fixes normally come from. But because the same crash appears on GeForce hardware, a Radeon driver fix would not address every report, and a game patch may be needed as well. Nobody has committed to a date for either.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • AMD · Release notes · checked Oct 4, 2026

    • AMD Software: Adrenalin Edition 26.9.2 is dated 29 September 2026
    • Under Known Issues, 26.9.2 lists: Intermittent application crash or driver timeout may be observed while playing Assassin's Creed Black Flag Resynced on Radeon RX 7000 series graphics products
    • 26.9.2 offers no workaround for the Assassin's Creed Black Flag Resynced known issue, unlike the War Thunder RX 5000 entry on the same page which tells affected users to install 26.9.1
    • Under Fixed Issues, 26.9.2 lists an intermittent driver timeout in Final Fantasy VII Rebirth on Radeon RX 7000 series graphics products
    • Under Fixed Issues, 26.9.2 lists an intermittent driver timeout or system freeze while playing HITMAN World of Assassination on Radeon RX 9000 series graphics products
    • 26.9.2 advises using the AMD Cleanup Utility when downgrading to a previous version of AMD Software: Adrenalin Edition
  • AMD · Release notes · checked Oct 4, 2026

    • AMD Software: Adrenalin Edition 26.9.1 is dated 3 September 2026
    • The Known Issues list in 26.9.1 contains no entry for Assassin's Creed Black Flag Resynced
    • 26.9.1 supports Radeon RX 7900/7800/7700/7650/7600 Series graphics, so the RX 7600 and RX 7600 XT are RX 7000 series parts
    • 26.9.1 advises using the AMD Cleanup Utility when downgrading to a previous version of AMD Software: Adrenalin Edition
  • Microsoft · Documentation · checked Oct 4, 2026

    • 0x887A0006 is DXGI_ERROR_DEVICE_HUNG, described as: The application's device failed due to badly formed commands sent by the application. This is a design-time issue that should be investigated and fixed.
    • 0x887A0005 is DXGI_ERROR_DEVICE_REMOVED, which Microsoft describes as the video card having been physically removed or a driver upgrade having occurred
    • 0x80070057 is not a DXGI error code; the DXGI error list is confined to the 0x887Axxxx range
  • Steam Community · Forum · checked Oct 4, 2026

    • Players report the game crashing with a DirectX 12 error within roughly five to thirty minutes of play
    • The crash is reported on NVIDIA hardware as well as AMD, including an RTX 2080 Ti and an RTX 5080
    • Crashes are reported to occur regardless of graphics preset or resolution
    • Disabling ray tracing is reported to stop the crashes by more than one player in this thread
    • Disabling FSR upscaling, and substituting FSR 3 for FSR 4, are each reported to stop the crashes
    • Some players in the thread report that they continue to crash after trying these settings changes
  • Steam Community · Forum · checked Oct 4, 2026

    • A player on a Radeon RX 7600 XT reports the game freezing and then crashing with DX12 Error 0x887A0006, roughly once an hour
    • The same crash is reported in this thread on NVIDIA cards including an RTX 4080
    • Disabling ray tracing is reported to reduce how often the crash happens
    • One player with an AMD card reports the crash stopping after updating to the latest AMD driver, not after downgrading
    • A player suggests a -dx11 launch parameter as an alternative, with no confirmation in the thread that it works
  • Steam Community · Forum · checked Oct 4, 2026

    • A player proposes pinning the Radeon core clock to a narrow range in AMD Adrenalin as a workaround for the 0x887A0006 crash
    • Another player in the thread disputes that advice, arguing it points at local system instability rather than a fix for the game
    • No reply in the thread reports that the clock-pinning workaround actually stopped the crash
  • Wikipedia · Reference · checked Oct 4, 2026

    • Assassin's Creed Black Flag Resynced released on 9 July 2026 for PlayStation 5, Windows and Xbox Series X/S
    • The game is developed by Ubisoft Singapore and published by Ubisoft