Everything posted by TerraRaptor
-
Emil.SU's 7 min 41 sec 657 ms SuperPi - 32M run with Core i7 Extreme 980X
Much respect
-
GKVV's 1 min 11 sec 712 ms y-cruncher - Pi-2.5b run with Core i5 12600HX (4P)
nice gold
- ale belo's 27324 MIPS 7-Zip run with Phenom II X2 570 BE
- ObscureParadox's 4820.22 MHz CPU Frequency run with Pentium 4 2.0Ghz (Northwood)
- Dim0n527's 4 min 33 sec 154 ms SuperPi - 32M run with Core Ultra 9 285K (8P)
- Dim0n527's 27 sec 829 ms y-cruncher - Pi-1b run with Core i3 12100F
- lkozarov's 7 min 43 sec 921 ms SuperPi - 32M run with Core i7 930
-
Asus Maximus IX Apex and Coffee Lake Cpu's !
TerraRaptor replied to Alex@ro's post in a topic in Skylake/Kaby Lake/Coffee Lake (-X) (Z170/Z270/Z370/X299) OCWhats new?
- looze's 1671 MHz Memory Frequency run with DDR3 SDRAM
- New SuperPi 32M record by MickaShuBL
- nv1diafan's 37479 points Unigine Superposition - 1080P Xtreme run with GeForce RTX 5090
-
about HWBOT benchmark
Even if smth impacts performance, it impacts performance for all of us. So old x265 codec etc doesn't affect relative performance. We use superpi benchmark that uses ancient algorithm for 3 decades, able to somehow compare raw single thread x86 performance between cpus without SSE and latest designs. Benchmarks here are valued for their consistency, ability to compare through database that was collected for ages. Why would we change x265 to better algorithm? To put zero value on older 100000 scores that were done with slower codec?
- GKVV's 46548 marks 3DMark - Port Royal run with GeForce RTX 5090
-
Gorod's 41252 marks 3DMark - Port Royal run with GeForce RTX 5090
Good score!
-
Overclocking ASUS Rampage Extreme X48 and 16GB RAM
You will likely need to adjust these going higher frequency and tighter timings (if minimized for lowest values before). Nb volts mostly depend on ram frequency and timings, vtt volts depend on fsb (though to some extent both of these voltages may affect stability of fsb and ram).
-
Overclocking ASUS Rampage Extreme X48 and 16GB RAM
Try bumping vtt to 1.35v Check voltage values in hw monitoring page in bios - are these in line with what was actually set?
-
Overclocking ASUS Rampage Extreme X48 and 16GB RAM
Because nb is at high load. Try bumping nb voltage to 1.45v. Some boards may need to be re-pasted as nb thermal paste is likely dry af.
- GKVV's 46452 marks 3DMark - Port Royal run with GeForce RTX 5090
- Emil.SU's 13 sec 967 ms PYPrime - 2b with BenchMate run with DDR3 SDRAM
-
Overclocking ASUS Rampage Extreme X48 and 16GB RAM
Some boards struggle to do 2000 even with 2x2GB. Chipset is limiting factor. Making 4x4GB running at 1800 is already quite strong. Best memory for 4x4 should actually be rev4.13 dominators (d-die based) if you care of performance, yet 2000 is likely impossible to be rock stable
- GKVV's 25414 points Unigine Superposition - 8K Optimized run with GeForce RTX 5090
- GKVV's 25316 points Unigine Superposition - 8K Optimized run with GeForce RTX 5090
- GKVV's 62121 marks 3DMark - Fire Strike Extreme run with GeForce RTX 5090
-
HYperSLI problem
Just use original msdn image of 8.1 from 2014
-
HYperSLI problem
My guess is that hypersli uses modified hal.dll (or, probably ntoskrnl too).As Win 8.1 may need special tweaks including ACPI patches etc, hypersli may break that.