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.
If you're clocks are dropping, you'd notice the FPS drops in game without having to look at any log/monitoring.
Hi Peeps...
Well, today whilst playing R6 Siege, I got a case of "severe gpu downclocking whilst in a particularly tricky bad guy stand off" that resulted in a very bad end for my character![]()
So, after deciding for the 200th time "Enough with this power saving AMD bullsh*t !!!", I decided to start the great internet search for the fabled reg edit of legend...
After several hours of fruitless searching, I happened across the below link & post (the Link will be at the end of this post)...
I followed the simple instructions and in minutes, AMD GPU downclocking was securely ejected from the ****ing building :banana: :banana:
Holy Crap !!! I had found "The Holy Grail" it would seem :kermit: :cheers:rder: :mhp:
This fix was originally directed towards Fury/390 series GPU's as these were the ones most important to AMD & performance junkies alike... There are reports however that the reg edit entries also work on the majority of GCN architecture cards of the feature level 1.0 upwards...
I can confirm that after using just one edit, I had completely eliminated GPU downclocking outside of game menus, which completely emulates the zero core features of previous & sound 15.x.x catalyst drivers...
I have tested also with over 65 AAA/AA game titles including 95% of the latest releases over the last 2 yrs...
The other awesome thing about this fix is that now the full power of my 390 gpu is unlocked, In-Game performance from the 16.2 crimson driver is nothing short of !!! STUNNING !!! I mean it, !!!STUNNING" I tell ya :gape: :gape:
Anyway peeps, enough talk, more action... Checkout the link & post, complete the edit, switch off un-official OC mode in AB, set ya max clocks, enjoy ya games again & **** you AMD !!! What, ya could'nt incorporate this reg edit into the crimson driver yourselves? ****ing retards :bang:
!!! EDIT !!!
The first reg edit is for GCN cards follow the instructions & you are GOLDEN :thumbup:...
The other additional reg edits are to be included for non-GCN cards...
!!! Instructions !!!
1. Search for TFQ_NA in Regedit. This will take you to a folder like HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000. Inside the 0000 folder, you'll see lots of registry keys like "RadeonSoftwareEdition." If you do, you're in the right place!
2. Add a new DWORD 32-bit key in the 0000 folder and name it: PP_AllGraphicLevel_DownHyst
3. Set the value data to decimal 20
4. Reboot
!!! Additional Edits !!!
You can also add these DWORD 32-bit keys, as they may also help resolve the issue if the above edit fails or you have a non-gcn card.
1a. PP_ActivityTarget (value data 30 decimal)
2a. PP_AllGraphicLevel_UpHyst (value data 0 decimal)
3a. PP_AllGraphicLevel_DownHyst (value data 100 decimal) : Note that this edit replaces step 2+3 from above...
Fury/390 series GPU DownClock fix : www.reddit.com/r/Amd/comments/477ot0/how_to_fix_fury_x_clock_throttling_on_radeon/
Have Fun Gaming people :thumbup:
Peace peeps...
Any sign of a driver to fix The Division?
im sure he means to fix the flickering and poor performance related to crossfire only shanks.
Yeah because I was thinking game is running superb here for me single GPU.
Runs pretty good for me on a 290x @1440p but would be nice for crossfire to be working so I can turn up more settings![]()
When the profile was added and 16.2.1 was released, the issue did not exist. We're investigating, that's all i have for now Puppetmaster.
That's the one, the lead Devwas promising a new driver today - maybe he's working on AMD time though.
Runs pretty good for me on a 290x @1440p but would be nice for crossfire to be working so I can turn up more settings![]()
Has AMD managed to get a big title to have working crossfire recently at launch?
Witcher 3/Tomb Raider/The Division/Fallout 4 - all didn't have working Xfire at launch, although I think Fallout had a quick fix.
And then you get posts on Twitter teasing new drivers - will we actually see said driver today?
It's getting more than a little frustrating.
Looks like we're about to get new driver tomorrow anyway? Or what you think of this teaser?
https://twitter.com/CatalystMaker/status/707306465112006658
leaving it late indeed.
yeah i know mate, usually drops around 8pm our time doesn't it. That seems to be around the popular time anyway. Soooooo hope this has The Division crossfire fix, would love it if they've nailed it like they did the Fallout 4 crossfire hotfix a day after it was launched.