IntelBurnTest - The new stress-testing program

Great time saving program for overclockers, i like it.

Much better than all others in my opinion.:up:

Quote:

---

Originally Posted by jason str

Great time saving program for overclockers, i like it.

Much better than all others in my opinion.:up:

---

Right on Jason. I won't spend hours priming. I don't even like running an hour of OCCT. I can run this little app and within 5-10 minutes I can pretty much know if my system will be able to run WCG units without errors.

I heard from a friend at the Striker II Extreme thread that he would pass this 10 times, but while priming in less than an hour, it would fail on one core.

Hmmmm

I also heard of a few instances where people passed IBT but failed Prime.

Is there any way to turn somekind of verbosity on? It's annoying to not know what the IBT is doing and how many tests it passed. When trying to find stable clocks it would be nice to see test fail, stop the program and adjust vcore or something.

Otherwise it's a great program!! Even without knowing what the program is doing it
takes a lot of waiting off of my shoulders.

EDIT: After I wrote this post when booting back to windows (my main OS is Gentoo. There's no net in windows. It's purely for overclocking and gaming.)
there was the option to run without error detection. The option appeared to the program after I lowered my FSB enough as it wasn't there before.
Running without error detection is good way to monitor the progress, but IMHO it should verbose what it is currently doing and how many test has
been passed succesfully with the error detection on too.

Quote:

---

Originally Posted by webwilli

@AgentGOD

many thanks for IntelBurnTest.

we love it. :D

is it possible that IntelBurnTest stopps when it find an error?

we make 50 or more tests with error detection.
so, when test 25 (for example) fail, we must wait till IntelBurnTest have finished all the 50 tests.

i hope you understand what i mean.

---

I also request this.

Also, when you run it with error checking, why does it hide the information which is displayed when you run it without error checking?

It would be nice to see how long it has been running with all the info displayed and to also halt running when an error is detected.
Error checking should not be a switch but should be enabled all the time.
Stop on error should be user selectable.

Quote:

---

Originally Posted by Dee

I also heard of a few instances where people passed IBT but failed Prime.

---

All depends on how long you run IBT.

I usually run 10 loops using approx 6.6GB of RAM. (just over an hour)
It it passes, then I run 40 passes.
It that passes, I let it run 150 passes overnight.

Of course, when I am happy with the speed I want and it passes 150 loops, then I do not need to run it again :clap:

Quote:

---

Originally Posted by tombman

Hmm, try EVEREST and check your temps. I don't think air cooling can handle 4Ghz quadcores @ full linpack load. I have highend watercooling and still get 72°C on max load on ONE QX9650@4Ghz. (1.31vcore under max load, watertemo = 35°C).

So i HIGHLY doubt any air cooler can handle that kind of heat. (and you even have two cpus, which make ambient temps even higher)

This linpack test is really hardcore, so better get watercooling, or chilled watercooling.

---

Actually at 4Ghz the QX9775 is surprisingly cool and doesn't heat up that much. Compared to my old QX6700 which can reach up to 83 degrees, these processors are relatively easy to cool and I know quite a few people with Skulltrail running at 4Ghz with the same system. These same CPU's were used in a custom built vapor system and another heavily insulated motherboard and can run 4.8Ghz 24/7 with 100% load for days on end and could boot into Windows at 5.5 Ghz. But that isn't the point, the point is that it this stress test cannot run even at default speeds and voltages with cooling that can otherwise easily handle 4 Ghz. I have even underclocked it to 2.8 Ghz from 3.2 Ghz and still it crashes.

Having said that, this software is fantastic for Quadcores. I have been able to fine tune several Quadcores using this. In one case I was able to shave .5v of my old QX6700 and still be stable at 20 runs at an overclocked 3.2 Ghz. It allowed me to adjust my radiator fan where it is barely audible and still maintain 100% stability. I can now quickly tune a Quadcore with high confidence of stability. I just wish it could be compatible with Skulltrail systems.

Quote:

---

Originally Posted by Dee

I also heard of a few instances where people passed IBT but failed Prime.

---

i passed IBT then hard locked in cod4 with 2 different clocks, but i know it was my mem divider becase I changed it, it passed then stopped hard locking.

Yeah, im burn test stable for 20 passes but fail prime within 18min :shrug:.

Quote:

---

Originally Posted by AgentGOD

Readme

Code:

---

IntelBurnTest v1.6
by AgentGOD
----------------------------

Benefits of using Linpack:
3. Use the same stress-testing engine that Intel uses to test their products
  before they are packed and put on shelves for sale.

---

---

I would be *very* interested to know if it is being used with success at Intel on the BOXD5400XS.

Quote:

---

Originally Posted by spiro

... the point is that it this stress test cannot run even at default speeds and voltages with cooling that can otherwise easily handle 4 Ghz... I just wish it could be compatible with Skulltrail systems.

---

Exactly... you and me both... I'm sorry Spiro, I didn't log the specifics (i.e. IntelBurnTest version / mem amount tested / bios settings) when I did get a 5-run pass... Best I remember it was with a version where one had to enter the amount of mem to test with. And when I said "small" amount of memory, I'm guessing between 256MB and 512MB (probably using default bios settings too). I also had several runs where 2 or 3 iterations posted before blue screening (again using very little memory).

hmm run the software and got 1 error of out 20. run it again without changing anything and got 100% :(

Quote:

---

Originally Posted by jarthel

hmm run the software and got 1 error of out 20. run it again without changing anything and got 100% :(

---

All errors are random/probability based. It is just like prime/orthos giving an error in 45 minutes on first run, then not until 2-3 hours or in 20 minutes on the next with same settings.

I think 5 to 10 runs are great for quick adjustments, which is what I will use this program for primarily. And 20 runs (assuming setting 1) may prove you are within a notch or two of stability. From there, some will game/fold/etc as final test...others prime/orthos overnight...others 50+runs of this test.

In my post 206 in this thread...I tested at 1 notch vcore below stability, where orthos 10ffts and prime small ffts has failed at 8 and 10hrs. Intelburntest failed one 30 run at max and passed one. It made 2 errors in first 60 run, and 1 error in second 60 run but not until line 49, so may well pass a 60 run if ran enough times. Odds are also unlikely it would pass 2 60 runs (3 hours total) in a row and odds are it would fail the first run. But it is all probability of error over time.

Quote:

---

Originally Posted by Darkatom

Yeah, im burn test stable for 20 passes but fail prime within 18min :shrug:.

---

This is a new program...and would be nice to learn what it's capabilities are for rigs other than mine. Hence it would be nice if you guys could post comparison pics so we can see settings you use and specs of your rig....like...
http://www.xtremesystems.org/forums/...&postcount=376

Otherwise what I learned from your post is :shrug:

Quote:

---

Originally Posted by rge

Otherwise what I learned from your post is :shrug:

---

would people care if you learned nothing from their post? ;)

Quote:

---

Originally Posted by jarthel

would people care if you learned nothing from their post? ;)

---

LOL...I did not mean to come across that way...but if you are going to go through the work to compare the two programs...how hard is it to hit print screen and post so that others can learn something? I realize some are just socializing...

Quote:

---

Originally Posted by Zaskar

Depends on howmany runs you selected in the last option. Keep Everest's stability test window open to monitor CPU core temps along a graph, you will see it peak up and down for every finished test, the IntelBurnTest window wont actually show any updates till it finishes all the runs you had it do.

---

Thanks Zaskar, that clears things up a bit.

Just wanted to give a :up: for this little proggy! My chip managed to run 6 rounds correctly on the seventh it bsoded from overheating, it was running at 88°C. :shocked:

Well done! :up:

i just tested

E8400 C0 (570x7 @1.28750V)
Ballistix PC2-6400 2x1GB (1140 CL5 @2.21V real probe)
P5Q Deluxe bios v.1306

- Stress : LV. 1
- Times to run : 10
- that really will kill my cpu and ram with extreme temperature (CPU core 77'C / RAM 57'C with the RAM's fan OCZ XTC)

result 100% pass (i tested for 3 times and all got 100%)

is that mean full stable?

i don't know how to test the full stable >_<"

-------------------------------------------------------
i will post images later, now i'm on test Othos - Blend

Thank you

Quote:

---

Originally Posted by ti20n

I just asked him that in a PM :rofl:

---

Replied

Quote:

---

Originally Posted by tombman

Intel .pdfs clearly state that most quadcores should not go higher than 70°C, preferably below 65°C, not higher. Over 80°C is clearly out of spec...

---

Can anyone else confirm this warning for me? I have a Q6600 G0 stepping that I'm OC'ing to 8x425. Temps easily get in the 90's (°C) running IBT. I worry that it might be my OCZ Vendetta 2 air cooler -- I've had trouble mounting it in the past, might have to either lap it or invest in a bolt-thru-kit, or both. Read from someone else here that temps should not reach within 10°C of TJ Max, so if my TJ Max is 100°C then is 90°C okay? I certainly don't want to kill my chip. Maybe my OC is too aggressive?

Quote:

---

Originally Posted by AgentGOD

Replied

---

And for the rest of us who also asked ? :cat:

Quote:

---

Originally Posted by ti20n

He said an abort-on-error feature would require a big rehaul of the IntelBurnTest code, so we're out of luck for now. But he mentioned that if you want to see results before the end, you can turn off error-detection, and it will just show residuals one after another for you to look through manually.

---

I use this mode when trying to get IBT to run, and would like a quit test option like escape. X'ing means I lose the results

Quote:

---

Originally Posted by jolliffee

I use this mode when trying to get IBT to run, and would like a quit test option like escape. X'ing means I lose the results

---

That's exactly what I needed today. I wondered if the Esc. key worked but now I have my answer.

Quote:

---

Originally Posted by ti20n

He said an abort-on-error feature would require a big rehaul of the IntelBurnTest code, so we're out of luck for now. But he mentioned that if you want to see results before the end, you can turn off error-detection, and it will just show residuals one after another for you to look through manually.

---

Seems strange to me.

Also, I cannot understand why you cannot have error-detection on and still display running results to the screen, especially if the running results are already being written to a file which can be viewed whilst the test is till active.