Intel Burn Test & LL integrity
 

Sup dawgs

So I've been crunching at 3.2GHz on my i5 750 for a week or so now but have decided to crank up the clocks. I have the system on 3.8GHz with 1.312V, and it has passed the intel burn test (linx) successfully set on maximum memory saturation and ran through 50 runs (which took about 80 minutes).

Am I right to say I shouldn't have jeopardised the integrity of my (future) LL results?

I think if you want to ensure that your system is stable for Prime95 then you should be running Prime95. Running some other test program will only prove it to be stable for that other test program.

[quote=retina;203139]I think if you want to ensure that your system is stable for Prime95 then you should be running Prime95. Running some other test program will only prove it to be stable for that other test program.[/quote]

Yes but I have had prime95 run for an hour without error, then as soon as I use linx it often fails within the first or second test...

[QUOTE=hj47;203148]Yes but I have had prime95 run for an hour without error, then as soon as I use linx it often fails within the first or second test...[/QUOTE]Well same thing applies I guess. If you want to ensure that your system is stable for Linx then you should run Linx. Running Prime95 will only prove it to be stable for Prime95. Other apps/OSes will use different resources/drivers/hardware etc. So even if Prime95 passes all tests perfectly for a week that still doesn't mean your X graphics driver is going to work perfectly when you start editing a PNG file.

In that case I guess doing 100 runs of linx + 12 hours of blend + 12 hours small FFT + 12 hours of large FFT's test should suffice?

Not really. It might find a problem or it might not find a problem. Your best bet would be to dedicate your hottest core to doublechecks and check if you get any errors/mismatches. BTW, 1.312 is a bit low. I got to 3.8 but had to up it to 1.375 to avoid once a week errors.

[QUOTE=garo;203170]Not really. It might find a problem or it might not find a problem. Your best bet would be to dedicate your hottest core to doublechecks and check if you get any errors/mismatches. BTW, 1.312 is a bit low. I got to 3.8 but had to up it to 1.375 to avoid once a week errors.[/QUOTE]

So you've been running 3.8 since November without any errors?
I need to try to bump mine up more.

I used the stardard EasyTune which maxes at 3.2. I'm getting DC iteration times of 20 to 21 ms.

Thanks

[QUOTE=hj47;203163]In that case I guess doing 100 runs of linx + 12 hours of blend + 12 hours small FFT + 12 hours of large FFT's test should suffice?[/QUOTE]

As Garo said, the best thing to do is let Prime95 run in the OS you will be using to do double checks. If you are running say 4 double checks at the same time to stress all 4 of your physical cores, then when that set is done, you can check the Prime95 server to see if the results match the previous one. If they all match you should be good since it will take days to complete the test.

I have had cases where running a day of Intel Burn Test and a day of Prime95 torture tests did not find any problems but running something for days or weeks would error out. Turned out in my case the voltage was a little to low but not enough to notice any problems for every day stuff.

Jeff.

I was running 3.8GHz at 1.35V and I got errors. I have not had any errors since I upped the voltage to 1.375V. I still have a couple of unconfirmed results so I'll wait until they are confirmed/rejected before deciding to go down to 3.6V.

This is interesting, argh now I've gotta find the sweetspot for performance/voltage/temperature/reliability.

Doublechecking is the only way to go I guess.

Cheers

[URL="http://www.mersenneforum.org/showthread.php?p=203232"]This thread[/URL] may be of some relevance here--there's an example of a setup that passed Intel Burn Test but failed Prime95's Large and Blend tests. Perhaps the Intel Burn Test only does the equivalent of Prime95's small-FFT test? (Disclaimer: I've never used the IBT myself.)