[solved] Computer crashing & hard-resetting all over the place (was: Huge issues with RX 5700 XT, now with R9 270X too)

[velis]

Ever since I bought a RX 5700XT I have games crashing on me. Different reasons, but crashing A LOT. Also while browsing.

I thought it was the XFX 5700XT thiss II ultra - it was really hot to touch while gaming. But OTOH, it crashed even with card copletely cool, set to 1080p gaming, etc. Or in browser, sometimes windows itself.
So today a friend lent me his old R9 270X. Tried it immediately with my two currently played games. Both crashed within minutes. Same crash reports / dialogs as 5700.

I replaced an NV card with that RX 5700XT and both of these games were running completely fine with that card.

I don't get it: I'm pretty sure these two cards work just fine for people. After all, the R9 was successfully used by my friend for quite a while.
I even replaced my old Intel setup and went with a 2700X / B450 trying to fix these issues. Windows 10 freshly installed, the whole shebang. AMD driver cleaner ran a gazillion times, multiple driver versions tried too. No dice.

I just cancelled my replacement order with Amazon until I figure out what the heck is wrong with my setup. Tomorrow I'm switching the R9 with an 1060 GTX in one of my servers and trying that one out in my gaming rig.

But I would really like to get that 5700XT working, it' way more price-effective than current NV offerings. Anyone have a good idea on what else I could try?

 

[Glo.]

Reinstall drivers. Completely removing all of Nvidia driver stuff.

 

[CuriousMike]

Any chance your power supply is wonky?

 

[Chapbass]

What drivers are you on? Right now I have problems with crashing if I use the newest. I've been on 19.2.1 I believe and they've been rock solid.

 

[Steltek]

Don't use the drivers that came with the card. Download the newest ones from AMD as there have been a lot of recent changes and bugfixes since the RX5700 XT was released.

 

[DooKey]

Try DDU and uninstall NV and AMD video drivers. Reinstall AMD drivers. If that doesn't work then you are one of several having trouble with 5700 series cards and drivers.

 

[VirtualLarry]

Had a heck of a time with screen black-outs with my XFX reference blower RX 5700, on 20.1.4, much better on 20.2.1.

 

[EliteRetard]

Back in the day AMD got themselves a bad rap for drivers...and for the longest time it haunted them even though it was a complete non issue.

I guess since everybody kept slamming them for it, they decided might as well just give up on drivers...and now this is what we get.

Really unfortunate, as it felt like people were just starting to let go of the misinformation and their bias and actually realize that everything was good.

 

[VirtualLarry]

they decided might as well just give up on drivers...and now this is what we get.

Comments like this, off-hand about AMD "abandoning" their drivers, when any old bloke can see that they're just put in a huge effort in releasing fully-revamped "Adrenaline 2020" drivers, is why no-one takes anything you say seriously.

I'm willing to give them at least a little slack, they did just introduce their biggest new GPU arch in years, too - "RDNA".

 

[Stuka87]

To the OP, you need to fully remove ALL graphics drivers. Run DDU to remove both the nVidia and AMD drivers: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

What you describe is not uncommon if you have a mix of both drivers.

When you install the AMD drivers again, download the latest drivers, don't use the drivers that came with the card.

 

[Stuka87]

Back in the day AMD got themselves a bad rap for drivers...and for the longest time it haunted them even though it was a complete non issue.

I guess since everybody kept slamming them for it, they decided might as well just give up on drivers...and now this is what we get.

Really unfortunate, as it felt like people were just starting to let go of the misinformation and their bias and actually realize that everything was good.

Its a bit hypocritical to go through and talk about people spreading misinformation about AMD drivers while you one line above spread disinformation about AMD drivers....

 

[killster1]

Comments like this, off-hand about AMD "abandoning" their drivers, when any old bloke can see that they're just put in a huge effort in releasing fully-revamped "Adrenaline 2020" drivers, is why no-one takes anything you say seriously.

I'm willing to give them at least a little slack, they did just introduce their biggest new GPU arch in years, too - "RDNA".

i think his post was funny, of course they are not serious, but really they produce a card with crappy drivers? WHY? rushed? rather wait for proper working cards then trick people into buying them (most of which seem like AMD fans) im all for competition as its good for everyone but they still suck until they can beat the 1080ti with out massive issues. wonder when that will be. 1080ti was released March 10, 2017. lulz

 

[DAPUNISHER]

Hardware Unboxed addressed this early today -

I had fits with my 5700XT at launch. It put me off Navi, and given how many are still struggling with the 5700 series, I won't be buying one anytime soon. Bought a 2060 Super and 2070 Super, and both have been excellent. I still have my Red Devil Vega 56 too, and it is a rock solid card, and drivers issues are as non existent as on my Nv cards. Navi will get there in time, but there are still issues to sort out.

 

[EliteRetard]

Comments like this, off-hand about AMD "abandoning" their drivers, when any old bloke can see that they're just put in a huge effort in releasing fully-revamped "Adrenaline 2020" drivers, is why no-one takes anything you say seriously.

I'm willing to give them at least a little slack, they did just introduce their biggest new GPU arch in years, too - "RDNA".

Did I forget /sarcasm/ mode?
Obviously they didn't abandon driver development.

However there's no denying that they failed at delivering proper software at the time of hardware launch.
Actually AMD has been having a tough time with software, firmware, and BIOS over the last couple years.

I think that deserves some razzing.

 

[velis]

Thanks guys for all the suggestions. However, as I said: this was a completely blank Win10 install. It has never seen NV drivers. If any drivers need to be purged, it's Intel because when I replaced my MB, I didn't reinstall.

I think I have another M.2 lying around, will try reinstalling from scratch again, but TBH I'm not holding my fingers crossed.

@CuriousMike : there's always a chance. I'm afraid I have little option in way of testing ATM as I have no spares. Been thinking of getting a spare one, so maybe it's a good time to do it. However, I have already started a return procedure for the 5700XT at Amazon. Any further testing will have to be done by the R9 since I now have to return the 5700XT.
But, this same PSU was running the 970 GTX just fine and it should also run the R9 just fine. Power draw from the wall with 5700XT inside is 300W under full load while the PSU is 560W (recommended for the 5700XT is 600W).

@Chapbass & others: I never touch the CDs that come with stuff. I always only download the official drivers. I tried 2019.7.something and latest 2020 stuff. Similar issues on all versions.

 

[Shmee]

I would check PSU as mentioned, though it could also be a RAM/CPU issue, try running memtest.

 

[VirtualLarry]

Did I forget /sarcasm/ mode?
Obviously they didn't abandon driver development.

However there's no denying that they failed at delivering proper software at the time of hardware launch.
Actually AMD has been having a tough time with software, firmware, and BIOS over the last couple years.

I think that deserves some razzing.

Yeah, you did forget the /s, but you do also have a point, AMD should have been "ready to go" - "on day one" of their new architecture, and as that linked HardwareUnboxed video commented, "AMD has been using their users (of 5700(XT)) as beta-testers for the last 7 months".

I've been dealing with issues too. I don't use mine for gaming (not yet, anyways), just mining, alongside a GTX 1660ti Gaming X, in the same box (asking for trouble, I guess).

The recent 20.2.1 drivers seem worlds better than the 20.1.4 drivers, which were again worse than the 20.1.2 and 20.1.3 as far as black-screen issues. Unlike what HUB mentioned, mine black-screen, then come back a few seconds later, generally. They don't require a force power-off.

That said, my Reliability Monitor graphs look pretty ugly, and I suspect that is mostly due to my RX 5700 GPU.

I'm testing out a new all-core 4.0Ghz OC on my R5 3600 now, with the AGESA 1.0.0.4 patch B, and it seems stable. Here's hoping that it's actually MORE STABLE than just leaving it on auto/default.

 

[Stuka87]

Thanks guys for all the suggestions. However, as I said: this was a completely blank Win10 install. It has never seen NV drivers. If any drivers need to be purged, it's Intel because when I replaced my MB, I didn't reinstall.

I think I have another M.2 lying around, will try reinstalling from scratch again, but TBH I'm not holding my fingers crossed.

So I reread your initial post again, and I did miss a detail. You tried an old 270X and have the same crashing. Drivers for that card are rock solid, have been for years. So I am also starting to think this is a PSU issue.

I cannot think of any driver related reason for the 270X to have the same issues as the Navi card.

 

[velis]

Latest update: discussed this with a friend, realised that I changed TWO components at one time: the GFX card and the M.2 SSD. Upgraded from 960 evo 500 GB to 970 evo 2TB.
Just switched them, first played EverSpace for half an hour on the 1060 GTX, then on 2700 XT. No crashes whatsoever.

I'm now putting the 970 EVO back in expecting that Everspace is going to crash within 5 minutes.

After that, I'm reinstalling again and also trying the M.2 slot at the back side of the MB. See what happens, see if I can get it to work reliably at all.

But right now it seems I mistakenly blamed the graphics card for something it wasn't guilty of. Even if the error messages were saying it was

Edit: Yep: took it 5 minutes to crash this time. Maybe it's very temp sensitive as it's placed directly under the GFX card? Trying to move it to back side of the MB now, see what happens.

 

[godsis]

There is a possibility that drivers are conflicting. It is difficult to say more specifically.

 

[Zstream]

Latest update: discussed this with a friend, realised that I changed TWO components at one time: the GFX card and the M.2 SSD. Upgraded from 960 evo 500 GB to 970 evo 2TB.
Just switched them, first played EverSpace for half an hour on the 1060 GTX, then on 2700 XT. No crashes whatsoever.

I'm now putting the 970 EVO back in expecting that Everspace is going to crash within 5 minutes.

After that, I'm reinstalling again and also trying the M.2 slot at the back side of the MB. See what happens, see if I can get it to work reliably at all.

But right now it seems I mistakenly blamed the graphics card for something it wasn't guilty of. Even if the error messages were saying it was

Edit: Yep: took it 5 minutes to crash this time. Maybe it's very temp sensitive as it's placed directly under the GFX card? Trying to move it to back side of the MB now, see what happens.

It could be temp sensitive or something odd with the channels going to the CPU. Some sort of conflict between the two. However, I’d cool the drive first, or look into some bios settings.

 

[velis]

I checked BIOS for any M.2-related settings. Found none. I have now backed up the SSD to a spinster and have just finished initial Windows install on the SSD, again completely from scratch.

I will have the test games installed shortly, hopefully this time they won't crash. I'm hoping that it was the mess with swapped MB that got it to go so unstable. Though the issues started apperating the moment i upgraded the SSD & GFX last time, I also did a clean install then... We shall see.

BTW, I tested the overheating hypothesis: it was completely invalid. SSD temperatures reported did not change significantly when I was playing a game. Can't testify for any prolonged periods as crashes were really easy and fast to get, but in five minutes of GFX card working TOO hard (I used a super res), the SSD temps only went up a degree or so.

 

[PhonakV30]

some people fixed their problem with just one driver :

https://www.reddit.com/r/Amd/comments/f4nham

 

[maddie]

Did I forget /sarcasm/ mode?
Obviously they didn't abandon driver development.

However there's no denying that they failed at delivering proper software at the time of hardware launch.
Actually AMD has been having a tough time with software, firmware, and BIOS over the last couple years.

I think that deserves some razzing.

Having to put /s for good sarcasm is as terrible as putting /j when making a joke.

 

[Chapbass]

Thanks guys for all the suggestions. However, as I said: this was a completely blank Win10 install. It has never seen NV drivers. If any drivers need to be purged, it's Intel because when I replaced my MB, I didn't reinstall.

I think I have another M.2 lying around, will try reinstalling from scratch again, but TBH I'm not holding my fingers crossed.

@CuriousMike : there's always a chance. I'm afraid I have little option in way of testing ATM as I have no spares. Been thinking of getting a spare one, so maybe it's a good time to do it. However, I have already started a return procedure for the 5700XT at Amazon. Any further testing will have to be done by the R9 since I now have to return the 5700XT.
But, this same PSU was running the 970 GTX just fine and it should also run the R9 just fine. Power draw from the wall with 5700XT inside is 300W under full load while the PSU is 560W (recommended for the 5700XT is 600W).

@Chapbass & others: I never touch the CDs that come with stuff. I always only download the official drivers. I tried 2019.7.something and latest 2020 stuff. Similar issues on all versions.

To clarify my post:. I was NOT referring to the drivers on the CD, OR the newest drivers. I'm saying I've had great luck with SPECIFICALLY these drivers: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-12-1

Anything in the 20.x line I've had issues with.