1073741205 Error Code (Unknown Error)

Message boards : Number crunching : 1073741205 Error Code (Unknown Error)
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 3 · 4 · 5 · 6

AuthorMessage
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22158
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1793196 - Posted: 3 Jun 2016, 19:51:43 UTC - in response to Message 1793151.  

William - I tried to get the, what for me is a 1 in 100 restart fault, and failed to get any issues on the old application this afternoon, so its going to be a long haul job. As I said - it passed the first test, many more rounds to go, including stability.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1793196 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1793248 - Posted: 4 Jun 2016, 2:51:00 UTC - in response to Message 1793187.  
Last modified: 4 Jun 2016, 3:10:42 UTC

...On the one hand, it makes no sense for the target OS to dictate what error code the loader is going to return. It's not your program that's going to receive the error code!

On the other hand, programs targeting different OS versions and different subsystem might take different routes through the loader. One codepath might return STATUS_DLL_INIT_FAILED and another path might return STATUS_DLL_INIT_FAILED_LOGOFF. As it happens, the program are compiled for different subsystem:
...


Yes definitely a conundrum for Boinc and windows to duke out (wrt Error codes and starting stuff during shutdown).

Lack of consistency on the choice of subsystem could be a thing, As Jeff mentioned different behaviour between the GPU apps and some or another CPU app.

I probably need to have an invisible window-handler in the future, for driving an OpenGL/Vulkan renderloop to feed the GPUs and CPU threads in a throttle-able way. So it would make sense to me if the client could handle both situations sensibly.

[Edit:] perhaps adding another layer of complexity, the 32 bit apps on x64 will be running via WoW32... I imagine anything in that would have to be force shutdown before the native space cleanup can complete, so apps disappearing before Boinc realises what's going on could be a thing.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1793248 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1793272 - Posted: 4 Jun 2016, 5:33:50 UTC - in response to Message 1792760.  

I'm getting the sense that if we really looked for them, we'd find that this is becoming an increasingly common error and something worth keeping an eye on to see if it's possible to nail down the configurations where it occurs.

Well, to kill a half hour or so before bedtime, I decided to go looking. It wasn't that difficult to find several more hosts that have recently experienced this error. Some of the configurations are ones that we've seen before, but there are a couple new ones, too.

7972610 - Windows 7 - BOINC 7.6.22
5630554 - Windows 7 - BOINC 7.6.22
7987945 - Windows 7 - BOINC 7.6.22
7995362 - Windows 7 - BOINC 7.6.22
7177464 - Windows 7 - BOINC 7.0.64
7031086 - Windows 7 - BOINC 7.0.64
7370900 - Windows 7 - BOINC 7.0.64
7032239 - Windows 7 - BOINC 7.0.64
7364388 - Windows Server 2008 "R2" - BOINC 7.2.42

Some of them just have one or two of the errors currently in their task lists, others a dozen or so, but I think I saw one with over 40. I'm pretty sure all were CPU tasks.

Ahhh...that should help put me to sleep. ;^)
ID: 1793272 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1793700 - Posted: 5 Jun 2016, 16:50:47 UTC

Just ran across a host, 7321604, which has gotten some of these errors on v8.12 (opencl_intel_gpu_sah), in addition to CPU tasks. That's the first time I've seen that happen. The host is running Windows 7, BOINC 7.2.42.
ID: 1793700 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1794020 - Posted: 6 Jun 2016, 17:19:35 UTC

I just ran a shutdown test of the BOINC 7.6.33 version. It doesn't seem to have fixed the problem. The results appear to be about the same as that test I ran a few days ago of Richard's private build.
06-Jun-2016 10:00:45 [SETI@home] Started upload of 30my10aa.24060.21335.8.35.46_0_0
06-Jun-2016 10:00:53 [SETI@home] Finished upload of 30my10aa.24060.21335.8.35.46_0_0
06-Jun-2016 10:01:29 [SETI@home] Task 31mr10ac.31259.11122.7.34.193_1 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task 30my10aa.12339.476.14.41.113_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 exited with zero status but no 'finished' file
06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.11122.7.34.193_1 using setiathome_v8 version 800 (cuda50) in slot 8
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 6
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 3
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task 30my10aa.12339.476.14.41.113_0 using setiathome_v8 version 800 in slot 18
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7
06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 using setiathome_v8 version 800 in slot 11
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18897.416.17.26.187.vlar_1 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18799.831.18.27.189.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.6571.13052.11.38.24_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.18777.17654.12.39.199_1 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.12339.19699.14.41.124_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] Task 29au10ad.31633.244789.12.39.72_2 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] Task 31mr10ac.31259.11122.7.34.193_1 exited with a DLL initialization error.
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 exited with a DLL initialization error.
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 exited with a DLL initialization error.
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with a DLL initialization error.
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 exited with a DLL initialization error.
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 exited with a DLL initialization error.
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.12339.476.14.41.113_0 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with a DLL initialization error.
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 exited with zero status but no 'finished' file
06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18897.416.17.26.187.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 0
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18799.831.18.27.189.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 19
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.6571.13052.11.38.24_0 using setiathome_v8 version 800 in slot 12
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.18777.17654.12.39.199_1 using setiathome_v8 version 800 in slot 13
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.12339.19699.14.41.124_0 using setiathome_v8 version 800 (cuda50) in slot 10
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 29au10ad.31633.244789.12.39.72_2 using setiathome_v8 version 800 in slot 1
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.11122.7.34.193_1 using setiathome_v8 version 800 (cuda50) in slot 8
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 6
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 3
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.12339.476.14.41.113_0 using setiathome_v8 version 800 in slot 18
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7
06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 using setiathome_v8 version 800 in slot 11
06-Jun-2016 10:04:40 [---] Starting BOINC client version 7.6.33 for windows_intelx86
06-Jun-2016 10:04:40 [---] log flags: file_xfer, sched_ops, task, cpu_sched

Fortunately, the shutdown didn't take long enough for any of the CPU tasks to error out, even though about half of them did restart once.
ID: 1794020 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14649
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1794034 - Posted: 6 Jun 2016, 17:55:42 UTC - in response to Message 1794020.  

I just ran a shutdown test of the BOINC 7.6.33 version. It doesn't seem to have fixed the problem. The results appear to be about the same as that test I ran a few days ago of Richard's private build.

No surprise there - the private and public builds were made from the same source code.

But the question is - does the new build, either version, reduce the number that fall all the way through to 0xC000026B?

Temporary exits are untidy and to be avoided if possible, but are nothing like as serious as task errors. If we've eliminated the real horrors, I can live with the untidiness.
ID: 1794034 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1794044 - Posted: 6 Jun 2016, 18:11:45 UTC - in response to Message 1794034.  

But the question is - does the new build, either version, reduce the number that fall all the way through to 0xC000026B?

Temporary exits are untidy and to be avoided if possible, but are nothing like as serious as task errors. If we've eliminated the real horrors, I can live with the untidiness.

Funny, I would have thought any effort should have been directed toward fixing the broken leg, not just putting a bandage on it. Ah, well, socialized medicine seeps into everything eventually, I guess. ;^)

I'll have to see if I can manage to test that minor fix without sacrificing more than a couple of my CPU tasks.
ID: 1794044 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1794060 - Posted: 6 Jun 2016, 19:05:03 UTC

Okay, I suspended all my CPU tasks, both running and ready to start, except for 3 freshly launched tasks (so that I wouldn't lose too much if they failed), launched Process Monitor, then did a system shutdown/restart. The results, limited though they are, look encouraging as far as the Band-aid goes.

06-Jun-2016 11:26:18 [SETI@home] task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 suspended by user
06-Jun-2016 11:26:19 [SETI@home] [cpu_sched] Preempting blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 (removed from memory)
06-Jun-2016 11:27:05 [SETI@home] Task 30my10aa.7465.20108.15.42.50_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 30my10aa.7465.21335.15.42.155_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 03se10ab.12907.21748.6.33.177_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 20au10ab.18727.11114.16.43.202_3 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 29au10ad.12786.1707.10.37.44_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 31mr10ac.18449.15621.8.35.184_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.20108.15.42.50_0 using setiathome_v8 version 800 (cuda50) in slot 2
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.21335.15.42.155_0 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.21748.6.33.177_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 20au10ab.18727.11114.16.43.202_3 using setiathome_v8 version 800 in slot 20
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 29au10ad.12786.1707.10.37.44_2 using setiathome_v8 version 800 in slot 21
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 31mr10ac.18449.15621.8.35.184_0 using setiathome_v8 version 800 in slot 22
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 03se10ab.12907.13977.6.33.87_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 03se10ab.12907.16840.6.33.67_1 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 30my10aa.7465.20108.15.42.50_0 exited with a DLL initialization error.
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:07 [SETI@home] Task 30my10aa.7465.21335.15.42.155_0 exited with a DLL initialization error.
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:07 [SETI@home] Task 03se10ab.12907.21748.6.33.177_0 exited with a DLL initialization error.
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:07 [SETI@home] Task 20au10ab.18727.11114.16.43.202_3 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 29au10ad.12786.1707.10.37.44_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 31mr10ac.18449.15621.8.35.184_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 16
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 19
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 using setiathome_v8 version 800 (cuda50) in slot 10
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.13977.6.33.87_0 using setiathome_v8 version 800 (cuda50) in slot 0
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.16840.6.33.67_1 using setiathome_v8 version 800 (cuda50) in slot 8
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.20108.15.42.50_0 using setiathome_v8 version 800 (cuda50) in slot 2
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.21335.15.42.155_0 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.21748.6.33.177_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 20au10ab.18727.11114.16.43.202_3 using setiathome_v8 version 800 in slot 20
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 29au10ad.12786.1707.10.37.44_2 using setiathome_v8 version 800 in slot 21
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 31mr10ac.18449.15621.8.35.184_0 using setiathome_v8 version 800 in slot 22
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 03se10ab.12907.13977.6.33.87_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 03se10ab.12907.16840.6.33.67_1 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 30my10aa.7465.20108.15.42.50_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 30my10aa.7465.21335.15.42.155_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 03se10ab.12907.21748.6.33.177_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 20au10ab.18727.11114.16.43.202_3 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task 29au10ad.12786.1707.10.37.44_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task 31mr10ac.18449.15621.8.35.184_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 6
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 3
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 16
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 19
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 using setiathome_v8 version 800 (cuda50) in slot 10
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.13977.6.33.87_0 using setiathome_v8 version 800 (cuda50) in slot 0
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.16840.6.33.67_1 using setiathome_v8 version 800 (cuda50) in slot 8
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.20108.15.42.50_0 using setiathome_v8 version 800 (cuda50) in slot 2
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.21335.15.42.155_0 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.21748.6.33.177_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 20au10ab.18727.11114.16.43.202_3 using setiathome_v8 version 800 in slot 20
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 29au10ad.12786.1707.10.37.44_2 using setiathome_v8 version 800 in slot 21
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 31mr10ac.18449.15621.8.35.184_0 using setiathome_v8 version 800 in slot 22
06-Jun-2016 11:29:37 [---] Starting BOINC client version 7.6.33 for windows_intelx86
06-Jun-2016 11:29:37 [---] log flags: file_xfer, sched_ops, task, cpu_sched

I've highlighted one of the three CPU tasks in the Event Log, above. All 3 seem to have behaved the same. Each was apparently shut down by Windows 3 times, then restarted by BOINC 3 times before the system finished shutting down. None of them actually displayed the DLL Initialization error (unlike the GPU tasks), but I don't suppose that's definitive as to whether or not they actually encountered them. They all restarted successfully after the system restart.

A look at the Stderr from Slot 20 for the highlighted task shows:

Build features: SETI8	Non-graphics	FFTW	USE_SSE3	x86	
     CPUID: Quad-Core AMD Opteron(tm) Processor 2389 

     Cache: L1=64K L2=512K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSE4A 
ar=0.414118  NumCfft=199195  NumGauss=1141825356  NumPulse=226448017394  NumTriplet=452862338944
In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768

Windows optimized setiathome_v8 application
Based on Intel, Core 2-optimized v8-nographics V5.13 by Alex Kan
SSE3xj Win32 Build 3330 , Ported by : Raistmer, JDWhale

SETI8 update by Raistmer
Work Unit Info:
...............
Credit multiplier is :  2.85
WU true angle range is :  0.414118

Build features: SETI8	Non-graphics	FFTW	USE_SSE3	x86	
     CPUID: Quad-Core AMD Opteron(tm) Processor 2389 

     Cache: L1=64K L2=512K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSE4A 
ar=0.414118  NumCfft=199195  NumGauss=1141825356  NumPulse=226448017394  NumTriplet=452862338944
In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768

Windows optimized setiathome_v8 application
Based on Intel, Core 2-optimized v8-nographics V5.13 by Alex Kan
SSE3xj Win32 Build 3330 , Ported by : Raistmer, JDWhale

SETI8 update by Raistmer
Work Unit Info:
...............
Credit multiplier is :  2.85
WU true angle range is :  0.414118

Although it doesn't display any timestamps, it appears to show the task only restarting once, which I assume would be the restart after the system restart.
ID: 1794060 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1794063 - Posted: 6 Jun 2016, 19:31:52 UTC - in response to Message 1794060.  


Although it doesn't display any timestamps, it appears to show the task only restarting once, which I assume would be the restart after the system restart.

or prev restarts were before app aquired redirected to file stderr to say anything at its death.
ID: 1794063 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1795953 - Posted: 13 Jun 2016, 20:14:14 UTC

I did a bit testing. I created two 32-bit test applications with VS2010's New project wizard. One was a Win32 application and the other one a Win32 console application. Neither created any windows or had any dependencies. The program code for both consisted of only a Sleep(INFINITE). The only difference between the two apps was subsystem.

Then I created a third application which launches one copy of both test applications, sleeps one second, checks if the apps are still running and re-starts them if necessary. In other words, a bare bones BOINC client.

On 32-bit Windows 7 SP1 with approximately no updates on top of the SP, after I initiated the reboot, both apps failed to re-start with c0000142=STATUS_DLL_INIT_FAILED error.

On fully updated 64-bit Windows 7, after I initiated the reboot, the GUI app failed to re-start with c000026b=STATUS_DLL_INIT_FAILED_LOGOFF error. The console app continued to fail to re-start with c0000142=STATUS_DLL_INIT_FAILED error.

Since the subsystem of the apps seems to be the key here, I think it would be best for Raistmer and Eric to rebuild their apps as console applications. Even though a new version of client is out that can handle the new error code it will take a good while before everyone has updated to the new version.
ID: 1795953 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1795960 - Posted: 13 Jun 2016, 21:09:56 UTC - in response to Message 1795953.  

On 32-bit Windows 7 SP1 with approximately no updates on top of the SP, after I initiated the reboot, both apps failed to re-start with c0000142=STATUS_DLL_INIT_FAILED error.

On fully updated 64-bit Windows 7, after I initiated the reboot, the GUI app failed to re-start with c000026b=STATUS_DLL_INIT_FAILED_LOGOFF error. The console app continued to fail to re-start with c0000142=STATUS_DLL_INIT_FAILED error.

Those references reminded me that I had intended to check my Windows updates from April to see if I could notice anything that might have caused these task errors to suddenly start appearing (at least on my 2 Win7 boxes) only beginning in late April, even though the "restart during shutdown" behavior has been occurring for much longer.

So, I just did that and I ran across a curious security update, KB3145739, which also includes "Non-security-related fixes that are included in this security update", to wit:
When you repeatedly run a script in session 0, a "0xc0000142" error is recorded in the System event log. In some cases, you may receive a "0xc0000142" error message in a popup window.

For example, this problem may occur if you use task scheduler to start a batch file (*.bat). In this scenario, Windows starts the cmd.exe process, and then the 0xc0000142 error occurs.

Is it possible that in trying to eliminate the 0xc0000142 error in these particular circumstances, Microsoft exposed the 0xc000026b error in other cases? Would it be worthwhile, or even possible, to install this update on your 32-bit machine and rerun your test, to see if the results are altered?

BTW, I installed this particular Windows update on my two Win 7 boxes (both of which have gotten the errors) on April 22, on my Win 8.1 box (which gets the "restart during shutdown" occasionally, but no errors, yet) on April 13, and my Win Vista box (no restarts and no errors, so far) on April 22.
ID: 1795960 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1796583 - Posted: 16 Jun 2016, 12:49:54 UTC - in response to Message 1795960.  

Installed KB3145739 on the 32-bit Windows and now it matches the 64-bit Windows.
ID: 1796583 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1796658 - Posted: 16 Jun 2016, 17:28:32 UTC - in response to Message 1796583.  

Installed KB3145739 on the 32-bit Windows and now it matches the 64-bit Windows.

So, that would definitely seem to point to the KB3145739 update as being the trigger for the recent appearance of the 0xc000026b errors. It's too bad that Microsoft bundled that change into a security update. Otherwise, rolling back the update might be another workaround to avoid the error, since any fix in a future BOINC version might never get implemented by some users. However, I don't think it would be wise to back out a Windows security update.
ID: 1796658 · Report as offensive
Juha
Volunteer tester

Send message
Joined: 7 Mar 04
Posts: 388
Credit: 1,857,738
RAC: 0
Finland
Message 1796675 - Posted: 16 Jun 2016, 18:56:54 UTC - in response to Message 1796658.  

It's too bad that Microsoft bundled that change into a security update.


Hard to tell without seeing the changeset but it might have been a defence-in-depth change with some visible changes. Usually programs shouldn't need to know what error codes the OS might return when it doesn't want to start another program. All normal programs need to know is that it failed. BOINC is in an unfortunate situation where it actually has a good reason to know such details.
ID: 1796675 · Report as offensive
Harri Liljeroos
Avatar

Send message
Joined: 29 May 99
Posts: 3988
Credit: 85,281,665
RAC: 126
Finland
Message 1796891 - Posted: 17 Jun 2016, 18:14:59 UTC

Today I got 26 WU fail with this error while I was updating windows. One software refused to close while Windows was shutting down and Windows showed that this software was prohibiting windows shutdown. So I had to cancel the Windows restart and kill the stuck software and then do the restart. Unfortunately 26 WUs were trashed during this.

I'm now uninstalling the KB3145739 and see what this does.
ID: 1796891 · Report as offensive
atlov

Send message
Joined: 11 Aug 12
Posts: 35
Credit: 32,718,664
RAC: 34
Germany
Message 1796895 - Posted: 17 Jun 2016, 19:14:04 UTC - in response to Message 1796891.  

Today I got 26 WU fail with this error while I was updating windows. One software refused to close while Windows was shutting down and Windows showed that this software was prohibiting windows shutdown. So I had to cancel the Windows restart and kill the stuck software and then do the restart. Unfortunately 26 WUs were trashed during this.

I'm now uninstalling the KB3145739 and see what this does.

To be honest, that's the first time I see GPU WUs trashing this way.
ID: 1796895 · Report as offensive
Profile Jeff Buck Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 11 Feb 00
Posts: 1441
Credit: 148,764,870
RAC: 0
United States
Message 1796896 - Posted: 17 Jun 2016, 19:17:39 UTC - in response to Message 1796895.  

Today I got 26 WU fail with this error while I was updating windows. One software refused to close while Windows was shutting down and Windows showed that this software was prohibiting windows shutdown. So I had to cancel the Windows restart and kill the stuck software and then do the restart. Unfortunately 26 WUs were trashed during this.

I'm now uninstalling the KB3145739 and see what this does.

To be honest, that's the first time I see GPU WUs trashing this way.

It's from one of the OpenCL apps, which behave like the CPU apps in this situation. The CUDA apps don't get that same error.
ID: 1796896 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7489
Credit: 91,093,184
RAC: 0
Australia
Message 1796990 - Posted: 18 Jun 2016, 3:31:45 UTC

Just a sidenote/point-of-order: I'd advise keeping the applicable update in place, because trying to launch processes during shutdown is a legitimate vector for malware. Perhaps that's not so much a concern for dedicated crunching machines, but in the larger scheme of things it's something the Boinc client needs to change its behaviour with.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1796990 · Report as offensive
Previous · 1 . . . 3 · 4 · 5 · 6

Message boards : Number crunching : 1073741205 Error Code (Unknown Error)


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.