Caporegime
You wouldn't, Crossfire is total garbage, it just doesn't work.
-
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
Associate
you are wrong.
Permabanned
I wouldn't touch this with a barge pole, Gigabyte seem to always be cutting corners with AMD cards lately, I bought a similar looking 4gb 560 from Gigabyte a couple of months back and it was a terrible noisy thing, We all saw the poor Gigabyte 480 review from JZ2C as well. When I go with Vega I want a good quality cooler like was on the Fury Tri-x, Not a lightweight plasticky pos like this will be.
Associate
- Joined
- 2 Oct 2017
- Posts
- 6
Can You explain to my why, instead of a childish 1 word flaming answer?
Ans some articles comparisons to prove your argument.
Soldato
Crossfire doesnt work in all games is most of that argument, check the game you play most
Crossfires just been dropped by AMD. No crossfire for Vega and very patchy crossfire in the preceding models. It's certainly not worth it going forward.
Soldato
Amd has only other week released its vega crossfire driver. Only two GPUs supported though.
Associate
Well, Vega 10 cards you have to do a little bit of tinkering before you get the results which you might be looking for. For instance without doing any overclocking and by simply Under-Volting the card and setting the power limit to +50% in AMD Wattman utility, you can get not only drastically improve the performance of the card but also lower them Temps. i have my set on 1120 & 1140 and HMB2 on 1000 and with overclocking my temps dont get hotter then 75c and performance is beyond 1080 gtx in most if not all games i play and benchmarks i run. Vega cards just need a little lovin
... Besides a lot of game titles dont support Crossfire nor are they planning to, it a dying technology i think. And if you think the power draw is bad with Vega then do some research on how much 2 rx580 in crossfire will pull. Vega card's architecture is very promising and just isnt well optimized for a lot of games today but with proper driver optimization and proper optimization by game developers we will soon enough will start seeing performance increase like we did in Forza 7 where it outperforms gtx1080Ti in 1080p & 1440p. ( that is if you want to stick with AMD ) but if you really dont care about all this stuff, then you maybe just shoulda gotten a GTX 1080 or something.Thats y i directed you to the undervolting guide on earlier post, and there are better guides out there you just have to look around and find one that you think is easier to understand
Last edited:
Soldato
That's mGPU not Crossfire (yes it's the same thing, but it's not branded as Crossfire any more)Amd has only other week released its vega crossfire driver. Only two GPUs supported though.
Caporegime
As said above, it doesn't work in all games, some games you'll get worse performance than a single card, you'll get stuttering, flickering textures, this that and the other.
Ive had my second card disabled for about 2 years now, as i just got sick of booting games up, only to have to quit them to disable Crossfire, due to the problems, absolute nightmare, now, i just boot up a game and play.
Soldato
Does Vega offer anything different for the name change etc?
Soldato
I don't think so, I think it's just because of DX12/Vulkan that they've changed the brand name.
Associate
- Joined
- 2 Oct 2017
- Posts
- 6
Well, Vega 10 cards you have to do a little bit of tinkering before you get the results which you might be looking for. For instance without doing any overclocking and by simply Under-Volting the card and setting the power limit to +50% in AMD Wattman utility, you can get not only drastically improve the performance of the card but also lower them Temps. i have my set on 1120 & 1140 and HMB2 on 1000 and with overclocking my temps dont get hotter then 75c and performance is beyond 1080 gtx in most if not all games i play and benchmarks i run. Vega cards just need a little lovin
Thats y i directed you to the undervolting guide on earlier post, and there are better guides out there you just have to look around and find one that you think is easier to understand
Thank You, I did look and try settings from the link you provided yesterday, but for me it seemed the more i tweeked it the worse the performance got. and the card runs faster with windows 7 than windows 10, but win 10 cant use dx12. Im getting terrible stuttering trying to play low end game on steam, maybe its changes devs made, but the stuttering was not as bad on my much lower spec 1060. Illl try again and see if i can match your perfomance. I hear you on the drivers optimisation too. Ill give it some more thought,work and time.
Thank You very to You and all who provided information for me to ponder
Associate
Thank You, I did look and try settings from the link you provided yesterday, but for me it seemed the more i tweeked it the worse the performance got. and the card runs faster with windows 7 than windows 10, but win 10 cant use dx12. Im getting terrible stuttering trying to play low end game on steam, maybe its changes devs made, but the stuttering was not as bad on my much lower spec 1060. Illl try again and see if i can match your perfomance. I hear you on the drivers optimisation too. Ill give it some more thought,work and time.
Thank You very to You and all who provided information for me to ponder
yea, not sure if maybe you aren't doing something correct or maybe not undervolting it enough or setting power limit high enough. i had similar frustration with the card when i got it and was ready to tell AMD to shove it and to add the icing on top of that my pc would constantly reboot while running DX11 and somE OpenGL APIs only come to fing out that my power supply was the problem. But after my pc instability was resolved by swapping PSU and after watching a few tutorials and playing with voltage and clock settings and keeping my power limit at +50%(as it is VERY important to do so) i found the sweet-spot. The RX Vega has a lot of potential, i really recommend searching on youtube for undervolting guides and find one that is more up to date and more comprehensive then maybe the one i tagged you in. But if you dedicate a day to find that sweet-spot i promise you will be just as satisfied with the performance as i am.
Also I've noticed my performance increased in windows 10 using the 17.9.3 latest amd driver makesure you are using that.
and the flicker problem is something usually caused by windows DVR feature. Just go to settings, Gaming, and disable GAME BAR and Game DVR features in windows 10 that helped resolve my flicker issue. not sure if that's what you are also seeing.
And remember watching the guides don't settle for the values the reviewer is showing/setting his card at. all Vega cards are different, you know silicon lottery lol, so you might be able to push your card higher or maybe ease up on some of the undervolting depending on what your card can take, also look into HMB2 voltage in wattman while undervolting as that can help your overall undervolting, also overclocking your HMB2 to about 1020-1030 will alone boost your performance but you might be able to push it further then that. mine works up until 1075MHz some can push their HMB2 to 1100MHz
right now the sweet-spot on my vega 64 is state 6 & 7 Voltage control @1135&1140 ans Frequency 1592MHz & 1692MHz. my HMB2 set to 1060MHz with 1040 Voltage. my power level is turned up all the way to 50 and manual fan control min @ minimum RPM & Target @ max RPM. you can try these settings and maybe work your way to find the sweet spot for yours
Last edited:
Associate
- Joined
- 2 Oct 2017
- Posts
- 6
@ Sharmanov. Thanks for those tips, I was using win 10 with 17.9.3, but the cards performance was abysmal. Here is example, Balanced setting with just fan speeds set to min 3600 max 3800rpm and using claymores duel eth miner my card was doing 13-31Mh/s with an averge of 27Mh/s Eth and Pasc 660Mh/s but with same driver but with windows 7, it was consistent at same settings on wattman, doing 35Mh/s Eth and 1060Mh/s pasc. I then after tried some games, and to me its performs so much better under win 7 OS. Ill keep the card, and keep looking for optimizations and tweaks for wattman. My current settings are balanced except for fan control min 400 max 3800 and temp control max 65'c Its running stable at those with 220w gpu draw. This is best i can find atm as any thing other, and ive tried many individual and combined settings the performance drops no matter how much power i push it to.
Associate
cant do balanced dude... have to go custom.. and undervolt.. will get better performance, temps, and power draw
Associate
- Joined
- 2 Oct 2017
- Posts
- 6
Yeah i know, i just set balances as a kind of reset before i select custom to change settings. Ill look during break at playing with undervolting, but im thinking my cpu may be bottlenecking, so this evening ill run perfmon while trying some games at various graphics settings then take a look at the logs to see if it is bottlenecking, and if so ill prob get a new MB and a Ryzen 16 core threadripper.
Associate
you are actually better of clicking 'reset', towards the top right of crimson, than changing to the actual profile.
Associate
Well I can't comment on the mining but I've got some good stable bench/daily settings for my Vega64 which top out at 65C.
First up I should say I flashed my BIOS to the MSI Liquid Cooled V64 BIOS version 8774 available on Techpowerup. Being Liquid Cooled on an Air Cooled card causes Wattman to not read fan speeds correctly though with a little trial and error you can use it to match up fan speeds correctly (just annoying). However to solve this and Wattman's repeated crashes I use OverdriveNTool available on Guru3D's forums. Much more robust, saves profiles but only for the overclocking side of Wattman. Doesn't change any of the other global settings like HBCC or FPS Max limits etc...
Onto my settings:
Core P6 - 1667MHz (stock for LC BIOS) @ 900mv
Core P7 - 1752MHz (stock for LC BIOS) @ 950mv
HBM2 - 1050MHz @ 900mv
Fans set to 500 RPM Min and 3800 RPM Max
Temp Max 70C (Max for LC BIOS)
Temp Target 65C (If mining drop that to 58C as above 60C HBM timings loosen and ~20% compute performance loss occurs)
Power Target +10%
In Superposition I'll see a stable consistent ~1580MHz with those settings. They aren't my max bench settings but they are consistently stable and fast. No core speed fluctuations due to temp/power throttling.
In PUBG I see between ~1590 and ~1680MHz fluctuating depending on how dense the scene is (@99-100% GPU load it'll be at the low end, though PUBG is often at around 50-60% load). To keep Framerates stable and remove stutter I use ClockBlocker to keep the card in P7 state so it can't downclock and cause stuttering.
BTW this is on an HIS Vega64 Air Cooled normal black version. Of course YMMV so if the 900mv is too low for your card, of course test until you find the min stable voltages for your card (I recommend using Superposition for this).
If you have the RAM for it I'd also enable HBCC as it is a measurable improvement in most use cases for me, though again I can't attest to mining efficiency.
Associate
Hi all. I put one of the air cooled reference cards under an Eiswolf over the last couple of days. The EW seems to do the job, 48c under timespy on GPU and HBM. However, I really want to know where this "hot spot" lives as it's hitting 105c .... seems almost like it might be somewhere in the VRM/power delivery section.
I tried putting the LC 016.001.001.000.008734 BIOS but it didn't seem stable, I'll have to try one of the older revisions. Stepping shows as C0 with the LC BIOS so that must be set in the BIOS rather than pulled from somewhere else.
I tried putting the LC 016.001.001.000.008734 BIOS but it didn't seem stable, I'll have to try one of the older revisions. Stepping shows as C0 with the LC BIOS so that must be set in the BIOS rather than pulled from somewhere else.