Message boards :
Number crunching :
1073741205 Error Code (Unknown Error)
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · 6 · Next
Author | Message |
---|---|
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
So the damage was all done in the 49:42 second, long before BOINC's own shutdown in the 49:49 second? That's telling us something, though I'm not quite sure what. Probably that BOINC was still starting things up well after Windows had started shutting them down. Thanks. Yes, the original task shutdowns appear to have come from the system. The actual system shutdown appears to have started about 4:48:51 and the first task shutdown at 4:49:01+. So, for over 40 seconds, the whole BOINC environment looks like a game of Whac-A-Mole. I haven't had the time yet to figure out exactly when the BOINC client got the shutdown message, but I'm guessing it's buried somewhere in those 275,858 event messages. ;^) EDIT: After the first round of task shutdowns by the system, I think it was more likely the DLL Initialization errors that were ending the subsequent tasks, rather than anything the system was doing. It's just that BOINC was relentlessly trying to restart them, or start new ones. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Yes, the original task shutdowns appear to have come from the system. The actual system shutdown appears to have started about 4:48:51 and the first task shutdown at 4:49:01+. So, for over 40 seconds, the whole BOINC environment looks like a game of Whac-A-Mole. Some of BOINC's key processes run on a 'once a minute' polling cycle - like, 'do I next to ask a project for more work?'. If "do I need to shut down?" was in a 60-second loop (it shouldn't be, it should be much more responsive than that), a 40-second delay would still be possible. I haven't had the time yet to figure out exactly when the BOINC client got the shutdown message, but I'm guessing it's buried somewhere in those 275,858 event messages. ;^) That's really two questions: when was the shutdown message sent, and when did the BOINC client notice and start acting on it. The answer to both parts should be as near as dammit the same, but we're looking for something where *should* isn't happening. EDIT: After the first round of task shutdowns by the system, I think it was more likely the DLL Initialization errors that were ending the subsequent tasks, rather than anything the system was doing. It's just that BOINC was relentlessly trying to restart them, or start new ones. But it's "the system" (i.e. the Windows OS) which is preventing the DLLs from initialising. I'd rephrase that as "the DLL Initialization errors were ending the subsequent tasks, rather than anything BOINC was doing." |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
Just to wrap up the "last task standing" info, here are all the entries generated by the last GPU task, which was restarted (in Slot 14) much closer to the end of the shutdown window. I've omitted all the boinc.exe entries this time, most of which occur between the 4:49:49.3900936 and 4:49:49.3983733 entries, because I don't see anything that appears to be related to terminating this task. 4:49:49.3900904 PM Lunatics_x41zi_win32_cuda50.exe 1032 Process Start SUCCESS Parent PID: 2768, Command line: projects/setiathome.berkeley.edu/Lunatics_x41zi_win32_cuda50.exe --device 3, Current directory: C:\ProgramData\BOINC\slots\14\, Environment: =C:=C:\ProgramData\BOINC ALLUSERSPROFILE=C:\ProgramData APPDATA=C:\Users\jrbuck\AppData\Roaming CommonProgramFiles=C:\Program Files\Common Files COMPUTERNAME=XW9400 ComSpec=C:\Windows\system32\cmd.exe FP_NO_HOST_CHECK=NO HOMEDRIVE=C: HOMEPATH=\Users\jrbuck LOCALAPPDATA=C:\Users\jrbuck\AppData\Local LOGONSERVER=\\XW9400 NUMBER_OF_PROCESSORS=8 OS=Windows_NT Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\NVIDIA Corporation\PhysX\Common PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER=x86 Family 16 Model 4 Stepping 2, AuthenticAMD PROCESSOR_LEVEL=16 PROCESSOR_REVISION=0402 ProgramData=C:\ProgramData ProgramFiles=C:\Program Files PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC=C:\Users\Public SESSIONNAME=Console SystemDrive=C: SystemRoot=C:\Windows TEMP=C:\Users\jrbuck\AppData\Local\Temp TMP=C:\Users\jrbuck\AppData\Local\Temp USERDOMAIN=xw9400 USERNAME=jrbuck USERPROFILE=C:\Users\jrbuck windir=C:\Windows windows_tracing_flags=3 windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log 4:49:49.3900936 PM Lunatics_x41zi_win32_cuda50.exe 1032 Thread Create SUCCESS Thread ID: 2972 4:49:49.3983733 PM Lunatics_x41zi_win32_cuda50.exe 1032 Load Image C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\Lunatics_x41zi_win32_cuda50.exe SUCCESS Image Base: 0x140000, Image Size: 0x69d000 4:49:49.3984986 PM Lunatics_x41zi_win32_cuda50.exe 1032 Load Image C:\Windows\System32\ntdll.dll SUCCESS Image Base: 0x77440000, Image Size: 0x142000 4:49:49.3986409 PM Lunatics_x41zi_win32_cuda50.exe 1032 CreateFile C:\Windows\Prefetch\LUNATICS_X41ZI_WIN32_CUDA50.E-CF0CD4B6.pf SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: None, AllocationSize: n/a, OpenResult: Opened 4:49:49.3986844 PM Lunatics_x41zi_win32_cuda50.exe 1032 QueryStandardInformationFile C:\Windows\Prefetch\LUNATICS_X41ZI_WIN32_CUDA50.E-CF0CD4B6.pf SUCCESS AllocationSize: 16,384, EndOfFile: 16,150, NumberOfLinks: 1, DeletePending: False, Directory: False 4:49:49.3987158 PM Lunatics_x41zi_win32_cuda50.exe 1032 ReadFile C:\Windows\Prefetch\LUNATICS_X41ZI_WIN32_CUDA50.E-CF0CD4B6.pf SUCCESS Offset: 0, Length: 16,150, Priority: Normal 4:49:49.3987511 PM Lunatics_x41zi_win32_cuda50.exe 1032 CloseFile C:\Windows\Prefetch\LUNATICS_X41ZI_WIN32_CUDA50.E-CF0CD4B6.pf SUCCESS 4:49:49.3987666 PM Lunatics_x41zi_win32_cuda50.exe 1032 IRP_MJ_CLOSE C:\Windows\Prefetch\LUNATICS_X41ZI_WIN32_CUDA50.E-CF0CD4B6.pf SUCCESS 4:49:49.3990639 PM Lunatics_x41zi_win32_cuda50.exe 1032 CreateFile C:\ProgramData\BOINC\slots\14 SUCCESS Desired Access: Execute/Traverse, Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a, OpenResult: Opened 4:49:49.3992384 PM Lunatics_x41zi_win32_cuda50.exe 1032 Load Image C:\Windows\System32\kernel32.dll SUCCESS Image Base: 0x765c0000, Image Size: 0xd5000 4:49:49.3994079 PM Lunatics_x41zi_win32_cuda50.exe 1032 Load Image C:\Windows\System32\KernelBase.dll SUCCESS Image Base: 0x75510000, Image Size: 0x4b000 4:49:49.4062692 PM Lunatics_x41zi_win32_cuda50.exe 1032 Thread Exit SUCCESS Thread ID: 2972, User Time: 0.0000000, Kernel Time: 0.0000000 4:49:49.4063041 PM Lunatics_x41zi_win32_cuda50.exe 1032 QueryNameInformationFile C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\Lunatics_x41zi_win32_cuda50.exe SUCCESS Name: \ProgramData\BOINC\projects\setiathome.berkeley.edu\Lunatics_x41zi_win32_cuda50.exe 4:49:49.4063416 PM Lunatics_x41zi_win32_cuda50.exe 1032 QueryNameInformationFile C:\Windows\System32\KernelBase.dll SUCCESS Name: \Windows\System32\KernelBase.dll 4:49:49.4063670 PM Lunatics_x41zi_win32_cuda50.exe 1032 QueryNameInformationFile C:\Windows\System32\kernel32.dll SUCCESS Name: \Windows\System32\kernel32.dll 4:49:49.4063942 PM Lunatics_x41zi_win32_cuda50.exe 1032 QueryNameInformationFile C:\Windows\System32\ntdll.dll SUCCESS Name: \Windows\System32\ntdll.dll 4:49:49.4064210 PM Lunatics_x41zi_win32_cuda50.exe 1032 QueryNameInformationFile C:\Windows\System32\apisetschema.dll SUCCESS Name: \Windows\System32\apisetschema.dll 4:49:49.4064690 PM Lunatics_x41zi_win32_cuda50.exe 1032 Process Exit SUCCESS Exit Status: -1073741502, User Time: 0.0000000 seconds, Kernel Time: 0.0000000 seconds, Private Bytes: 6,258,688, Peak Private Bytes: 6,348,800, Working Set: 868,352, Peak Working Set: 868,352 4:49:49.4064782 PM Lunatics_x41zi_win32_cuda50.exe 1032 CloseFile C:\ProgramData\BOINC\slots\14 SUCCESS 4:49:49.4064916 PM Lunatics_x41zi_win32_cuda50.exe 1032 IRP_MJ_CLOSE C:\ProgramData\BOINC\slots\14 SUCCESS One interesting thing I noticed is that the Exit Status for this task is very similar to the one that ends up on the error tasks for the CPU. However, this one happily restarted after the system restart and completed successfully (as did all the other GPU tasks). |
rob smith Send message Joined: 7 Mar 03 Posts: 22204 Credit: 416,307,556 RAC: 380 |
Richard - first test passed OK. Swapped existing boinc.exe for your hand cranked version, restarted BOINC Manager, and didn't loose any tasks :-) Let's see how it behaves for the next few hours..... Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Juha Send message Joined: 7 Mar 04 Posts: 388 Credit: 1,857,738 RAC: 0 |
One interesting thing I noticed is that the Exit Status for this task is very similar to the one that ends up on the error tasks for the CPU. However, this one happily restarted after the system restart and completed successfully (as did all the other GPU tasks). Similar perhaps but different. 4:49:42.3202976 PM MB8_win_x86_SSE3_VS2008_r3330.exe 5096 Process Exit SUCCESS Exit Status: -1073741205, User Time: 0.0000000 seconds, Kernel Time: 0.0000000 seconds, Private Bytes: 892,928, Peak Private Bytes: 897,024, Working Set: 1,961,984, Peak Working Set: 1,966,080 4:49:49.4064690 PM Lunatics_x41zi_win32_cuda50.exe 1032 Process Exit SUCCESS Exit Status: -1073741502, User Time: 0.0000000 seconds, Kernel Time: 0.0000000 seconds, Private Bytes: 6,258,688, Peak Private Bytes: 6,348,800, Working Set: 868,352, Peak Working Set: 868,352 -1073741205 = c000026b = STATUS_DLL_INIT_FAILED_LOGOFF -1073741502 = c0000142 = STATUS_DLL_INIT_FAILED Special handling of STATUS_DLL_INIT_FAILED_LOGOFF was added to the client yesterday, STATUS_DLL_INIT_FAILED has been there much longer. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
MB8_win_x86_SSE3_VS2008_r3330.exe has a dependency on libfftw3f-3-3-4_x64.dll I don't know why the exit behaviour should be different: if anything, I would have said that the CUDA application, which has additional dependencies down the line on the Video driver, which has to run in a user graphics context, would be the one to fail at logoff: SSE3 is capable of running as a service in a system context, and thus survive longer - although it won't be in this case. |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
MB8_win_x86_SSE3_VS2008_r3330.exe has a dependency on libfftw3f-3-3-4_x64.dll Basically these exits arise way before any true application code is reached (as may be evidenced by not opening any Cuda or other DLLs, beyond kernel). [i.e they were summarily killed for starting while Windows was shutting down] "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. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Understood, but I was trying to understand why the behaviour was different. BOINC understood the error message thrown by the application (CUDA) built against a much older API: the newer app, against a newer API, was unrecognised. That could have implications for other projects? |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Understood, but I was trying to understand why the behaviour was different. BOINC understood the error message thrown by the application (CUDA) built against a much older API: the newer app, against a newer API, was unrecognised. That could have implications for other projects? Sure. I usually build to XP spec, maybe someone decided the configuration should be Vista+ so they gain extra random error codes, as Juha Suggested ? "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. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Maybe that's why you don't receive WindowMessages direct from Windows 7? |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
Maybe that's why you don't receive WindowMessages direct from Windows 7? 'My' application is console and has no Window message or console handler. Its messages are received through Boinc shared memory [/boincapi]. [Important point: These applications aren't reaching boincapi initialisation] "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. |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
Richard - first test passed OK. did you reproduce the error behaviour with the old build before you dropped in the new one? can't know if you've cured, if you don't have symptoms in the first place... [and just because you don't have symptoms any more, doesn't mean you've been cured...] A person who won't read has no advantage over one who can't read. (Mark Twain) |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
I'll let Juha work through the implications of all this - I was just trying to bring him up to speed with the characteristics of the two applications he was drawing a distinction between. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
Guess I should be one of the ones testing the new build. Okay, I'll go give it a try on my xw9400 and get back to you folks later. |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
I'll let Juha work through the implications of all this - I was just trying to bring him up to speed with the characteristics of the two applications he was drawing a distinction between. Well no distinction AFAICT, other than I build to XP spec, so am not going to receive error codes in Vista format. "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. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
First attempt with Richard's private BOINC build doesn't look encouraging. 03-Jun-2016 09:34:19 [SETI@home] This computer has reached a limit on tasks in progress 03-Jun-2016 09:36:15 [SETI@home] Task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.238.vlar_0 exited with zero status but no 'finished' file 03-Jun-2016 09:36:15 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:15 [SETI@home] Task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.232.vlar_1 exited with zero status but no 'finished' file 03-Jun-2016 09:36:15 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:15 [SETI@home] Task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.28256.0.18.27.146.vlar_1 exited with zero status but no 'finished' file 03-Jun-2016 09:36:15 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:15 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.238.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 3 03-Jun-2016 09:36:15 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.232.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 0 03-Jun-2016 09:36:15 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.28256.0.18.27.146.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 7 03-Jun-2016 09:36:17 [SETI@home] Task 18no10ab.25389.84724.8.35.214_1 exited with zero status but no 'finished' file 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:17 [SETI@home] Task blc5_2bit_guppi_57451_25670_HIP69732_0021.31763.0.18.27.11.vlar_0 exited with zero status but no 'finished' file 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:17 [SETI@home] Task 18no10ab.25389.84724.8.35.234_1 exited with zero status but no 'finished' file 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:17 [SETI@home] Task 18no10ab.25389.84724.8.35.239_0 exited with zero status but no 'finished' file 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:17 [SETI@home] Task 20au10ab.11405.7429.6.33.59_0 exited with zero status but no 'finished' file 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:17 [SETI@home] Task 20au10ab.11405.7429.6.33.184_1 exited with zero status but no 'finished' file 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reset the project. 03-Jun-2016 09:36:17 [SETI@home] Task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.238.vlar_0 exited with a DLL initialization error. 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reboot your computer. 03-Jun-2016 09:36:17 [SETI@home] Task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.232.vlar_1 exited with a DLL initialization error. 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reboot your computer. 03-Jun-2016 09:36:17 [SETI@home] Task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.28256.0.18.27.146.vlar_1 exited with a DLL initialization error. 03-Jun-2016 09:36:17 [SETI@home] If this happens repeatedly you may need to reboot your computer. 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task 18no10ab.25389.84724.8.35.214_1 using setiathome_v8 version 800 (cuda50) in slot 1 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_25670_HIP69732_0021.31763.0.18.27.11.vlar_0 using setiathome_v8 version 800 in slot 19 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task 18no10ab.25389.84724.8.35.234_1 using setiathome_v8 version 800 (cuda50) in slot 11 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task 18no10ab.25389.84724.8.35.239_0 using setiathome_v8 version 800 (cuda50) in slot 10 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task 20au10ab.11405.7429.6.33.59_0 using setiathome_v8 version 800 (cuda50) in slot 8 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task 20au10ab.11405.7429.6.33.184_1 using setiathome_v8 version 800 (cuda50) in slot 12 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.238.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 3 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.19850.831.17.26.232.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 0 03-Jun-2016 09:36:17 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_26010_HIP69732_OFF_0022.28256.0.18.27.146.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 7 03-Jun-2016 09:38:48 [---] Starting BOINC client version 7.7.0 for windows_intelx86 The shutdown appears to have been quick enough to stave off any tasks actually getting computation errors but the "restart during shutdown" behavior is still there. I think it usually takes a second restart attempt for a task to actually fail. I could probably try running Process Monitor during shutdown again, since that seemed to slow up the shutdown, but I'm not eager to do so unless it's necessary. ;^) EDIT: I see only one of the restarting tasks was a CPU task. There would have been 8 CPU tasks and 12 GPU tasks running at the time of shutdown, so BOINC doesn't appear to have had time to try to restart them all during this particular shutdown. That's typical of normal shutdown behavior (or behaviour, if you prefer). |
jason_gee Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0 |
I could probably try running Process Monitor during shutdown again, since that seemed to slow up the shutdown, but I'm not eager to do so unless it's necessary. ;^) Do it, and put it on an invoice to Berkeley. "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. |
Wiggo Send message Joined: 24 Jan 00 Posts: 34754 Credit: 261,360,520 RAC: 489 |
Now that sounds like a well over committed CPU there. :-O Have you tried using less CPU cores to see if that behaviour persists? Cheers. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
Actually, under S@H v8, that seemed to be just right....prior to guppi VLARs going to the GPU, anyway. Once all the dust settles with those and SoG and such, I do need to revisit it. Have you tried using less CPU cores to see if that behaviour persists? Actually, the problem can be traced back at least as far as last December (when I was running fewer tasks under v7), and I think Richard posted some even earlier examples in other projects. It also occurs here on my daily driver, with only two cores and a single GPU task on a GT630. I'm not sure what some of the other RPs configurations are but it's likely that, while a heavier load might magnify the problem at shutdown, it's not at the root of it. |
Juha Send message Joined: 7 Mar 04 Posts: 388 Credit: 1,857,738 RAC: 0 |
I'll let Juha work through the implications of all this - I was just trying to bring him up to speed with the characteristics of the two applications he was drawing a distinction between. 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: AKv8c_r2549_winx86-64_AVXxjfs.exe: PE32+ executable (GUI) x86-64 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86-64_SSE2xjfs.exe: PE32+ executable (GUI) x86-64 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86-64_SSE3xjfs.exe: PE32+ executable (GUI) x86-64 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86-64_SSE41xjfs.exe: PE32+ executable (GUI) x86-64 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86-64_SSE42xjfs.exe: PE32+ executable (GUI) x86-64 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86-64_SSSE3xjfs.exe: PE32+ executable (GUI) x86-64 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86_AVXxjfs.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86_SSE2xjfs.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86_SSE3xjfs.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86_SSE41xjfs.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86_SSE42xjfs.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows AKv8c_r2549_winx86_SSSE3xjfs.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows AP7_win_x64_AVX_CPU_r2692.exe: PE32+ executable (console) x86-64, for MS Windows AP7_win_x64_SSE2_CPU_r2672.exe: PE32+ executable (console) x86-64, for MS Windows AP7_win_x64_SSE3_CPU_r2692.exe: PE32+ executable (console) x86-64, for MS Windows AP7_win_x86_AVX_CPU_r2692.exe: PE32 executable (GUI) Intel 80386, for MS Windows AP7_win_x86_SSE2_OpenCL_ATI_r2742.exe: PE32 executable (console) Intel 80386, for MS Windows AP7_win_x86_SSE2_OpenCL_Intel_r2742.exe: PE32 executable (console) Intel 80386, for MS Windows AP7_win_x86_SSE2_OpenCL_NV_r2887.exe: PE32 executable (console) Intel 80386, for MS Windows AP7_win_x86_SSE3_CPU_AMD_r2696.exe: PE32 executable (GUI) Intel 80386, for MS Windows AP7_win_x86_SSE3_CPU_r2692.exe: PE32 executable (GUI) Intel 80386, for MS Windows AP7_win_x86_SSE_Brook_r2904.exe: PE32 executable (GUI) Intel 80386, for MS Windows AP7_win_x86_SSE_CPU_r2703.exe: PE32 executable (console) Intel 80386, for MS Windows Lunatics_x41zi_win32_cuda23.exe: PE32 executable (console) Intel 80386, for MS Windows Lunatics_x41zi_win32_cuda32.exe: PE32 executable (console) Intel 80386, for MS Windows Lunatics_x41zi_win32_cuda42.exe: PE32 executable (console) Intel 80386, for MS Windows Lunatics_x41zi_win32_cuda50.exe: PE32 executable (console) Intel 80386, for MS Windows MB7_win_x86_SSE2_OpenCL_ATi_HD5_r2929.exe: PE32 executable (console) Intel 80386, for MS Windows MB7_win_x86_SSE2_OpenCL_ATi_r2929.exe: PE32 executable (GUI) Intel 80386, for MS Windows MB7_win_x86_SSSE3_OpenCL_Intel_r2929.exe: PE32 executable (GUI) Intel 80386, for MS Windows MB8_win_x64_AVX_VS2010_r3330.exe: PE32+ executable (GUI) x86-64, for MS Windows MB8_win_x64_SSE2_VS2008_r3330.exe: PE32+ executable (GUI) x86-64, for MS Windows MB8_win_x64_SSE3_VS2008_r3330.exe: PE32+ executable (GUI) x86-64, for MS Windows MB8_win_x86_AVX_VS2010_r3330.exe: PE32 executable (GUI) Intel 80386, for MS Windows MB8_win_x86_SSE2_OpenCL_ATi_HD5_r3330.exe: PE32 executable (console) Intel 80386, for MS Windows MB8_win_x86_SSE2_OpenCL_ATi_r3330.exe: PE32 executable (GUI) Intel 80386, for MS Windows MB8_win_x86_SSE2_VS2008_r3330.exe: PE32 executable (GUI) Intel 80386, for MS Windows MB8_win_x86_SSE3_VS2008_r3330.exe: PE32 executable (GUI) Intel 80386, for MS Windows MB8_win_x86_SSE_VS2008_r3330.exe: PE32 executable (GUI) Intel 80386, for MS Windows MB8_win_x86_SSSE3_OpenCL_Intel_r3330.exe: PE32 executable (GUI) Intel 80386, for MS Windows setiathome_7.00_windows_intelx86.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows, UPX compressed setiathome_8.00_windows_intelx86.exe: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for MS Windows setigraphics_8.00_windows_intelx86.exe: PE32 executable (GUI) Intel 80386, for MS Windows |
©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.