IntelBurnTest - The new stress-testing program

[AgentGOD]

I did a default test to check temps only and they went from 40 to 55°C. Nothing dramatic, which means my cooling is good (its the ambient which is hot)

It scales higher with more voltage.

[AgentGOD]

Updated to v1.3
- Added automatic error-detection feature (choose at the beginning)
- Added elapsed time at the end
- Added updated 32-bit and 64-bit Intel(R) Linpack binaries from Intel(R)

[BeastNotro]

AgentGOD

I just tried version 1.3 with error checking on and i got a BSOD... ?

Now i no my system is stable as it Orthos Stable and Linkpack Stable v1 and v2.... i think something wrong with error checking somewhere..... when i booted back up and allowed windows vista 64-bit i have to check for A SOLUTION it state in the popup "Issue with Central Processing Unit caused windows to reboot" .. CPU basically ... so make sure your error checking program is 100% up to snuff..... test it out.... i have same CPU as you, maybe its a memory module incompatility.. so check into it ASAP.

[Loser777]

Make sure v1 and v2 were completely stable, try doing more than FIVE tests.

[BeastNotro]

Make sure v1 and v2 were completely stable, try doing more than FIVE tests.

I ran them at least 8 times on different memory Free settings to .. like 1700, 1886, 2000, 2200, 3000.... i only have 4GB total and all passed.... no issues, but as soon i ran v3 and checked off error checking ... not even 3 secs into first test ... poof BSOD .. i telling ya i thinks it the error checking part that has an issue .... maybe compatibility with certain memory modules or just has issues period....

[Loser777]

3000?
I have 4GB memory and I run 21,000.

[BeastNotro]

3000?
I have 4GB memory and I run 21,000.

3000 = 3GB when you get to choose how much Free memory is available in v1 and v2.

[Loser777]

Sorry about that, I use the Intel Release of Linpack.
----------------
Do a retest of v1 and v2... I usually run 10 tests... if it's not stable now, then it's a sign that your chip burned in or degraded.

[BeastNotro]

Here is v2 which same as v1 except he added he option of choosing Max Free, Half Free or Low Memory to run. I chose Max usually and/or half at first.

This one is MAX FREE and 10 Passes and it Passed....so like i said v3 has some issue when i put error check on (It BSOD on me in 3 secs of first test with error check on), i did not run it after that as i choose not to test without error check on ... incase its some coding issue cause of the update of error checking was added.

Anyone wanting to use v3 ... read my post here and wait for AgentGod to see whats wrong.....
http://www.xtremesystems.org/forums/...&postcount=154

[Toysoldier]

I have no problems with v1.3



If you get a BSOD when running v1.3 then something is wrong with your rig. I have run v1.3 four times now without any issues. All the other versions of IntelBurntest all ran fine too.

In my opinion it's the 450 MHz FSB that's giving you issues.

[AgentGOD]

Anyone wanting to use v3 ... read my post here and wait for AgentGod to see whats wrong.....

The biggest variable in this release is a newer version of Linpack. It's possible that the new Linpack is more accurate and stressful than the last. I mean, that explains it. It seems to work fine for everyone else that has a proven stable OC.

#EDIT:
Basically what the guy above this post said :P (Toysoldier). It works fine for him apparently.

[BeastNotro]

Fine for one does not mean fine for all.

My rig is stable ... folding for hours and hours, Orthos upto 12 hours before i shut it down, memtest86 ran it for 6 hours and both v1 and v2 linpack .... v3 is ok if i don't run error check .... I think there is an issue with the program itself only with error check enabled ..... maybe for certain memory modules and or FSB settings ... heck it can even be the Bios too for this mobo.

By the way Toysoldier is running a Maximus Formula motherboard.

[AgentGOD]

Try the version I PM'd you.

[BeastNotro]

What version is it?

if it is v3 again.. i will try .... and post about it soon.

[WoZZeR999]

1.3 worked great for me, though some sort of status bar or something to let you know how many tests have completed would be nice.

[Zigosity]

1.3 closes itself as soon as it starts the test o_O. All the others were 100% stable, and I'm really not pushing this system right now anyway.

Weird.

-Zigosity

EDIT: Oh, and I'm on 32-bit XP.

EDIT2: And if I turn off error checking, it works, but not with maximum memory selected. It tells me I don't have enough memory O_o. Guess it's not detecting my available memory right under 32-bit. Ah well.

EDIT3: Aaand I'm going to switch to 64-bit XP, enough of this foolish 32-bit Icantuseallmyram nonsense. I'll get back to you on how well it works after that's all done.

[JohnZS]

Version 1.3 made my system unstable...until I raised my VDIMM (DRAM volts) by one small notch up to 1.84 Volts. I know get the following result.

Looks stable, but notice the temps...ouch even hotter with this release.
Keep up the good work AgentGOD!
It's nice to see my quad flexing it's muscles as most applications really do not use it to it's full potential!
John

[RejZoR]

This tool is just awesome for stability testing. I usually use it like this...

Very quick stability check (excellent for fine-tuning voltages, so you don't overuse it while still be able to slightly increas it to make normals equal between loops)
128MB / 20 loops

Normal stability check (this is quick test when you think you got the sweet spot and done some basic tuning of parameters)
256MB / 10 loops

Final stability check (as the name suggests, final thorough testing when you're done)
2048MB / 5 loops

I hope this latest version still has option to manually enter desired memory size because it seems very useful if used right.

[BeastNotro]

Read Exstensively AgentGod and anyone else as v3 is harder testing:

I done a lot of hair pulling out on v3 to get system stable on it ..... as you know v1 and v2 were np's. I figured it was the coding of the error results ... i thought that was the issue for the BSOD's i got after trying v3 out.

I tried the modded version you PM me and it also BSOD, but in 9 min instead of 3 secs of the Non modded v3.

So after the modded one BSOD i knew then that the binaries in v3 is a ball breaker and tougher on system stability.

So i tried to figure out what my BSOD could mean and it was the infamous 0x00000124 error, which can happen due to video drivers or sound drivers, but it can also happen with OCing an as to what .. usually voltage some way or another and as to which one or which ones it maybe is trial and error.

So i was pulling my hair out and i figured well it has to do with calculations between memory and NB or it was a PLL issue.

Here is what i did and i used v3 initial released one for all tests and used MAX memory available = around 2900-3000 in tests out of 4GB that i have thats like 74-75% of memory being tested:

Initial PLL was at 1.54v and NB was at 1.22v ..... v1 and v2 passed np's 5-10 loops many times.

Here what i tested with:

PLL was at 1.54v
NB was at 1.22v, tried to 1.26v = BSOD in 3 min

PLL was at 1.54v, tried 1.56v
NB was at 1.22v, tried to 1.26v = NO BSOD, but only got 4 x 5 tests passed

PLL was at 1.54v, tried 1.56v
NB was at 1.22v, tried to 1.28v = NO BSOD, but Again only got 4 x 5 tests passed

PLL was at 1.54v, tried 1.58
NB was at 1.22, tried to 1.26 = NO BSOD, but only got 1 x 5 tests passed


So i was stuck and thinking what the heck is wrong here....


Now i happen to read JohnZS post about he had to up his Vdimm for v3 to pass successfully.

I got to thinking about this a lot .. like 10 mins or so and i remembered something about my modules and how others stated about these modules using to high of a voltage on OC or even the stock voltage for around 1000mhz can cause some stability issues in programs.

Well sure enough i am @ 901 mhz and the ram is 1000mhz memory and at that speed (1000mhz) the vdimm according to G.skill is 2.0-2.1v max.

Well i was using 2.0 volts in the bios (actual = 2.04v) as i figured 901mhz is close to 1000mhz and all my voltages prior to changing them 1-2 hours ago .. were/are memtest86+ stable, Orthos Blend Stable 11hrs 5min (i stopped program as it is good enough usually for me) and stable in Linpack versions 1 and 2.

Well i was like WTF maybe i damaged something:

Well low and behold i was remembering about to high volts can cause issues just as much as to low of vdimm volts can.

So i lowered the Vdimm to 1.96v in Bios and kept the NB at 1.26v and the PLL at 1.56v as those settings stopped the BSOD issue as using 1.28 NB never did anything better.

Well i loaded v3 up ... the inital release one and set it MAX and turned error detection on..... set passes to 5 loops.

I waited the 15 min and i was crossing my fingers cause if it failed again i was going to smoke all my cigarettes before payday...

And guess what ,,,,,, she passed all 5 passes and here is the pic to show it:

This program is a system ball breaker for sure.... Now i guess 1.26 NB and 1.56 PLL is safe guys?

I will test longer as i like 5-10 loops for best results and i will test a few times, tommorow and next day after as you never ... the bugger may go unstable ...

I have updated my Signature to reflect new Template with New Settings.

[AgentGOD]

PLL is fine up to 1.7v, and NB is fine up to 1.4v afaik.

Also, the test version I PM'd you used the older binaries. That's the ONLY difference.

And yeah, I think these new binaries are even more accurate. And for our purposes, that's great.

[BeastNotro]

PLL is fine up to 1.7v, and NB is fine up to 1.4v afaik.

Also, the test version I PM'd you used the older binaries. That's the ONLY difference.

And yeah, I think these new binaries are even more accurate. And for our purposes, that's great.

Weird the PM one BSOD with older binaries using v2 binaries ... as version 2 i ran how many times and posted on here 5-10 loops for the past day or so... well like a few tests each day ... all passed.... you sure thats all that was different???

In the PM one i chose Error detection too.. ?

No doubt v3 is a harsher test then previously as i noted in my big arse post above....

And at least now i pass v3 too so far so good .... woot woot

Oh and THKS so much dude for your great efforts into this and helping me out too.

[AgentGOD]

You're welcome mate.

Also, I just realized how similar our systems are, LOL!

[BeastNotro]

You're welcome mate.

Also, I just realized how similar our systems are, LOL!

Yes i noticed that we have very similar rigs, maybe you should try my settings and get that Q6600 to 3.6ghz stable.

Also the 4850 cards rock for the price, but in folding they are only using 1/4 their potential.. until a new client comes out.... i hope i see 6000 PPD per card or more instead of 1400-1500 PPD per card.

Nvidias 8800 gts and GT's get 3000-5000 PPD.

[AgentGOD]

My system didn't stop failing with Linpack at 3.6 GHz until about 1.53v on the vcore, but that caused the CPU to start throttling (two cores were hitting 95*C in Real Temp). At that point, I just decided to back down and settle with 3.5 GHz.

Also, my chip has a VID of 1.3125v, so it sucks.

[BeastNotro]

Well even a 1.3125 can do 3.6ghz, but wowzer thats a lot of volts.

Is it a B3 if so then i can see why it needs a lot more volts, if its a G0 then 1.42-1.45 is usually what most need.

What about GTL settings and the rest of the settings, check my template and try is all .. to get the vcore down and ghz up or at least vcore down at 3.5ghz.

Also 1201 Bios is awesome so far .. try it out as when i was using 803 and 704 bio's i had to use 1.35-1.38v for 3.4gz and if i wanted 3.5-3.6ghz i had to use 1.45-1.46v. and the temps rose like no other .. lol

Bios 1103 was the same as 1201, but many seem to be ocing better and more stable on 1201.

Oh and test with Linpack v3 ...