Windows 64 bit users seeing errors in work unit for Nbody Version 1.06 will want to use the reset option to have the software. This will redownload the dlls and fix a bad file that was transferred in the initial download.

Alternatively you can manually update the file per these steps
1. Stop MilkyWay@home
2. download the pthreadGC2_64_nbody_1.06.dll from http://milkyway.cs.rpi.edu/milkyway/download/pthreadGC2_64_nbody_1.06.dll
3. place pthreadGC2_64_nbody_1.06.dll into your mw directory


A more detailed discussion is in the following thread:

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3128


Jeff

Thanks Jeff,

Sounds like an easy fix, will reset project now.


Keep Crunchin'
Dave

---

A more detailed discussion is in the following thread:

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3128


Jeff

Making your link clickable.

Resetting the project is a safe and reliable way of overcoming this problem - though volunteers also running GPU applications for other parts of the milkyway project may wish to set 'No New Tasks' first and report all completed GPU work before resetting.

I'm a little worried by the 'download and rename' workround, for reasons I'll explain in the discussion thread, in a few minutes.

Would it be fair to say the following?

So omitting the steps 4 and 5should suffice if reset can not be done.


Though using the reset is the preferred option.


Jeff

Placing the 'versioned' DLL (pthreadGC2_64_nbody_1.06.dll) in the project directory should be sufficient, because of the happy accident that the faulty version of the file and the replacement have exactly the same size.

If the two files had different sizes, BOINC would detect that the file had been "tampered with" at the next core client restart, and download a new copy anyway.

Danke für die Info.
Mich hatte es schon gewundert warum den ganzen Tag andauernd Fehler produziert werden. ;-)

Und für alle die nur schlecht englisch können:

Milkyway@Home unter Projekte auswählen und auf Zurücksetzen klicken.
Dann wird die "Engine" neu geladen und der Fehler ist weg.
Aber vorher noch aktualisieren, damit die Punkte die noch hochgeladen werden müssen nicht weg sein. ;-)

---

Might I suggest posting this message as a "notice" in the BOINC Manager? (Whatever that entails) Users aren't going to see it unless they go to milkyway's website, and it does seem like a lot of users haven't seen it yet, as many of my n-body tasks are still not granting credit due to too many errors by other users.

Anxiously applied this fix but am still having computation errors. Any other ideas would be greatly appreciated.

Thanks,

Mark

Anxiously applied this fix but am still having computation errors. Any other ideas would be greatly appreciated.

Seems the quick fix didn't work out for you.
Your choices are
- to set mw to NNT and after all tasks are sent back do a reset of the project
- or to disable n-body in the preferences until v1.07 is out (expected tomorrow)

In your case I would choose to reset mw to make sure you have a fresh and clean mw folder with no old/bad nbody dll hanging around.

Hint me please!
Shall I let go and continue at the risk to sure go behind Validation Date with at least unit2 or skip them for renew? Why I ask? Well, you put the pressure on it, I got all the time it takes, when it rewards :)

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=399687871(State:36%@43h)

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=395028142(State:12%@90h)

Thanks for help in advance :)

Hint me please!
Shall I let go and continue at the risk to sure go behind Validation Date with at least unit2 or skip them for renew? Why I ask? Well, you put the pressure on it, I got all the time it takes, when it rewards :)

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=399687871(State:36%@43h)

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=395028142(State:12%@90h)

Thanks for help in advance :)

I'd say continue. It's highly unlikely, that the result that will be created and send out once your times out will be returned before yours. It might time out as well or even error out. Or become inconclusive and need another wingman anyway. So your result very likely will contribute to science and by not aborting it you also do not increase the probability, that these WUs get too many error results.

---