2 Attachment(s)
LinX 0.4.9.1 - renewed GUI & AMD support
As you've probably read in post's title this new LinX has AMD support (it's so pretty stupid to say that in Intel thread :D).
But, it was done not by me but by forums.overclockers.ru member Right, so all credit goes to him. :clap:
I just added this to LinX with his permission and wish to thank him for that once more. Intel users, there's no performance difference from previous versions, so don't worry. If you still want to stick with Intel-only files you can use those from previous versions or download them here (but there's really no difference in performance/error finding efficiency as well as in heat generation :)).
Other changes include slightly redesigned UI and the ability to resize program window horizontally in Detailed log mode. Bug reported by Pyro (thanks to him!) was also fixed.
Attachment 86591
Download link : LinX 0.4.9.1
Quote:
Originally Posted by DildePer
Thank you very much for the quick answer. Even when using 25 runs of 5000 sizes it still reboots my comp, where I could run ORTHOS for about an hour!
Although it seems that Orthos generates more heat? Was getting 48-50 load temps with ORTHOS and 44-45 with LinX?
Very effective, thanks again!
It's kinda weird you're getting lower temps with Linpack than with Orthos. This is normally just the opposite. And BTW have you managed to make it pass LinX or it still reboots?
Trying to understand Linpack errors
After playing with new rig I decided to make some Linpack error interpretations, which might be helpful for those unfamiliar with Linpack. Note that these are based upon my observations and can't be 100% true. You are welcome to share your experience.
Basically if you get an error you would have x same (correct) results and 1 different (an error):
- if the incorrect result differs slightly from the rest (numbers very close, same powers in Residual & Residual (norm)) it is most likely that there's not enough vcore. In this case only a small vcore bump is usually needed to stabilize the system (alternatively, Vtt & GTL tweaking can sometimes fix this too)
- if the wrong result differs much from the others (different power or even positive power in Residual or Residual (norm)) it might be 1) insufficient vcore (the error would happen at the very first runs then) or 2) some memory / NB instability (when it worked for say 10 minutes ok and then produced a different result)
Now more serious errors:
- a BSOD during testing (at the very first runs) is often caused by too low vcore
- if the system hangs and remains hung it is almost 100% not a CPU but memory or possibly NB issue
- if the system reboots (with no hang prior to reboot and no BSOD) - a CPU issue, but not vcore related (insufficient PLL or Vtt I guess)
- if it hangs for a short while and then BSODs - once again NB or memory problem (but might be wrong Vtt / GTL setting as well)
- if it hangs and then just reboots - wrong Vtt (too low or too high) or GTL settings
P.S. Despite being probably the most stressful stability checking program for CPU Linpack is not that good at finding memory errors, so checking memory with tools like Memtest, OCCT & Prime Blend will be a better idea.
P.P.S. Please correct me if I'm wrong. :)