Printable View
May I know if the figure(s) in the "Results" column matter when it comes to stability? i.e. I'm able to complete 25runs of IBT using different OC settings, but sometimes I get 2.something instead of the more "common" 3.something in the results column. Does that make a difference?
Also, since I can complete IBT on a few different set of OC settings, I should use the one that takes the shortest time per run & give the highest Gflops right?
Updated to v2.51
- Linpack binaries updated + patched for AMD CPUs
- Official support for Six-Core CPUs and Sandy Bridge Architecture
- Added new algorithm to detect calculation errors faster
- Fixed a bug that caused blank results to be valid
Hopefully this update helps address issues and concerns raised by you guys. Haven't had time to maintain the program until now. I appreciate the support and encouragement that you guys have given me :)
Looking great! Thanks for all your great work, about everything you do is amazing! :)Quote:
Originally Posted by AgentGOD
+1 :up: - who want's to run 24hrs of Prime95 when you can run IBT for 5 or 10 passes and have the same confidence in your overclock!Quote:
Originally Posted by AgentGOD
Cheers and keep up the good work!
Great job buddy. Can't wait to try this out on Sandy when it gets here Wednesday.Quote:
Originally Posted by AgentGOD
I can tell you 24 hours of Prime95 does NOT equal 10 runs of linpack, I don't know where that came from. Its more like 24 hours of Prime95 (blend using all memory customly) is more equal to 10 hours of linpack all memory regardless of max RAM.Quote:
Originally Posted by cbjaust
Threads on auto is still broken for i7 920 and probably all other 4 core HT CPUs, all threads jump around 40%~60% use I still have to manually set it to 8 threads, as well xtreme stress mode near instantly freezes the system overclocked, stock, underclocked, every system its been tried on. Other than that its fine I'm starting to use it more over LinX it has slightly higher GFlops with slightly less time.
The "Auto" mode goes by what Intel's Linpack decides to do. From what you describe, it sounds like it's defaulting to loading up threads only up to the number of physical cores.Quote:
Originally Posted by GigaByte
It's not frozen. It may appear that way because Linpack is given the highest priority in Xtreme Stress Mode.Quote:
Originally Posted by GigaByte
Well, thank you.Quote:
Originally Posted by GigaByte
So is it 8 threads or 16 threads for core i7 2600K now?
4 cores, 8 threads ;)
Thx I cant seem to hit a 5ghz OC without crazy voltage, my max seem to be 4.8 before I hit the wall. Not even stable at 1.52v in bios for 5ghz on maximus iv extreme mobo w/1303 bios.
4.8 is stable at 1.42
I'm having a bizzare problem that seems to have started out of the blue. As of a week ago I could run any varrient of linpack ( old or newer supporting avx intructions ) at max memory. Now when I try the executable instantly crashes (ie linpack_xeon64.exe or linpack64.exe) I can set any value at or below 4gb without issue and can run hundreds of passes without error.
The bizzare thing is this is occuring at stock cpu / memory clocks, overclocked and even underclocked. I've tried switching the dimms, made sure the pins were clean / dust free , no cigar. I've ran memtest on them for multiple passes no issue. And now the strange part, I can run 2 different varrients of linpack through different gui with 4 threads each and affinity set by exe ( 1 in ibt and another in linx ) with memory set close to 90% between the 2 ( 3072 per instance ) and no problem at all. Everything I've tried indicates a software issue when attempting to address more than 4gb to a single executable and for the life of me I can't figure out what it could be.
Heres an example of what I did :
http://img813.imageshack.us/img813/7...x3072mb.th.jpg
And here is IBT with just 1024MB problem size :
http://img718.imageshack.us/img718/9...x1024mb.th.jpg
I've ran 1024 300 passes no problem and 4096 a good 50 passes. Before this issue surfaced I had been able to run roughly 7000 for 40 passes.
If anyone has any suggestions as to what might be causing this I'm all ears. I'm still fairly confident it isn't a hardware problem based on my findings however so any software suggestions are welcomed.
EDIT: There appears to be an exact amount where things crash. With the linx binaries I can't set a problem size any larger than 4111MB and with the BurnTest binaries I can't set a size larger than 4295. In both cases 1MB more results in an instant crash. Looking at memory usage in the task manager they were both addressing around 4230MB to 4230MB with a very similar commit charge at the time (5505-5510) I ran mem test another 5 full passes for comformation and no errors... This crap is werid.
EDIT2 : I cross referenced the application exception codes and no suprise they match...
Intel burn test (linpack64.exe) – EC c0000005 – EO 000000000032bf0a
Ychruncher (x64 ACX) – EC c0000005 – EO 0000000000001f80
LinX (linpack_xeon64.exe) – EC c0000005 – EO 0000000000002da1
I then figured why not try these in safe mode ( had it in my head that wouldn't work - suffered a medication reaction and was in the hospital over the weekend so still not all here cognitively ) and to my surprise they all worked fine addressing the full amount of memory. Now I'm down to trying to figure out what driver / application is at fault. The only thing I recall changing is going from the forware 268.55 to the 270.61s ( again ) Who knows... I'll add more when I find the culprit.
SOLUTION : Found the culprit... Comodo Firewall. It recieved an update recently which fits my timeline for being able to run said applications trouble free beforehand. Trying to figure out if I can work around it or if it must be a software fix on their end. I'm also running Comodo on my file server so I will be sure to test this out on it as well *** Tested on other machine and comfirmed, Comodo is causing applications wanting to address more than 4gb to crash. Uninstalling Comodo solves the issue, still playing around with things to see if a work around is possible.
Glad you figured out what was causing Linpack to fail ;)
Mine's reporting wrong memory? Less than installed and wont run. 2GB installed, reports around 500MB but varies a little. I5 2500K and P8P67 Pro...
It's reporting free memory amount. ;)Quote:
Originally Posted by peterpiper
Thx zalbard. Forgot I posted here!
Thanks for this awesome app.
I just used it to check stability on my new AMD chip. Hopefully this means that my system will now be F@H 24/7 stable. Keep up the great work! :up:
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:
http://img651.imageshack.us/img651/2905/unledupa.th.jpg
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.
Updated to v2.52
- Linpack binaries updated (7-29) + patched for AMD CPUs
- Branding update for Xtreme Gaming Studio
Awesome! thank you AgentGOD! IBT is the best to keep my machine 100% stable! Q9650 @ 4ghz here!Quote:
Originally Posted by AgentGOD
How much memory should be used for the test and how many loops?
Quote:
Originally Posted by shimmishim
from the OP/1st post, you got to scroll down and it will say....
2. Use the most available RAM possible (IntelBurnTest can now do this on
its own automatically). The more memory it uses, the more accurate.
However, most people can use "Standard" mode as it should be sufficient.
3. Select the run # (should use at least 5 at minimum, no more than 20).
I have a Llano mobile chip.
This cpu allows me to change cpu multiplier, while everything else remains stock.
I want to use IBT to test cpu only, minimal ram.
If I set custom to 128 MB, and let it run for several hours, will that give me a good cpu-only test ?
I did a short run of 20 times, and it did peg the cpu at 100% load, so running for a few hours should be good ?
Thanks. I didn't make it quite that far down. :)
Quote:
Originally Posted by Gomnadz
lol, done that before....... :D
Quote:
Originally Posted by shimmishim
u only got 8 thread, why would you choose 16 for? that prolly why your results are all over the place.Quote:
Originally Posted by cmay119
Updated to v2.53!
- Linpack binaries updated (12-18) + patched for AMD CPUs
- Added "All" threads option to allow full utilization of SMT threads (e.g. HyperThreading units)
- Default times to run is now set to 10
Note: for Core i7 CPU owners, since v2.53, use the "All" threads option to fully utilize HyperThreading units.
Quote:
Originally Posted by AgentGOD
Excellent. Thank you!
My two cents but I would NOT use this or anything like it for testing.
These apps are designed to kill chips not test them in any real world way.
Again, I know most here will disagree but this is how I feel and I'm not alone on this.
Test with the apps that you will use.
Movieman: i mentioned this I think it was 4 years ago (?), when the Linpack thread created all the rage here, and I got rediculously flamed for it. Gamers should game, folders/crunchers should use prime, etc. Linpack's target audience are chip relibility testing, to test and bin silicon. Definitely NOT to run overclocked, overvolted chips for hours on end with Linpack.
I mean, movieman, it's gotten a bit absurd now what people are doing here. When Linpack/IBT first came out, everyone agreed that 5 runs was enough. Then when people wanted to find any little itty ounce of instability, it became 10 runs. Now people are running these CPU killing tools *OVERNIGHT*.
Stress testing is all about making sure your hardware will work long term, reliabilty, at *STOCK* settings, and weeding out defects. That's the entire point of stress testing. Once you start throwing overvolting and overclocking into the mix, you're already running out of specification, so you can't be surprised if your CPU's wind up degrading from it (funny how so many people claimed it was a myth, but now, there are many reports from people that had to raise their once stable voltages, even in the 2600k batch thread, and the other thread on degradation, which seems to have died). As well as on other forums.
I have no problems using these Apps but some idiots started to spread Chinese whispers that you need to run 100loops or XX hours which is totally stupidity!
I run the default 5 loops and would run say 15 at most ?(takes longer the more RAM you have if you set to use all it all!
The only software I know of that could kill hardware was that certain build of FurMark until Nvidia limited it in drivers (you could override that though) and I am sure the newer builds are a bit gentler!
I have stopped using it and use Heaven instead!
I just run 10 loops max memory
Thanks for the update.
That's 10 too many!:DQuote:
Originally Posted by Rattle
My personal feeling is if you want to do stability tests then upclock your machine 200-300mhz above what you will run it at and then test your apps
at that speed. If issues you'll find out and if not your fairly sure to be fine at your normal speeds and you don't risk killing your chips.
I highly doubt the peep who kindly makes this App (freely) wants you to be scaremongering (more than once) in his thread.
I also doubt anyone here cares what you say and will do their own thing.
Your probably scared to run it as your OC (if you do OC) is not stable. ;)
1)The "peep" as you describe them are the ones who explained exactly what the purpose of this app was and they cringed when I told them how it was being used on XS and elsewhere. Yes, I got my info from the Intel engineers who designed this app.Quote:
Originally Posted by humeyboy
2) Now that is up to the individual. I'm just expressing my feelings.
3)Now thats where your wrong. I do OC on everything I own and mine are stable and not just for a few seconds or minutes but for years at 100% load 24/7
The defense rests.:D
Stable in your opinion and running PI no doubt? LOL!
I know who made it but AFAIK AgentGOD has worked on it for us (I could be wrong) and I highly doubt you have inside info at Intel but many claim such things!
Do not even see the point in you posting in this thread if you dislike this App TBH!
1) No, not PI my friend..I do DC apps where the machines run 100% load 24/7/365.25Quote:
Originally Posted by humeyboy
2) HMM, how to answer this...Ok, don't take my word for it.
Ask around. I know a few people and one more point: I don't lie,ever.
3) Posted to say to people that running IBT is a mistake that can have very expensive consequences.
I have to agree with Dave on this one. IBT can do some real damage to your CPU and if they are overclocked high running this for more then one pass of the long run it truely not needed.Quote:
Originally Posted by Movieman
Run the Crunching app like Dave has said and if passes after a day you can't ask for more really.
I run many different stress tests on my rigs before I send them out. Some check out memory issues very well, other stress the caches and others this and that. I can run some Mathlab scripts that will not pass but IBT will. IBT can and will kill CPU's if run long enough, if not degrade the heck out of them for no good reason. Crap run Prime95 for a little bit and if that passes what more do you want.
The program was created to save time on CPU stability testing while at the same time being more accurate in doing so than the traditional ways (e.g. Prime95).
It was not meant to be run for an absurd number of loops (e.g. 20+, 50+, 100+) as some people here (and elsewhere) are doing.
Correct and if idiots (2nd time I have said this) start telling peeps they need to run 100 loops etc then that is when issues can arise!
On the other side of the coin scaremongers are not really bringing anything to this thread and if not happy with this App should ignore thread!
I have not heard of anyone killing a modern CPU with it esp when the CPU will throttle and PC will no doubt BSOD/Restart!
Nothing worst than running Prime for many hours trying to reach a target of XX hours and you get up next morning and its crashed, at least if you run a few loops of this 1st it takes far less time and you know it stands a better chance of passing Prime and not wasting your time before you adjust settings to try Prime once again!
AG is there any truth that SB does not ideally like LinPack/LinX or has that been changed by updates as AFAIK this App is based opn LinPack/LinX correct?
Both IntelBurnTest and LinX are using Intel Linpack.Quote:
Originally Posted by humeyboy
I don't know anything about Sandy Bridge architecture not "liking" a particular program.
Just Chinese Whispers I have read on various sites, no biggy!
I guess that it's become fashionable to call people names when you disagree with their perspecive but be that as it may I repeat that IBT was not designed
to be any sort of stability test but rather to root out any weak chips by putting such a heavy load on them that any potentiak weakness would cause failure.
You folks decide for yourself whether you want to risk expensive chips by running this app.
No I've had my 3 cents of imput and will leave this thread.
Best of luck to you all and a safe and Happy holiday.
Think this threads resident Troll needs to take his meds as I do not see anyone calling him names! :confused:
I was referring to YOUR use of the word "scaremonger" and I'll say this politely but if you call me a troll one more time you can kiss your account here goodbye.Quote:
Originally Posted by humeyboy
Now I've been very patient with your sarcasm so be a smart guy and don't push this.
lol yeah really movieman, stop being such a troll LMAO
lol you guys are taking this way too seriously :p:
Be quiet Dino or I'll have you put down under down under!:rofl:Quote:
Originally Posted by dinos22
I really wasn't.. Just sharing my perspective based on what I know BUT I don't appreciate being called a troll.Quote:
Originally Posted by dinos22
i seriously don't think i can be any more down under (unless i go to Tasmania -errrrrrrrr) :p:
meh anyone that calls movieman a troll is a bit "loco"
Well, you could be "under the down under"Quote:
Originally Posted by dinos22
Out here they find them buried outside Las Vegas but damn, you guys got the whole of the outback to "lose" someone in!:rofl:
IBT tests like prime 95 without the IMC stress. It's why so many ram guys love to use it for reviews and call it stable......
If it's not blend 3 hours plus it aint stable.......IMC wise ;)
Of course running any of this crap is harmful to your system especially when running the edge of safe voltages.
Also I agree that crunching can pick up :banana::banana::banana::banana: that not even stress tests can, I ran a boinc system way back in the day for dave on phase 24/7. It required more fiddling around to keep it running and error free 24/7 balls to the walls than any normal rig I have run daily.....
Side note, I know how you love car comparisons.
Buddy rips his cylinder head off, oilpan and connecting rods, and removes pistons. Hones out cylinders in car, installs new parts and cleans and reassembles it the best he can in a car.....10K later he tosses a main bearing.
Moral of story. There is no true substitute for time.
Had he built his engine properly like mine he could rev his 2.0 single overhead hampster to 9500 rpms like me and still be driving and dragging it 20K miles later.
Back to hibernation for me, see ya in a few years or so.
:rolleyes: Your're killing me MM. This was my go to app for stability testing. :( I've never gone past 20 passes. Temps always monitored and less than 75C 1366 and 1155. 10-15 passes usually prove WCG stable. Will that really kill a chip???? :confused:Quote:
Originally Posted by Movieman
My belief based on what I know is that IBT slowly degrades the chips and as such is a mistake to use it.Quote:
Originally Posted by WFO
You mention WCG. When I set a machine to run WCG I look for that sweet spot between high voltage and high overclock.
When I set up the SR2 last year with the X5680's I could run 24/7 100% load at 1.35V with temps in the low 60's.
Now I could also run that system with 1.4V at 4400 and still within what I consider safe temp margins( 65C max)
but the increased elec draw for work done wasn't worth it.
For testing I did push that machine to 4600 with 1.4v using WCG and it was stable with temps right at 65C
This was with TRUE's and 113cfm Delta's
Bottom line is test with the apps your going to run every day as each has different factors.
Noted. Thanks for the quick reply! :up:Quote:
Originally Posted by Movieman
You do not threaten my account TROLL (I did state this thread only)!Quote:
Originally Posted by Movieman
Advise you shut your mouth!
My advise to AG/OP, report him for derailing your thread which is about your kind FREE work!
Not really, he was not called any names when he still came in spouting more BS and crying saying he had been called names, so his amount of posts derailing this thread is TROLLING!Quote:
Originally Posted by dinos22
Post count or any donations given in past do not change that fact and also I knew his previous post was not his last for the holidays as he just cannot help himself!
And running your CPU at stock also slowly degrades it, running overclocked also degrades it a big faster but still still last you more years then you will want to use it by times its old tech unless your stupid and put very high VCore/PLL through it added to not cooling it well!Quote:
Originally Posted by WFO
Oh-oh, I know the difference between mud and crappola. Jeesh, at least you can't say you've not been warned.Quote:
You do not threaten my account TROLL (I did state this thread only)!
Advise you shut your mouth!
My advise to AG/OP, report him for derailing your thread which is about your kind FREE work!
Anyway, back on-topic: As someone here has mentioned, under normal operation, you have slow degradation of your CPU, as it is subject to electron-migration. If you start increasing the Vcore, you accelerate this condition in a CPU. Now, with pretty high Vcores, as well as subjecting the CPU to stability-testing, by using IBT, as an example, you may accelerate electron-migration to such a point that instead of having a CPU last 20 years+ under normal conditions, you can shorten this to mere months.
We have seen enough of the 'sudden-death' cases to realise this is a real concern.
So, humeyboy, show a bit of respect to guys like Dave (Movieman), who has been around the block more times than quite many of us here, and heed his advice, as it's good advice. Behaving like a spoilt brat is not conducive to good relations, and you can pretty quickly find yourself out in the cold.
Let's keep it civil.
ps: Dave, you can sent Dinos to Antarctica - I think the Aussies are laying claim to a 3rd territory Down Way South :rofl:
You were warned but I sort of knew you'd be back and use the word so realistically you've banned yourself.Quote:
Originally Posted by humeyboy
I've seen this before. It's what I call the marytr syndrone.
When warned the person feels compelled to push the matter even though they've been told they will be banned if they do so.
Done
My apologies to the rest here.
I repeat, my only purpose in posting in this thread was concern for the members investment in their hardware and my comments were based on good info from
two different engineers at Intel.
I'm grateful for that, movieman.
I still remember when Linpack binaries first appeared, and I think they appeared during the beginning core 2 days, and there was a note saying that these binaries were used for *internal* CPU testing. But someone or something requested that they release them, and then came the "new stress tool released: now find if your cpu is truly stable! more accurate than prime" etc...
While I do understand Agentgod's point that this was used to be a time saving mechanism, I also fully understand the other person's post in that he said "there is no substitute for time."
I guess a question I can ask Movieman AND AgentGod is:
What is more harmful to a 1.45v 5 ghz CPU?
5 passes of Linpack/LinX/IBT, or 8 hours of prime 95?
Which will cause more degradation?
The problem of course is, even prime 95 can degrade cpu's if they are running highly out of specification. I've already degraded two 2600k's with prime, and neither one of them even saw a linpack run, except a quick 5 loop test at 4 ghz stock voltages, which was safe, and that was a gflop test. I'm lucky that I can still do 5 ghz at 1.45v. And since I'm a gamer, after all, I think some good old Black Ops and Battlefield 3 works better for me than burning my CPU up with hours of prime.
Of course, for folders, who crunch data that needs to be accurate, prime can be a good test, but I STILL remember a post on the [H], where a person who folded 24/7 at 5 ghz 1.5v, had to reduce his overclock to 4.6 ghz after 3 months, due to degradation.
Degradation has happened to enough people now, so that no one questions whether it's "real" or not (unlike that famous GNDS thread, where many of us were called incompetent overclockers, until the problem became so widespread, no one could deny it anymore).
I guess this is all old hat now. The BIG question is how Ivy Bridge will overclock, and how well the 22nm process tolerates voltages over long term. And of course, no one will know without guinea pigs to test their processors....
That would IMO depend on the amount of current the application draws and how much the degradation is accelerated not only with overcurrent but time. Should be interesting to see how prime95 performs when fully optimized for AVX. BTW AFAIK Linpack is just a benchmark to measure throughput of floating point computation whilst giving an indication of instability and not as a bining tool.Quote:
Originally Posted by Falkentyne
While increased voltage will produce more current not many people seem to be interested in how much that current is but just interested in vcore. I would think overvoltage (a voltage that causes a junction to breakdown) will kill a cpu instantly while overcurrent would be more subtle by degrading and once degradation starts will only get worse with continually excessive load before finally failing.
So maybe the real question is how much current is too much, how far past maximum can you push and still have a decent life expectancy. Temperatures are likely to affect results too.
Movieman is beyond hilarious.... so im not even going to bother with my explanation, some peoples' "beliefs" are just.... ...
True and Valid?
I fully agree with everything Movieman says. If you don't agree with him, then go blow up some chips on your own with your 8 hour linpacks. We don't need to hear about it. Seriously.
You know, insulting a mod of a forum is not the best way to keep membership here....
I think that guy didint realize who Movieman was and that's why he went over his head... :)
Anyways, recently i started using this program, regardless of the dangers and i have also upgraded my RAM to 8gb from 4gb. Just by using more RAM i have noticed that my stable overclock from before wasnt stable when i used 6.5Gb ram with IBT. Now i am down by about 30mhz in order to stabilize 7 runs at 6.5GB ram (110Gflops/run). Also i found that if i stabalize my CPU with Prime 95, IBT would instantly blue screen with 101 error. IMO 5 runs per session of IBT in the course of 3-4 days(5 runs per day) is a better testing strategy for stability. This way you dont put a massive stress on your CPU at once, but rather spread it in a few days. Furthermore, the hardware would not "cook/degrage" as much and it would give you some idea of your stability. Same thing with Prime 95, it is better off to test for 1 week (30 minutes a day) rather than a 24 hour run that would damage your expensive CPU. If there is some sort of instability of the CPU it might not show up in the first day but it would eventually show up later on. ;)
my 2cents
Dave you sorta promised the community to put Dino down ! Just do it !Quote:
Originally Posted by Movieman
Maybe AG can make a normal version with loops selection to eg max 20 and an Extreme one clearly stating the risks of frying CPU, motherboards plus an inbuild-no-nagging tool on forums...
Merry X-mass and a happy New year.... darn them Aussies are gonna beat us belgians again by partying a day earlier... Life is so cruel..
I run nothing less than 2000-3000 iterations depending on memory size just for the hell of it and then drop 100Mhz. And above 1.200V may degrade the chip doing so, but <1.200 should be fine.
Using IBT 2.53 to stress test my i7-2600K. It's stable for 10 runs on Standard and is Prime 95 stable for 9.5 hrs. But if I try IBT at High or Very High stress level, it fails after the 2nd run. Should I be concerned about my system stability?
Yes.
I for one took MM's advice to heart. :yepp: Instead of trying to get 15-20 IBT loops at Max stable, I just go for a 5 loop standard run. If that's stable, I go for a 5 loop test on "High." If that is stable, it's usually good enough to prevent BSOds in WCG or F@H. After that it's just about adding enough more v-core to prevent computation errors on the WUs. :) Quick and dirty crunch/fold worthy OCs in an hour or less. :D BT is valuable and I appreciate AG's work.!!! :up: It used to take more than twice as long with P95. :(
Ummm... unless I'm suffering xtreme memory loss, Fugger works for Intel. How long have MM and Fugger been friends??? How many industry contacts does MM have? :shrug: I wish I knew at least 10 more people like MM!!! I'd probably have to go back 50 years to find them. :rolleyes: People that know right from wrong and tell the truth regardless of whether it is popular or will take a dollar out of their pocket are very rare today. ;)
(Don't let that go to your head MM! You are on the FBI's most wanted list of cell phone battery killers! :stick: :rofl: )
Thank you..Quote:
Originally Posted by WFO
Updated to v2.54!
- Linpack binaries updated (7-20-2012) + patched for AMD CPUs
- Improved effectiveness of Xtreme Stress Mode
:up: This thrad neds to be stickied.
^ Agree.
You probably have a memory issue. Very High tries to use all the memory it can get. Do about 10 runs of memtest86+. I know 10 runs seems like overkill, however i have seen where errors did not show up until the 9th run.Quote:
Originally Posted by wongnog
IntelBurnTest v2.54- new Linpack (11.0.1.005)
http://www.mediafire.com/?azzprpvwkonowbv
-Updated with both xeon64.exe and xeon32.exe with the newest Linpack.
Havent used this program in over a decade.
So i just ran 5 loops on High for the fun of it. After 3rd run i could smell something burning, and i have never had a burning smell when using other programs in the past.
2500k @ 4.2Ghz, v1.21
As others have said, be very careful when using this program.
Never had any problems with IBT. Infact, for me it has been the defacto stability test for quite a while now.
My current setup 2500k@4.7GHz has been proven stable initially upon building, and the later on when upgrading to a new bios. Running 1.32v with Silver Arrow, and my temps hover around 70c. EIST is also enabled so it's not 4.7GHz 24/7. I'm accustomed of leaving IBT running while I sleep. So my standard run is around 6-8h.
My overclocking has always been about finding the sweet spot for daily use, and not the very far end for cpuz validation screens. I gues that means I'm not that xtreme. And from the looks of it, 2500k will remain the last pinnacle of overclockable cpu's. There will probably never be such chips in the future, which makes me sad... :(
Thanks for the update. Unfortunately the linpack files are for Intel only. You forgotQuote:
Originally Posted by stasio
to put the patch files which are usable by AMD users like me. :(
Before patch:
http://s19.postimage.org/rphposyw3/IBT254_Err.png
After patch:
http://s19.postimage.org/pjneuavfn/IBT254_OK.png
Don't worry AMD users, just download the patch files here:
Mediafire :
Datafilehost :Code:http://www.mediafire.com/download.php?ybc3pbiwswbso3s
Code:http://www.datafilehost.com/download-b6f1cf10.html
Dudes,
What gives..when I run my 3770k it reports only hitting 81 gflops with HT, 90-91 without..?
Did you try setting threads to 8 when you have HT on?Quote:
Originally Posted by Jonny5isalivetm
with 8 threads it went upto 84 only
Does oc slow it down ?
edit, just tried auto setting and it hit 98 ? :D
great soft. any chance to stress ram using this soft
Prime95 is still the best of all times - RAM, CPU, it's the King!Quote:
Originally Posted by sikvdila
IBT 2.54: BUG REPORT - Please confirm
If you put 0 (zero) in "Times to run", you get a "Linpack64 stopped unexpectedly" error at the end of the first pass.
Many programs assume "infinite" when you put zero for such a parameter, and that's what I assumed for IBT.
I just couldn't get my new 3770K IBT-stable consistently. Prime95 v27.9 ? -- no sweat!!
But IBT? No way, Jose.
Then I tried 10000 instead of 0 in "Times to run" and it's still running ...
:mad::mad::mad::mad::mad::mad::mad::mad::mad::mad: :mad::mad::mad::mad::mad::mad:Other than that, it's a great program for us WCG number-crunchers especially.
It's much harder to pass than Prime95 or Super-Pi.
Before signing out your overclock as fully stable, it's not a bad idea to try a mixture of some threads running IBT, and some running another stress-test such as P95 or SPi.
Thanks, AG !! :up:
IME P95 and OCCT in there various configurations provides the best stress testing of both the CPU and RAM. ITB and Linpack are mostly a CPU stress test. The "blend" in P95 and "large data set' in OCCT are the best overall test. The "small data set" options stress mostly the CPU - similar to IBT/Linpack. OCCT also offers a GPU and PSU stress test. Any reliable PC will pass all of these stress tests though ITB and Linpack are some what redundant if you use either P95 or OCCT.
If you get errors in any of the above tests and you have not already recently run Memtest86+ for 6+ hours without errors, you should do so as I am seeing a number of brand name RAM kits failing in as little as 2 weeks to a few months when run at their rated frequency and voltage.
IBT can really thrash the RAM as well as the CPU:
Before you start, temporarily set the "Stress level" to Maximum, to see how much RAM is available to test. Should be about the same as "Available" value in Task Manager > Performance tab.
Subtract about 200MB from the max to leave some headroom for Windows housekeeping, select "Custom" in IBT, enter your RAM amount and set it going ...
-------
Am having trouble with the 3770K, am thinking the chip is a lemon. It crashed a while ago after crunching easy WCG tasks for a couple of days with 4.2GHz/1.14V (load), mem at 1333. Am running Windows mem diagnostic with mem at its rated 1600, to check RAM. Have another 3770K crunching hard WCG tasks (3 x CEP2) happily for weeks doing 4.3GHz/1.112V.
CPU #1 (good) is in an Asus P8Z77-M Pro, CPU#2 (lemon-flavoured?) is in a GA-Z77MX-DH3. With the DH3 there are no settings for Uncore Volts ("VCCSA") (to set IMC & cache) or Vtt. Though I've never had to alter VCCSA or Vtt, it's useful to be able to try, so I would not buy a DH3 again. With the P8Z77-M you can even set them from Windows, but the overclock settings in its BIOS are really quirky and it keeps silently trying to turn "turbo" etc back on.
not to revive a thread but thought i would bring it up that the guy that made this, also makes hacks for a few pc games. Personally i would not support any of his work. many people probably dont know that he does (and probably don't care) but for those that do care, think twice before hitting that donate button.
Interesting to note this. I had thought this program was interesting several years ago. Now, there are no posts from AgentGOD in his own thread for over 1.5 years. He has likely moved on to bigger and better things as far as he is concerned. Movieman has done a good job of articulating the risks associated with this program in a previous post.Quote:
Originally Posted by atm743
Quote:
Originally Posted by Razmatazz
ahh i didnt see his post. i just noticed that the guy that made this also was responsible for making hacks and mods for games (mostly hacks) and selling them. i also find it funny, when you press the donate button it takes you to his forum that shows all of these hacks and "buy it now for full access" banners.
Bug: Intel Burn Test 2.54 Linpack randomly fails to properly load the cores and shows real low GFlops. When this occurs, I must reboot or close and reopen Intel Burn Test.
I have to get a hold of AgentGOD, he and I go back-- I wonder if he has time to update this. He's a busy guy with a real job now.
All the links are a parked domain!