Arrgh Win SMP F@h Unknown Error

[MGP]

Windows SMP client, current version. Whatever I do it just gives the message:

Entering M.D
Rejecting chekpoint
Gromacs Error
folding@home Core Shutdown: UNKNOWN_ERROR
folding@home Core Shutdown: UNKNOWN_ERROR

I've rebooted, I've wiped and reinstalled the entire f@h including the smpd thingy, which has forced it to download cores and stuff. Whatever I do it stops.

It was fine till sometime early this morning. Rest of the PC seems fine, and as far as I can tell nothing has changed.

Anyone got any ideas?

 

[BillytheImpaler]

Are you running as a service? A few weeks back my main desktop was doing this. I disabled the service from auto-starting in lieu of starting manually and the problem stopped.

 

[MGP]

Nope not a service.

 

[MGP]

Solved it. Looks like it was a dodgy WU, that despite clearing out the entire folding folder Stanford kept insisting on reassigning it to me: "project 2610 run 0 clone 90 gen0"

Changing the configuration machine ID seems to have told Stanford to have sent me a different WU, and now it's happily crunching. It's going to hurt my output this week though

 

[Biffa]

I had a funky one tonight stopped at 100% and got stuck, you can see it stopped at quarter past nine and then where I shut down the service at half past 12.

[20:18:09] Completed 500000 out of 500000 steps  (100 percent)
[20:18:10] Writing final coordinates.
[20:18:11] Past main M.D. loop
[20:18:13] Will end MPI now
[23:26:42] Service stop request received.

Luckily after restarting it sent

 

[Snapshot]

Solved it. Looks like it was a dodgy WU, that despite clearing out the entire folding folder Stanford kept insisting on reassigning it to me: "project 2610 run 0 clone 90 gen0"

Changing the configuration machine ID seems to have told Stanford to have sent me a different WU, and now it's happily crunching. It's going to hurt my output this week though

It can take up to five downloads of the same WU before the server at Stanford gets the idea and sends you something else. Had a couple of dodgy 2652's a few days ago....

 

[A.N.Other]

Bah I lost a WU last night when windows decided that it needed to restart after some updates.