If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. Registration is $1 to post on this forum. To start viewing messages,
select the forum that you want to visit from the selection below.

I will say I like this tool allot, but the output reading could have been easier. It took me to look at the actual numbers from Loonym to see what was the diffrence with a stable results ( numbers stay equal ).

Well I was a big fan of linpack initially, but went back to prime simply because linpack will run on my Q6600 even when prime fails.
It's much like Furmark vs. ATITool with GFX cards, FUR heats the card up all right but ATITool is the one to detect the errors.

It would be nice if there was option that would automatically dedicate all available memory to the program to test. Right now users have to find out on their own how much they can use. Two options would be ideal. Minimal possible for maximal CPU stress and maximal possible for maximal overal system stress.

Good Tool Mr AgentGod,
Just a quick question, what is deemed a "safe" (or thereabouts) maximum temperature for 45nm Yorkfield CPU?'s
IntelBurnTest got one of my cores up to a scorching 67C
All numbers were the same at the end though.
Just worried seeing such a high temperature on Core2. Cores 1 3 and 4 reached 63C (which is still hot!!)
John

Ive had times where stability is rock solid during the day (12 hour passes starting at 6 am-6pm.
And then Ive had other times when i start at 6pm till 6 am (showing that Temp doesnt spike because of night..) And itll cause errors,

But Can we get like a post stating a good way to use this program, I see that we should be doing one with barely any memory and one with all the memory.

BSODS are a bad sign and Abnormal residual numbers mean unstable data but is ok to have a couple scrambled numbers...??

@JohnZS
As long as temps are below 70°C you really don't have to worry... Also note that actual games and programs never heat up the CPU as much so worry even less.
You can check that with some graph monitoring tool or by RealTemp's Max Temp values. Just reset them before playing some game or using intensive app.

Hm, is it normal for this test to take longer than on lower clocked CPU ? With 3,3GHz it took 120 seconds for each loop. With 3,5GHz it takes 155 seconds for each. End results were consistent between all 5 loops. Is this normal? Oh, i used 2048MB of memory for each run.

Hm, is it normal for this test to take longer than on lower clocked CPU ? With 3,3GHz it took 120 seconds for each loop. With 3,5GHz it takes 155 seconds for each. End results were consistent between all 5 loops. Is this normal? Oh, i used 2048MB of memory for each run.

With all other values the same more cpu speed should give a faster run

Here are my results first at 3.2 then 4ghz with the quad : so 400FSB X 8 , then 10X... ram and co at 1066Mhz 5-5-5-5, 2048MB tested on WinXP64 Pro

Last edited by Leeghoofd; 08-11-2008 at 02:16 AM.

Question : Why do some overclockers switch into d*ckmode when money is involved

The data is easy to look at, because you can scroll through it extremely fast, and if any line is different, you will notice very easily because it sticks out like a sore thumb. But still, it would be nice to have it report if there is an error.

Also, I believe that even if they all are the same, but the number is simply too large, then that also means it's not stable. I'm not sure what the cutoff for stable vs not stable is though.

I still dont get how you see if the test failed. Can someone post an example screenshot of succeed/fail, highlighting the error line?
I have never used linpak...

Well, i've got another rampage and a q6600 on my 2nd rig, so i tried this tool to see if it gives me strange behaviour too. So i've run a 10 cycle test and it runs very smooth without an issue!
Now i'm sure it's not a software fault, but something in my first rig that doesn't work. But the fact that even with stock settings i've got this strange behaviour worries me a bit...don't want to rma this board!
I'll track down every component of this rig to search for the guilty one...any suggestion?