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

Advanced search

Message boards : Number crunching : (unknown error) - exit code -1073741515 (0xc0000135)

Author Message
corris
Avatar
Send message
Joined: 6 Mar 15
Posts: 11
Credit: 3,672,272,554
RAC: 9,114,542
Message 21348 - Posted: 28 Sep 2015, 16:42:20 UTC

All WUs suddenly erroring with this error code in stderr output

Running intel gpu opencl 1.1




Are intel WUs now unsupported?





Please advise if anyone has a clue



Thanks

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 2
Message 21349 - Posted: 28 Sep 2015, 16:50:15 UTC - in response to Message 21348.

All WUs suddenly erroring with this error code in stderr output
Running intel gpu opencl 1.1
Are intel WUs now unsupported?
Please advise if anyone has a clue
Thanks


Which platform?
Which application?
Since you have hidden everything, all we can do is guess. So.... here goes.
I'm guessing you are now getting sieve workunits and that you don't have the latest Microsoft C++ runtime for both 32 and 64 bit platforms. If that isn't the case, then more information will be needed.

corris
Avatar
Send message
Joined: 6 Mar 15
Posts: 11
Credit: 3,672,272,554
RAC: 9,114,542
Message 21351 - Posted: 29 Sep 2015, 0:14:33 UTC - in response to Message 21349.

Yep, I seem to have moved onto sieve from the minis I was running before

win7 pro 64bit on intel HD Graphics 4000 (1624MB) OpenCL: 1.01


Trawled the net for MS c++ runtime, got directed to these 2 files & so installed them : vcredist_x64.exe & vcredist_x86.exe ( no idea if these are the correct files)


Tried to download again but boinc event log says there are no intel WUs available




Any ideas or has Intel been dropped?

corris
Avatar
Send message
Joined: 6 Mar 15
Posts: 11
Credit: 3,672,272,554
RAC: 9,114,542
Message 21354 - Posted: 29 Sep 2015, 7:33:22 UTC - in response to Message 21351.

I am now getting intel gpu sieve WUs

Still same error code, but now some (very) few seconds processing until error - before installing the 2 files above processing was 0.00 seconds before error

At a guess, I've got the wrong 2 files ... any ideas which are the correct ones?


Thanks

Profile [AF>HFR>RR] Jim PROFIT
Send message
Joined: 12 Jul 09
Posts: 8
Credit: 361,937,272
RAC: 51,535
Message 21394 - Posted: 3 Oct 2015, 3:35:40 UTC

Same issue for me.
Microsoft C++ runtime for both 32 and 64 bit platforms installed and error seem to be gone;
But why I can't use CUDA apps?

Stick
Send message
Joined: 30 Apr 10
Posts: 20
Credit: 10,818,888
RAC: 51,892
Message 21484 - Posted: 10 Oct 2015, 21:23:37 UTC

I've got basically the same issue on computer 68709. The error messages are slightly different different: -1073741819 (0xffffffffc0000005) Unknown error number - but the symptoms are the same. The stderr txt says: Unhandled Exception Detected... Reason: Access Violation (0xc0000005) at address 0x000000007779AC04 write attempt to address 0x00000024.

And my Microsoft Visual C++ runtime files are up to date. I even did repair re-installs of them just in case they were damaged.

Note that my GPU is an AMD and the errors are with Collatz Sieve v1.21 (opencl_amd_gpu). And it never had any problems with the now deprecated Large and Solo apps.

Stick
Send message
Joined: 30 Apr 10
Posts: 20
Credit: 10,818,888
RAC: 51,892
Message 21497 - Posted: 11 Oct 2015, 21:54:44 UTC - in response to Message 21484.
Last modified: 11 Oct 2015, 22:12:29 UTC

I've got basically the same issue on computer 68709. The error messages are slightly different different: -1073741819 (0xffffffffc0000005) Unknown error number - but the symptoms are the same. The stderr txt says: Unhandled Exception Detected... Reason: Access Violation (0xc0000005) at address 0x000000007779AC04 write attempt to address 0x00000024.

And my Microsoft Visual C++ runtime files are up to date. I even did repair re-installs of them just in case they were damaged.

Note that my GPU is an AMD and the errors are with Collatz Sieve v1.21 (opencl_amd_gpu). And it never had any problems with the now deprecated Large and Solo apps.

Nevermind! I just updated my GPU driver to the latest version of Catalyst (v15.7.1) and downloaded some new WU's. It's still early, but the first task didn't crash immediately and seems to be progressing OK. I would also note that my old driver wasn't that old - probably less than a year.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 2
Message 21507 - Posted: 13 Oct 2015, 2:32:08 UTC - in response to Message 21497.

I've got basically the same issue on computer 68709. The error messages are slightly different different: -1073741819 (0xffffffffc0000005) Unknown error number - but the symptoms are the same. The stderr txt says: Unhandled Exception Detected... Reason: Access Violation (0xc0000005) at address 0x000000007779AC04 write attempt to address 0x00000024.

And my Microsoft Visual C++ runtime files are up to date. I even did repair re-installs of them just in case they were damaged.

Note that my GPU is an AMD and the errors are with Collatz Sieve v1.21 (opencl_amd_gpu). And it never had any problems with the now deprecated Large and Solo apps.

Nevermind! I just updated my GPU driver to the latest version of Catalyst (v15.7.1) and downloaded some new WU's. It's still early, but the first task didn't crash immediately and seems to be progressing OK. I would also note that my old driver wasn't that old - probably less than a year.


The AMD drivers for Apple almost all crash. It looks like their "new" drivers are several years old. It has mostly to do with the way it does the optimization. The newer drivers seem to be able to handle both reading and writing to the kernel parameters whereas the older drivers would crash when the kernel tried to write to a parameter after it had previously read from the same variable. At lease PCs have the ability to update the drivers. Apple users are "stuck" with the drivers shipped with the OS version.

Profile sosiris
Send message
Joined: 11 Dec 13
Posts: 123
Credit: 55,800,869
RAC: 0
Message 21751 - Posted: 17 Nov 2015, 7:51:39 UTC - in response to Message 21507.


The AMD drivers for Apple almost all crash. It looks like their "new" drivers are several years old. It has mostly to do with the way it does the optimization. The newer drivers seem to be able to handle both reading and writing to the kernel parameters whereas the older drivers would crash when the kernel tried to write to a parameter after it had previously read from the same variable. At lease PCs have the ability to update the drivers. Apple users are "stuck" with the drivers shipped with the OS version.


Should I adjust the kernel code so that the kernel uses different buffers for reading /writing?
____________
Sosiris, team BOINC@Taiwan

Profile heffalumpen
Send message
Joined: 2 Mar 11
Posts: 15
Credit: 1,021,822,925
RAC: 1,207,035
Message 21755 - Posted: 18 Nov 2015, 12:27:20 UTC
Last modified: 18 Nov 2015, 12:29:19 UTC

And its the same here,all 1.21 sieve tasks error out,with this message:-1073741515 (0xffffffffc0000135) Unknown error number. So,what to do?

My computer:128783 at work,the same thing with my home computer.


Post to thread

Message boards : Number crunching : (unknown error) - exit code -1073741515 (0xc0000135)


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.