Issue with Asus GPU Tweak II

[Juu Nii]

Issue:

Whenever I set my GPU clock. It automatically ups it with 20MHz. It's very weird as today is the only time I noticed this. I've hated the whole thing since I got this GPU. Now If I wish to go to "Silent Mode" I need to manually set to clock to 1270MHz so it ups it into the clock of 1290MHz which is the silent mode clock. Why I need to go to Silent mode is because the GPU will crash on EVERY game on the other 2 preset clocks which are OC Mode (1330MHz) and Gaming Mode (1310MHz) Which I think might be because my PSU is too crappy or it thinks it's overheating.

Specs:
GPU: Asus ROG STRIX AMD Radeon RX 480 OC, 8GB
Memory: Kingston 8GB(2x4GB) HyperX Fury DDR4 2133 MHz, CL14
Processor: Intel Skylake i5-6500, LGA1151, 3,2GHz
Mobo: AsRock Fatal1ty B150 Gaming K4
PSU: Corsair VS550
OS: Windows 10 home 64-bit, Finnish

 

[Ironsounds]

Hello... in the Digital world there are clock signals/crystals... and thus changes are not a exactly settable... what you are seeing Normal. B )

 

[Juu Nii]

So. It is normal that it inceases the clock by 20 MHz? Even on the preset clocks?

 

[Ironsounds]

Hello... Yes... your thinking in the "Analog" world... it a math thing with the original set Clock/crystal signals... you Sync to the signal below or above your setting, in some cases. Also the memory has to sync to the GPU too... and you will see crashes if you are not sync'd with the memory too... if you make a chart you will see what mghz numbers work vs others... Sometimes ODD or Even number changes will show up for "Best" choices too... The timing crystals used are not changeable/adjustable... 100 Mhz crystals are common, but in the real world it might run at 99.999 Mhz Or 100.1 B /

 

[Juu Nii]

I just don't get it how it started doing it today...
It's also weird when I put it through the presets it doesn't adjust the Voltage and I do have to do that manually. While adjusting the GPU clock manually it does infact change the voltage then. But. So far the only time it doesn't crash anything is when I have the Clock at 1290MHz and the voltage at 1150mV. Adjusting the voltage up only delayed the crashes with the higher clock presets. But this may be as I am afraid to higher it above 1156mV since afterall it's just a scary thought to fry an 1000€ PC. This is just a weird thing that occured to me today and I just wanted to see if it was alright. But I should do an another post prob'ly if I were to discuss how to overclock properly or watch a tutorial or something.

 

[Ironsounds]

Hello... You have physically made chips on the GPU... they are not perfect from the materials or process used... Some chips do better than others. You got to find the "magic" numbers for your product and not compare un-exact science to others results.

Yes there is a science or procedure to Over clocking... memory does not OC well because it is very fast already and there is never massive cooling attached like the GPU... and typically Heat dictates your OC to anything in our physical world. So you need to paying attention to your Temps when doing this, Summer, Winter, and air humidity will affect your Cooling performance... What works today may not work 6 months from now B /

Typically I find the "Magic" numbers and Flash the GPU with them and shut off the APP used to find them... and Done.

Yes there are plenty of tutorials on line... and is how I learned B )

 

[Juu Nii]

Well. I'm just gonna do it like this now.
Up the clock. Start a game or an app like 3Dmark. If it crashes I up the mV. Once I find a spot where it doesn't crash I repeat if I want to.

 

[Ironsounds]

Hello... Raising voltage will increase heat to the semi-conductors, but is needed to get to the next level of "Good" numbers. Vary your 10mhz increase to 20mhz or 30mhz too... because of the ODD-EVEN syncing math of it... and with the memory too... like I said you will see a pattern of 'Good" numbers to use. B )

It could take a couple days to find the best stable settings... relax and let the "Product" tell you what numbers are good for it... VS you trying to tell the product what to do B )