First of all, I have to give all lovers of the well-groomed sensation a little damper – there is a lot going on and the air up is also plentiful – but you run, if you are honest with yourself and your card, then into a wall that only with much more Effort to scratch something, but not really to smash it. Nevertheless, today's reading is worthwhile, because it also shows the possibilities and limitations in one.
Recognition number one: you don't need extreme manipulations with the power-play tables (PPT), a more moderate PPT and a maximum limit of 60 to 70 are enough. And you have to play very cleverly with the beat and the tension if you want to achieve really stable and good results. The cards scatter extremely and mine was quite well subvolted, but in the other direction she likes less. That was the (somewhat bitter) realization number two.
And so you end up with knowledge number three, which tells me that good cooling is the be-all and end-all and that the infinite story with amD's power supply seems to be open to the outside world, but internally in the firmware at Power Tune a small one , but has installed very effective Klaus-Kevin-Trap, because that a slightly raised voltage despite supposedly open limits causes a clock drop, was also somewhat new to me until then. At least in this intensity.
By the way, the 3DMark FireStrike uses a Core i9-7980XE with 4.8 GHz clock, the Aorus X299 Master from the last motherboard review, a whopping 32 GB Patriot 4 Viper with DDR4 4000 on all four modules, as well as the obligatory chiller from Alphacool and of course the one with the EKWB Vector delighted Radeon VII. The rest consists of en masse hose, 10 liters of water and Alphacool quick caps. After all, it is not more practical.
On the other hand, I benchmark the games on my usual test system with a Core i7-8700K, which I adapted at the speed of my US colleague's system to stay comparable in the results and to ensure the exchange of data. But FireStrike-Punke can only be collected with fat hardware, since the mouse does not bite a thread.
The "I-have-the-longest-time-variant" and the bitter truth behind it
You get, at least for the aquarium, quite continuous "stable" through the 3DMark FireStrike, if you aim at the 2120 MHz. With the setting from the graphic below, I also manage a run with 2118 MHz – with hangings and strangles, but at least with every second or third attempt. Yes, you can specify with this and if you also "cheat" something, then there are already 33,300++ graphic points in it, which could imply, the map also ran stable with 150 MHz+.
But since you can't play with such settings, nor can you use them in any way for something else, I just leave that. For the very brave, I also have the settings for the 2118 MHz here, but as i have already written: I am not suitable as the exhibition manager for the Gallery of Vanities. How to outwit the 3DMark, of course, I don't write for understandable reasons, but you need a second monitor and a secure hand. The HMB2 runs at a whopping 1300 MHz, but the system frees in all games at some point, just not in the short FireStrike run.
If you leave it at this voltage and push the clock controller to 2150 MHz, then you can at least pull such exotic screenshots as this one from the menu of Witcher 3, where the voltage converters at over 2700 FPS and a power consumption for the entire map of approx. 400 watts, like loud hyperventilating cicadas screaming. You can give yourself exactly one thing, but of course this action does not really bring any added value. Am I the greatest now? Probably not.
But in order to be able to operate all other games and applications in a really stable way, you really have to go different and less spectacular ways. And that's where we get back to the bottom of the facts, which is still a decent lifting platform.
Stable setting for 2050 to 2064 MHz
There's something going on, after all. But since each card is a kind of unique and you never know whether you have caught a Golden Sample or a potato chip, you always have to test it very elaborately and test yourself to the "Wall". My rather mediocre card manages all this stable over all applications with these settings and final 1250 MHz clock on the HBM2 (Timings Auto):
This means that the 2050 to 2064 MHz are stable under real full load, depending on the application. In simpler games, the average value over the entire runtime was 2062 MHz, although there were even peaks up to over 2100 MHz. But these are short-term values and not averages, even if some You-Tubbie like to sell it differently. After all, I came up with more than 31,300 graphic points in the FireStrike and if you want to see it in detail, click here: https://www.3dmark.com/fs/18750492
Kevin-Klaus Käppi and a very serious video
I thought that if I work on the weekends and also have fun with our friends in the Tube, I could take some of the usual video protagonists a little bit. That's why I shot my very serious video with some costumes, because it has to come across a little bit stylish. You also need a good skill amplifier and matching clothes. Then the records sizzle all by themselves. Yes., isso 😉
And for the attention-grabgers among you who see small speed cameras in the FireStrike – it's exactly what I described above with YouTube-stable, which I referred to as the 2118 MHz profile. Flashing twice (despite successful run) means simply not uploading it, even if you only end up in 19th or 25th place. That dictates one at the end of decency. Nevertheless, you should watch the video in a quiet minute to understand my "suffering".
For the time after that, of course, I have all the benchmarks again in detail with individual graphics, Frame Times and variances on the next four pages. So as it should be. And I continue to wander between the worlds and now fight with text, image and additionally also the sound and my face. Don't go any different, because you have to fight for ranges every day and it's fun from time to time. In the end, you are even happy about every subscription twice. 😀
Kommentieren