Gday folks just thought you might want to check out the completed wu's reported a little while ago.


http://milkyway.cs.rpi.edu/milkyway/results.php?userid=6106&offset=20

Still getting no errors all well so far....
Glenn

---

As of now my Quad, the working one that is and the one giving errors, is on the stock client.

The swap back was a pain in the arse, which seems to be my experience over the last 2 weeks.

I needed a detach and reattach to get back to the stock.

Now all is running, and I will leave it like that the rest of the day.

heh may have to try that

nm_s86_r8_61958_1234514904_0

Couldn't find input file [astronomy_parameters.txt] to read astronomy parameters

---

Only at my 64 Bit System crashed the nm_s82 WU. :( The other systems work fine.

---

Constant dripping wears away the stone. :)

First 4 on the stock client reported OK.

Now to see a lot more through

I had two WUs on my lappy crunching with stock app v0.17 now.
Both seem to have finished without failure but one WU has vanished from my results' list as soon as it was reported so I can't say for sure. :-(
The other one has gone now, too and was here (at least I have seen that result marked as succesful before it was purged).

PS#1: This is no sign at all that the opti app isn't working correctly because:
a) not all WUs are erroring out while using opti app!
b) most of the errors are download errors which have nothing to do with any app!
Even the ones which are declared as "Compute error" are in fact download errors, see example:

<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>stars-82-v2.txt</file_name>
<error_code>-200</error_code>
</file_xfer_error>
</message>

The other errors I had yesterday (exceeded disk limit and some Windows Dumps) seem to have gone on all my system today. ;-)

PS#2: Concerning the download errors there must be something wrong on the server side, I guess... Because even the stock app doesn't know where to get the input files from, right? *grin*
I mean the server is giving out these input files and also the info where they are stored...

---

Lovely greetings, Cori

this is true none of this started happening till the last server crash and also this new run of wu's.. up untill then everything was smooth as silk and i know i havent changed ANYTHING as far as set up and still using the same OPT app...

so it must be something server side... like i said up to 2-3 days ago smooth as silk.

so if we the crunchers have changed nothing well then whats left :)

---

I had two WUs on my lappy crunching with stock app v0.17 now.
Both seem to have finished without failure but one WU has vanished from my results' list as soon as it was reported so I can't say for sure. :-(
The other one has gone now, too and was here (at least I have seen that result marked as succesful before it was purged).

PS#1: This is no sign at all that the opti app isn't working correctly because:
a) not all WUs are erroring out while using opti app!
b) most of the errors are download errors which have nothing to do with any app!
Even the ones which are declared as "Compute error" are in fact download errors, see example:

<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>stars-82-v2.txt</file_name>
<error_code>-200</error_code>
</file_xfer_error>
</message>

The other errors I had yesterday (exceeded disk limit and some Windows Dumps) seem to have gone on all my system today. ;-)

PS#2: Concerning the download errors there must be something wrong on the server side, I guess... Because even the stock app doesn't know where to get the input files from, right? *grin*
I mean the server is giving out these input files and also the info where they are stored...

I would agree that the compute errors are also download errors. But after reading both threads again, it seems to be restricted to quad cores & up. My 1Gig up to the core 2 duo all are working fine, just the i7 having issues.

FWIW, I too am using the opti app from zslip (win32) and have not had any errors at all with it, so it seems to be just a couple people having a problem.

... I would agree that the compute errors are also download errors. But after reading both threads again, it seems to be restricted to quad cores & up. My 1Gig up to the core 2 duo all are working fine, just the i7 having issues.

Funny enough I had problems on all my 4 puters... *sigh*

These are:
- C2D lappy (Win XP 64-bit)
- Quad (Vista 32-bit)
- P4 (Win XP 32-bit)
- P4 lappy (Win XP 32-bit)

So it seems to affect not only faster/newer boxes. But it seems to affect only Windows machines, is that right?

---

Lovely greetings, Cori

I just had another download error (still using the stock app!) on my C2D lappy:

13.02.2009 12:46:53|Milkyway@home|Finished download of /stars-79.txt
13.02.2009 12:46:54|Milkyway@home|[error] MD5 check failed for /stars-79.txt
13.02.2009 12:46:54|Milkyway@home|[error] expected c0053b930967ae032adc2b8f23015a93, got 61a14313a3f0244e7f7be2df1645d5d8
13.02.2009 12:46:54|Milkyway@home|[error] Checksum or signature error for /stars-79.txt
13.02.2009 12:46:58|Milkyway@home|Finished download of stars-82-v2.txt
13.02.2009 12:46:58|Milkyway@home|[error] Checksum or signature error for stars-82-v2.txt
13.02.2009 12:47:01|Milkyway@home|Finished download of /stars-82-v2.txt
13.02.2009 12:47:01|Milkyway@home|[error] MD5 check failed for /stars-82-v2.txt
13.02.2009 12:47:01|Milkyway@home|[error] expected 49c31e6d724772838c734817b7ac113e, got 798817981b84182b99faf9c1cb6fe75e
13.02.2009 12:47:01|Milkyway@home|[error] Checksum or signature error for /stars-82-v2.txt

These two files are the troublemakers! :-)))


EDIT: To me it seems that these files are downloaded for each WU again even if they have been downloaded before...
At least the stars-79.txt file has been already sitting on my lappy and when I got more WUs the BOINC manager was told to re-download it... is that the reason for the checksum errors?
Or are there different files with the same name??? *scratches head*


EDIT 2: I think I'll revert to the opti app again - the errors are happening no matter which app I use. ;-(

---

Lovely greetings, Cori

I've started getting the same errors now. Only with stream 82, not with anything else. A lot are obviously download errors, and even say so. Somer say "maximum disc usage exceeded. The partition BOINC is on is 50GB, with 37GB free, BOINC offered 50% (now increased to 75%) up to a maximum of 100GB, and being told to only leave 0.001GB (before which Windows would ahve complained).

An example of the error file is (wu nm_s82_r7_16247_1234506175_0):

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x7D61F185 write attempt to address 0x00000024

Engaging BOINC Windows Runtime Debugger...



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


BOINC Windows Runtime Debugger Version 6.3.11


Dump Timestamp : 02/13/09 07:28:36
Install Directory :
Data Directory : C:\Program Files\BOINC\Application Data\BOINC
Project Symstore :
LoadLibraryA( C:\Program Files\BOINC\Application Data\BOINC\dbghelp.dll ): GetLastError = 126
Loaded Library : dbghelp.dll
LoadLibraryA( C:\Program Files\BOINC\Application Data\BOINC\symsrv.dll ): GetLastError = 126
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( C:\Program Files\BOINC\Application Data\BOINC\srcsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126
LoadLibraryA( C:\Program Files\BOINC\Application Data\BOINC\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\Program Files\BOINC\Application Data\BOINC\slots\0;C:\Program Files\BOINC\Application Data\BOINC\projects\milkyway.cs.rpi.edu_milkyway;srv*C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\symbols*http://msdl.microsoft.com/download/symbols;srv*C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\symbols*http://boinc.berkeley.edu/symstore


ModLoad: 00400000 000eb000 astronomy_0.16_SSE2.exe (-nosymbols- Symbols Loaded)

ModLoad: 7d600000 000f0000 ntdll.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.3959

ModLoad: 7d4c0000 00130000 kernel32.dll (5.2.3790.4062) (-exported- Symbols Loaded)
File Version : 5.2.3790.4062 (srv03_sp2_gdr.070417-0203)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.4062

ModLoad: 7d930000 000d0000 USER32.dll (5.2.3790.4033) (-exported- Symbols Loaded)
File Version : 5.2.3790.4033 (srv03_sp2_gdr.070228-0030)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.4033

ModLoad: 7d800000 00090000 GDI32.dll (5.2.3790.4396) (-exported- Symbols Loaded)
File Version : 5.2.3790.4396 (srv03_sp2_gdr.081022-1212)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.4396

ModLoad: 005a0000 0009b000 ADVAPI32.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.3959

ModLoad: 7da20000 000e0000 RPCRT4.dll (5.2.3790.4115) (-exported- Symbols Loaded)
File Version : 5.2.3790.4115 (srv03_sp2_gdr.070709-2335)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.4115

ModLoad: 7d8d0000 00050000 Secur32.dll (5.2.3790.3959) (-exported- Symbols Loaded)
File Version : 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.3959

ModLoad: 6d580000 000a8000 dbghelp.dll (5.2.3790.1830) (-exported- Symbols Loaded)
File Version : 5.2.3790.1830 (srv03_sp1_rtm.050324-1447)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.1830

ModLoad: 77ba0000 0005a000 msvcrt.dll (7.0.3790.3959) (-exported- Symbols Loaded)
File Version : 7.0.3790.3959 (srv03_sp2_rtm.070216-1710)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 7.0.3790.3959

ModLoad: 77b90000 00008000 VERSION.dll (5.2.3790.1830) (-exported- Symbols Loaded)
File Version : 5.2.3790.1830 (srv03_sp1_rtm.050324-1447)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.2.3790.1830



*** Dump of the Process Statistics: ***

- I/O Operations Counters -
Read: 9, Write: 0, Other 103

- I/O Transfers Counters -
Read: 0, Write: 46, Other 0

- Paged Pool Usage -
QuotaPagedPoolUsage: 72496, QuotaPeakPagedPoolUsage: 72632
QuotaNonPagedPoolUsage: 3904, QuotaPeakNonPagedPoolUsage: 3904

- Virtual Memory Usage -
VirtualSize: 42483712, PeakVirtualSize: 42483712

- Pagefile Usage -
PagefileUsage: 1728512, PeakPagefileUsage: 1728512

- Working Set Size -
WorkingSetSize: 2809856, PeakWorkingSetSize: 2809856, PageFaultCount: 696

*** Dump of thread ID 468 (state: Ready): ***

- Information -
Status: Base Priority: Above Normal, Priority: Above Normal, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 85128648.000000

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x7D61F185 write attempt to address 0x00000024

- Registers -
eax=00000000 ebx=00000000 ecx=00000024 edx=00000020 esi=00000024 edi=00000000
eip=7d61f185 esp=002cf894 ebp=002cf8a0
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202

- Callstack -
ChildEBP RetAddr Args to Child
002cf8a0 0042dca2 00000020 0042e5ff 00000000 00000000 ntdll!RtlEnterCriticalSection+0x0
002cf8dc 00407743 00000000 00446df0 01d83da0 0000000b astronomy_0.16_SSE2!+0x0
01d83da0 01d80178 00020010 0008017f c0000005 0000000b astronomy_0.16_SSE2!+0x0
01d84e78 69725020 7469726f 41203a79 65766f62 726f4e20 astronomy_0.16_SSE2!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '01d80178'
00000000 00000000 00000000 00000000 00000000 00000000 astronomy_0.16_SSE2!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '69725020'

*** Dump of thread ID 2696 (state: Waiting): ***

- Information -
Status: Wait Reason: ExecutionDelay, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 85128648.000000

- Registers -
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=01feff78
eip=7d61cca8 esp=01feff3c ebp=01feffa0
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202

- Callstack -
ChildEBP RetAddr Args to Child
01feffa0 7d4d14ef 00000064 00000000 01feffec 00408ee8 ntdll!ZwDelayExecution+0x0
01feffb0 00408ee8 00000064 7d4dfe21 00000000 00000000 kernel32!Sleep+0x0
01feffec 00000000 00408ee0 00000000 00000000 00000000 astronomy_0.16_SSE2!+0x0


*** Debug Message Dump ****


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

Exiting...

</stderr_txt>
]]>

---

I would add that all the wu I have ahd fail say they failed after 0.0 seconds, so I do not feel I have lost any crunching time or that the project has lost a vast amount of work time, although as long as this is happening it will affect what time the CPU is available to crunch, as it it giving over time to debugging problems.

---

... I would agree that the compute errors are also download errors. But after reading both threads again, it seems to be restricted to quad cores & up. My 1Gig up to the core 2 duo all are working fine, just the i7 having issues.

Funny enough I had problems on all my 4 puters... *sigh*

These are:
- C2D lappy (Win XP 64-bit)
- Quad (Vista 32-bit)
- P4 (Win XP 32-bit)
- P4 lappy (Win XP 32-bit)

So it seems to affect not only faster/newer boxes. But it seems to affect only Windows machines, is that right?

yes, from what i've read, only windows. i've been running the gpu app on the i7 and opti apps on all other machines. watching the i7 this morning once the star file download fails, those that download after it fail, but those that successfully downloaded before start failing with compute errors. but then boinc starts scheduling way in the future, so it never sends back the failed wu's and doesn't try to download star files again. once i run an update, it downloads star files successfully and runs about another 3 hours before failing again. I've just downgraded to the opti app on the i7 to see what happens.

EDIT 2: I think I'll revert to the opti app again - the errors are happening no matter which app I use. ;-(

Yes, I think my optimized app is not the reason for the errors. Otherwise it would be really strange that Cappy (and all the others from SETI.USA using the optimized version compiled by Crunch3r) gets the same errors as the people with my one.

And as you stated, these errors also occur with the stock application. So one has to look for something server side. What has changed there after the database crash?

I have not seem the WUs (mainly stripe 79 and 82) error, they are reported as erroring on the servers. I have looked at the BOINC Manager's messages tab and seen nothing.

Currently running the stock application and all seems to go OK, after the "waiting to report" and reporting. But, dashing over to see the results, before the instant purge removes them, proves fruitless as they have gone already (as Cori says).

I think I will now revert to the opti client again, as the stock seems to be running down the cache and I have not set the NNW flag.

I just waited until the last 4 stock WUs were completed, and results sent. They registered as OK and credited in the PC results. But the instant purge took these results within 20 - 25 seconds of the results being sent.

Definitely instant purge!

No repeat of the errors so far.

Yeah, right... same here, no errors anymore. *knocks on wood* ;-)

---

Lovely greetings, Cori

Just got this in the last 10 mins, plus a host of computation errors about 3 hours ago...

13/02/2009 20:19:43|Milkyway@home|Started upload of nm_s86_r8_20449_1234528575_0_0
13/02/2009 20:19:43|Milkyway@home|Started upload of nm_s79_r6_22537_1234528985_0_0
13/02/2009 20:19:43|Milkyway@home|Sending scheduler request: To fetch work. Requesting 3091001 seconds of work, reporting 0 completed tasks
13/02/2009 20:20:19|Milkyway@home|Task nm_s86_r6_30370_1234530309_0 exited with zero status but no 'finished' file
13/02/2009 20:20:19|Milkyway@home|If this happens repeatedly you may need to reset the project.
13/02/2009 20:20:19|Milkyway@home|Task nm_s82_r7_32733_1234530772_0 exited with zero status but no 'finished' file
13/02/2009 20:20:19|Milkyway@home|If this happens repeatedly you may need to reset the project.
13/02/2009 20:20:19|Milkyway@home|Task nm_s86_r8_33946_1234530963_0 exited with zero status but no 'finished' file
13/02/2009 20:20:19|Milkyway@home|If this happens repeatedly you may need to reset the project.
13/02/2009 20:20:19|Milkyway@home|Task nm_s86_r6_37865_1234531615_0 exited with zero status but no 'finished' file
13/02/2009 20:20:19|Milkyway@home|If this happens repeatedly you may need to reset the project.

---

If the problem is with the stars files, then how come I can take the stars files from a machine not reporting any errors and copy them to another machine that has about 50% errors and still have the same problem?