Hello Crunchers,

I have just put out application version 900 for owners of Pascal GPUs. To test this you need:

* A Geforce 10-series or Tesla P-series GPU
* 64 bit Windows 7 or later
* NVIDIA Driver 360+
* Accept beta work, and WUs from the acemdbeta and acemdshort applications

Please report all problems in this thread.

WOW

EDIT: It's not listed in the http://www.gpugrid.net/apps.php page.

EDIT of EDIT: Now it's listed in short runs too as 9.10 :)

MJH,

After a plethora of failed downloads (well, 14) with various PASCALS, SDOERR_CASP10s and the like, I've had several of the new CUDA80 items actual get to the point of running with the following results:

* failed using application v9.05 (per https://www.gpugrid.net/result.php?resultid=15432601)
* failed using application v9.10 (per https://www.gpugrid.net/result.php?resultid=15433137)
* failed using application v9.10 (per https://www.gpugrid.net/result.php?resultid=15433749)

There are more downloading, but I suspect they'll also fail; if I get a successful run, I'll post again.

Note: I'm using BOINC 7.6.22 on Windows 7 Pro SP1 (64bit) with NVIDIA GTX1060 (3GB) running v372.70 drivers.

Cheers
Dave

Just tried to get some test apps and it took me three times just do download the main DLL. Now, after successfully downloading after all, it immediately quit with a crash. Ouch.

Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: acemd.904-80.exe
Anwendungsversion: 0.0.0.0
Anwendungszeitstempel: 58100aa4
Fehlermodulname: ntdll.dll
Fehlermodulversion: 6.3.9600.18438
Fehlermodulzeitstempel: 57ae642e
Ausnahmecode: c000007b
Ausnahmeoffset: 00000000000ecdd0
Betriebsystemversion: 6.3.9600.2.0.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: ac05
Zusatzinformation 2: ac0507478d1c5bd693cfc4fe3987e900
Zusatzinformation 3: ac05
Zusatzinformation 4: ac0507478d1c5bd693cfc4fe3987e900


Edit: my GPU is a Palit GTX 1070 Super Jetstream.
Driver is 10.18.13.6839
OS is Win8.1/64 Bit

---

I would love to see HCF1 protein folding and interaction simulations to help my little boy... someday.

All three with

(unknown error) - exit code -1073741515 (0xc0000135)

- which is very far from being an 'unknown' error: it's the extremely common NTSTATUS error

0xC0000135
STATUS_DLL_NOT_FOUND
{Unable To Locate Component} 
This application has failed to start because %hs was not found. Reinstalling the application might fix this problem.

Recommended action: check all application dependencies using Dependency Walker, and compare with the files supplied and listed in the <app_version> segment of client_state.xml

All three with

(unknown error) - exit code -1073741515 (0xc0000135)

I've got the same error.

All three with

(unknown error) - exit code -1073741515 (0xc0000135)

I've got the same error.

So, we need to find out which (needed) DLL matt has forgotten to define in app_version. Sorry, I don't own a Pascal card (yet): it's down to you early adopters to debug.

So, we need to find out which (needed) DLL matt has forgotten to define in app_version. Sorry, I don't own a Pascal card (yet): it's down to you early adopters to debug.

CUDART64.DLL - missing underscore at the 1st character in the file name
CUFFT64_80.DLL - missing underscore at the 1st character in the file name
TCL86.DLL - missing underscore at the 1st character in the file name

So, we need to find out which (needed) DLL matt has forgotten to define in app_version. Sorry, I don't own a Pascal card (yet): it's down to you early adopters to debug.

Richard -- are you saying you got the app but dont have a Pascal card? That shouldn't have happened! Could you link to the WU/result please?

CUDART64.DLL - missing underscore at the 1st character in the file name
CUFFT64_80.DLL - missing underscore at the 1st character in the file name
TCL86.DLL - missing underscore at the 1st character in the file name

[/quote]

There are 3 aux files -- cudart64_80.dll cufft64_80.dll and tcl86.dll . I'm distributing those with underscore prefixes, but then they make it into the BOINC slot directory they should be named without the _.

Could you inspect the slot directory and see what's there, please?
Althernatively, if you cant get to a slot directory, rename the files without the _'s and try dependency walker again.

So, we need to find out which (needed) DLL matt has forgotten to define in app_version. Sorry, I don't own a Pascal card (yet): it's down to you early adopters to debug.

CUDART64.DLL - missing underscore at the 1st character in the file name
CUFFT64_80.DLL - missing underscore at the 1st character in the file name
TCL86.DLL - missing underscore at the 1st character in the file name

I've copied the filed without the leading "_", but the dependency walker still shows a lot of yellow question marks. It's so many, that I think it's caused by a missing compiler option or something similar.
API-MS-WIN-CORE-HANDLE-L1-1-0.DLL
API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL
API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL
(Thousands of similar)
EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL
EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOYONECORE-L1-1-0.DLL
....
EXT-MS-WIN-GDI-PATH-L1-1-0.DLL
EXT-MS-WIN-NTUSER-SYNCH-L1-1-0.DLL

Could you inspect the slot directory and see what's there, please?
Althernatively, if you cant get to a slot directory, rename the files without the _'s and try dependency walker again.

It's ok in the slot directory.

BTW the exe I've received is acemd.904-80.exe
Is it okay? (9.04)

API-MS-WIN-CORE-HANDLE-L1-1-0.DLL
API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL
API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL
(Thousands of similar)
EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL
EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOYONECORE-L1-1-0.DLL
....
EXT-MS-WIN-GDI-PATH-L1-1-0.DLL
EXT-MS-WIN-NTUSER-SYNCH-L1-1-0.DLL

And when it ran inside dependency walker, did it complete (text console opens, a few lines are output briefly, then it closes) or did you get an error dialog?

BTW the exe I've received is acemd.904-80.exe
Is it okay? (9.04)

Yep, 9.04 is right

So, we need to find out which (needed) DLL matt has forgotten to define in app_version. Sorry, I don't own a Pascal card (yet): it's down to you early adopters to debug.

Richard -- are you saying you got the app but dont have a Pascal card? That shouldn't have happened! Could you link to the WU/result please?

No, not me - I looked at the results (failures) reported by others, and tried to analyse what the problems were from there.

My maximum capability is GTX 970 at the moment, and I'm still getting app v8.48 as expected.

Edit - my local trade counter has some GTX 1050 Ti in stock - I could pick one up in the morning if you're still stuck.

API-MS-WIN-CORE-HANDLE-L1-1-0.DLL
API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL
API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL
(Thousands of similar)
EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL
EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOYONECORE-L1-1-0.DLL
....
EXT-MS-WIN-GDI-PATH-L1-1-0.DLL
EXT-MS-WIN-NTUSER-SYNCH-L1-1-0.DLL

Could you try installing the Visual Studio 2010 Redistributables

https://www.microsoft.com/en-US/download/details.aspx?id=14632

All three with

(unknown error) - exit code -1073741515 (0xc0000135)

I've got the same error.

All WU are erroring out:
1073741515 (0xffffffffc0000135) Unknown error number on 5-MJHARVEY_PASCALx4002-0-10-RND1192_4 and
App acemd 9.04-80 has stopped responding with regular CASP short WU on Maxwell [-1073741515 (0xffffffffc0000135) Unknown error number.]
Every WU download has a file that stalls.

EDIT- App acemd 9.04-80 has stopped responding details fault module as zlib.dll version 6.3.9600.17736

My host not allowe anymore tasks - I've used up daily quota of WU due to errors. Maybe a reset or change to a higher amount for beta testing would help?

API-MS-WIN-CORE-HANDLE-L1-1-0.DLL
API-MS-WIN-CORE-RTLSUPPORT-L1-2-0.DLL
API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL
(Thousands of similar)
EXT-MS-WIN-NTDSAPI-ACTIVEDIRECTORYCLIENT-L1-1-1.DLL
EXT-MS-WIN-APPXDEPLOYMENTCLIENT-APPXDEPLOYONECORE-L1-1-0.DLL
....
EXT-MS-WIN-GDI-PATH-L1-1-0.DLL
EXT-MS-WIN-NTUSER-SYNCH-L1-1-0.DLL

Could you try installing the Visual Studio 2010 Redistributables

https://www.microsoft.com/en-US/download/details.aspx?id=14632

It might be worth simply double-clicking on the executable file - completely outside the BOINC environment. Last time I had an app fail to run, it popped up a dialog to say which runtime version was missing - and there's a %hs placeholder in that NTSTATUS description, which might get populated and displayed.

It might be worth simply double-clicking on the executable file - completely outside the BOINC environment. Last time I had an app fail to run, it popped up a dialog to say which runtime version was missing - and there's a %hs placeholder in that NTSTATUS description, which might get populated and displayed.

This method gives the error saying zlib1.dll is missing :)