IntelBurnTest - The new stress-testing program

[loonym]

You do realize that that isn't stable right?

No, I guess I don't know how to read the result?

I've never had any signals of any sort of instability, 0 WU errors running boinc wcg, gaming, etc. Uptimes for days on end, I guess it's good enough for me

[Peen]

No, I guess I don't know how to read the result?

I've never had any signals of any sort of instability, 0 WU errors running boinc wcg, gaming, etc. Uptimes for days on end, I guess it's good enough for me

Ya I got the same thing, I even tried running completely stock bios defaults and the numbers were different. This program def gets the CPU nice and toasty though

[HDCHOPPER]

anything but a rar

[Leeghoofd]

Glad you told Loonym to look at the scores, thought if it did its passes it would be okay lol...



My parents rig look sweet at 3.6ghz at 1.1volt..

[panheimer]

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.

[Amurtigress]

Hi,

I am using a Q9300 processor at 3.2 Ghz and was wondering why I am only getting a performance of roughly 21 GFlops as floatingpoint performance, while I should have roughly twice that much? this looks like the program was only using two CPUs instead of all fours despite detecting four threads and four CPU cores.

I am running the 64 bit version of Intelburntest, on Windows Server 2003 x64.

Any ideas?

[Bandit_44]

This is weird,I have an ASUS Striker II Formula and when i test my E8500 with Supertalent ( Super*Talent T800UX2GC4
)DDR2 800 MHz memory it tests stable 1 time then the next it doesn't! I changed to Transcend DDR2 800 and it's Perfect everytime but the ST ram has been checked and is not Defective!I'm running both in dual channel mode,yet the ST will be perfect everytime in single channel mode! Any idea's why?
BTW,Thanks AgentGOD,exellent Stability tester!























E8500@ 3.82 Ghz,Asus Striker ll Formula 0902,2 x WD 320 GB,EVGA 9800 GTX,2 GB ST RAM,SB X-FI EXTREME Music SC,PC P&C 750 Quad P/S,2 LG DVDRW’s,Zalman9700 CNPS Cooler,Antec 1200

[snipper_cr]

Holy $#%#$

That was something to see my physical memory sky rocket like that in the task manager then see all 4 cores cap out at 100%.

Previously I ran Seti@home on 4 cores and I would get around 65*C. When I ran this, within seconds I was over 70* and stopped it so it didnt trigger my auto shutoff (Yes, I know. My new heatsink should be here tomorrow!)

[mutang]

thanx for the programm.

[Luciano90]

Hi there, I was testing my Q6600 + TRUE + SlipStream 1.900RPM on a Gigabyte EP35-DS3L board. PSU is an Topower 520w, HD4850 [nothing to do with this...], and 2x2GB SuperTalent 800mhz + 2x2GB Mushkin 800mhz.

So, I had 3.6GHz @ 1.55v. It had 20h in Blend on Prime95. I've put the test with Thread's manually setted in 4, and got an error.
I started lowering frecuency, to 3.1GHz @ 1.55v, and it continued to be unstable.

Then changed to 333x9 [3GHz] @ 1.4v.
6 times, 4 threads, standard -> Error.
Standard, 6 times, Auto threads -> OK.
High, 7 times, threads Auto -> OK.
Standard 7, 4 threads -> error.
Standard, 10 times, threads Auto -> OK.

So, is it really unstable or it's just setting 4 threads the problem?

[Luciano90]

Hi there, I was testing my Q6600 + TRUE + SlipStream 1.900RPM on a Gigabyte EP35-DS3L board. PSU is an Topower 520w, HD4850 [nothing to do with this...], and 2x2GB SuperTalent 800mhz + 2x2GB Mushkin 800mhz.

So, I had 3.6GHz @ 1.55v. It had 20h in Blend on Prime95. I've put the test with Thread's manually setted in 4, and got an error.
I started lowering frecuency, to 3.1GHz @ 1.55v, and it continued to be unstable.

Then changed to 333x9 [3GHz] @ 1.4v.
6 times, 4 threads, standard -> Error.
Standard, 6 times, Auto threads -> OK.
High, 7 times, threads Auto -> OK.
Standard 7, 4 threads -> error.
Standard, 10 times, threads Auto -> OK.

So, is it really unstable or it's just setting 4 threads the problem?

Ok, yes, setting 4 threads is the real problem.
Using last setting (333x9 @ 1.4v): 20 times, very high, threads in auto: run ok.

[ilear]

Hello, nice app, thank U for that.
I've got question. I cant get pass 8 threads, first run is always ok, second always failure. I read it doesnt mean my settings are unstable right? 16 thread works fine 5 run at Very High.

Second thing,
Cant get Maximum Stress Level. When setting it and start, app is closing becouse there is no ram to run Im running it on 7

[cmay119]

I've just ran IBT for 5 Passes @ Maximum stress level. It passed, but my GFlops were only @ 40. I reran it now with just Standard Stress level, but my Gflops are all over the place:

1st pass: 32.2105
2nd pass: 48.3728
3rd pass: 36.4371
4th pass: 37.1269
5th pass: 45.2307

This was with IBT 2.51 loading 16 threads.

The results are coming in appropriately, but I'm unsure whether this is stable or not?

Specs are correct in sig.

Follow-up question, is this a good stress-test to determine RAM stability when running the Stress level on Maximum?

EDIT - Here's a screenshot:



Uploaded with ImageShack.us

EDIT 2: I forgot to note that both C1E & Intel Speed Step are disabled in the BIOS. So I don't believe any throttling is happening. My temperatures for each core (according to Realtemp) are 81-82c on the 1st core, 79-80c on the rest.

[gotendbz1]

I've just ran IBT for 5 Passes @ Maximum stress level. It passed, but my GFlops were only @ 40. I reran it now with just Standard Stress level, but my Gflops are all over the place:

1st pass: 32.2105
2nd pass: 48.3728
3rd pass: 36.4371
4th pass: 37.1269
5th pass: 45.2307

This was with IBT 2.51 loading 16 threads.

The results are coming in appropriately, but I'm unsure whether this is stable or not?

Specs are correct in sig.

Follow-up question, is this a good stress-test to determine RAM stability when running the Stress level on Maximum?

EDIT - Here's a screenshot:



Uploaded with ImageShack.us

EDIT 2: I forgot to note that both C1E & Intel Speed Step are disabled in the BIOS. So I don't believe any throttling is happening. My temperatures for each core (according to Realtemp) are 81-82c on the 1st core, 79-80c on the rest.

u only got 8 thread, why would you choose 16 for? that prolly why your results are all over the place.

[AgentGOD]

Updated to v2.54!
- Linpack binaries updated (7-20-2012) + patched for AMD CPUs
- Improved effectiveness of Xtreme Stress Mode

[WoZZeR999]

It uses Intel's Linpack math libraries. While Prime95 uses 100% of your CPU, there are still lot's of wait statements involved. The linpack libraries are designed to get the data you need as fast as possible. You could try running the tester at lower priority to see if that fixes it.

Edit: Also make sure you didn't use too much ram. Figure out how much you need based on free ram.

[panheimer]

As you suggested i've tried to run the test with less memory but the results still remain the same: test run fine, but pc gone crazy!
So i've swapped to the default settings, to see if these issues still persist.
Well, even with stock settings my system goes crazy during test: usb wireless dongle lost, everest nb & sb going crazy and then stopped reading and lcd poster starts flashing.
I'm running win Xp pro 32 bit.
Anyone else experienced strange issue like these?

BTW, i've didn't run with lower priority. i think if it runs at lower priority it doesn't use 100% cpu so the test will be useless, am i wrong?

[Warboy]

As you suggested i've tried to run the test with less memory but the results still remain the same: test run fine, but pc gone crazy!
So i've swapped to the default settings, to see if these issues still persist.
Well, even with stock settings my system goes crazy during test: usb wireless dongle lost, everest nb & sb going crazy and then stopped reading and lcd poster starts flashing.
I'm running win Xp pro 32 bit.
Anyone else experienced strange issue like these?

BTW, i've didn't run with lower priority. i think if it runs at lower priority it doesn't use 100% cpu so the test will be useless, am i wrong?

Your NB/RAM needs more volts or your powresupply can not keep up with the demand.

[WoZZeR999]

It will still use 100% of the cpu, but if there is a function call to anything else in the system then windows will run it first.

[WoZZeR999]

Yeah, it's a better stability tool for servers where you need 100% data integrity.

[loonym]

So it should look like this? Same settings on my pc, I just selected less ram... meh close enough

[Loser777]

So it should look like this? Same settings on my pc, I just selected less ram... meh close enough

It should be the max amount of RAM you can use... if you set it lower, it won't give accurate results... it's like running Small FFTs on Prime vs Blend.

Not testing everything...

I also don't like running just five tests, I usually run ten... sometimes my system will just BSOD after 6 tests if it's not stable. (even though the first 6 tests were all error-free)

[Zigosity]

Just tried this, system passed (woot!), but holy crap, it got HOT!

Realtemp reports the maximum temperature at 74*C. That's over 10 degrees hotter than Prime95 gets at these voltages... Yeesh. But if it does beat out prime 95 for showing stability issues, and only takes 8 or so minutes to complete, wow, I'm all for it. Really neat little program!

-Zigosity

[Peen]

Mine was hitting 105c and throttling back, I need a new cooler this Coolermaster sphere is worse then a stock one! Contact is good on CPU and everything + good case airflow

[mikeyakame]

Residual needs to be a value of less than e^-09 ie e^-10, e^-11, etc, and Residual Normalised value should be roughly between e^-02 to e^-04. Ie 0.01 to 0.0001. Outside these ranges indicates memory or cpu errors.