IntelBurnTest - The new stress-testing program

[wongnog]

I ran v1.9 on my Q6600 (405x8) and it was stable for 25 passes at max ram, but then core 4 failed P95 within 27 mins. I'm upping vcore a bit and will test again.

[radaja]

@adya i have the same problem when selecting maximum stress level 1.not sure why it does that?

[AgentGOD]

wow it failed a max test of 10 in less than one sec ???

but ive tested on occt for almost 4 hours stable?
could it be an error? i mean in less than one sec?
damn i really thought i was stable here.

Could you show us a screenshot?

It would give us a better picture of what you're saying. Thanks.

[jcool]

Back to i7 testing...

Disabling HT on an i7 gives you 100% CPU load across all 4 cores, temps are a tad higher than with HT on I think.
Running linpack64 with 12GB of mem on xp x64 (so 11,6 usable) gives a nice problem size btw, 700 seconds per loop on a 4Ghz i7

[AgentGOD]

How's stability coming with that i7?

[jcool]

Prime is harder on it than linpack atm, but it's working amazingly well with 12GB, considering I have 6GB with Samsung and 6GB Quimonda-based ICs
Just got an average clocker here, does 3,8Ghz with stock Vcore but needs almost 1,4V to do 4Ghz, lol. It's not my private rig, just for testing purposes, so I don't mind. I'm cheering for my 965 to come

[adya]

Could you show us a screenshot?

It would give us a better picture of what you're saying. Thanks.

im not doubting its correct. im just shocked it found an error in less than a second while other progs would take hours.
maybe im using it wrong?

[radaja]

thats exactly what mine looked like. but now when i tried it seems to work fine,could it be that it was not totally stable?

[AgentGOD]

im not doubting its correct. im just shocked it found an error in less than a second while other progs would take hours.
maybe im using it wrong?

That only happens when you don't have everything in the same folder.

Let me emphasize this again: you MUST extract everything from the zip to the SAME folder while maintaining the original directory structure, or it will not work at all, and it will look like that when you try to run a test.

[adya]

thanks agent. i suspected i did something wrong there.
as soon as i finish a game on bf2 ill dl it again and reinstalling it like u say. see if works.
but bf2 comes first ,stability second , so ill do it later lol

[emoners]

Agent: whatever color it is, it's still a GREAT app!

[AgentGOD]

Thanks.

And just to let you guys know, v2.0 will most likely be a complete re-code and will have a Windows GUI instead of a command line console to improve the user-friendliness.

[adya]

i luv this little program its so quick.
now i can play with vtt and test straight away. usually for 24/7 i need 4 hours of occt or prime for even longer.
was getting fails at first on the 5th run, but after adjusting vtt and gtls from 1.45v to 1.3v ,93/90/70 i finally got 5runs stable sometimes less is more i guess.

[AgentGOD]

10 runs is even better :P

[Ledge]

Wow this thing really puts it to your CPU!!!!!!!!!!!!

It had mine pegged at 94c!

[Cyber-Mav]

have to say thankyou again to you AgentGOD, this utitlity is awsome regarless of whichever colour you use. it really hammers the cpu well and is the best stability tester iv used for cpu overclock testing todate (on 64bit setups). i just let it rip overnight for a good 12hours or so on the systems i build to check for stability. far faster at finding cpu errors than programs like prime/orthos etc. second best app iv used is SNM which seems to do a bit better on 32bit setups.

again thanks for your wonderful contribution to the overclocking community.

[HuffPCair]

Wow this thing really puts it to your CPU!!!!!!!!!!!!

It had mine pegged at 94c!

OMGGGGG is that safe lol


And yes this is the best stress test I have ever used. NOW IF I could get my RAM to work at a higher mhz

Just tested mine 10 times and 20 times and no fails so I am happy. Wish I could go farther then 3.5GHz on my Q66 but I gues I am happy for now.

[adya]

i had no idea it was green hey .. i thought it was just black and white lol i dont normally give it way but i am colourblind . green brown red its all the same lol when i read green , i had a look and thought green? wheres the fkn green ?lol

[vega22]

Some news about the Core i7 compatibility? New version release soon?

[jcool]

Yah, and also on the wishlist for next release: with error detection enabled, could you still make the program output the residual norm values? So you don't have to guess all the time how far it is along.

[jcool]

have to say thankyou again to you AgentGOD, this utitlity is awsome regarless of whichever colour you use. it really hammers the cpu well and is the best stability tester iv used for cpu overclock testing todate (on 64bit setups). i just let it rip overnight for a good 12hours or so on the systems i build to check for stability. far faster at finding cpu errors than programs like prime/orthos etc. second best app iv used is SNM which seems to do a bit better on 32bit setups.

again thanks for your wonderful contribution to the overclocking community.

I agree & use it, too.. Just don't forget a prime blend/custom inplace run afterwards, as linpack sometimes won't detect instabilities coming from the mobo (like not enough MCH).

[vega22]

I agree & use it, too.. Just don't forget a prime blend/custom inplace run afterwards, as linpack sometimes won't detect instabilities coming from the mobo (like not enough MCH).

EXACTLY...i agree. Linpack is the best for vcore and Vdimm. For vNB (and too for GTL adjusting), prime/occt.

We need two whislist: for the very dear friend AgentGod: when error detection enabled, the program output the residual norm values. For Intel: new linpack version for i7

[Newblar]

10 runs is even better :P

agentgod, dont tell me you still play sc with that comp =_=

[koltbuut]

Here is my idea to combine setfsb and ibt. Ibt outputs tmpOut and then this ahk script decides to lower fsb, and outputs tmpOut1 with Mhz/Loops.

ht2=334
tt2=60
ts0=D:\p2\IntelBurnTest\tmpOut

FileGetSize, ts1, %ts0%
Loop
{
FileGetSize, ts2, %ts0%
if (ts2>ts1)
{
Loop, read, %ts0%
to1 := A_LoopReadLine
StringRight, to3, to1, 13
Loop, read, %ts0%
{
to2 := A_LoopReadLine
StringRight, to4, to2, 13
to9+=1
if (to4=to3)
to5+=1
else
to5:=0
}

if (to5=1 and to9>20 or tt1>tt2)
{
ControlClick, X425 Y156, SetFSB
ControlClick, X316 Y177, SetFSB
if to7>1
FileAppend, %c17%`t%c31%`t%to7%`n, %ts0%1
if to7=1
FileAppend, %c17%`n, %ts0%1
ht2:=ht1
}
if (to5>1 and ht1<ht2-1)
{
ControlClick, X465 Y156, SetFSB
ControlClick, X316 Y177, SetFSB
}

FileRead, to8, %ts0%1
TrayTip,, %c17%`t%c31%`t%to5%`t%to9%`n%to8%
to7:=to5
to5:=0
to9:=0
ts1:=ts2
}

ControlGetText, s31, Static31, CPU-Z
StringLeft, c31, s31, 5
ControlGetText, s17, Static17, CPU-Z
StringLeft, c17, s17, 5
ControlGetText, s133, Static133, SetFSB
StringLeft, ht1, s133, 3
ControlGetText, s23, Static23, Core Temp
StringMid, tt1, s21, 2, 2
sleep, 2000
}

The first run, week ago crashed at 199 loops 273.1Mhz
Then my cpu degraded, because of 24 hour ibt at 1.5v, currently 270.5Mhz 190loops stable.

272.6 1.184 7
272.3
274.2 1.184 22
273.9
273.5 1.184 12
273.1
272.7 1.184 13
272.3
271.8 1
271.4

http://img218.imageshack.us/img218/1605/271190lra5.gif

[rockfella]

Damn 24 hour IBT testing? I just ran IBT for 3 loops thats it!
Guys IBT is way too stressfull..... degradation can happen...