How to "Torture" test your system! * Not loo related*

It maybe that the system isn’t as stable as you first thought
I'd change the "maybe" to a "may be".
you need to monitor the system temperatures as this imperative
I think you need an "is" between this and imperative.
However, all are excellent utility
"utilities"
Lastly, and most importantly, you need patients.
"patience"
Although your test may have not even start
"not even started yet"

Apologies but just noticed a few typos on a quick scan through, other than that it seems a good guide to me. Are you going to do similar for graphics cards? E.g. with utilities like rthdribl or ATItool?
 
Some of these are not necessarily problems with what you've written, it's just how I would write the same thing if I had to do it. Take my advice or leave it. :)
Begin pedantry:
So you’ve built a new system or you have just applied some overclocking parameters in the BIOS.
So you’ve built a new system or you have just applied some overclocking parameters in your BIOS.
Let’s assume you have managed to boot into windows and have successfully run your first benchmarks.
Let’s assume that you have managed to boot into Windows and have successfully run your first benchmarks.
Benchmarks are great for checking your systems performance but stress testing is an excellent means of checking the stability of your PC.
Thoughbenchmarks are great for checking your system's performance, stress testing is an excellent means of checking the stability of your PC.
First, you will need some software to "torture" your CPU and or system to its maximum. If you are using a multi core CPU, then you need to stress all cores concurrently.
First, you will need some software to "torture" your CPU and system to its maximum. If you are using a multi-core CPU, then you need to stress all cores concurrently.
There’s little between these utilities really and it’s purely preference to which one you use. Both can be run from Windows and can test multi-core CPUs.
There’s little difference between these utilities really and it’s purely preference as to which one you should use. Both can be run from Windows and can test multi-core CPUs.
The only different is that Prime95 is easier to use for quad core CPUs, as it will create four threads to test the four cores. Orthos (for the time being) on the other hand, can only check two cores which means you will need to run two instances of the application to test all four cores.
The only difference is that Prime95 is easier to use for quad core CPUs, as it will create four threads to test all four cores. Orthos (for the time being) on the other hand, can only check two cores, which means you will need to run two instances of the application to test all four cores.
Everest (trial version but worth buying for Diagnostics and collecting system information)
CoreTemp
SpeedFan
Everest (trial version but worth buying for Diagnostics and collecting system information)
CoreTemp (Only works with Intel Core CPUs, not Pentium D and below)
SpeedFan
I’ve opted for Core-Temp because I’ve found it very reliable in the past. However, all are excellent utility and will do the same job.
I’ve opted for CoreTemp because I’ve found it very reliable in the past. However, all are excellent utilities and will do the same job.
End Pedantry

Looks like a very handy guide for novices, Huddy. Good work. :)
 
maybe mention adding "Round off checking" from the Advanced menu in Prime to avoid soft fails? otherwise, very nice work mate :).
 
Back
Top Bottom