- Joined
- Sep 17, 2014
- Messages
- 24,053 (6.14/day)
- Location
- The Washing Machine
System Name | Tiny the White Yeti |
---|---|
Processor | 7800X3D |
Motherboard | MSI MAG Mortar b650m wifi |
Cooling | CPU: Thermalright Peerless Assassin / Case: Phanteks T30-120 x3 |
Memory | 32GB Corsair Vengeance 30CL6000 |
Video Card(s) | ASRock RX7900XT Phantom Gaming |
Storage | Lexar NM790 4TB + Samsung 850 EVO 1TB + Samsung 980 1TB + Crucial BX100 250GB |
Display(s) | Gigabyte G34QWC (3440x1440) |
Case | Lian Li A3 mATX White |
Audio Device(s) | Harman Kardon AVR137 + 2.1 |
Power Supply | EVGA Supernova G2 750W |
Mouse | Steelseries Aerox 5 |
Keyboard | Lenovo Thinkpad Trackpoint II |
VR HMD | HD 420 - Green Edition ;) |
Software | W11 IoT Enterprise LTSC |
Benchmark Scores | Over 9000 |
That's basically my method. If I goto +165 on the core, I start noticing the scores going down slightly.
It worked quite well to find the top Core / Mem clocks. Saw artifacts in Kombustor at +950 mem, so that's when I dialed it back. Also, testing with 3DMark can be a complete PITA when the system crashes and you have to reboot. With Kombustor, it crashes "gracefully" ... so it's a great tool for getting close to the "zone"
Do whatever you like but I can only add to this that Valley and Heaven NEVER fail when it comes to determining the maximum core clock. Your method is just wrong.
Another big advantage is that they will never force a reboot, the worst you'll get (unless you do something really stupid I suppose like set core to +400) is a locked application, close the process, done.
But above all: Valley and Heaven are very good at showing the minute performance differences that result from your OC. I mean stability is one thing, but if your highest clocks still result in lower performance (especially memory clocks too high can do this, they can even create stutter which is punished HARD in Unigine scores) then its pointless to push those clocks, all it serves then is an e-peen screenshot or something.
I have honestly never needed Furmark/Kombustor for any GPU ever to get it stable. The only purpose it has is frying your GPU back in the day, and today it really has no purpose at all. It doesn't test stability, it doesn't test actual clocks, and it doesn't test actual temps. All you realistically test is how fast can you yank a card into the highest power state and top-end temperature allowed in its BIOS. Well yay!