You should try it on that old AMD rig of yours, just to see how it stands up to the power of IntelBurnTest :ROTF:
Printable View
You should try it on that old AMD rig of yours, just to see how it stands up to the power of IntelBurnTest :ROTF:
Don't forget the eMachines too :)
Tried it on a Dual S771 rig yesterday.. linpack64 is really nice. Around 220W from the wall running prime, 250W running in 32bit mode and a whopping 280W max for the x64 with 7,55GB of used memory :up:
Dual E5440, Supermicro X7DCA-L (insanely efficient mobo, below 100W idle drain :shocked: ), 8GB Reg ECC DDR2.
Oh yeah, it also collapses my phase unit after a while if I run it on the Q6600 (the CPU is already at 260W prime...). :shakes:
Well, thank you for your thorough testing :p: Interesting to see. That gives a legitimate justification for using 64-bit over the 32-bit.
hi i have a problem.
I pass 50 loops of IBM (xp 32 bit IBM 1.8)with no errors and i keep having bsods.
Any ideas?
IBM is not THE TOOL.Quote:
Originally Posted by johnysb
It tests very rapidly any cpu instability but it is not so clever in detecting RAM/NB one.
Try prime95 blend or OCCT in RAM test or latest memtest for windows.
That usually indicates instability of something other than the CPU.
Any updates are coming?
That's to be announced.
Updated to v1.9
- Official Intel(R) support for Core i7 processors
- Fixed a bug that caused crashing when using a 32-bit OS and having more than 2 GB of memory free
- Changed interface colors for better visibility
- Revised "wordy" prompts
Thanks to Rob Williams from Techage for Core i7 testing.
Updated WinPE native 64-bit version
- Same changes as in the hybrid executable
thanks! great app! :up:
Please do comment on the new colors too :D
why green? :) looks like a chalkboard now :)
Because somebody didn't like the red.Quote:
Originally Posted by emoners
Well you got two against the green :p would be nice to see the end result flash green or red when it failed, but backgroudn would be nice to have white or black... program works nice on 2GB 32bitand 4GB 64bit, will test with 4GB on 32bit OS now
I had 4 friends against the red :(
Thank you AgentGOD! Nice colours btw. Keep doing a great job :up:
AgentGOD,
V1.9 doesn't work properly on my i7 940 with HT enabled. It only loads up 4 threads, leaving the CPU at 50% overall load. Using XP x64 with 6GB of mem...
Well, Intel says this binary has official support for Core i7. I believe there's a good reason why it's "only using 50% of the CPU."
Yeah well, right now it's pretty lame. Running prime for a few hours gets me clsoe to 70C on all cores at 3,8Ghz (Noctua U12P air cooler in push-pull). 50% Linpack obviously doesn't get me over 60C. Disabling HT uses 100% but then it's still 20-30% les stress on the CPU... Darn Sissys at Intel, it's like AMD slowing down their cards if you run fur.exe :mad:
Why? (A little too much between the lines for me. What's Intel hiding?).Quote:
Originally Posted by AgentGOD
Until linpack can use all threads on core i7, it will be less useful if run by itself.
For 4/4.2 prime stable on i7 940 I need 1.35 vcore bios loadline on, 1.31 vcore load.
I can run linpack for hours, never get an error, at several notches of vcore below that, because with only about half cores loaded vdroop only goes to 1.33. which makes linpack useless by itself on i7 for trying to pin down a stable overclock, until intel can get it optimized to load all cores.
on the other hand if you run prime, then run ibt with prime running (b/c prime causes full vdroop) though linpack takes longer to run, you get the full load/vdroop effect of prime and the increased effciency of IBT. AT least temp fix until linpack uses all cores. For example at 2 notches below stable, prime running itself error or reboot after about 4 hours. Running prime then IBT, IBT will give me an error in ~10 mins or cause reboot within a few minutes. And at my prime stable 12 hrs 4/4.2 ghz setting, I can run both programs simultaneously nonstop.
Lol! Prime + Linpack at the same time? Please, spare your poor chip, dude :(
Whatever works for you I guess.