That means you did not extract everything and keep the directory structure intact.
Printable View
jesus, i had to do a small vcore bump on something that was 36 hours prime small fft's stable to get 10 maximum runs here.
great feeling to have it pass though.
btw, agentGOD, you rock, and i think you made prime obsolete.
Very nice AgentGod as winter came i have 22C inside my room and i was able to do a quick test of your app as this batch is very low vid 1,1875 i have to be careful with temps.
http://img198.imageshack.us/img198/2...coreibtsti.jpg
Cheers :up:
Sergio
Nice chip, I want it :D
lol
Thanks :up:
I tried new IBT 2.0 with an Asus Rampage II Extreme and a Xeon W3520 with HT enabled under Win7 x64 and I was not able to load cpu cores at 100%.
Is there any button/command that I haven't seen or is it an issue of the new program?
Great job, Agent!
AgentGOD, i just want to say Thanks for this great program. I've been experiencing problems for some time and thought it was a hardware failure because my system was 24+ hours Prime stable.
But Linpack failed just after the first loop. So I corrected the voltages and now everything works great. :up:
Q9550 @ 4250mhz
MemTest86+ = OK!
IBT v2 Standard = Success!
IBT v2 Maximum = freeze :(
Updated IntelBurnTest to v2.1!
- Optimized error-checking code, reduces CPU overhead
- Now displays more accurate ending time
- Simplified graphical user interface further
- Improved color of captions in the GUI
- Added ability to override the number of threads for Linpack to use (as requested by users)
- Added display of progress in the title bar
- Now outputs current time for each iteration to log file (hh:mm:ss)
- Now auto-scrolls output list to the bottom as results are outputted
- Fixed a GUI quirk
Core i7 users, please confirm if the new thread-forcing feature is working :D
Thanks, and enjoy!
Seems to not be working? unless I did something wrong?
http://i18.photobucket.com/albums/b140/hoss3430/ibt.jpg
Same results?
http://i18.photobucket.com/albums/b1...s3430/ibt2.jpg
Hmm... try changing it to Auto/16.
Lol, I thought the same thing, tried both, still same. :(
Ok, I've updated the release version, please re-download via main link. Should work fine with threading now.
Also guys, if you could, please test using 64-bit OS and forced 8-threads on a quad-core (like a Q9xxx/Q8xxx/Q6xxx) and Custom memory size of 64 MB, with 10 runs. (Just a tiny experiment, I'd like to see)
Because according to my little experiment, my Q6600 isn't stable. Failed within 1.76 seconds of doing this test, but passed the Standard test fine @ Auto threading (4 threads).
See screenshot:
http://i43.tinypic.com/11lpf05.jpg
Agent, is it possible if you could add a module to support temperature display as well? I know we can run other temp monitoring program to do that, but it would really be nice if you could add a module so the correct temp of each core are displaydd somewhere also. Thanks...
i get that same error on my q9550 when i run 8 threads, 64mb test.
I just downloaded the newest version, awesome work, great program :up: