Your Win32 machines will no longer be receiving Modfit work units so that won't be a problem any more.

I was aware of the ongoing Win32 problems and that you had subsequently blocked Modfit from Win32 machines. I was just trying to add some specifics to the discussion - that my Win32 errors were immediate computation errors [-1073741515 (0xffffffffc0000135) Unknown error number]. Other posts on this thread seemed to indicate that some Win32 units were failing after processing for significant amounts of time.

As for your 64 bit computer that is completely normal. We require ~3 computers to return the same result for every work unit we send out. Validation inconclusive just means we are waiting for others to return their results for the work unit before we award credit. This ensure people aren't trying to game the system just for credits and it ensures we are getting reliable results for our optimizations.

It may be Milkyway "completely normal" but it's not BOINC "completely normal". ;-)

Your Win32 machines will no longer be receiving Modfit work units so that won't be a problem any more.

I was aware of the ongoing Win32 problems and that you had subsequently blocked Modfit from Win32 machines. I was just trying to add some specifics to the discussion - that my Win32 errors were immediate computation errors [-1073741515 (0xffffffffc0000135) Unknown error number]. Other posts on this thread seemed to indicate that some Win32 units were failing after processing for significant amounts of time.

Isn't 0xc0000135 (expressing it in 32 bits) the very old and very well known 'The application failed to initialize properly' STATUS_DLL_NOT_FOUND?

Shouldn't somebody be checking to see what DLLs are required by the application (http://www.dependencywalker.com/ is your friend), what DLLs are being sent out, and why there's a difference between the two?

Thank you Richard. I will look into it when I get a chance. Might not be for a few days though. Things have gotten very busy here.

Jake W.

Several people running ati? were experiencing 6% validate errors on modfit runs.

I just started with my HD7950 with same drivers I have been using for several years. These drivers produced no invalids back in April for a team challenge.

SETI recently noticed that an API bug in BOINC truncates the STDERR sent to the server. ALL of my Invalids have this example
Stderr output

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=573186&offset=0&show_names=0&state=5&appid=

Windows 7 64 bit boinc 64 bit. FX-8350

My i5-3570 with GTX660 does not show any invalids

Thanks

Will test my A8-5800 in a couple of days it also has an HD7950

Thank you for the reply. I'll allow another load of work units to be off loaded onto my computer and see how it goes. As I recall, some Modfit 1.36 wu's were still coming through and gumming up the works, lol. Hope you have a good weekend. Mike

I've been running this N-body simulation wu (one core, not modfit) since oct 6. The estimated remaining time always says 16 hours, but it already has had 77 CPU hours and it's only at 30% and today's the deadline. Any idea why it takes so much time? It's the first wu that takes this long. Usually the estimates are optimistic.

Hey all,

Tom*, we did some updates to the BOINC libraries we compile against so maybe the issue lies there. I will look to see if there are any newer versions for us to use. Thank you for the reply.

Cosmin, I don't work much on the nbody application but 77 hours seems pretty long, probably okay just to abort that. If you post in one of the nbody posts on the news section, someone who works more closely with nbody might be better able to answer your question.

Jake W.

Tentatively i have activated modified-fit yesterday.
To date, over one day no error occurred.
It seems ok.

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=510433

Thanks! Glad everything is working well on your end. I appreciate the extra help.

Jake W.

I'm too seeing a higher error rate of the Modfit since a few weeks (several dozen invalids per day). Had to opt-out...

Hi Mumak,

Looks like you are also running into the AMD issue. I will try to look into the issue a bit more and see if it needs to be a fix on our end or BOINC.

Jake W.

switched back to 64 bit boinc last week. things are running smooth now.
open cl problems solved as well
so back to letting this project churn in the background and turn back some smooth results now.