AMD Radeon Software Crimson ReLive 17.7.2 driver download

Graphics cards - AMD Adrenaline (Windows 10/11) 468 Updated 2017-07-26 22:57 by Hilbert Hagedoorn

Click here to post a comment for AMD Radeon Software Crimson ReLive 17.7.2 driver download on our message forum

#5458632

wotan

2017-08-03 07:05

@Unwinder thank you for the Fix...all working great now with my R9 390 :banana:

#5458707

pakoo

2017-08-03 11:22

Did you read the notes?

I cant downclocking memory, only at 1000 MHz downclocking nice, Above this system crash 🙁. Remember with 16.11.5 drivers I can downclocking memory at 625 MHz in 3 cards and all runs good (temps runs 15-20º least) 🙁. When arrive "relive drivers", I cant never downclocking memory above 1000 MHz 🙁. Hope understand me, Im use google translator. Thanks.

#5458718

ninja750

2017-08-03 11:49

I've updated MSI AB with new ODN X2 API support.

i read your post, i haven't understood if you have found a workaroud waiting the official SDK or if someone gave you the current SDK

#5458719

Passus

2017-08-03 11:50

I cant downclocking memory, only at 1000 MHz downclocking nice, Above this system crash 🙁. Remember with 16.11.5 drivers I can downclocking memory at 625 MHz in 3 cards and all runs good (temps runs 15-20º least) 🙁. When arrive "relive drivers", I cant never downclocking memory above 1000 MHz 🙁. Hope understand me, Im use google translator. Thanks.

Instalar revive 17.7.1 y usar MSI Afterburner para reducir las tarjetas gráficas Yo también usé google translate

#5458724

A2Razor

2017-08-03 11:58

i read your post, i haven't understood if you have found a workaroud waiting the official SDK or if someone gave you the current SDK

Answered in Unwinder's prior update-post on the SDK status, follow that link and read the "good" section. Specifically: "I've just got my copy via MSI"

Some news (both good and bad) on 17.7.2 overclocking compatibility with third party applications.

#5458794

pakoo

2017-08-03 14:32

Instalar revive 17.7.1 y usar MSI Afterburner para reducir las tarjetas gráficas Yo también usé google translate

Thanks!!!. Lastest Msi afterburner from unwinder (from this thread)? I can dowclocking memory? Thanks again

#5458795

Unwinder

2017-08-03 14:34

If AMD driver can, then you can do it in AB. Stable clock limits do not depend on applicaiton.

#5458832

ReaperXL2

2017-08-03 15:51

If AMD driver can, then you can do it in AB. Stable clock limits do not depend on applicaiton.

Thanks dude (I speak for all I think) for your swift action with regard to 17.7.2 API support & MSI AB. Is there a specific link to download the updated AB as I can not seem to locate it (I just find 440 beta12). Again, thanks bro :thumbup: EDIT ==== Never mind bro, located the link in your update post (need to wear my glasses more)... :cheers:

#5458888

Passus

2017-08-03 17:25

Thanks!!!. Lastest Msi afterburner from unwinder (from this thread)? I can dowclocking memory? Thanks again

http://office.guru3d.com/afterburner...p440Beta15.rar Que la versión ahora funciona de nuevo con el controlador 17.7.2, también puede undervolt con él

#5458890

Passus

2017-08-03 17:26

New Afterburner beta confirmed working fine on GCN 1.0 thanks Unwinder

#5458902

pakoo

2017-08-03 17:48

http://office.guru3d.com/afterburner...p440Beta15.rar Que la versión ahora funciona de nuevo con el controlador 17.7.2, también puede undervolt con él
Hola!. Undervolt si que puedo, lo que no puedo es hacer downclock a la memoria 😀. Con los drivers 16.11.5 (antes de los relive) podía poner la memoria al minimo (625 MHz) con su correspondiente Undervolt, las temperaturas bajan muchísimo. Pero desde los drivers relive (16.12.1 creo) no puedo bajar la memoria mas alla de los 1000 MHz, bajando de ahí el pc se bloquea. Con estos últimos 17.7.2 en las release notes dice que puedo hacer underclocking a la memoria pero en mi caso es mentira, solo puedo bajarla hasta 1000 MHz (de stock van a 1250). Sorry all for using another language 😀.

#5458906

THEAST
2017-08-03 17:53

New Afterburner beta confirmed working fine on GCN 1.0 thanks Unwinder
Working fine how? Just like the v17.6 driver, GCN v1.0 is on OverDrive instead of Wattman in this driver (it has been moved back and forth between OverDrive and Wattman multiple times since Wattman was introduced) and I can neither overclock nor underclock either of my cards without my machine crashing during 2D cutscenes in games. If I underclock either of my cards, during 2D cutscenes, the clock of the underclocked card will constantly fluctuate between UVD and 2D clocks (500 and 300 MHz core clock), resulting in heavy flickering and eventually black screen. If I overclock, in such cutscenes, the gpu clock will get stuck on 300 MHz, and the memory clock will get stuck on some very low clock, resulting in the same scenario as before. I can 100% reproduce this with the cutscenes in Assassin's Creed - Brotherhood, using both Afterburner and OverDrive, which means there is something wrong with the driver. This started with either 17.5 (never installed this one, so I am not sure) or 17.6; everything was fine on 17.4. If it wasn't for the CRU bug, I would have stayed on 17.4. But yeah, my cards are too old and apparently, expecting AMD to not break stuff that already work is too much to ask. When it comes to fixing the UVD bug, GCN v1.0 is too old, but when it comes to forcing the new overclocking API and breaking overclocking and underclocking with it, GCN v1.0 is suddenly supported...

#5458924

Passus
2017-08-03 18:17

Working fine how? Just like the v17.6 driver, GCN v1.0 is on OverDrive instead of Wattman in this driver (it has been moved back and forth between OverDrive and Wattman multiple times since Wattman was introduced) and I can neither overclock nor underclock either of my cards without my machine crashing during 2D cutscenes in games. If I underclock either of my cards, during 2D cutscenes, the clock of the underclocked card will constantly fluctuate between UVD and 2D clocks (500 and 300 MHz core clock), resulting in heavy flickering and eventually black screen. If I overclock, in such cutscenes, the gpu clock will get stuck on 300 MHz, and the memory clock will get stuck on some very low clock, resulting in the same scenario as before. I can 100% reproduce this with the cutscenes in Assassin's Creed - Brotherhood, using both Afterburner and OverDrive, which means there is something wrong with the driver. This started with either 17.5 (never installed this one, so I am not sure) or 17.6; everything was fine on 17.4. If it wasn't for the CRU bug, I would have stayed on 17.4. But yeah, my cards are too old and apparently, expecting AMD to not break stuff that already work is too much to ask. When it comes to fixing the UVD bug, GCN v1.0 is too old, but when it comes to forcing the new overclocking API and breaking overclocking and underclocking with it, GCN v1.0 is suddenly supported...
Maybe it has something to do with using crossfire mate?

#5459123

THEAST
2017-08-04 04:21

Maybe it has something to do with using crossfire mate?
It could, but it doesn't change the fact that I didn't have this problem with the v17.4 driver and everything that came before that.

#5459134

dsbig
2017-08-04 06:08

sometimes when I start afterburner, my system will freeze and then bsod....:3eyes:

#5459256

ldwar
2017-08-04 13:19

thanks Unwinder, works like a charm!

#5459301

Noisiv
2017-08-04 14:54

sometimes when I start afterburner, my system will freeze and then bsod....:3eyes:
same here, and its been like that for ages. I think i fixed it byticking off low level access.. or something similar... not sure, cant check now, away from home for a week or so.

#5459323

AlleyViper
2017-08-04 16:15

^ X2, I've had a 7970 in the past that only in combination with particular MB required that to be disabled, else it'd crash the system if AB was launched while the GPU was under load.

#5459366

THEAST
2017-08-04 17:54

Hmm, I am not sure if it is the latest Skype update or this driver, but it seems Skype calls do not trigger the UVD bug on my system anymore.

#5459376

XPzKiber
2017-08-04 18:21

How to disable edid in the driver 17.7.2, I used to install the resolution of 2560x1080 on an ordinary FullHD monitor with VSR earlier on the old driver and just appear black bars at the top and bottom and the picture was normal, and now when trying to put 2560x1080 the picture is stretched, how to fix it? The permission I add in the register DALNonStandardModesBCD1. Sorry for english.

Previous Page

Next Page