How to Fix Apex Legends Error 0x887A0006 (DXGI_ERROR_DEVICE_HUNG)
What Error 0x887A0006 means
When you see Error 0x887A0006: DXGI_ERROR_DEVICE_HUNG, the message is coming from Windows' graphics layer, not from Apex Legends itself. In plain terms, the game handed a batch of drawing commands to DirectX, DirectX handed them to your graphics card, and the card's driver stopped responding. After a timeout, Windows steps in, resets the graphics driver, and the game has no choice but to crash.
This error hits Apex Legends players especially hard in the game's DirectX 12 mode. Apex's DX12 renderer is aggressive: it compiles shaders with many threads at once, uses bindless textures to squeeze out extra performance, and leans heavily on your graphics card's video memory. Any one of those behaviors can hang a driver that other, lighter games never push hard enough to expose. That's why the crash can appear suddenly — often right after a game update, a graphics driver update, or a settings change — and why it can keep happening at the same point, like in the drop phase or during intense fights.
The good news is that this is almost never a dead graphics card. The card itself is usually healthy; the problem is the conversation between the game, DirectX, and the driver breaking down. The fixes below repair that conversation, from the most common cause (the driver) down to the most stubborn settings.
Common causes
- Buggy or corrupted GPU drivers: a bad driver update — or old driver files left behind by previous updates — is the single most common trigger.
- Unstable overclocking: factory or manual overclocks on the GPU (and sometimes the CPU) make the driver hang under Apex's heavy rendering load.
- Overheating: a graphics card running too hot throttles or stalls, which DirectX reads as a hung device.
- Video-memory pressure in DirectX 12: Apex's DX12 mode is greedy with VRAM. If the Texture Streaming Budget asks for more memory than your card has, the driver can panic and reset.
- Corrupted game files or shaders: damaged Apex files or half-compiled shader caches crash the rendering pipeline mid-draw.
How to fix Error 0x887A0006 — step by step
Work through these fixes in order. Most players are fixed by step 1, 3, or 4.
- Clean-install the latest GPU driver. Don't trust Windows Update for this — get the newest driver from NVIDIA, AMD, or Intel directly. In NVIDIA's GeForce Experience, choose Custom (Advanced) install and check "Perform a clean installation" so old driver files are fully wiped first. AMD's installer has a similar factory-reset option. Restart your PC when it finishes, then test Apex before changing anything else.
- Verify the game files. In Steam, right-click Apex Legends in your library, choose Properties, then Installed Files, and click "Verify integrity of game files." In the EA app, open your Library, click the three dots on Apex Legends, and choose Repair. Let the check run to completion — it re-downloads anything damaged, including broken shader data.
- Add DirectX-safe launch options. In Steam, right-click Apex Legends, choose Properties, and find the Launch Options field. Add +staticprop_color_use_bindless 0 +staticprop_depth_use_bindless 0 +r_drawworld_depth_bindless 0 — these tell Apex to load certain textures through a safer rendering path instead of the bindless-texture path that hangs some drivers. If the crash continues, replace those with -numPSOThreads 2, which limits how many threads compile shaders at once (a known DX12 crash point).
- Lower the Texture Streaming Budget. Launch Apex, open Settings, then Video, and drop the Texture Streaming Budget down one or two notches from your current setting. DirectX 12 mode uses far more video memory than the old renderer, and exceeding your card's VRAM is a classic way to make the driver reset itself. Also close background apps that eat memory, like Wallpaper Engine, while you test.
- Stop overclocking and check temperatures. If you overclock the GPU or CPU — or run tools like MSI Afterburner with an overclock profile — disable the overclock and restore factory clock speeds. Overclock instability is a textbook cause of this exact error. While you're at it, make sure your PC has clear airflow and the GPU fans are dust-free, since overheating triggers the same hang.
- Run the game as administrator. Right-click your Apex Legends shortcut (or the game's r5apex.exe file), choose Run as administrator, and confirm the prompt. Elevated permissions fix DirectX initialization failures where the game is blocked from the graphics resources it needs.
Did this fix it? Quick checklist
- The game launches and reaches the lobby without crashing
- You can finish a full match, including the drop phase, with no 0x887A0006
- The GPU driver version you installed is the latest from NVIDIA, AMD, or Intel
- No crash after a full PC restart with the launch options still in place
If the crash keeps happening after a clean driver install, the launch options, and a lowered Texture Streaming Budget, try switching Apex to DirectX 11 if that option is available — the older renderer is far less aggressive and rarely triggers this hang. If other demanding games crash too, especially at the same point every time, the graphics card itself may be failing; test it in another PC or have it checked before buying a replacement.
Frequently asked questions
What does DXGI_ERROR_DEVICE_HUNG mean?
DXGI_ERROR_DEVICE_HUNG means Windows asked your graphics card to do its job and the graphics driver stopped responding in time, so Windows reset it. In Apex Legends it appears as error 0x887A0006 when DirectX sends the GPU commands it cannot finish, usually because of a driver bug, overheating, an unstable overclock, or the game pushing video memory too hard.
Is error 0x887A0006 a hardware problem?
Usually not. It looks like a broken graphics card, but 0x887A0006 is almost always a software problem: the GPU driver, the DirectX 12 rendering path, or game settings asking too much of your video memory. If the card runs other demanding games without crashing, your hardware is fine — work through the driver, launch-option, and settings fixes instead.
Why does 0x887A0006 happen mostly in Apex Legends?
Apex Legends is unusually heavy on the graphics pipeline, especially in its DirectX 12 mode, with aggressive shader compilation and high video-memory use. A driver quirk or a memory limit that other games quietly survive can be exactly enough to hang the driver in Apex, which is why the fixes here target Apex's DirectX behavior specifically.
What do the bindless launch options do?
The launch options +staticprop_color_use_bindless 0, +staticprop_depth_use_bindless 0, and +r_drawworld_depth_bindless 0 tell Apex Legends to load certain textures through a safer, older rendering path instead of bindless textures. For some graphics cards, bindless texture loading in the DirectX 12 engine has a bug that hangs the driver and throws 0x887A0006 — turning it off is one of the most reliable fixes.
Should I play Apex in DirectX 11 instead of DirectX 12?
If the DirectX 12 mode keeps crashing with 0x887A0006 after you try the fixes, switching to DirectX 11 is a reasonable workaround — the older path is less aggressive about video memory and shader threading, so it hangs drivers far less often. You may lose a few frames, but the crashes usually stop.