![]() ![]() ![]() If it wasn't for the CRU bug, I would have stayed on 17.4.īut yeah, my cards are too old and apparently, expecting AMD to not break stuff that already work is too much to ask. This started with either 17.5 (never installed this one, so I am not sure) or 17.6 everything was fine on 17.4. ![]() 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. 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. 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. 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. New Afterburner beta confirmed working fine on GCN 1.0 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |