Everyone talks game about how they don’t care about power consumption. We took that comment to the extreme, using a registry hack to give Vega 56 enough extra power to kill the card, if we wanted, and a Floe 360mm CLC to keep temperatures low enough that GPU diode reporting inaccuracies emerge. “I don’t care about power consumption, I just want performance” is now met with that – 100% more power and an overclock to 1742MHz core. We've got room to do 200% power, but things would start popping at that point. The Vega 56 Hybrid mod is our most modded version of the Hybrid series to date, and leverages powerplay table registry changes to provide that additional power headroom. This is an alternative to BIOS flashing, which is limited to signed drivers (like V64 on V56, though we had issues flashing V64L onto V56). Last we attempted it, a modified BIOS did not work. Powerplay tables do, though, and mean that we can modify power target to surpass V56’s artificial power limitation.
The limitation on power provisioned to the V56 core is, we believe, fully to prevent V56 from too easily outmatching V64 in performance. The card’s BIOS won’t allow greater than 300-308W down the PCIe cables natively, even though official BIOS versions for V64 cards can support 350~360W. The VRM itself easily sustains 360W, and we’ve tested it as handling 406W without a FET popping. 400W is probably pushing what’s reasonable, but to limit V56 to ~300W, when an additional 60W is fully within the capabilities of the VRM & GPU, is a means to cap V56 performance to a point of not competing with V64.
We fixed that.
AMD’s CU scaling has never been that impacting to performance – clock speed closes most gaps with AMD hardware. Even without the extra shaders of V64, we can outperform V64’s stock performance, and we’ll soon find out how we do versus V64’s overclocked performance. That’ll have to wait until after PAX, but it’s something we’re hoping to further study.
X299 VRM thermals have been a topic of interest in the lab lately, as we’ve continued to learn how to work with our new power testing tools and have fully revamped CPU thermal testing. The time will come eventually, but for now, we’ve worked with Buildzoid to run some calculations on VRM thermals with the Gigabyte X299 Gaming 9 motherboard. These numbers are based off of GN testing for this video, where we overclocked the CPU to 4.5~4.6GHz and checked for power consumption at the 8-pin headers (of which there are two).
The Gigabyte X299 Gaming 9 motherboard makes some interesting choices with its VRM components, ultimately balancing between “ridiculous overkill,” to quote Buildzoid, and merely adequacy. The board is one of the higher quality motherboards out there right now, and so is worth a watch on the PCB break-down:
Following our AMD Radeon Vega: Frontier Edition review and preceding tear-down, Buildzoid has now returned to analyze the AMD Vega: Frontier Edition PCB & VRM. This is a 12-phase design (doubled-up 6) that ultimately resembles something similar to a 290X Lightning, making it the hands-down best VRM we've seen on a reference card. Given that Vega: FE is $1000, that sort of makes sense -- but Buildzoid does pose some questions as to what's necessary and how much current is really going through the card.
When interviewing EVGA Extreme OC Engineer “Kingpin,” the term “dailies” came up – as in daily users, or “just gamers,” or generally people who don’t use LN2 to overclock their GPU. The GTX 1080 Ti Kingpin card is not a device built for “dailies,” but rather for extreme overclockers – people who are trying to break world records.
Cards like this – the Lightning would be included – do have a reason to exist. Criticism online sometimes calls such devices “pointless” for delivering the same overall out-of-box experience as nearly any other 1080 Ti, but those criticizing aren’t looking at it from the right perspective. A Kingpin, Lightning, or other XOC card is purchased to eliminate the need to perform hard mods to get a card up to speed. It’s usable out of the box as an XOC tool.
We moderate comments on a ~24~48 hour cycle. There will be some delay after submitting a comment.