AMD Crimson 17.7.1 drivers fix D3D error with Tekken 7, Little Nightmares

A very specific issue with RX 300 series cards in a couple of games has been addressed by the latest AMD Crimson driver set. Version 17.7.1 claims to have fixes for an error that affected Tekken 7 and Little Nightmares.

The bug in Tekken 7 apparently only affected 380s, while in Little Nightmares all 300 series cards were at risk. I’ve got a 380X and experienced the crashes in both games (albeit far, far less in Tekken 7). Here’s a longer description of the problem in Little Nightmares, but in short the game would crash (at a certain point, every time) with a Unreal Engine 4 D3D error about the GPU device being ‘lost’.

If AMD really has cleared that one up (I’ve not had chance to test them both), then that would be good news. Here’s a summary of the rest of the features, fixes, and remaining known issues in 17.7.1.

Update 12 July: They certainly didn’t clear it up entirely. Reports from players on the AMD forums (regarding Tekken 7) and Steam forums (for Little Nightmares) indicate the crashes are alive and well. Thanks to ‘guywhowantstoplaytekken’ (appropriate) for the Tekken 7 info.

Support For

Radeon RX 460/470 Series Graphics-based mining cards
Radeon RX 550/560 Series Graphics

Fixed Issues

Fixed a bug causing crashes on Tekken 7 on Radeon RX 380 Series graphics products.
Fixed a bug causing crashes on FFXIV and Little Nightmares on Radeon RX 300 Series graphics products.
Fixed an issue causing crashes with Adobe Lightroom CC 2015.10

Known Issues

Graphical corruption may be experienced in Tom Clancy’s: Rainbow Six Siege when MSAA is enabled.
A small number of apps may experience issues with Borderless Fullscreen mode and AMD FreeSync technology if other applications or game launchers are running on the primary screen in the background.
Counter-Strike: Global Offensive and World of Warcraft may experience flickering or performance issues the first time the game is launched on a system boot with AMD FreeSync technology enabled. Workarounds include exiting and restarting the application or task switching (alt+tab) in and out of the game to fix the issue.