KNOWN ISSUE: "DXGI_ERROR_DRIVER_INTERNAL_ERROR" on AMD Driver Version 26.6.2 & 26.6.4

Issue Type (Required):

Crash - on Launch

Issue Description (Required):

GUID: 0d664ff6-6f20-438f-8e24-c6fe7e6273de

Log File:
Info Type:

[Engine Error]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DRIVER_INTERNAL_ERROR, assert: ``

[PC] Do You Use Mods? (Optional):

No, I don’t use mods

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

PC - Steam

New Update for AMD Adrenaline - 26.7.1. Still can’t play Darktide. It’s been OVER A MONTH. I’m getting pretty pissed about this.

Can someone at FatShark PLEASE reach out to AMD and request a progress report on fixing this issue?!?!

UPDATE: Some folks on reddit suggested that my issues are now controller related since I don’t crash or get the error message anymore. So, on a whim, I decided to check my Steam controller layout for Darktide, and somehow, I don’t know when or how, the button assignments got ALL messed up. The Directional pad buttons were mapped to the X, Y A, and B buttons, the X and Y buttons were mapped to the directional pad, and A and B weren’t mapped at all. I fixed all that, then turned off Steam Input for controllers all together, and now it works just fine! I just finished a game. I have to assume the 26.7.1 update fixed everything else, because I didn’t experience any crashes as I logged in to the game multiple times.

Now the only thing I need to figure out is how to activate FSR 4.1 on Darktide!

Appreciate you flagging that 26.7.1 is also not playing nicely. I’ve updated the initial post to include this.

I’ll make some further noise internally about this, and reach out to AMD :saluting_face:

UPDATE: Some folks on reddit suggested that my issues are now controller related since I don’t crash or get the error message anymore. So, on a whim, I decided to check my Steam controller layout for Darktide, and somehow, I don’t know when or how, the button assignments got ALL messed up. The Directional pad buttons were mapped to the X, Y A, and B buttons, the X and Y buttons were mapped to the directional pad, and A and B weren’t mapped at all. I fixed all that, then turned off Steam Input for controllers all together, and now it works just fine! I just finished a game. I have to assume the 26.7.1 update fixed everything else, because I didn’t experience any crashes as I logged in to the game multiple times.

Now the only thing I need to figure out is how to activate FSR 4.1 on Darktide!

Ohh, interesting! Appreciate you updating again here. Fingers crossed that driver version 26.7.1 may be stable then.

If anyone else has updated to driver version 26.7.1 and can confirm, that would be great :crossed_fingers:

Only other thing of note - if I have Darktide set to “Global Gaming Experience (HYPR-RX)”, AMD FSR 4.1.1 doesn’t show up in game settings. HOWEVER, if I change it so that Darktide is set directly to “HYPR-RX”, then 4.1.1 does show up in game settings. Not sure what this means in terms of where the issue is, but thought I’d let you know.

I’ve updated to 26.7.1 and I’ve managed to launch the game and walk around the morning star without issue. So that would mean the original fault has been resolved, at least for me.

No problems here with the new driver. game runs very well.

I had tried with RX6700GPU with Win11 within 26.7.1. But still going same crash info as 26.6.4

the crash goes when I go for Expeditions mode. Crash always come when getting into ready screen or loading screen, with D3D crash info.

But it all goes well with OptiScaler When I use DLSS-FSR both Frame Generation and Upscale

I doubt there’s problem on application on FSR complication, not the Driver side