I downloaded linpack64 a couple days ago. That program is very inefficient at finding unstable overclocks. You have to run it once for long enough to get an error (but you have no idea length run needed). Then run it again and compare results to see if there was an error. You get no clue as to ram or cpu, or how far off you are. And since it does not notify right when error occurs, you could run it for hours needlessly, when orthos or prime would notify you right away.

IMO, it is piss poor at efficiency and thus worthless for overclock testing.

If you want to argue that after you find your stable overclock with orthos, you could find out if it is even more stable by running linpack64, then first you would have to demonstrate a need, and second prove that its better.

If my system is orthos stable on both small ffts 8-64 and on large ffts or blend, both for 15 hrs, I have never had a system crash or instability problem. Therefore there is no need for a better program than orthos or prime for my desktop. And second, you haven't even proved that it does a better job of finding instability, even though its a worthless endeavor even if it did.

If there is more to linpack64, and an efficient way to help with stability testing, please educate me, I am all ears. Until you have shown me that, I will go on thinking you are selling something or smoking something.