Vega owners club

[acperience7]

Anyone having problems with wattman not saving profile with 17.9.2 drivers? Mine keeps resetting back to balanced after shut down,would it be because of stability or is it because i turn the desktop off from mains?

I had this issue yesterday. However, it didn't default everything. It left everything in manual, and defaulted the core, fans, and power limit. All of them were still on manual mode though. I have only done 1 restart since installing the drivers though.

 

[TheoneandonlyMrK]

I had this issue yesterday. However, it didn't default everything. It left everything in manual, and defaulted the core, fans, and power limit. All of them were still on manual mode though. I have only done 1 restart since installing the drivers though.

That's indicative of instability of core clock at a particular voltage.

 

[acperience7]

That's indicative of instability of core clock at a particular voltage.

Guess I'll have to do some tweaking. The clocks/voltages I have on it now seemed fine in the last 2 driver releases.

 

[TheoneandonlyMrK]

Guess I'll have to do some tweaking. The clocks/voltages I have on it now seemed fine in the last 2 driver releases.

Drivers can change stuff that much tbh ,i have not installed the latest yet though so ill see.

 

[kurosagi01]

So an update..after i complain it doesn't save my wattman custom profile on here,boot my PC and it actually saved it lol.

 

[fullinfusion]

does anyone have the silver limited edition? please gpuz shot that

Vega 56 = C3
Vega 64 = C1
Vega 64 Liquid = C0
Vega 64 Limited = ??

I poked the Vanguard team to get the limited revision for ya. I'll post a screenshot if any have the card

 

[fullinfusion]

FE

 

[Eric3988]

Bump!

Flashed my 56 BIOS to 64 last night and am pleased with additional headroom for the clocks. Had an hour of testing but only started using Wattman last night because I haven't used an AMD for some time. It's more complicated to OC these things than in times past, but I guess it's nice to be able to fine tune your card more now.

Firstly, I think I'll want to see how how I can push the clocks at stock power settings to see how they do. It's fascinating to see the clocks go everywhere during a 60-120 second bench. The one thing I noticed at the stock settings is how the HBM clocks behave. The stock 64 target is 940 MHz and with my card I noticed during the FUR Mark test is how it bounce between 940 and 800. Managed to get a stable 950 with a reduction in the core clocks, so I'm guessing this is a power issue seeing as I hadn't messed with that. Besides that FUR Mark test I'll be using the in-game benchmarks for Total War: Warhammer 2 to see how the settings behave. Stay tuned...

 

[fullinfusion]

Bump!

Flashed my 56 BIOS to 64 last night and am pleased with additional headroom for the clocks. Had an hour of testing but only started using Wattman last night because I haven't used an AMD for some time. It's more complicated to OC these things than in times past, but I guess it's nice to be able to fine tune your card more now.

Firstly, I think I'll want to see how how I can push the clocks at stock power settings to see how they do. It's fascinating to see the clocks go everywhere during a 60-120 second bench. The one thing I noticed at the stock settings is how the HBM clocks behave. The stock 64 target is 940 MHz and with my card I noticed during the FUR Mark test is how it bounce between 940 and 800. Managed to get a stable 950 with a reduction in the core clocks, so I'm guessing this is a power issue seeing as I hadn't messed with that. Besides that FUR Mark test I'll be using the in-game benchmarks for Total War: Warhammer 2 to see how the settings behave. Stay tuned...

don't use furmark period.. Use Unigine supposition and it'll show the clock fluctuations..

try 1110mv in state 6 and 7
set power limit to +50
try +4 on the core and 1100Mhz on the HBM and also change the fan curve

here look at mine

 

[londiste]

The one thing I noticed at the stock settings is how the HBM clocks behave. The stock 64 target is 940 MHz and with my card I noticed during the FUR Mark test is how it bounce between 940 and 800. Managed to get a stable 950 with a reduction in the core clocks, so I'm guessing this is a power issue seeing as I hadn't messed with that.

are you monitoring hbm temps? 800mhz should be thermal throttle.
on my vega, hbm was always ~15c hotter than core.

 

[Eric3988]

don't use furmark period.. Use Unigine supposition and it'll show the clock fluctuations..

try 1110mv in state 6 and 7
set power limit to +50
try +4 on the core and 1100Mhz on the HBM and also change the fan curve

here look at mine

Thanks for the tips, will try that ASAP. How would you classify your settings, BTW? Slight OC with reduced energy usage?

are you monitoring hbm temps? 800mhz should be thermal throttle.
on my vega, hbm was always ~15c hotter than core.

FYI, I was referring to the frequencies, not temps.


EDIT: Here are some captures of my flash from GPU-Z

 

[fullinfusion]

Thanks for the tips, will try that ASAP. How would you classify your settings, BTW? Slight OC with reduced energy usage?

no it's how these card overclock to keep the frequency more higher for longer with lower heat...

I see ppl add voltage but all it does is add heat to the card and causes the core to downclock real fast.

Experiment with lower voltage and you'll see what I mean

But the key is the power slider, keep it to +50 and play with the voltages on the core, lower the better for heat wise.

My clocks are 1702 core and 1150 memory

 

[Vayra86]

I can even suggest Witcher 2 as a great way to check stability. When I passed 10-15 minutes of simple gameplay without CTD incidents, I was sure of the settings being rock stable. Dragon Age Inquisition also is a good way of this test imho.

A heavy CryEngine game does the work too, Crysis 3 being the best one not in the least because its also a massive CPU load, so you simulate a heavy gaming load also in terms of case temps. You just need a recent, full fledged engine at work, one that tickles all the subsystems of the GPU.

Unreal Engine by comparison tells you zero about stability.

Sorry for barging in as a 1080 owner, but very nice work on these tweaks! Genuine interest 1630 mhz and up (!) is pretty sweet for GCN. Damn

 

[londiste]

FYI, I was referring to the frequencies, not temps.

that's what i was talking about. the moment something goes wrong, hbm reverts to 800mhz, even on v64. that includes thermal throttling.

 

[Eric3988]

no it's how these card overclock to keep the frequency more higher for longer with lower heat...

I see ppl add voltage but all it does is add heat to the card and causes the core to downclock real fast.

Experiment with lower voltage and you'll see what I mean

But the key is the power slider, keep it to +50 and play with the voltages on the core, lower the better for heat wise.

My clocks are 1702 core and 1150 memory

Still haven't settled on my clocks just yet, but I have question for you. Does WattMan like to reset your custom settings frequently on reboots? I had the settings stay last night after a stable setting was found, then this morning I fire it up and I see it defaulted to the Balanced profile and reset my custom settings. I suspected this would happen and took a screencap of my previous settings so all good here. Just wondering if other users got to deal with this too. Anyways, I'm going to run on 1525 @ 1050 mV and 1625 @ 1050 mV on P6/7 respectively. Memory will be at 1080 at 1050 mV. Fan is going to be 700-2800 RPMs, so it's not too loud. These clocks got me over 4K on the Superposition Benchmark, so gonna try some gaming today to see if it's stable and without artifacting.

 

[fullinfusion]

Still haven't settled on my clocks just yet, but I have question for you. Does WattMan like to reset your custom settings frequently on reboots? I had the settings stay last night after a stable setting was found, then this morning I fire it up and I see it defaulted to the Balanced profile and reset my custom settings. I suspected this would happen and took a screencap of my previous settings so all good here. Just wondering if other users got to deal with this too. Anyways, I'm going to run on 1525 @ 1050 mV and 1625 @ 1050 mV on P6/7 respectively. Memory will be at 1080 at 1050 mV. Fan is going to be 700-2800 RPMs, so it's not too loud. These clocks got me over 4K on the Superposition Benchmark, so gonna try some gaming today to see if it's stable and without artifacting.

what driver are you using?

And yes they seem to default to a point, kinda hit n miss right now.

 

[Eric3988]

Using the latest driver 17.9.3

 

[fullinfusion]

Using the latest driver 17.9.3

Yeah I believe AMD did a quick fix for now just to keep people from overclocking too high and not being able to recover. I'm pretty sure the next driver release should have it fixed

 

[Eric3988]

Yeah I believe AMD did a quick fix for now just to keep people from overclocking too high and not being able to recover. I'm pretty sure the next driver release should have it fixed

No sweat, I know its a new feature.

 

[turbogear]

Still haven't settled on my clocks just yet, but I have question for you. Does WattMan like to reset your custom settings frequently on reboots? I had the settings stay last night after a stable setting was found, then this morning I fire it up and I see it defaulted to the Balanced profile and reset my custom settings. I suspected this would happen and took a screencap of my previous settings so all good here. Just wondering if other users got to deal with this too.

I experience this same issue time to time.
Though my OC on Vega 64 is stable, but after rebooting PC sometimes the WattMan resets seting to balanced mode. It does not happen every time. It is random and happen every now and then.
I am also on 17.9.3, but saw this also on older driver versions.

 

[Eric3988]

I experience this same issue time to time.
Though my OC on Vega 64 is stable, but after rebooting PC sometimes the WattMan resets seting to balanced mode. It does not happen every time. It is random and happen every now and then.
I am also on 17.9.3, but saw this also on older driver versions.

Sure enough, after another reboot, the settings are reset again, so if you find something you like, take a screenshot like me. I played Warhammer 2 all day with these settings and it worked like a charm. Max temperature was 78 C after several hours of sustained gaming. I would leave the game on idle from time to time so not all of it is taxing action, but still promising start. I know I can push the clocks higher, but my goal is to get to 79 C or below for max temp.

 

[fullinfusion]

Nice going!

Saturday I gamed all afternoon and down volted even more, 1.01v and ran sustained frequency of 1670 ish. Temps in the closed case hit 68 max and HBM of 53ish c.

I'm still swapping from the 56 to the 64 to find the sweet spot between the 2

 

[turbogear]

Sure enough, after another reboot, the settings are reset again, so if you find something you like, take a screenshot like me. I played Warhammer 2 all day with these settings and it worked like a charm. Max temperature was 78 C after several hours of sustained gaming. I would leave the game on idle from time to time so not all of it is taxing action, but still promising start. I know I can push the clocks higher, but my goal is to get to 79 C or below for max temp.

Here is the screen shot of setting I am using on the Wattman for the Vega 64.
As explained in the previous post, I have been using these settings for some time now on my custom liquid cooled Vega 64.
https://www.techpowerup.com/forums/threads/vega-owners-club.236314/page-2#post-3716160

I have increased the voltage from 1075mv to 1085mV over the course of time. 1075mV was unstable in some very few cases.
With 1085mV the Vega 64 is rock stable for many weeks now. The highest GPU temperature in gaming that I ever get is 42°C.
The power consumption is about 25W higher than the balanced mode, but performance is much better.
The average clock speed of the GPU is always in the range of 1620MHz or higher depending on the games.
In Witcher 3 average clock is around 1620MHz and Battlefield 1 at around 1638MHz.

 

[Eric3988]

Here is the screen shot of setting I am using on the Wattman for the Vega 64.
As explained in the previous post, I have been using these settings for some time now on my custom liquid cooled Vega 64.
https://www.techpowerup.com/forums/threads/vega-owners-club.236314/page-2#post-3716160

I have increased the voltage from 1075mv to 1085mV over the course of time. 1075mV was unstable in some very few cases.
With 1085mV the Vega 64 is rock stable for many weeks now. The highest GPU temperature in gaming that I ever get is 42°C.
The power consumption is about 25W higher than the balanced mode, but performance is much better.
The average clock speed of the GPU is always in the range of 1620MHz or higher depending on the games.
In Witcher 3 average clock is around 1620MHz and Battlefield 1 at around 1638MHz.

Very nice temps and clocks, sir.

As for me, I think I finally found the sweet spot with my 56. Basically running everything at 1 volt too, check this out. My temps vary according to ambient temps; when my living room is 25.5C my top temp on the Vega will be 80C, but when I have it cooler at night I saw that drop to 76C.

 

[kurosagi01]

So i've witnessed my first potential bottleneck on Battlefront 2 beta which i'm guessing its my CPU,i had the beta on ultra with one of the filter options on highest option and the GPU was running below 80%. Lowered the option down by 1 and it started performing above 80%.