cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

8-fingered
Adept III

Shadow of the Tomb Raider Crashes / Hangs when DX12 enabled with Vega 56 but not with R9 290X

I'm getting either a crash to desktop on startup with '0x887A0007:DXGI_ERROR_DEVICE_RESET' or a black screen and a hang with the fans on max. Only happens when DX12 is enabled. Tried swapping in a a 290x that I had installed until recently and it works with DX12 enabled.

I've done the clean driver install dance. Used DDU, ran 'sfc /SCANNOW' and DISM /Online /Cleanup-Image /RestoreHealth.

I tried disabling the antivirus and getting rid of the system tray clutter.

I verified the system is stable with Prime95, Kombustor and Memtest86.

I updated to the latest motherboard BIOS.

System:

i7-4790K 4GHZ

16GB Corsair Vengeance RAM (4x4, purchased as a kit)

Asus Z97 Pro WiFi ac Motherboard (Bios 5303)

PowerColor Red Dragon Vega 56 (upgraded from Asus DCUIIOC 290x)

EVGA SuperNOVA 1200 watt Power Supply

I'm on a clean install of Adrenalin 19.2.1.

20 Replies
8-fingered
Adept III

Additional debugging:

I tried various settings for the Timeout Detection and Recovery Registry Keys.

I disabled the Windows Game Bar and the Steam Overlay.
I repaired or reinstalled all the Microsoft Visual C++ Redistributables.
I had Steam verify the game files.
I uninstalled and re-installed the game.
I tried all available game builds via the Steam Beta feature.
I tried different display resolutions.
I tried various combinations of settings including the lowest possible settings.
I swapped the system power supply for a known good unit.
I tried moving the graphics card to another x16 slot.
Also, additional symptom. Sometimes I get a system tray message:
SOTTR.exe has been blocked from accessing graphics hardware.
8-fingered
Adept III

I've also done a clean uninstall/reinstall and moved to Adrenalin 19.2.2. 

isaida
Journeyman III

Are you on a windows insider preview? Anything from around November onwards ? If so, that is the problem.

I was on Windows 10 build 1709. I upgraded to 1803 and it seems to have fixed the problem.

isaida wrote:

Are you on a windows insider preview? Anything from around November onwards ? If so, that is the problem.

No, that is definitely *not* his problem...;)  I've been in the Insider's for 4 years now (started 10/1 2014) and I am now on version 1903, build 18343 and SoftTR runs like a top in DX-12 multigpu on my RX-590/480 8GB Crossfire system--the game runs fine on every Insider's build, in fact.  Need to look elsewhere...RUnning the Adrenalin 19.2.2's...Indeed, I have ~300 games (or more) actually installed (8TBs storage + is only about half full!) and every single one of them runs fine--the compatibility is far better than with Windows 7, for instance. 

0 Likes
harbi
Adept III

Played the previous Rise of the Tomb Raider last month with crossfire Vega 64.
Same generation card & same engine used for both games.
.
DX11, no crashes with single gpu or crossfire
DX12, A LOOOT of crashes with a similar DXGI_ERROR_DEVICE but I forget the exact number. In both single & dual gpu setups. Same thing, black screen and a hang, with fans on max.
.
The fix for me was the general Undervolt profile I had for my Vega 64, 1 year without any issues but this was the only game that needed more power. So I changed my undervolt from 1000mV to 1030mV. Game ran smoothly without issues after that.
.

I tried disabling the antivirus and getting rid of the system tray clutter.

I verified the system is stable with Prime95, Kombustor and Memtest86.

I tried various settings for the Timeout Detection and Recovery Registry Keys.

I disabled the Windows Game Bar and the Steam Overlay.
I repaired or reinstalled all the Microsoft Visual C++ Redistributables.

To be honest, good troubleshooting but rarely fixes stuff. The previous Rise of the Tomb Raider had a lot of issues with it's DX12 version when it launched. I still haven't played Shadow btw.

.

SOTTR.exe has been blocked from accessing graphics hardware.

hmmm, had a similar issue with Witcher 2 back when I had a 390x. What a headache, I remember reading quite a number of articles and doing a lot of troubleshooting. Nothing worked until I upgraded my very old 2009 motherboard in 2016

It is unforgivable that we are going on 2 years now of this nonsense with default settings on drivers not working. Almost every Vega, RX470-RX590 user has to change from defualt settings to get the cards to be able to run game. We tell people here the same advice you just gave on the Vegas and it's a different set of tricks that gets the polaris cards going. The cards that existed before the Wattman drivers all ran better and still do on the older drivers. Why AMD doesn't acknowledge this and correct it is beyond me. Now with the 2019 drivers they have even made it worse screwing up the Fan and Temp controls further.

Please report your issues to AMD it's all we can do, the website even buries this contact form in 3 layers deep and makes it very hard to find:  Online Service Request | AMD 

I have made multiple reports against the 2019 drivers and opened a Customer Care Ticket. I also have a ticket open with Square Enix support over this and have provided them with logs and dumps.

It seems that an upgrade from Windows 10 build 1709 to build 1803 may have fixed the problem, but I think there is some problem between SOTTR, Windows and the 2019 AMD drivers that needs to be fixed.

I just hope build 1803 fixes more than it breaks.

Honestly 1809 is the one to go with if you are on the 2019 drivers. They build test the drivers to the current release. So if you are upgrading Windows go to 1809. 1809 IMHO is much better for gaming that any of the 3 prior releases.

pokester wrote:

It is unforgivable that we are going on 2 years now of this nonsense.

Please report your issues to AMD it's all we can do, the website even buries this contact form in 3 layers deep and makes it very hard to find Online Service Request | AMD 

Does it really make a difference? asking for real.

I know they lurk the reddit AMD forums a lot and get feedback there but... I don't know why I've became numb with AMD's driver issues. I got frustrated and stopped reporting them. 

Now I'm an early adopter of Radeon Vii. The fan curve issues still exists for 2-3 months now, they are not even acknowledging the fan curve problem. Fan speed still jumps between points instead. Last stable one is 18.2.1, the one just before the revamped 2019 one.

Which link should I use?

Online Service Request | AMD 

AMD Issue Reporting Form 

The issue reporting form is to notify them of bugs. The other is for support, and they are supposed to reply with help. My personal experience is that the rarely do. I'd say they have for me about 25% of the time but not once in the last 6 months. So GOOD LUCK WITH THAT. 

I actually bought an RTX 2060 Friday night to replace my RX 580. I'm so tired of all the issues and so far this is working great without a problem. Time will tell for sure. 

ah! RTX 2060, grats, good purchase. 

.

To be completely honest, I was quite close to buying an RTX 2080 but a last minute decision... Radeon Vii.

Not as hot and loud as some say. Minor tweak to voltage, temps reach 65c max, junction temp 85c max.

.

I do know that if I bought an RTX 2080, I would generally be getting a better product overall but... I don't know why I keep supporting underdogs in general. I just hope AMD gets their GPU division in order.

I got mine for 314 bucks and it over clocks to 2050 gpu and 8000 mem. It is as fast as a Vega 64 and GTX 1080, with that OC. So pretty sweat deal for the money. I only have a 1440p, 75hz monitor so it's just perfect for that. 

Damn good deal! 

pokester wrote:

I got mine for 314 bucks and it over clocks to 2050 gpu and 8000 mem. It is as fast as a Vega 64

Plus lower power consumption, heat & fan noise : D 

0 Likes

I don't even here the fan over the CPU fan at full load. So far it is rock solid. Got that Anthem game with it. Wow is that game horribly optimized. Horrible frame rates. There are people with the RTX 2080s complaining they can't even get 60 fps at 1080. I'm fluctuating from 28-60 fps on mine. Every reviewer is talking how bad it is. Even on the consoles its bad. Every other game is way faster though. about 150% of my RX580.

The stupid day one patch broke it.

Don't forget, it's a pretty demanding game with top of the line engine.

I played the early access version a week before. 1440p, max settings, solid 65-75 fps outdoors, 110-130 fps indoor. Now I'm getting 45-55 fps outdoors, 90 fps indoor.

The game has great potential, patches and content updates will definitely make up for the crappy launch.

Reviewers are giving it lower score than Fallout 76 lol... its not that bad. Great game-gunplay triumphs over anything. It just came at a time where people are just fed up with games broken at launch, the whole "launch now, patch later" is not going to work anymore.

Anthem Game definitely has severe issues.

Star Wars Battlefront II is IMHO the most pretty graphics I have seen. And boy does it scale to be better the higher you go. I am using the in game scaling and have it set to 1440 @150 scale, Ultra, so close to 4k, my RTX 260 is running that game at 100-120 fps. This is a AAA title that is still receiving engine updates and uses the latest Frostbite engine.

Battlfield V is just gorgeous and has as much going on in it as Anthem and I get 100 fps at 1440p Ultra. It doesn't have any scaling options or I would up that a bit. Also the latest Frostbite Engine and unlike Battlfield 1, DX 12 runs like a dream, even on Nvidia RTX, cards.

Anthem at 1440p all low setting with no anti-aliasing and low post processing it fluctuates hugely between  26 fps and 60 fps.   If I switch to 1080p it is honestly no better and blurry not being my native res. Something is hugely wrong with this game.

Touché...

Actually ROTTR was working fine, I re-installed it to test it. The DX12 there was a bolt-on, SOTTR was built from the start with DX12. I think SOTTR may make the most extensive use of DX12 of any currently released title.


I think I have a fix, an upgrade from Windows 10 build 1709 to 1803 seems to have fixed the problem. Hopefully it didin't break anything else.

That's great to hear, have fun.