Soldato
Vega just eats through MSAA like it's nothing 
8x MSAA 1440p Ultra
8x MSAA 1440p Ultra -
Competitor rules
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.
The RX Vega 64 Owners Thread
- Thread starter Kaapstad
- Start date
Res was 1440p, Mem at 1040 iirc. FH3 was maxed out settings x4AA, unlocked framerate.
Was late when I did it so might re-run again if I get time, also forgot how nice the game looks at times and so want to try it out at 4K on the TV at some point.
@shankly1985
Did another quick run to confirm mem at 1040. Still playing about with my card settings for clocks, power etc so will probably tweak this further.
Also hope to put something like an Eiswolf on it at some point, so not spending too much time on it at the moment.
Associate
Just put mine under water as the noise was doing my head in. Max temps of 35c so far, using a 360mm rad with only the gpu in the loop. Big rad only because I had it spare from a previous build.
Time to see how far this can clock
Time to see how far this can clock
Soldato
@shankly1985
Did another quick run to confirm mem at 1040. Still playing about with my card settings for clocks, power etc so will probably tweak this further.
Also hope to put something like an Eiswolf on it at some point, so not spending too much time on it at the moment.
Thanks for doing this, I just can not get my memory to max out unless I put more demand on the memory like 8xmsaa very strange
Definitely true, AMD clearly rushed Vega and didn't test things properly. That and drivers are still missing support for all hardware functions. But at least there's progress, whereas Nvidia has a year+ to polish their drivers.
Some people would call drivers fixing what looked to be pure hardware problem as magical, but in that sense AMD conjured magic this time. So there's hope for the future!
That is, if they actually know what and how they fixed...
Associate
At least I know for 100% sure mine was dodgy.
Last edited:
NP.
I've only really been monitoring it when running benchmarks at the moment but I'll keep an eye out for it when gaming.
Only really playing PUBG at the moment but I can imagine it doing it in that as that game is still all over the place at times with frame rate.
Soldato
Watched the video when he uploaded it. It's one thing him saying about altering the powerplay in registry, but how do you do that lol
no issue here but with an SSD it loads pretty quick so not sure if that affects things?
Trying to figure out if the issue I am having is a hardware issue with my card (RX Vega AC) or that it is just software instability. If anybody would be willing to check would be awesome! Thank you
Issue persists with drivers 17.8.2 and 17.9.1. Taking out the Vega and using the iGPU fixes the issue even with AMD driver installed.
Steps to reproduce: (Only for RX Vega owners)
- Install 3DMark Advanced edition
- Repeat for 10 times:
- Open 3DMark and while it loads the menu, move mouse frantically over 3DMark window till it is done loading (Tab that should be loaded is home with the Timespy background)
- Report back if your system freezes
It seems my system locks up when the fading animation is going on in the menu and so far I cannot find any reports of the same issue.
Hate to ask but....how in the blue hell would anyone even manage to create that oddly specific scenario in the first place?
Soldato
Been keeping an eye on my memory too over the last few days - although my card is an AOI, it is locked at the 1080 I have it set to.
Hi all,
Been keeping an eye on this thread for a while, thought I might as well post what I've been able to do with my card so far.
I've got the Standard Vega 64 Air.
In summary, I think the card has a lot of a potential and it certainly ***** all over my 2x r9 290x's that I've been running for ages now.
Due to only having bought an Acer XF270HU Freesync monitor a year ago, I've been pretty hyped about this car for a long time.
That being said, I'm hoping that future driver updates can sort some of the issues I've had, which I'll explain below.
I've had a bit of a roller coaster with what I've been able to do with the card, in summary on 17.8.2 I'd managed to achieve:
1630mhz core @ 1000mV 1025mhz Memory @ ~70c under load (2750rpm)
This was all good, wasn't actually hitting the 1630mhz - in general testing it would normal level out around 1590mhz - but if I set it any lower the core clock would drop (I don't really understand why this happens) I didn't try going any higher than 1630mhz, as pretty much as soon as I got this to be stable, the new driver came out.
So then I installed the new driver - on 17.9.1 I've managed to acheive:
1600 core @ 1125mV 1000mhz Memory @ ~80c under load (2750rpm)
I have no idea why, but on this new driver, this is highest core/mem and lowest voltage combination I can seem to get - I've had enough bench marking today so I might see if I can push past the 1600 tomorrow with other settings the same.
But basically, if I lower the voltage any significant amount or try to raise the memory speed - I can't get through the 3d Mark Timespy stress test. I couldn't even get through the normal benchmark sometimes (my PC crashes and restarts)
I'm really confused because on the previous driver, as you can see, I could volt much lower and clock higher and had no issues getting through the same stress test.
Has anyone had similar issues with being able to achieve different results on different drivers or is it just me?
Been keeping an eye on this thread for a while, thought I might as well post what I've been able to do with my card so far.
I've got the Standard Vega 64 Air.
In summary, I think the card has a lot of a potential and it certainly ***** all over my 2x r9 290x's that I've been running for ages now.
Due to only having bought an Acer XF270HU Freesync monitor a year ago, I've been pretty hyped about this car for a long time.
That being said, I'm hoping that future driver updates can sort some of the issues I've had, which I'll explain below.
I've had a bit of a roller coaster with what I've been able to do with the card, in summary on 17.8.2 I'd managed to achieve:
1630mhz core @ 1000mV 1025mhz Memory @ ~70c under load (2750rpm)
This was all good, wasn't actually hitting the 1630mhz - in general testing it would normal level out around 1590mhz - but if I set it any lower the core clock would drop (I don't really understand why this happens) I didn't try going any higher than 1630mhz, as pretty much as soon as I got this to be stable, the new driver came out.
So then I installed the new driver - on 17.9.1 I've managed to acheive:
1600 core @ 1125mV 1000mhz Memory @ ~80c under load (2750rpm)
I have no idea why, but on this new driver, this is highest core/mem and lowest voltage combination I can seem to get - I've had enough bench marking today so I might see if I can push past the 1600 tomorrow with other settings the same.
But basically, if I lower the voltage any significant amount or try to raise the memory speed - I can't get through the 3d Mark Timespy stress test. I couldn't even get through the normal benchmark sometimes (my PC crashes and restarts)
I'm really confused because on the previous driver, as you can see, I could volt much lower and clock higher and had no issues getting through the same stress test.
Has anyone had similar issues with being able to achieve different results on different drivers or is it just me?
Last edited:
Caporegime
Thank you very much! The menu fading thingy should take about 1-2 seconds regardless of quick loading. Your my 2nd report of fail, so I think my card is dodgy.
Magic! Internet! Nah, was benching for stability with 3DMark and noticed crashing on startup and "Gathering System Info". It caught my attention I was moving the mouse everytime and I tried to break it on purpose; with success! As you can gather, having to restart the system, open all monitoring tools, load 3DMark gets pretty frustrating when your system crashes every 10th time so I wanted to know what was going wrong. Seems to be the card.
My memory is maxed out to whatever I set my last P state for memory when playing Doom without VSync, 3DMark Firestrike or Unigine Superposition. Might try any of those options to check?
EDIT: You sure your aren't frame limiting the card in any way?
Caporegime
Magic! Internet! Nah, was benching for stability with 3DMark and noticed crashing on startup and "Gathering System Info". It caught my attention I was moving the mouse everytime and I tried to break it on purpose; with success! As you can gather, having to restart the system, open all monitoring tools, load 3DMark gets pretty frustrating when your system crashes every 10th time so I wanted to know what was going wrong. Seems to be the card.
Chalk up another one!
Chalk up another one!
You mean you are having the same crashes with a RX Vega (56/64 AC/64 LC) and 3DMark?
Soldato
Benchmarks seem fine, I only really monitored Forza so might just be that title.
How do I know if I frame limiting?
Is your FPS locked to some number (VSync ingame, VSync in driver, Radeon chill etc.) ? If so, it can decrease your GPU load. How high is your GPU load? If the GPU load is not maxed, it will not need max memory speed.
Soldato
latest driver brilliant here. So pleased, HEVC recording bug fixed, no stuttering on video playback and now rock solid 1720/1100 gaming. I'm so happy with this card.