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.

Please check the readme for usage instructions
In my own experience, I used Prime95 on my Q6600 with Small FFTs, which showed that it was stable for 10 hours overnight at the current voltage. However, running Linpack with the most memory I had available (I have 64-bit XP, so I see all 4 GB of my RAM), it indicated instability. I had to raise the voltage up a couple of notches to get it fully stable. This will ensure me that it's now at least 24 hours Prime95 stable, if not 100% stable.

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.

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.

Number being too large does indicate instability as well, but when that occurs, the other Residual(norm) values will not be equal.

Originally Posted by WoZZeR999

Will this automatically report if there's an error? I remember running linpack the first time, and it was a hassle to figure out if it errored out because you had to actually look at the data.

It was a hassle because using Linpack alone did not output the results directly to the screen. With IntelBurnTest, it's one of the features.

Yes; however, you haven't run it long enough to be considered a real test. You need to have at least 8 hours to be safe. Also, why are your GFlops so low? I get 50GFlops with my Q9450, which is clocked slightly below yours.

Looks like there is finally some software available to test the PROCHOT# section in RealTemp! This info is displayed for each core. The Wolfies should show a check mark in The PROCHOT# - History box (right box) at approximately 93C. Every processor is unique but generally this is the magic number. Throttling will be so minor at first that you might not even be able to detect a drop in MHz in CPU-Z or RealTemp.

If things continue to get hotter then the Status box in RealTemp (left box) will light up along with the History box and then both programs should start to report that your multi is getting cycled down to 6.0 to help keep the temps from getting too crazy. Thermal shut down isn't until 125C so no need to worry just yet.

What the hell?!?!?!
As soon i've read this post, i've downloaded this utility, unpacked it and run a short 5 times test. Well all 5 five test reports the same number, so the system is supposed to be ok, BUT: everest lost nb & sb temp readings, the rampage's lcd poster started flashing and the 3com usb wireless dongle stopped working...
After a system restart everthing goes back normal, but what happended? It may be a beta release issue or is my system not really stable? Don't dare to run it again before someone give me some explanation...
BTW I've primed it for about 10 hours without an error.