Yeah its quite a bit newer than that one and also far newer than the one that worked on haswell (for me) before. It's harder, I think you can reduce the problem size to throw errors rather than BSOD's, but I've just been leaving it at the largest problems size that it picks automatically based on RAM amount I think. But BSOD city lol. I found some interesting rules based on the creators experiences, based on his description, i'm having RAM trouble as I get a freeze for a few seconds, then it BSOD's, It's not something I can fix easily though as it's to do with the way I mounted my CPU, no IHS and no hold down bracket, so I'm not getting correct pin contact in the socket. I can't be bothered doing another tear down and rebuild though just yet, just been playing around with how tight the water block is done up, I've loosened it off a bit, the temps went up a few degrees, but I can now run 2600 XMP profile where before it wouldn't even boot for a few days, even though I had been using it for a couple of months with 2600 XMP prior to mounting it this way and worked fine for a week or two mounted this way. I changed my water loop last week and have had issues since then, so I must have moved the waterblock enough to disturb the way it was touching the pin's prior to that.
This is the quote from the developer in the XS thread about the error's/bsodWarning: Spoiler! (Click to show)
Post 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.
Some of this relates to old CPU's though.