Associate
- Joined
- 2 Sep 2017
- Posts
- 2
Using HWINFO64?
No, it was enhanced sync apparently. Turned it off and right away, no more stuttering.
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.
Using HWINFO64?
So these arrived earlier this week (sadly no Haribo, despite all the waiting), but had to wait a bit as I was still upgrading from a Phenom II X3 710 to a Ryzen 7 1700 (testing the difference it made with my existing graphics card):
In my Vega64 box the card was a bit lonely with just a generic quick installation guide and an address slip for Sapphire Technology for company; but really I don't miss the superfluous CDs, cables of dubious quality, plastic blanking plugs or plastic film.
Aside from upgrading the Phenom II that I've been using for ages, I'm also levelling up from this AIO-cooled HD 6850:
The black reference shroud seems to be metal and not the plastic of the Polaris cards - this card has some heft to it! Finally got my pre-build together last night:
Have tested a few games with both CPU & GPU at stock settings, and fantastic to be able to play Cities: Skylines without stuttering at 1080p - roughly twice the FPS and all fluidly smooth with all settings turned up.
The card has been stable so far - have run 3dmark a few times, and have had no problems so far with overclocking it on the 600W PSU. Will continue to tweak and test things with their stock air coolers for a bit before setting up the water cooling.
What are your clock settings at on this video Matt? This looks more like what I see playing games, boosting up to around 1725. Still haven't managed to get the clock any higher than that regardless of what game or benchmark I run on 17.8.2. Any attempts of actually setting the clock higher than 1750 has resulted in a crash...Some BF1 performance testing at max settings 3440x1440.
These are my Wattman settings. It varies from game to game what clock speeds i get, but it does hit 1802Mhz sometimes, but mostly it's mid-low 1700's.What are your clock settings at on this video Matt? This looks more like what I see playing games, boosting up to around 1725. Still haven't managed to get the clock any higher than that regardless of what game or benchmark I run on 17.8.2. Any attempts of actually setting the clock higher than 1750 has resulted in a crash...
See my previous post on this Tony.Interesting to see Matt on the 17.8.2 driver now and the card not hitting the 1800mhz core speed with ease like it was previously. That's what I thought would happen eventually, the earlier drivers just didn't seem to be accurately reporting the clock speeds. I just don't think these cards will go much higher than 1800mhz IMO, that's just way to much of an overclock. I think now things are settling, we'll start to see that a very good overclock will be between 1775mhz and 1825mhz. I've got mine set at 1750mhz but it rarely even hits 1730mhz when gaming. Maybe once drivers mature, we'll see the maximum clock speeds being hit more often.
Clock fluctutation is a feature of ACG = Advanced Clock Generator, which is enabled for DPM states 5/6/7. It will naturally fluctuate when there are current spikes. When current spikes occur voltage droops, to avoid instability during the droop, frequency must be decreased to match. This is why you see the fluctuation in the frequency.
To maximise highest possible performance, set +50% power limit + increase state 7 frequency and voltage if required. I use state 6 as stock max boost frequency and undervolt by -0.075mv and state 7 as my max stable core overclock + maximum voltage. This works well for me Vega and allows a nice performace increase over stock boost clock/voltage.
I recommend enabling HBCC too globally, even with just 16GB of system memory.
He did it to stabilize closer to 1752 instead of that being the peak.Ahh nice. Thanks Matt.
I've got state 6 and state 7 at 1750mhz and 1200mv. What's the benefit of settings state 6 to boost clock frequency exactly?
You don't need afterburner. With RTSS installed an running you can right click on items you want to monitor in HWinfo and select osd RTSS settings and enable it. In that same menu you can specify where you want it to be column and row.OK how do I get the OSD working in Hwinfo64? I've downloaded RTSS so how do I now get the two to work together? Do I also need MSI Afterburner? Cheers
He did it to stabilize closer to 1752 instead of that being the peak.
Not exactly, 17.8.2 behaves a bit differently than previous bios. If you set p7 to 1752 you'll never hit it. Go look through his videos, he often hits 1800+, it just depends on several factors.I achieve that by just running state 6 and state 7 the same.....at 1750mhz. My clock speed in games fluctuates between 1700mhz and 1730mhz. If Matt isn't getting to 1800mhz now, and like he says normally low to mid 1700's, then he could just set 1750mhz for state 6 and 7. That was kinda my point.
I achieve that by just running state 6 and state 7 the same.....at 1750mhz. My clock speed in games fluctuates between 1700mhz and 1730mhz. If Matt isn't getting to 1800mhz now, and like he says normally low to mid 1700's, then he could just set 1750mhz for state 6 and 7. That was kinda my point.
You don't need afterburner. With RTSS installed an running you can right click on items you want to monitor in HWinfo and select osd RTSS settings and enable it. In that same menu you can specify where you want it to be column and row.
Not exactly, 17.8.2 behaves a bit differently than previous bios. If you set p7 to 1752 you'll never hit it. Go look through his videos, he often hits 1800+, it just depends on several factors.