Could somebody with posting rights copy the following information to the project's News thread, please? Their message boards are locked up so tight that a new users can't even post an explanation for why their new app isn't going to give them enough credit to post...

0xC0000135 isn't exactly an unknown error - it means 'The application failed to initialize properly'. That's usually a missing DLL - and no, thank you Google, NOT usually the silly 'dot Net' framework.

Sure enough, trusty old Dependency Walker indicates a need for LIBGOMP_64-1.DLL, and the app_version supplied for the app doesn't reference it:

<app_version>
    <app_name>milkyway_nbody</app_name>
    <version_num>94</version_num>
    <platform>windows_x86_64</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>2503477159.822932</flops>
    <api_version>6.13.0</api_version>
    <file_ref>
        <file_name>milkyway_nbody_0.94_windows_x86_64__mt.exe</file_name>
        <main_program/>
    </file_ref>
</app_version>

Also, I was expecting this to be a multi-threaded app, and I see _mt at the end of the file name: yet there's no MT plan class, and <max_ncpus> is just 1. If the app itself is going to try to use more cores than BOINC frees for it, that's going to cause major scheduling problems.

Done

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3046&nowrap=true#56180

Done

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3046&nowrap=true#56180

Thanks Byron.

Since then, I've found another dependency (on pthreadGC2_64.dll) - with both DLLs manually downloaded and popped into the project folder, the app just about runs:

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=479865&offset=0&show_names=0&state=3&appid=7

But 0.36 credits still doesn't allow me to post. Perhaps you could do the honours again?

You're welcome Richard.

The next error, once the DLLs are in place, is usually 0xc0000374 for memory heap corruption. They'll need to go back to code, and see where they're writing outside the bounds of allocated memory, for that one.

The next error, once the DLLs are in place, is usually 0xc0000374 for memory heap corruption. They'll need to go back to code, and see where they're writing outside the bounds of allocated memory, for that one.

Posted to the thread as well.