• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

This is the driver thread, not an RMA thread. Don't clutter up this thread with your RMA issues.

Considering I originally thought it was a driver issue, and others also responded with similar issues, texture stretching, black streaks and some artifacting on new drivers, it seemed very relevant at the time.

Without posting here, discussing, and trying other member's suggestions I would not have found the true issue.

I'm so terribly sorry the community working together and trying to find a solution upsets you.
 
Considering I originally thought it was a driver issue, and others also responded with similar issues, texture stretching, black streaks and some artifacting on new drivers, it seemed very relevant at the time.

Without posting here, discussing, and trying other member's suggestions I would not have found the true issue.

I'm so terribly sorry the community working together and trying to find a solution upsets you.

The community working together is indeed great and should be encouraged.

It should also be encouraged to know when it's worth posting your own thread with your own issues, instead of cluttering up the driver thread with details of your faulty GPU's and RMA experience. Simply courtesy really :)
 
faulty GPU's and RMA experience. Simply courtesy really

What RMA details? Mentioning Germany? That and mentioning I'm boxing up the item is hardly details. Considering Nexus and JediFragger also mentioning rainbow flashing and checkerboarding in the Division shortly after I experienced it?
Even prjwebb mentioned rainbow colours in the exact same game on the latest drivers.

All sounds very reasonable to me, as it again pointed more at a driver issue; and as you said this is the driver thread.
Without their and other's comments with similar, and vastly different issues pinpointing the issue would not have been possible

Or do you really think making a thread on it's own, only to have people with similar issues with drivers make sense? To me, it's more of a courtesy to keep the similar issues in the relevant thread, even if the end conclusion ends up being different. It's certainly better than another thread clogging up the front page.
 
+1 @N19h7m4r3

I had a look at AMD reddit today for the new driver feedback and saw a few people posting the exact same as what we are having (although not quite as bad as yours :p)


Eh? :confused:

Eh to you too.

It's an essential rendering method for SteamVR that AMD keep promising to add to an upcoming driver.

I take it they haven't, my cousin will not be happy.
 
Eh to you too.

It's an essential rendering method for SteamVR that AMD keep promising to add to an upcoming driver.

I take it they haven't, my cousin will not be happy.
I know what it is (and no, afaik, it hasn't been added yet) but what has that got to do with my post, which you quoted?
 
so, i just upgraded from 16.12.1 to 17.2.1 (card is a r9 280). Couldn't get the installer to open from radeon settings so i had to download the 17.2.1 installer package from amd's website (WHQL-Win7-64Bit-Radeon-Software-Crimson-ReLive-17.2.1-Feb28)

Didn't choose the clean install option (should i have?, so i know in future), just the regular install (i guess it overwrites the old driver - i've never had a problem with that method before) & did a custom upgrade (all 3 driver boxes were ticked). Install went well until the screen went blank & stayed that way - i waited a few minutes until, i guess, the install finished (cpu activity light stopped flashing) & then reset my pc (reset button) & selected the option to get windows to start normally.

Seems ok (radeon settings shows the driver has been upgraded to 17.2.1). But, that's the first time that has happened to me (blank screen after driver install - i remember getting a blank screen during install with previous drivers but the screen never stayed blank). I submitted a report/survey about it to amd.
 
Last edited:
Anyone with a MSI 480 Gaming X having fan/temp reading issues since updating to these drivers? I updated between benchmarking runs and now my temps seem to be reading as lower than they should be and the fans are stopping when temps are high. I think it's the 17.3.2 update but I'm not sure.
 
Meh to these damn 17.xxxx drivers again... Getting some weird hitching in games with the newest drivers as well as the artifacting I mentioned a page or 2 ago.

Back to 16.11.5 I go, again...
 
Does anyone change Texture Filtering Quality from Standard to High in Radeon Settings? Does it actually make any difference to FPS or IQ?
 
Radeon Software Crimson ReLive Edition 17.3.3 Release Notes
Article Number: RN-WIN-RADEONCRIMSONRELIVE-17.3.3
Radeon Software Crimson ReLive Edition is AMD's advanced graphics software for enabling high-performance gaming and engaging VR experiences. Create, capture, and share your remarkable moments. Effortlessly boost performance and efficiency. Experience Radeon Software with industry-leading user satisfaction, rigorously-tested stability, comprehensive certification, and more.

Radeon Software Crimson ReLive Edition 17.3.3 Highlights

New Multi GPU profile:

  • Mass Effect™: Andromeda (DirectX®11)
    • Multi GPU can be enabled from command line using "-RenderDevice.AmdCrossfireEnable 1"
Fixed Issues

  • Texture flickering may be observed in Mass Effect™: Andromeda in Multi GPU system configurations.
Known Issues

  • Tom Clancy's Ghost Recon® Wildlands may sometimes fail to launch in three or four way Multi GPU enabled system configurations.
  • Tom Clancy's Ghost Recon® Wildlands may experience flicker in Multi GPU system configurations when performing a tsk switch or changing graphics settings while the game is running.
  • Application profiles in Radeon Settings may fail to retain after system log off or reboot for some gaming applications.
  • AMD FreeSync™ technology mode may not be compatible or function with Sniper Elite™ 4.
  • Enabling supersampling in Sniper Elite™ 4 may cause image cropping.
  • Radeon Settings may crash on switching Windows® user after toggling AMD CrossFire™ technology mode.
  • A small amount of apps may still 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.
  • Shadow Warrior 2™ may fail to enable Multi GPU on game launch due to a missing application profile in Radeon Settings.
Known Issues for Radeon ReLive

  • The XBOX™ DVR application may cause conflicts with Radeon ReLive, users are suggested to disable XBOX™ DVR if Radeon ReLive is experiencing issues.
  • Radeon ReLive may fail to install on AMD APU Family products or experience a system hang or failure to record when using the recording feature on AMD APU Family products.
  • Radeon ReLive may intermittently fail to work after performing task switches of applications. A work around is to disable and then enable the feature in Radeon Software.
  • Radeon ReLive may stop working after hot unplugging of a secondary display.
  • Radeon ReLive will not allow recording settings to change with Instant Replay enabled. A workaround is to disable Instant Replay and change settings then enable Instant Replay.
  • Vulkan™ applications may experience a game hang when using Radeon ReLive to record.
  • Radeon ReLive will not notify an end user of low disk space during recording.
  • System information overlay is only generated on first run and will not be repopulated when system configuration is changed.
  • Radeon ReLive may exhibit corruption in recordings when capturing Microsoft Office applications.
Package Contents

The Radeon Software Crimson ReLive Edition 17.3.3 installation package contains the following:

  • Radeon Software Crimson ReLive Edition 17.3.3 Driver Version 16.60.2911.1011 (Windows Driver Store Version 21.19.525.256)
 
Reinstalled doom today (haven't played in many months) and am getting a random hitch that happens quite a few times during a match (MP). This is in vulkan. Fps stays well above 100 and frame times are nice and consistent but out of nowhere I get a hitch/ sutter. In the performance metrics it's all green filled up then when the hitch happens I'll see one quick line of red in the total/fps/ and cpu graphs but not in the gpu.

Could this be driver related? Anyone had doom issues recently? Every other game is jamming fine :(
 
So I decided I wanted to overclock my 290x's some more as PUBG is pretty demanding.

Previously I had used afterburner and clocked both cards to 1070 with + 50mv. I did have it running at 1100 with +100mv but it wasn't stable in GTA.

I thought I would give Trixx a go since it can do +200mv. As soon as I change anything really I get the following:

https://youtu.be/oBHiFp3GM6A

Any thoughts? I don't have that issue with Afterburner at all. I am running 3x screens if it matters.]

Edit: Ignore, decided to overclock with afterburner but it wasnt stable at 1100 even with + 200mv
 
Last edited:
Back
Top Bottom