- Joined
- Jun 16, 2013
- Messages
- 1,457 (0.37/day)
- Location
- Australia
I've had this card - MSI RX 5700 XT Evoke edition, for about 2 yrs now, & apart from the first time I installed it, today I got a completely blank screen all whilst gaming in Borderlands 3.
Not sure if its a driver issue or a failing card but after doing a hard system shut down due to no visual control of options when it happened, upon rebooting the display resolution was capped at 1024x768 on my 1440p monitor.
Checking out device manager shows the card was now disabled...
Now the only time I've ever OC this card has been purely through AMD's software adrenalin edition suites. So it has only been a software type of OC at all. No fiddling with bios flashings, hard mods, etc...
I've had crashes before with this card in this particular game but presumed it was because of an over ambitions OC I had on it, restoring defaults stopped the crashes. I've got nearly a hundred hrs up on this game, so a fairly extensive run with an Unreal engine 4 based game. There was one mini map in the game where I had 3 crashes with the 22.5.2 drivers! but the rest of the game was stable after uninstalling them via control panel & reverting back o the 22.5.1 drivers.
Had 22.5.1 drivers running at the time & have even tried 22.5.2 drivers before, but this weird crash is a real eye opener imo. I uninstalled the 22.5.1 drivers & decided to try the 22.6.1 drivers as they are WHQL listed. So far so good, although only about an hour of gaming to test them at default settings in Radeon software suite with gaming profile enabled so far.
This is all under win 10, 21H2
So the real question is, is this because of the Game's code not being optimized in certain maps within the game or is this because of poor coding in the drivers themselves?
Not sure if its a driver issue or a failing card but after doing a hard system shut down due to no visual control of options when it happened, upon rebooting the display resolution was capped at 1024x768 on my 1440p monitor.
Checking out device manager shows the card was now disabled...
Now the only time I've ever OC this card has been purely through AMD's software adrenalin edition suites. So it has only been a software type of OC at all. No fiddling with bios flashings, hard mods, etc...
I've had crashes before with this card in this particular game but presumed it was because of an over ambitions OC I had on it, restoring defaults stopped the crashes. I've got nearly a hundred hrs up on this game, so a fairly extensive run with an Unreal engine 4 based game. There was one mini map in the game where I had 3 crashes with the 22.5.2 drivers! but the rest of the game was stable after uninstalling them via control panel & reverting back o the 22.5.1 drivers.
Had 22.5.1 drivers running at the time & have even tried 22.5.2 drivers before, but this weird crash is a real eye opener imo. I uninstalled the 22.5.1 drivers & decided to try the 22.6.1 drivers as they are WHQL listed. So far so good, although only about an hour of gaming to test them at default settings in Radeon software suite with gaming profile enabled so far.
This is all under win 10, 21H2
So the real question is, is this because of the Game's code not being optimized in certain maps within the game or is this because of poor coding in the drivers themselves?