What you need!
First, you will need some software to stress your system to its maximum. If you are using a multi core CPU, then you need to stress all cores at the same time. There are many applications available:
Orthas Prime 95
Prime95
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.
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. Orthas (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. For no reason, I’m going to use Orthas Prime95 for this guide.
Next up, you need to monitor the system temperatures as this imperative if you are to avoid permanent damage to your components. Again, there are a many utilities to choose from but here a few of the most popular.
Everest (trial version but worth buying for Diagnostics and collecting system information)
CoreTemp
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.
NOTE - Make sure you have the most up to date version of the software for your Operating System.
Most people like to take screen prints of the test and compare results with other users. Therefore, having the system values of the CPU and RAM on the same screen can be handy. CPU-Z is by far the most popular method of showing this information but is purely optional. Therefore, I’m not going to include this in my guide. It’s pretty straight forward if you need it.
Lastly, and most importantly, you need patients. Be prepared to leave the PC for a few hours so if you have something to do, then go and do it.
Setting up the session
Assuming you know have handy all the utilities you need it’s now time to start setting up the test session. We are going to run the stress software and system monitors concurrently so we need get the applications ready.
Firstly, you need to launch the stress test. As I’ve already stated, I’m going to be using Orthas Prime for this guide.
NOTE – Do not start the test
If you are not running quad core CPU or Orthas Prime, then you can skip this following part and go straight to Monitoring as setting the Affinity does doesn’t apply so off you go..
Setting the Affinity
If you are reading this, then you are running a quad core CPU. Lovely jubbly! Since Orthas Prime 95 will only run on two cores at a time, you will need to run two instances of Orthas to test all four cores.
You will then need to set the affinity of each instance to use only two cores each. So, for example, one instance is set to CPU #0 and CPU# 1 only and the other instance was set to CPU # 2 and CPU # 3 only.
To do this hit CTRL+ALT+DEL to bring up task manager. Then select the performance tab. Look down the list of processes and you’ll see the two instances of Orthas running. Right click on the first occurrence to bring up a selection menu and click on Set Affinity.
When the affinity screen appears, it will show all four cores ticked. For the first instance of Orthas, un-tick cores #2 and #3. This will make sure that only cores #0 and #1 will be used.
Repeat the process for the other instance of Orthas but this time un-ticking cores #0 and #1 leaving only cores #2 and #3 are being used.
You have now set the affinity for both instances of Orthas to run.
Don’t close down the task manager, as you will need this to monitor the performance.
Monitoring
You will need to see how much of CPU is being used during the test. I use the Windows performance monitor in task manager to see view the activity in legends. If you don’t already have windows task manager open, then CLT-ALT-DEL and select the performance tab. Keep this window open.
We need to check the CPU and system temperatures during the test and this is very important. I'm using Core-Temp to show real-time monitor of the temperatures.
Check that the temperatures are not too high when the system is doing nothing (idle) otherwise you may run into problems later. Look for the Tj. Max setting. Your Core temperatures at idle should be no where near a 3rd of this.
Note for Vista x64 users – You may have to run the CoreTemp start up batch file each time you start a new session. Just type "CoreTemp startup batch file" in google for download.
Lastly, if you haven’t done so already, come out of all other applications and arrange the windows so they are not overlapping.
You are now ready to start the test.
On your marks! Set! Go...
Before you do, you need to select the right test for the job.
I normally stress the CPU only first the "Gromac" CPU test on both instances for a few hours, then later test the stability with the RAM using the “Blend” but this is your choice.
Select the test from the drop down menu, and then click on “GO” on each instance.
When this starts, you will see activity on all screens.
The performance graph will show 100% activity on all four cores when using the “Gromacs” test and the temperatures will start to rise.
Watch for few minutes and keep an eye on those temperatures. After a few minutes, the temperatures should start to level out at a peak level. If they continue climbing and get anywhere near of 80% of the Tj Max setting, then stop the test. You may have a cooling problem. Sort this out before continuing.
When they do level out at a safe temperature, make note of the temperatures of each core (or core if you have one) then leave for a few hours.
When returning, providing the screen should still show green and that there are no errors, check the temperatures are roughly near what you made earlier and stop the test.
You have completed the CPU stress test. Now lets test it with the RAM using the “Blend” test.
Select "Blend" test on all instances of Orthas and select “Go” when you are ready. You’ll notice less activity on the CPU this time as both the CPU and RAM are being tested. Again, make notes and leave for a few hours..
Hopefully, you’ll return again and see all green screens. If this is the case, you have a totally stable system which will hold well. If you run into problems later, then it’s likely to anything other than the stability of your system.
Seeing Red!
If you are unfortunate to see red screens during the test or any other error if not using Orthas, then there is a problem that will need to look into. The system is not stable. The main thing here is not to panic.
If this is a new system that’s running on stock settings, make sure you have everything installed correctly.
If you are testing your overclock, then the system doesn’t like the settings you have made. It may be that the system or CPU doesn’t have enough voltage, or the system can’t cope with the overclock. Either which, you have some trouble shooting to do which is beyond the scope of this guide.
