MikeMK,
I'm not sure if I can do anything more to that «not enough memory» problem. LinX uses an approximated formula to calculate how much memory Linpack is going to consume at the given Problem Size. If the calculated amount of memory is bigger than what OS reports to be free memory then it shows that warning message saying that the values were corrected. When the «all mem» button is pressed LinX chooses the Problem Size value for Linpack to consume almost all free memory. But either that formula isn't correct enough for bigger numbers or Linpack doesn't like big numbers too. (Hopefully 2nd is the case as a 600 MB error doesn't make me a good mathematician and a programmer either)

I would be grateful if you could post or send me via PM a screenshot with LinX running at those 3.9 GB and a Task Manager window with a linpack_xeon64.exe process and its memory.

Quote Originally Posted by MikeMK
the program doesnt seem to max my cores to 100% when Im running it.
Linpack doesn't keep the cores always at 100%, its load is less consistent than that of Prime, especially at the beginning/end of each test. If that is what you experience then it's ok.

And yes, 3.9 GB is still quite enough for Linpack to check stability.