Problems with new client / AMD / W2K

[Michael H.W. Weber]

Anybody an idea how to cure this problem which occurs repeatedly on an Athlon system under W2K?

========================[ Jul 30, 2002 6:43 PM ]========================
ERROR: [000.000] {foldtrajlite.c, line 1157} Unable to check server status
ERROR: [001.013] {randwalk.c, line 3924} Discriminant =-1.#IND00 while calculating CB
ERROR: [001.001] {bbox.c, line 266} ..108..

ERROR: [001.001] {bbox.c, line 268} .. CB ..

ERROR: [001.001] {bbox.c, line 269} ..1..

ERROR: [001.001] {bbox.c, line 270} .. CA ..

FATAL ERROR: [004.001] {bbox.c, line 282} b-d node crash; node not inserted

It's the latest client...
Michael.

[Brian the Fist]

That is effectively a divide-by-zero error. IT is nothing new, and COULD happen theoretically though extremely rarely. I find it hard to believe it would happen more than once. If so, is it possible you have a buggy FPU or something? How many times did it happen?

[Michael H.W. Weber]

Hmmmm, the machine concerned runs absolutely fine with everything else. But DF does not run at all. Always gives this error after some time.

Michael.

[Brian the Fist]

The fact that other programs run fine does not mean that your hardware is not faulty. Quite a number of people have detected bad RAM from running our software and were completely unaware of it before then (an interesting side effect of our software as a RAM tester). If it only happens on one box, and does so repeatedly, most likely the FPU on the CPU is quirky/overheated.