Result ID 396014055
Name 09my03aa.866.3360.247158.3.125_3
Workunit 94952710
Created 14 Oct 2006 5:42:06 UTC
Sent 15 Oct 2006 11:28:49 UTC
Received 15 Oct 2006 17:07:26 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xc0000005)
Computer ID 2651629
Report deadline 8 Nov 2006 3:50:12 UTC
CPU time 20196.125
stderr out
<core_client_version>5.4.11</core_client_version>
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
ar=0.443248 NumCfft=70937 NumGauss= 442523228 NumPulse= 84781171327 NumTriplet= 7224462983168


**********
**********

BOINC Windows Runtime Debugger Version 5.5.0


Dump Timestamp : 10/15/06 11:06:20
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\\Program Files\\BOINC\\slots\\1;C:\\Program Files\\BOINC\\projects\\setiathome.berkeley.edu;srv*C:\\DOCUME~1\\jbaldwin\\LOCALS~1\\Temp\\symbols*http://msdl.microsoft.com/download/symbols;srv*C:\\DOCUME~1\\jbaldwin\\LOCALS~1\\Temp\\symbols*http://boinc.berkeley.edu/symstore


ModLoad: 00400000 0014a000 C:\\Program Files\\BOINC\\projects\\setiathome.berkeley.edu\\setiathome_5.15_windows_intelx86.exe (5.15.0.0) (-nosymbols- Symbols Loaded)
File Version : 5.15
Company Name : Space Sciences Laboratory
Product Name : setiathome_enhanced
Product Version: 5.15

ModLoad: 7c900000 000b0000 C:\\WINDOWS\\system32\\ntdll.dll (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 7c800000 000f4000 C:\\WINDOWS\\system32\\kernel32.dll (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 77dd0000 0009b000 C:\\WINDOWS\\system32\\ADVAPI32.DLL (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 77e70000 00091000 C:\\WINDOWS\\system32\\RPCRT4.dll (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 77f10000 00047000 C:\\WINDOWS\\system32\\GDI32.dll (5.1.2600.2770) (PDB Symbols Loaded)
File Version : 5.1.2600.2770 (xpsp_sp2_gdr.051005-1513)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2770

ModLoad: 77d40000 00090000 C:\\WINDOWS\\system32\\USER32.dll (5.1.2600.2622) (PDB Symbols Loaded)
File Version : 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2622

ModLoad: 68b20000 00020000 C:\\WINDOWS\\system32\\GLU32.DLL (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 77c10000 00058000 C:\\WINDOWS\\system32\\msvcrt.dll (7.0.2600.2180) (PDB Symbols Loaded)
File Version : 7.0.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 7.0.2600.2180

ModLoad: 5ed00000 000cc000 C:\\WINDOWS\\system32\\OPENGL32.dll (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 73760000 00049000 C:\\WINDOWS\\system32\\DDRAW.dll (5.3.2600.2180) (PDB Symbols Loaded)
File Version : 5.03.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.03.2600.2180

ModLoad: 73bc0000 00006000 C:\\WINDOWS\\system32\\DCIMAN32.dll (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 76b40000 0002d000 C:\\WINDOWS\\system32\\WINMM.DLL (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 6e880000 000d4000 C:\\Program Files\\BOINC\\projects\\setiathome.berkeley.edu\\libfftw3f-3-1-1a.dll (-exported- Symbols Loaded)
ModLoad: 74720000 0004b000 C:\\WINDOWS\\system32\\MSCTF.dll (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180

ModLoad: 05230000 00118000 C:\\Program Files\\BOINC\\dbghelp.dll (6.5.3.7) (PDB Symbols Loaded)
File Version : 6.5.0003.7 (vbl_core_fbrel(jshay).050527-1915)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version: 6.5.0003.7

ModLoad: 02a60000 00046000 C:\\Program Files\\BOINC\\symsrv.dll (6.5.3.8) (PDB Symbols Loaded)
File Version : 6.5.0003.8 (vbl_core_fbrel(jshay).050527-1915)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version: 6.5.0003.8

ModLoad: 05450000 00031000 C:\\Program Files\\BOINC\\srcsrv.dll (6.5.3.7) (PDB Symbols Loaded)
File Version : 6.5.0003.7 (vbl_core_fbrel(jshay).050527-1915)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version: 6.5.0003.7

ModLoad: 77c00000 00008000 C:\\WINDOWS\\system32\\version.dll (5.1.2600.2180) (PDB Symbols Loaded)
File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 5.1.2600.2180



*** Dump of the Graphics thread (9c0): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 312500.000000, User Time: 0.000000, Wait Time: 32355710.000000

- Registers -
eax=0022fc20 ebx=0022fdb0 ecx=7ffdf000 edx=00000001 esi=0022fdb0 edi=00000000
eip=7c90eb94 esp=0022fca4 ebp=0022fcc8
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
0022fca0 77d491be 77d51082 0022fdb0 00000000 00000000 ntdll!_KiFastSystemCallRet@0+0x0 FPO: [0,0,0]
0022fcc8 00458554 0022fdb0 00000000 00000000 00000000 USER32!_NtUserGetMessage@16+0x0
0022ff78 004011e7 00000001 00a82740 00a82ad0 00538000 setiathome_5.15_windows_intelx8!+0x0
0022ffb0 00401258 00000002 00000009 0022fff0 7c816d4f setiathome_5.15_windows_intelx8!+0x0
0022ffc0 7c816d4f 00000000 0000006c 7ffdb000 8054a6ed setiathome_5.15_windows_intelx8!+0x0
0022fff0 00000000 00401240 00000000 78746341 00000020 kernel32!_BaseProcessStart@4+0x0

*** Dump of the Worker thread (a98): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 3750000.000000, User Time: 201964535808.000000, Wait Time: 32355710.000000

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00000002 read attempt to address 0x00000002

- Registers -
eax=00000001 ebx=00f4f320 ecx=00000002 edx=474e5543 esi=ffffffff edi=02ae02f8
eip=00000002 esp=00f4f2f8 ebp=00f4f334
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202

- Callstack -
ChildEBP RetAddr Args to Child
SymFromAddr(): GetLastError = '126' Address = '00000002'
SymGetModuleInfo(): GetLastError = '126' Address = '00000002'
00f4f2f4 004d224c 00000001 00000001 432b2b00 474e5543 !+0x0
00f4f334 004c7e85 02ae02f8 004e4f10 00f4ffa4 004059db setiathome_5.15_windows_intelx8!+0x0
00f4f344 004059db 02ae0318 00534c7c 004e4f10 0049029c setiathome_5.15_windows_intelx8!+0x0
00f4ffa4 0045b731 806e4ef2 7c90e2dc 7c918e85 7c80b50b setiathome_5.15_windows_intelx8!+0x0
00f4ffec 00000000 0045b720 00000000 00000000 00000000 setiathome_5.15_windows_intelx8!+0x0

*** Dump of the Timer thread (7fc): ***

- Information -
Status: Waiting, Wait Reason: UserRequest, Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 32355656.000000

- Registers -
eax=00000001 ebx=00000000 ecx=0000002f edx=00000000 esi=00000001 edi=00a80000
eip=7c90eb94 esp=0114ff08 ebp=0114ffb4
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000296

- Callstack -
ChildEBP RetAddr Args to Child
0114ff04 7c90e9ab 76b5af21 00000002 0114ff6c 00000001 ntdll!_KiFastSystemCallRet@0+0x0 FPO: [0,0,0]
0114ff08 76b5af21 00000002 0114ff6c 00000001 00000001 ntdll!_ZwWaitForMultipleObjects@20+0x0 FPO: [5,0,0]
0114ffb4 7c80b50b 00000000 00a80000 0025c780 00000000 WINMM!_timeThread@4+0x0
0114ffec 00000000 76b5aee7 00000000 00000000 00000000 kernel32!_BaseThreadStart@8+0x0


*** Debug Message Dump ****


*** Foreground Window Data ***
Window Name :
Window Class :
Window Process ID: 0
Window Thread ID : 0

Exiting...

</stderr_txt>
Validate state Invalid
Claimed credit 44.4209203248794
Granted credit 0
application version 5.15

---

Dell workstation 650, dual XEON 3.4GHz, 4 GB RAM, SCSI 76GB HD, DVD drive, CD/RW/ROM, Win2k.


10/18/2006 6:24:50 AM|SETI@home|Deferring scheduler requests for 1 hours, 44 minutes and 5 seconds
10/18/2006 6:24:50 AM||Rescheduling CPU: start failed
10/18/2006 6:24:50 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:50 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:50 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:51 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:51 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:52 AM|SETI@home|Unrecoverable error for result 12my03aa.3866.257.836068.3.37_1 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:24:52 AM||Rescheduling CPU: start failed
10/18/2006 6:24:52 AM|SETI@home|Computation for task 10my03aa.132.29058.817336.3.181_1 finished
10/18/2006 6:24:52 AM|SETI@home|Unexpected state 7 for task 12my03aa.3866.257.836068.3.37_1
10/18/2006 6:24:53 AM|SETI@home|Finished download of file 10my03aa.132.29058.817336.3.186
10/18/2006 6:24:53 AM|SETI@home|Throughput 58080 bytes/sec
10/18/2006 6:24:53 AM|SETI@home|Finished download of file 08my03ab.18191.22898.654818.3.14
10/18/2006 6:24:53 AM|SETI@home|Throughput 57499 bytes/sec
10/18/2006 6:24:53 AM|SETI@home|Started download of file 10my03aa.132.29058.817336.3.185
10/18/2006 6:24:53 AM|SETI@home|Started download of file 10my03aa.132.29058.817336.3.188
10/18/2006 6:24:53 AM|SETI@home|Computation for task 12my03aa.3866.257.836068.3.37_1 finished
10/18/2006 6:24:54 AM||Rescheduling CPU: files downloaded
10/18/2006 6:24:54 AM||Rescheduling CPU: files downloaded
10/18/2006 6:24:54 AM||Using earliest-deadline-first scheduling because computer is overcommitted.
10/18/2006 6:24:54 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:55 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:55 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:55 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:56 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:57 AM|SETI@home|Unrecoverable error for result 08my03ab.18191.22898.654818.3.14_0 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:24:57 AM|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
10/18/2006 6:24:57 AM||Rescheduling CPU: start failed
10/18/2006 6:24:57 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:57 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:58 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:58 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:24:59 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:00 AM|SETI@home|Unrecoverable error for result 10my03aa.132.29058.817336.3.186_0 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:25:00 AM||Rescheduling CPU: start failed
10/18/2006 6:25:00 AM|SETI@home|Computation for task 08my03ab.18191.22898.654818.3.14_0 finished
10/18/2006 6:25:00 AM||Resuming round-robin CPU scheduling.
10/18/2006 6:25:00 AM|SETI@home|Unexpected state 7 for task 10my03aa.132.29058.817336.3.186_0
10/18/2006 6:25:01 AM|SETI@home|Computation for task 10my03aa.132.29058.817336.3.186_0 finished
10/18/2006 6:25:03 AM|SETI@home|Finished download of file 10my03aa.132.29058.817336.3.185
10/18/2006 6:25:03 AM|SETI@home|Throughput 45441 bytes/sec
10/18/2006 6:25:03 AM|SETI@home|Finished download of file 10my03aa.132.29058.817336.3.188
10/18/2006 6:25:03 AM|SETI@home|Throughput 45440 bytes/sec
10/18/2006 6:25:03 AM|SETI@home|Started download of file 10my03aa.132.29058.817336.3.180
10/18/2006 6:25:03 AM|SETI@home|Started download of file 10my03aa.132.29058.817336.3.183
10/18/2006 6:25:04 AM||Rescheduling CPU: files downloaded
10/18/2006 6:25:04 AM||Rescheduling CPU: files downloaded
10/18/2006 6:25:04 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:04 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:05 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:05 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:06 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:06 AM|SETI@home|Unrecoverable error for result 10my03aa.132.29058.817336.3.185_0 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:25:06 AM|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
10/18/2006 6:25:06 AM||Rescheduling CPU: start failed
10/18/2006 6:25:06 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:07 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:07 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:08 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:09 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:09 AM|SETI@home|Unrecoverable error for result 10my03aa.132.29058.817336.3.188_2 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:25:09 AM||Rescheduling CPU: start failed
10/18/2006 6:25:09 AM|SETI@home|Computation for task 10my03aa.132.29058.817336.3.185_0 finished
10/18/2006 6:25:09 AM|SETI@home|Unexpected state 7 for task 10my03aa.132.29058.817336.3.188_2
10/18/2006 6:25:10 AM|SETI@home|Finished download of file 10my03aa.132.29058.817336.3.180
10/18/2006 6:25:10 AM|SETI@home|Throughput 51613 bytes/sec
10/18/2006 6:25:10 AM|SETI@home|Finished download of file 10my03aa.132.29058.817336.3.183
10/18/2006 6:25:10 AM|SETI@home|Throughput 51270 bytes/sec
10/18/2006 6:25:10 AM|SETI@home|Started download of file 12my03aa.3866.257.836068.3.35
10/18/2006 6:25:10 AM|SETI@home|Computation for task 10my03aa.132.29058.817336.3.188_2 finished
10/18/2006 6:25:11 AM||Rescheduling CPU: files downloaded
10/18/2006 6:25:11 AM||Rescheduling CPU: files downloaded
10/18/2006 6:25:11 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:12 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:12 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:13 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:13 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:13 AM|SETI@home|Unrecoverable error for result 10my03aa.132.29058.817336.3.180_1 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:25:13 AM|SETI@home|Deferring scheduler requests for 1 minutes and 9 seconds
10/18/2006 6:25:13 AM||Rescheduling CPU: start failed
10/18/2006 6:25:13 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:14 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:14 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:14 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:15 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:15 AM|SETI@home|Unrecoverable error for result 10my03aa.132.29058.817336.3.183_3 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:25:15 AM|SETI@home|Deferring scheduler requests for 5 minutes and 39 seconds
10/18/2006 6:25:15 AM||Rescheduling CPU: start failed
10/18/2006 6:25:15 AM|SETI@home|Computation for task 10my03aa.132.29058.817336.3.180_1 finished
10/18/2006 6:25:15 AM|SETI@home|Unexpected state 7 for task 10my03aa.132.29058.817336.3.183_3
10/18/2006 6:25:16 AM|SETI@home|Computation for task 10my03aa.132.29058.817336.3.183_3 finished
10/18/2006 6:25:17 AM|SETI@home|Finished download of file 12my03aa.3866.257.836068.3.35
10/18/2006 6:25:17 AM|SETI@home|Throughput 66975 bytes/sec
10/18/2006 6:25:18 AM||Rescheduling CPU: files downloaded
10/18/2006 6:25:18 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:18 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:19 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:20 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:20 AM|SETI@home|Process creation failed: The system cannot find the file specified. (0x2)
10/18/2006 6:25:21 AM|SETI@home|Unrecoverable error for result 12my03aa.3866.257.836068.3.35_2 (CreateProcess() failed - The system cannot find the file specified. (0x2))
10/18/2006 6:25:21 AM|SETI@home|Deferring scheduler requests for 7 minutes and 25 seconds
10/18/2006 6:25:21 AM||Rescheduling CPU: start failed
10/18/2006 6:25:21 AM|SETI@home|Computation for task 12my03aa.3866.257.836068.3.35_2 finished

---

23-10-2006 18:47:29|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
23-10-2006 18:47:29|SETI@home|Reason: Requested by user
23-10-2006 18:47:29|SETI@home|Reporting 1 tasks
23-10-2006 18:47:34|SETI@home|Scheduler request succeeded
23-10-2006 18:47:35|SETI@home|Unrecoverable error for result 16my03aa.25290.12352.665884.3.128_1 ( - exit code -1073741674 (0xc0000096))
23-10-2006 18:47:35||Rescheduling CPU: application exited
23-10-2006 18:47:35|SETI@home|Computation for task 16my03aa.25290.12352.665884.3.128_1 finished


I'm using a P4 at 3.4Ghz, 4Gb RAM, Windows XP HEdition. SLI system ( 2x Asus 7900 GTX, DDR3, 512Mg)

I just checked my SETI statistics for the first time in a while, and wasn't amused to see that half my recent tasks are shown as "Client Error"/"Compute Error". It only shows the last seven: one still in computation, three success, three failed.

I checked Einstein - NO errors in the past 8 tasks on one machine, or the past 40 on the other (as far back as it goes).
Spinhenge - ONE error in 40+ tasks.

I assume there's something wrong somewhere with the SETI software, so I'm turning off SETI computation until I hear it's fixed. I'd rather the time went to projects that are using it effetively.

---

I assume there's something wrong somewhere with the SETI software, so I'm turning off SETI computation until I hear it's fixed.

Where as i assume there's nothing wrong with the software, as i've only had one or 2 client/compute errors in the last month on my 2 machines combined.

---

Grant
Darwin NT

Well, it's still zero errors on Einstein over the past several weeks. That's holding up well, and not wasting processor time on abortive crunching. I plan to leave SETI "turned off" on the XP machine unless I hear new news, and try again in a few months.

The Linux machine seems not to be having the problem, if that proves anything.

---

Hello!my name is TOYOAKI.
I'm japanese.25old.how talk naw?

The work unit I'm currently crunching has been running for 20 hrs!!!!
most units take 5-6 hrs to finish.

http://setiathome.berkeley.edu/workunit.php?wuid=97512238

it's only at 1.526%. should I abort? boinc says 30 hrs to completion.

---

The work unit I'm currently crunching has been running for 20 hrs!!!!
most units take 5-6 hrs to finish.

http://setiathome.berkeley.edu/workunit.php?wuid=97512238

it's only at 1.526%. should I abort? boinc says 30 hrs to completion.

Try stopping and restarting BOINC first. (Do a full file|exit from the manager)

Apparently that often sorts out a stuck WU, but if not, go ahead and abort it - then check out your system to see if anything's wrong, like a build-up of dust causing overheating.

Task is at 4hrs 51min now. (don't know why it said 20hrs before) but its at 13.306%. I will continue to watch this unit. No errors are being reported at this time. Also there's no dust problem, my case has a window in the side and I watch it closely. Also its on top of my desk vs being on the floor. This helps alot.

---

2 wu´s failed
Work Unit Info
True angle range: 0.872380
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.
look here --->
here
there

SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

It's not a failure or a problem- it was just a Work Unit with a lot of noise in it.

---

Grant
Darwin NT

I don’t know how long it’ll stay around for inspection, but I wanted to report this result from a Win2003/Xeon system. It exceeded the maximum CPU time after about 57 hours spent on what should have been at most a two-hour WU. Two other hosts had errors, but neither of them similar: one got “exit code -1 (0xffffffff)” immediately, while the other got “exit code -1073741819 (0xc0000005)” and a Windows debugging dump but reported a normal-looking time and credit claim.

---

There is something wrong w/ the work units being sent out. Has nothing to do w/ "dirty computers", bad "os's", overclocking, or any other of the BS that's been posted. I've got 7 (6 dedicated)computers all crunching SETI and there ALL getting the same "unrecoverable error......" message. This has caused my WU's to fall off by over 200 a day. Someone has got to fix this !!!

---

There is something wrong w/ the work units being sent out. Has nothing to do w/ "dirty computers", bad "os's", overclocking, or any other of the BS that's been posted. I've got 7 (6 dedicated)computers all crunching SETI and there ALL getting the same "unrecoverable error......" message. This has caused my WU's to fall off by over 200 a day. Someone has got to fix this !!!

What 'unrecoverable error' would that be? Your computers are hidden, so we can't diagnose the problem: and without diagnosis, we can't suggest a remedy either.

25,347,573 credits granted in the last 24 hours (BoincStats) suggests that there are a lot of working computers out there, and a lot of good WUs being sent out by, and returned to, Berkeley. If it's just your six/seven computers which are failing, then the common factor is you, and the "Someone has got to fix this" is also ... you!

If all your computers have the same sort of error, starting at the same time, then I would suspect that the common factor is your internet connection. Some people have had success with router firmware updates - perhaps that would be worth a try. But we need more/better information in order to be able to help.

There is something wrong w/ the work units being sent out. Has nothing to do w/ "dirty computers", bad "os's", overclocking, or any other of the BS that's been posted. I've got 7 (6 dedicated)computers all crunching SETI and there ALL getting the same "unrecoverable error......" message. This has caused my WU's to fall off by over 200 a day. Someone has got to fix this !!!

What 'unrecoverable error' would that be? Your computers are hidden, so we can't diagnose the problem: and without diagnosis, we can't suggest a remedy either.

25,347,573 credits granted in the last 24 hours (BoincStats) suggests that there are a lot of working computers out there, and a lot of good WUs being sent out by, and returned to, Berkeley. If it's just your six/seven computers which are failing, then the common factor is you, and the "Someone has got to fix this" is also ... you!

If all your computers have the same sort of error, starting at the same time, then I would suspect that the common factor is your internet connection. Some people have had success with router firmware updates - perhaps that would be worth a try. But we need more/better information in order to be able to help.

---

There is something wrong w/ the work units being sent out. Has nothing to do w/ "dirty computers", bad "os's", overclocking, or any other of the BS that's been posted. I've got 7 (6 dedicated)computers all crunching SETI and there ALL getting the same "unrecoverable error......" message. This has caused my WU's to fall off by over 200 a day. Someone has got to fix this !!!

What 'unrecoverable error' would that be? Your computers are hidden, so we can't diagnose the problem: and without diagnosis, we can't suggest a remedy either.

25,347,573 credits granted in the last 24 hours (BoincStats) suggests that there are a lot of working computers out there, and a lot of good WUs being sent out by, and returned to, Berkeley. If it's just your six/seven computers which are failing, then the common factor is you, and the "Someone has got to fix this" is also ... you!

If all your computers have the same sort of error, starting at the same time, then I would suspect that the common factor is your internet connection. Some people have had success with router firmware updates - perhaps that would be worth a try. But we need more/better information in order to be able to help.

1st, I have no doubt that your getting "credits granted". But durinmg the last 2-3wks, some of the work units are causing the computations stop. may have 1 @ 5% and has been running for 50hrs !!!. And it isn't just my problem, most of the post's in this forum are about this problem. I've gotten in the habit of aborting any unit aborting any unit that goes over 10 -15 hrs with little or % complete. The "router" solution doesn't hold water either. My computers are on 3 seperate routers on 3 completely different providers. (and I unhid the computers if you want to look at them. Didn't know they were hidden)

---

I see what you mean. From your first post, I'd sort of assumed that you'd got a whole lot of failures at once: but from what I can now see, you're just getting random failures in and amongst the good work. Also, I accept that if they're on different sites/ISPs, that blows my router theory out of the water!

For some reason, you seem to get a high proportion of WUs which, the quorum eventually decides, are going to end with a -9 overflow: often after a long and productive crunch. (I think I saw one which got a quorum credit award of over 60 credits, but still got an overflow: and there were others in the 40s).

Yet where other machines bowed out gracefully with a -9, yours often error out, or as you say get stuck and need a good kicking (sometimes a BOINC exit/restart is good enough). As you say, others have commented on these lock-ups recently, and it does seem as if there's a problem in the SETI app program code which means that 'overflow' WUs aren't always handled cleanly.

Here is one of your WUs (97609380) which I hope a programmer could have a look at before it gets purged. At least one cruncher escaped from its clutches with a clean -9 exit, but look at the weird and wonderful range of errors the others reported! Can anyone see a pattern?

Here’s another erroneous result from my Win2003/Xeon host: this time the error is an “exit code -1073741819 (0xc0000005)”, and judging from the credit claim it occurred about 80% of the way into the task. As before, the system has returned successful results both before and since, so I don’t think it’s a case of overheating, a bad network connection, or a like problem ‘at my end’. BOINC v5.4.11, stock S@h Enhanced v5.15.

---

Here’s another erroneous result from my Win2003/Xeon host: this time the error is an “exit code -1073741819 (0xc0000005)”, and judging from the credit claim it occurred about 80% of the way into the task. As before, the system has returned successful results both before and since, so I don’t think it’s a case of overheating, a bad network connection, or a like problem ‘at my end’. BOINC v5.4.11, stock S@h Enhanced v5.15.

Watch your quorum partners. The only one back so far has claimed 60+, but it's a false claim by BOINC 4.45. It's showing a -9 overflow: a very similar pattern to the ones RareBear alerted us to. Some sort of problem a good long way into the crunch: some app/client/platform combos error out, others report overflow.

[edit] That 4.45 seems normally to overclaim by about 25%, but on a VLAR (AR=0.084490) overclaimed by about 80%. More evidence that VLARs run long/undercount FLOPs? [/edit]