OK I've turned on work fetch again but there are no WU's to download a.t.m.

They take while, almost to the completion stage in some cases then suddenly the status changes to 'Computation failed' & progress zips to 100% and all I can do is update to get rid of them..

---

Peter
Toronto, Canada

Computation failed. the weird thing is that the log doesn't say that, it says merely that it finished. Weird.

http://milkyway.cs.rpi.edu/milkyway/results.php?userid=113796

Task 40402230

Name de_nbody_orphan_test_2model_4_8136_1306428741_0
Workunit 28100536
Created 26 May 2011 | 16:52:23 UTC
Sent 26 May 2011 | 17:05:36 UTC
Received 26 May 2011 | 17:11:10 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status -1073741511 (0xffffffffc0000139)
Computer ID 281790
Report deadline 3 Jun 2011 | 17:05:36 UTC
Run time 3.00
CPU time 0.00
Validate state Invalid
Credit 0.00
Application version MilkyWay@Home N-Body Simulation v0.40 (mt)
Stderr output

<core_client_version>6.12.26</core_client_version>
<![CDATA[
<message>
- exit code -1073741511 (0xc0000139)
</message>
]]>

---

Peter
Toronto, Canada

I see now that it's vanished from the work unit progress page here, why do they delete them so quickly? It serves no purpose except perhaps drive us insane.

I now have subsequent units in progress, so far so good, and those are all that now show there.

So unless you caught the above post yesterday and took a look I'm afraid you are out of luck.

---

Peter
Toronto, Canada

They delete them so quickly to reduce load on the database server. It had been totally overwhelmed ever since the ATIs entered service here. With the recent move to file-less crunching there might be more headroom again.. but I guess they don't want to touch what finally works.

MrS

---

Scanning for our furry friends since Jan 2002

Thanks for explaining that for us. ;-)

---

Peter
Toronto, Canada

Computation error since app update in April.

I've try all what I could find on this forum:
Update drivers
Restart project
Detached and reattached

Config:

BOINC 6.10.58
Radeon HD3850, Catalyst 11.3
Windows XP SP3 32Bit
Athlon XP 2600+


MilkyWay was running well with opptim app before app update.
I look for a solution since one month, and find nothing!
What is the problem? Is some one have the same problem or THE solution, please?


Error code:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Illegal Instruction (0xc000001d) at address 0x004051F9

The optimized applications are deprecated and won't validate anymore -- there were quite a few news threads about this. We've updated the server code and what we were sending to clients to help reduce server load, so the old optimized applications aren't receiving certain files they need to run.

I don't know if anyone has released any newer optimized applications that run with the new versions of the workunits, but you can always use the ones provided by the server.

Travis, I don't use optimized app any more.
Since the update I use the one from the server.

Here is a complete stderr:


Tâche 32809378

Nom de_separation_13_3s_fix20_2_1773374_1305575032_0
Unité de travail (WU) 22519574
Créé 16 May 2011 | 19:43:56 UTC
Envoyé 16 May 2011 | 19:45:57 UTC
Reçu 16 May 2011 | 19:56:27 UTC
État du serveur Sur
Résultats Erreur de calcul
État du client Erreur de calcul
État à la sortie -1073741795 (0xffffffffc000001d)
ID de l'ordinateur 254476
Date limite de rapport 24 May 2011 | 19:45:57 UTC
Temps de fonctionnement 514.59
Temps de CPU 6.47
Valider l'état Invalide
Crédit 0.00
Version de l'application MilkyWay@Home v0.62 (ati14)
Stderr output

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
- exit code -1073741795 (0xc000001d)
</message>
<stderr_txt>
<search_application> milkywayathome_client separation 0.62 Windows x86 double CAL++ </search_application>
Found 1 CAL devices
Chose device 0

Device target: CAL_TARGET_670
Revision: 41
CAL Version: 1.4.1332
Engine clock: 823 Mhz
Memory clock: 603 Mhz
GPU RAM: 512
Wavefront size: 64
Double precision: CAL_TRUE
Compute shader: CAL_FALSE
Number SIMD: 4
Number shader engines: 1
Pitch alignment: 256
Surface alignment: 256
Max size 2D: { 8192, 8192 }

Estimated iteration time 647.664793 ms
Target frequency 30.000000 Hz, polling mode 1, using responsiveness factor of 1.000000
Dividing into 20 chunks
Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Using { 1, 20 } chunk(s) of size { 1400, 80 }
<search_application> milkywayathome_client separation 0.62 Windows x86 double CAL++ </search_application>
Found 1 CAL devices
Chose device 0

Device target: CAL_TARGET_670
Revision: 41
CAL Version: 1.4.1332
Engine clock: 823 Mhz
Memory clock: 603 Mhz
GPU RAM: 512
Wavefront size: 64
Double precision: CAL_TRUE
Compute shader: CAL_FALSE
Number SIMD: 4
Number shader engines: 1
Pitch alignment: 256
Surface alignment: 256
Max size 2D: { 8192, 8192 }

Estimated iteration time 647.664793 ms
Target frequency 30.000000 Hz, polling mode 1, using responsiveness factor of 1.000000
Dividing into 20 chunks
Integration range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Using { 1, 20 } chunk(s) of size { 1400, 80 }
Integration time = 507.635358 s, average per iteration = 793.180247 ms


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Illegal Instruction (0xc000001d) at address 0x004051F9

Engaging BOINC Windows Runtime Debugger...



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


BOINC Windows Runtime Debugger Version 6.10.58


Dump Timestamp : 05/16/11 21:55:56
Install Directory : C:\Program Files\BOINC\
Data Directory : C:\Documents and Settings\All Users\Application Data\BOINC
Project Symstore :
Loaded Library : C:\Program Files\BOINC\\dbghelp.dll
Loaded Library : C:\Program Files\BOINC\\symsrv.dll
Loaded Library : C:\Program Files\BOINC\\srcsrv.dll
LoadLibraryA( C:\Program Files\BOINC\\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\Documents and Settings\All Users\Application Data\BOINC\slots\1;C:\Documents and Settings\All Users\Application Data\BOINC\projects\milkyway.cs.rpi.edu_milkyway


ModLoad: 00400000 0008f000 C:\Documents and Settings\All Users\Application Data\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.62_windows_intelx86__ati14.exe (-nosymbols- Symbols Loaded)
Linked PDB Filename :

ModLoad: 7c910000 000b6000 C:\WINDOWS\system32\ntdll.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : ntdll.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 7c800000 00106000 C:\WINDOWS\system32\kernel32.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : kernel32.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 69000000 0000e000 C:\WINDOWS\system32\aticalcl.dll (6.14.10.1332) (-exported- Symbols Loaded)
Linked PDB Filename : c:\workarea\8.831.2\drivers\cal\drivers\src\api\calcl\lib\build\2k\B_rel\aticalcl.pdb
File Version : 6.14.10.1332
Company Name : Advanced Micro Devices Inc.
Product Name : ATI CAL compiler runtime
Product Version : 6.14.10.1332

ModLoad: 00240000 0000f000 C:\WINDOWS\system32\aticalrt.dll (6.14.10.1332) (-exported- Symbols Loaded)
Linked PDB Filename : c:\workarea\8.831.2\drivers\cal\drivers\src\api\calrt\lib\build\2k\B_rel\aticalrt.pdb
File Version : 6.14.10.1332
Company Name : Advanced Micro Devices Inc.
Product Name : ATI CAL runtime
Product Version : 6.14.10.1332

ModLoad: 76ae0000 0002f000 C:\WINDOWS\system32\WINMM.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : winmm.pdb
File Version : 5.1.2600.5512 (xpsp.080413-0845)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 77da0000 000ac000 C:\WINDOWS\system32\ADVAPI32.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : advapi32.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2113)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 77e50000 00092000 C:\WINDOWS\system32\RPCRT4.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : rpcrt4.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5512

ModLoad: 77fc0000 00011000 C:\WINDOWS\system32\Secur32.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : secur32.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2113)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5512

ModLoad: 77ef0000 00049000 C:\WINDOWS\system32\GDI32.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : gdi32.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5512

ModLoad: 7e390000 00091000 C:\WINDOWS\system32\USER32.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : user32.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 02560000 004a7000 C:\WINDOWS\system32\aticaldd.dll (6.14.10.1332) (-exported- Symbols Loaded)
Linked PDB Filename : c:\workarea\8.831.2\drivers\cal\drivers\src\ddi\lib\build\2k\B_rel\aticaldd.pdb
File Version : 6.14.10.1332
Company Name : Advanced Micro Devices Inc.
Product Name : ATI CAL DD
Product Version : 6.14.10.1332

ModLoad: 10000000 00031000 C:\WINDOWS\system32\atiadlxx.dll (6.14.10.1054) (-exported- Symbols Loaded)
Linked PDB Filename : c:\workarea\8.831.2\drivers\adl\build\xp\B_rel\atiadlxx.pdb
File Version : 6.14.10.1054
Company Name : Advanced Micro Devices, Inc.
Product Name : ADL Component
Product Version : 6.14.10.1054

ModLoad: 7c9d0000 00825000 C:\WINDOWS\system32\SHELL32.dll (6.0.2900.5512) (-exported- Symbols Loaded)
Linked PDB Filename : shell32.pdb
File Version : 6.00.2900.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 6.00.2900.5512

ModLoad: 77be0000 00058000 C:\WINDOWS\system32\msvcrt.dll (7.0.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : msvcrt.pdb
File Version : 7.0.2600.5512 (xpsp.080413-2111)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 7.0.2600.5512

ModLoad: 77f40000 00076000 C:\WINDOWS\system32\SHLWAPI.dll (6.0.2900.5512) (-exported- Symbols Loaded)
Linked PDB Filename : shlwapi.pdb
File Version : 6.00.2900.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 6.00.2900.5512

ModLoad: 778e0000 000f8000 C:\WINDOWS\system32\SETUPAPI.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : setupapi.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 78130000 0009b000 C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_e6967989\MSVCR80.dll (8.0.50727.4053) (-exported- Symbols Loaded)
Linked PDB Filename : msvcr80.i386.pdb
File Version : 8.00.50727.4053
Company Name : Microsoft Corporation
Product Name : Microsoft� Visual Studio� 2005
Product Version : 8.00.50727.4053

ModLoad: 77390000 00103000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll (6.0.2900.5512) (-exported- Symbols Loaded)
Linked PDB Filename : MicrosoftWindowsCommon-Controls-6.0.2600.5512-comctl32.pdb
File Version : 6.0 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 6.00.2900.5512

ModLoad: 58b50000 0009a000 C:\WINDOWS\system32\comctl32.dll (5.82.2900.5512) (-exported- Symbols Loaded)
Linked PDB Filename : comctl32.pdb
File Version : 5.82 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 6.00.2900.5512

ModLoad: 76be0000 0002e000 C:\WINDOWS\system32\WINTRUST.dll (5.131.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : wintrust.pdb
File Version : 5.131.2600.5512 (xpsp.080413-2113)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.131.2600.5512

ModLoad: 779e0000 00097000 C:\WINDOWS\system32\CRYPT32.dll (5.131.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : crypt32.pdb
File Version : 5.131.2600.5512 (xpsp.080413-2113)
Company Name : Microsoft Corporation
Product Name : Syst�me d'exploitation Microsoft� Windows�
Product Version : 5.131.2600.5512

ModLoad: 77a80000 00012000 C:\WINDOWS\system32\MSASN1.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : msasn1.pdb
File Version : 5.1.2600.5512 (xpsp.080413-0852)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5512

ModLoad: 76c40000 00028000 C:\WINDOWS\system32\IMAGEHLP.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : imagehlp.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5512

ModLoad: 07eb0000 00115000 C:\Program Files\BOINC\dbghelp.dll (6.8.4.0) (-exported- Symbols Loaded)
Linked PDB Filename : dbghelp.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 04ff0000 00048000 C:\Program Files\BOINC\symsrv.dll (6.8.4.0) (-exported- Symbols Loaded)
Linked PDB Filename : symsrv.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 080d0000 0003b000 C:\Program Files\BOINC\srcsrv.dll (6.8.4.0) (-exported- Symbols Loaded)
Linked PDB Filename : srcsrv.pdb
File Version : 6.8.0004.0 (debuggers(dbg).070515-1751)
Company Name : Microsoft Corporation
Product Name : Debugging Tools for Windows(R)
Product Version : 6.8.0004.0

ModLoad: 77bd0000 00008000 C:\WINDOWS\system32\version.dll (5.1.2600.5512) (-exported- Symbols Loaded)
Linked PDB Filename : version.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5512



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

- I/O Operations Counters -
Read: 10, Write: 0, Other 1075

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

- Paged Pool Usage -
QuotaPagedPoolUsage: 67472, QuotaPeakPagedPoolUsage: 73104
QuotaNonPagedPoolUsage: 23872, QuotaPeakNonPagedPoolUsage: 23920

- Virtual Memory Usage -
VirtualSize: 113717248, PeakVirtualSize: 171073536

- Pagefile Usage -
PagefileUsage: 16121856, PeakPagefileUsage: 73498624

- Working Set Size -
WorkingSetSize: 16949248, PeakWorkingSetSize: 74297344, PageFaultCount: 19893

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

- Information -
Status: Base Priority: Unknown, Priority: Unknown, , Kernel Time: 37053280.000000, User Time: 27439456.000000, Wait Time: 844406.000000

- Unhandled Exception Record -
Reason: Illegal Instruction (0xc000001d) at address 0x004051F9

- Registers -
eax=003f6a70 ebx=00e1f874 ecx=003f6da0 edx=00000003 esi=003f6a70 edi=00000000
eip=004051f9 esp=00e1f838 ebp=00e1f860
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010212

- Callstack -
ChildEBP RetAddr Args to Child
00e1f860 004053b7 00000001 025619e1 00000018 00e1f8d8 milkyway_0.62_windows_intelx86_!+0x0
00e1f8d0 00405ccd 00000000 00405ccd 00e1f998 003f6a70 milkyway_0.62_windows_intelx86_!+0x0
00e1f96c 00405d99 00e1fc00 003f6a70 003f2a60 00e1fb98 milkyway_0.62_windows_intelx86_!+0x0
00e1fa00 00403ea0 00e1fc00 003f2a60 00e1fb98 00e1fa60 milkyway_0.62_windows_intelx86_!+0x0
00e1fb14 0040419b 00e1fc00 003f6a70 003f2a60 003f5130 milkyway_0.62_windows_intelx86_!+0x0
00e1fb54 00401661 003f6698 00e1fc00 003f6a70 00e1fbb8 milkyway_0.62_windows_intelx86_!+0x0
00e1fd80 0040185f 0047c200 0043dcbe 8de5fb89 003f4218 milkyway_0.62_windows_intelx86_!+0x0
00e1ff78 0043e203 0000001a 003f2ee8 003f3208 8de5f9f5 milkyway_0.62_windows_intelx86_!+0x0
00e1ffc0 7c817067 005f2cc0 00000000 7ffdf000 c000001d milkyway_0.62_windows_intelx86_!+0x0
00e1fff0 00000000 0043e259 00000000 00000000 00000000 kernel32!RegisterWaitForInputIdle+0x0

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

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

- Registers -
eax=0255fb58 ebx=00000000 ecx=8d040635 edx=e0000000 esi=00000000 edi=0255ff60
eip=7c91e4f4 esp=0255ff30 ebp=0255ff88
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206

- Callstack -
ChildEBP RetAddr Args to Child
0255ff88 7c802455 00000064 00000000 0255ffb4 00431e04 ntdll!KiFastSystemCallRet+0x0
0255ff98 00431e04 00000064 004342f0 003f2cb0 ceefbcbc kernel32!Sleep+0x0
0255ffb4 7c80b713 00000000 004342f0 003f2cb0 00000000 milkyway_0.62_windows_intelx86_!+0x0
0255ffec 00000000 00431df0 00000000 00000000 00905a4d kernel32!GetModuleFileNameA+0x0


*** Debug Message Dump ****


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

Exiting...

</stderr_txt>
]]>

Home | My Account | Message Boards


Copyright © 2011 AstroInformatics Group

My latest WU's seem to be better behaved with the last one completing without incident and I have 2 more on the go as we speak.

---

Peter
Toronto, Canada

I just noticed I now am getting computation errors on MW@Home. Not sure how to post the info or how toget it any more detailed than it shows in messages. Suffices to say at least ten tasks have went belly up that were going through the night. Not a single MW@Home success on the list. Other projects are having no such problem.

Going to withdraw support for a while until this gets ironed out.

---

32bit Windows XP Home
AMD Opteron 180
ASUS A8N-SLI Motherboard
Nvidia 450GTS GPU
4GB DDR Memory

It just happened again and same pattern as the previous pair of WU's. One completed and one failed 'Computation Error'.

Who is writing these things?

---

Peter
Toronto, Canada

Once again >50% of work units are failing due to computation error so am turning off work fetch for Milkyway until such time some kind of attention is paid to this ongoing problem.

---

Peter
Toronto, Canada

Once again >50% of work units are failing due to computation error so am turning off work fetch for Milkyway until such time some kind of attention is paid to this ongoing problem.

The Admins (Travis & Matt) have been and are well aware of the issue and are working to repair the issue.

---

Thanks for the info, glad it's being worked on.

---

Peter
Toronto, Canada

Here's what Windows reports..

Problem signature:
Problem Event Name: APPCRASH
Application Name: milkyway_nbody_0.40_windows_x86_64__mt.exe
Application Version: 0.0.0.0
Application Timestamp: 4d8d3724
Fault Module Name: KERNEL32.dll!RegCloseKey
Fault Module Version: 6.0.6002.18327
Fault Module Timestamp: 4cb74dd3
Exception Code: c0000139
Exception Offset: 00000000000b6f08
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 4105
Additional Information 1: fa3e
Additional Information 2: ac0507478d1c5bd693cfc4fe3987e900
Additional Information 3: fa3e
Additional Information 4: ac0507478d1c5bd693cfc4fe3987e900

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

---

Peter
Toronto, Canada

This might need to be posted elsewhere, but there seems to be no option to start a new thread on my display today.

AGAIN, I'm running Milky Way work units that run, complete and then disappear into thin air. No credit is being issued, I'm running the stock applicaiton. I'm processing on an AMD quad core CPU. The current work units I'm running are listed in my account and the notation at the end says "Not in DB". What does that mean?

This project is becoming increasingly frustrating to run. Work units take many hours to run and then it's like they never existed at all. I'm thinking that if I receive no credit, the project must not be receiving results. If that's the case, something needs to be fixed or changed. If no one is getting the benefit of the CPU time I'm donating, I'm not sure why I'm wasting the electricity....

Zen

I think I'll be turning off MW for a while as I'm getting too many 'Error While Computing' and 'Not in DB' WU's. I can't tell what the ratio of good to bad WU's is because they disappear so quickly.

Zen,

on you X4 945 you've got 4 WUs of the "de_separation" type listed. The strange thing is that the website says your app is not in the data base. This is not the WU! WUs finished (either successfully or with some failure) are deleted almost instantaneously here.. which is something that had been used in the past to help the server, but makes troubleshooting increasingly difficult.
In your case I'd try the following:

- Rest the project. You'll probably get a new app, which should then be in the data base again. This one should produce valid results.

- Update your BOINC. 6.4.x is really old and lots of bugs have been fixed since then. You issue could also be a communication problem between an older BOINC client and newer server software.

- Personally I wouldn't want to run separation tasks on any CPU. This app is perfect for GPUs and the ATIs crunch them within minutes instead of hours. And to make matters worse: results become less significant the longer it takes to return them. You could run the n_body app, but sadly I don't think you can choose between the two via the preferences.

MrS

---

Scanning for our furry friends since Jan 2002

The new 0.82 is running fine on my Windows Vista CPU, but N-Body continues to error out within minutes. I wish I could de-select N-Body WUs. Is there any way to do this?

---