P-1 on v30.3

[Minty]

Is P-1 work operating OK in v30.3? I downloaded v30.3, put it in c:, got a 100M exponent, allocated 42GB of 48GB with nothing else running. It did stage 1 OK but after 4 hours finished stage 2, said worker stopped, worker started then restarted stage 2 i.e. in a loop.
Also noticed timings took longer towards end of run while machine not being used. Definitely no thrashing of hard drive, anyone any ideas? Seems like something may not be right with P-1 on v30.3?
Everything was fine yesterday with v29.8

[Minty]

Fixed! I moved the folder to the desktop, reran from a save file and voila no problems. Sounds like putting the prime95 folder in the c: on Windows 10 was the problem. Still no factor though!

[kriesel]

Originally Posted by Minty

Fixed! I moved the folder to the desktop, reran from a save file and voila no problems. Sounds like putting the prime95 folder in the c: on Windows 10 was the problem.

Thanks for identifying the issue. I've added a caution about it to a reference post https://www.mersenneforum.org/showth...289#post488289.
Expect one factor in about 30 P-1 runs (of both stages), and expect considerable variation from that general guidance.
In future, please identify what program as well as OS when first reporting issues.
Have you looked at gpu GIMPS computing yet?

[Minty]

Thank you for replying and adding the reference, it's very much appreciated, the mersenneforum is such a great place. I'd noticed that it wasn't writing results files so that was also a clue, I'll be sure to identify the program and OS in the future.

Would you believe I have an old GTX570 (my most modern GPU!) and have been planning to do a little bit of TFing with it as winter is approaching

[kriesel]

Originally Posted by Minty

Would you believe I have an old GTX570 (my most modern GPU!) and have been planning to do a little bit of TFing with it as winter is approaching

Yes. I would. I have Quadro 2000s and newer, and even an ancient NVS295 as a cold last-resort display interface spare. (It can't run with an NVIDIA driver newer than 342, so is incompatible with gpus of reasonable age that require newer drivers, and it delivers a mere 2. GhzD/day in mfaktc, not worth the 20W it takes.)