Building an overclock/stability/benchmark library
- Thread starter mrapoc
- Start date
cpuz
gpuz
used to get information and check to what the settings actually are. and then varify.
orthos
rthdribl
furmark
Use orthos to stress the ram, cpu and ram+cpu
Use furmark and rthdribl to stress the graphics. i prefer furmark. less settings ;D
occt
used to keep a track of the voltages during testing if thre is something going wrong.
hwmonitor
like the above. Good if you want to stress overnight and quickly see averages min adn max
gpuz
used to get information and check to what the settings actually are. and then varify.
orthos
rthdribl
furmark
Use orthos to stress the ram, cpu and ram+cpu
Use furmark and rthdribl to stress the graphics. i prefer furmark. less settings ;D
occt
used to keep a track of the voltages during testing if thre is something going wrong.
hwmonitor
like the above. Good if you want to stress overnight and quickly see averages min adn max
LinX
HCI Memtest
Can't forget Prime95
PCMark Vantage is also a good stability test
RealTemp & CoreTemp
MemSet & CPU-Tweaker
Everest Ultimate Edition 5.02.1839
HCI Memtest
Can't forget Prime95
PCMark Vantage is also a good stability test
RealTemp & CoreTemp
MemSet & CPU-Tweaker
Everest Ultimate Edition 5.02.1839
Rastalovich
New member
Folding at home [smp]. (core interaction and general cpu)
Orthos. (thrash that cpu and memory)
3dmark. (tests the hardware and the drivers' stability)
I have created a folder that I call "IWANTTOBENCH". It sits mainly on a usb pen, and inside it are all the usual suspects mentioned above, plus all the futuremark stuff, superpi, coretemp, prime (i think), atitools, known solid drivers for various generations of card.
Generally when I rebuild a pc, I stick in the pen drive, copy over the folder, and install all the stuff in "IWANTTOBENCH", and run them. Make some changes and increases as I go, and hopefully take a bunch of screenshots along the way.
Submit them to hwbot under the guise of OC3D group ofc.
This way, not only are u contributing to the hwbot effort, but at the same time - I can safetly say that if I manage to compile all the screenshots for all the things u can submit - hey the pc has to be stable and working.
Being as they're all organized in one folder, the time to install the stuff really is minimal.
Orthos. (thrash that cpu and memory)
3dmark. (tests the hardware and the drivers' stability)
I have created a folder that I call "IWANTTOBENCH". It sits mainly on a usb pen, and inside it are all the usual suspects mentioned above, plus all the futuremark stuff, superpi, coretemp, prime (i think), atitools, known solid drivers for various generations of card.
Generally when I rebuild a pc, I stick in the pen drive, copy over the folder, and install all the stuff in "IWANTTOBENCH", and run them. Make some changes and increases as I go, and hopefully take a bunch of screenshots along the way.
Submit them to hwbot under the guise of OC3D group ofc.
This way, not only are u contributing to the hwbot effort, but at the same time - I can safetly say that if I manage to compile all the screenshots for all the things u can submit - hey the pc has to be stable and working.
Being as they're all organized in one folder, the time to install the stuff really is minimal.
