Discussion in 'Graphics Cards' started by Kaapstad, Aug 14, 2017.
Any chance of sharing those settings?
V64 is the best card around at the moment for serious gamers.
I am a bit wobbly updating at the moment as the Bacardi has taken a serious bit of err benchmarking.
I hope you are keeping well Tony.
If you look back through this thread it'll be in here, prob a fair way back now. I'll post them up again tomorrow evening as I won't be near pc till then.
Here you go, settings for 1750/1150. Does do 1180 mem speed with same voltage, i just cant find that post, thats what the firestrike run was done at.
Yep I'm good Kev thanks, might pop up and check out your latest toys soon if that's ok??
Lmao literally my reaction, the two Megatron's of the Vega 64 thread....
I realize the answer is super nuanced, and has probably been discussed ad infinitum in this thread, but...
What are the optimal settings in WattMan to get the best boost performance? Do I just max out the Power limit and then dial back the core voltage to 1100 mV on States 6 and 7?
You are welcome to take one of my Turing cards for a test drive.
The hard bit is finding software that the cards can use.
Heard they is only one single race track open allowing Turing. Its quite pricey though.
Also the Radeon software will tell you, Display , hover over Radeon freesync and it will tell you the range of the monitor
Just used Panos's settings which were running fine till the new driver update. Currently running on 19.1.2. System turns off every now and then (not frequent) and radeon says settings have to be reverted to default due to unexpected system failure. When the system shuts down, I cannot turn the PC on unless I switch the PSU off and then on again. Is this a PSU issue or a driver issue? The PSU is a Superflower Leadex Platinum 850W. Any help will be appreciated. GPU is a Sapphire Nitro Vega 64
Likely a driver issue. If the settings were fine prior to the driver then it's not likely to cause other hardware to cause issues with a driver change. Revert back to 19.1.1 or 18.12.2 and see if you have the same issues.
Or perhaps new driver optimisations are getting more performance from the GPU and his previous borderline stable settings are now unstable. Does it happen at stock? If so then yes perhaps a driver issue.
Wondering if any of you can shed any light on some mysterious behaviour I'm seeing when trying to overclock my Vega64 for the first time.
Following the guide:https://forums.overclockers.co.uk/t...king-undervolting-information-guide.18793012/
I have tried undervolting and overclocking. According to logs, the GPU frequency is up and yet when running firestrike the performance is significantly less. Any idea why a frequency increase would cause a decrease in framerate?
I'd say it's simply expecting too much from the gpu, Panos won the silicon lottery, you likely haven't at least not to the same extent, you also need to take his LC bios & custom waterloop into account. If you want a stable overclock you'll need to start a lot lower and work up. Taking everything into account ie: temps & noise targets as well as performance my Vega 64 sat stable at 1692/1080, I could boot up with clocks like 1725/1100 & it would even do successful Firestrike runs & run some games like that but it wasn't a 24/7 overclock. Like I said aiming for Panos's clocks isn't realistic unless you also won the lottery, start lower & work up, It took me weeks to work out the best stable clocks for my Vega Red Devil. In the future you may also find that some games aren't stable at your 24/7 overclock but that's what the separate game profiles in Wattman are for. In some games I would get crashes that could be days apart, to completely remove them I used a 1687/1050 profile for certain games, once you enable the profile it automatically down clocks when you start that particular game. Sometime it won't but that's just a bug the driver team need to fix.
I also found that there's a limit for clock by clock performance. I got to a point where I was at the sweet spot & pushing the clocks further was detrimental to performance. My sweet spot was 1692/1080 I found that I could run as an example 1712/1100 okay but when I benched at those clocks the performance results were lower than they were at 1692/1080. Every Vega is different and there's no quick way to get it right just take your time & start low.
That sounds like it might be related to your cards sweetspot as I mentioned in the post above.
DDU fixed this, if anyone has the same problem - thanks @faceman123
Separate names with a comma.