I have read several threads and flame wars on the subject of NaNs. Its just like back in my programming PM days, trying to keep engineers and programmers from coming to blows across the table.
My opinion is to keep running F@H, and if you see too many NaNs just stop the service, erase and start over.
One of my systems had about 80 EUEs a few weeks ago. I rebooted, it had a few more then suddenly everything was fine.
I know that F@H is an excellent system tester, catching hardware failures early on. I also know that F@H will eventually find every buggy device driver in your system, and a few in the underlying GROMACS and AMBER code.
New proteins always have about 50% EUEs as the software completes the boundary testing the hard way - compute until illegal.
Ok, thanks. I will start it back up and let it run.