Welcome to MilkyWay@home

Posts by Senilix

1) Message boards : News : MilkyWay@home Version 1.38 Released (Message 65174)
Posted 19 Sep 2016 by ProfileSenilix
Post:
Something's not right with the opencl_ati_101 app.

On my AMD Radeon R9 version 1.36 used to run 11 seconds, now version 1.38 needs more than 10 minutes (see http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1791907717)!?

Most of the time it's not even utilizing the graphic card but running solely on a full cpu core.

Greetings,
Senilix

Edit: I compared the stdout files of a 1.36 job and a 1.38 job. Looks like 1.38 doesn't detect my gpu anymore...
2) Message boards : Number crunching : Validator is down (Message 65030)
Posted 16 Aug 2016 by ProfileSenilix
Post:
Tons of pending work units are piling up.
3) Message boards : News : New Separation Runs Started (Message 57693)
Posted 28 Mar 2013 by ProfileSenilix
Post:
Yep, there definitely is something wrong with these tasks. Mine was crashing after a split second. Here's the stderr output:
<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
Unzul�ssige Funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.00 Windows x86 double </search_application>
Unrecognized XML in project preferences: max_gfx_cpu_pct
Skipping: 0
Skipping: /max_gfx_cpu_pct
Unrecognized XML in project preferences: apps_selected
Skipping: app_id
Skipping: /apps_selected
Unrecognized XML in project preferences: nbody_graphics_poll_period
Skipping: 30
Skipping: /nbody_graphics_poll_period
Unrecognized XML in project preferences: nbody_graphics_float_speed
Skipping: 5
Skipping: /nbody_graphics_float_speed
Unrecognized XML in project preferences: nbody_graphics_textured_point_size
Skipping: 250
Skipping: /nbody_graphics_textured_point_size
Unrecognized XML in project preferences: nbody_graphics_point_point_size
Skipping: 40
Skipping: /nbody_graphics_point_point_size
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' 
Error reading astronomy parameters from file 'astronomy_parameters.txt'
  Trying old parameters file
Integral area { 1819239215, 1769234796, 1008738314 } will overflow progress calculation
Error reading parameters file
Failed to read parameters file
19:51:28 (4132): called boinc_finish

</stderr_txt>
]]>
4) Message boards : News : New Separation Runs Started (Message 57691)
Posted 28 Mar 2013 by ProfileSenilix
Post:
Are these WUs much longer than the previous ones?

I'm asking because my BOINC client decided to switch to panic mode immediately after it got one of them.

Here's the WU's XML definition:

<workunit>
    <name>ps_separation_82_3s_dr8_2_1358941502_29559263</name>
    <app_name>milkyway</app_name>
    <version_num>100</version_num>
    <rsc_fpops_est>89643799999999993000000000000000.000000</rsc_fpops_est>
    <rsc_fpops_bound>89643799999999998000000000000000000.000000</rsc_fpops_bound>
    <rsc_memory_bound>50000000.000000</rsc_memory_bound>
    <rsc_disk_bound>15000000.000000</rsc_disk_bound>
    <command_line>
-np 20 -p 0.943595320917666 23.0867525425274 -17.2245569434017 30.1253113951534 27.7632766885683 1.17406084491819 4.12454840047643 13.0079187392257 -11.5395608730614 39.1341196808498 22.0797624444123 0.980515889188198 1.62739609185373 12.7507249950431 13.1226277071983 41.4128890240099 30.2472704153508 6.16794836081251 3.20157651974716 5.24611199158244
    </command_line>
    <file_ref>
        <file_name>p-82-3s-dr8-2.txt</file_name>
        <open_name>astronomy_parameters.txt</open_name>
    </file_ref>
    <file_ref>
        <file_name>stars-82-dr8.txt</file_name>
        <open_name>stars.txt</open_name>
    </file_ref>
</workunit>


<rsc_fpops_est> is much higher than it's used to be. BOINC deducted an estimated execution time of more then 24 hours...
5) Message boards : Number crunching : MilkyWay@Home v0.88 and MilkyWay@Home N-Body Simulation v0.66 (mt) (Message 50409)
Posted 27 Jul 2011 by ProfileSenilix
Post:
So it will ONLY got tasks from MW@Home, and not MW@Home N-Body Simulation (mt)?


Exactly - and the MW@Home tasks will finish much faster because the optimized app will use the SSE3 instruction set of your INTEL PC.
6) Message boards : Number crunching : No cache limit for CPU app??? (Message 50400)
Posted 26 Jul 2011 by ProfileSenilix
Post:
I'm running a GPU-only host on a dual core computer and my cache limit is set to 12 tasks - equaling 20 minutes.

Now i noticed a wingman with a CPU-only host http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=302135 and a cache of more than 2700 tasks - equaling 2,000,000 minutes or more than 3 years????

Is there no cache limit in effect for the CPU app - or is this just a bug?
7) Message boards : Number crunching : MilkyWay@Home v0.88 and MilkyWay@Home N-Body Simulation v0.66 (mt) (Message 50398)
Posted 26 Jul 2011 by ProfileSenilix
Post:
Sorry, i didn't notice that there is no instruction.txt file contained in the download.

First download the MilyWay@Home Windows 32/64 bit SSE3 INTEL CPUs ONLY Science App from http://www.mpits.net/opt_mw.php.
This should be the correct one for your type of computer/OS.

Installation of the optimized app is simple.

1) Stop BOINC service by going to the advanced menu and selecting "Shut down connected client, click okay and then click cancel. Then exit out of the BOINC Manager.

2) The zip file you've downloaded contains 2 files, an exe and an app_info.xml file. Extract both files into your BOINC\projects\milkyway.cs.rpi.edu_milkyway folder.

Windows 98/SE/ME: C:\Windows\All Users\BOINC\ or C:\Windows\Profiles\All Users\BOINC\

Windows 2000/XP: C:\Documents and Settings\All Users\Application Data\BOINC\

Windows Vista and Windows 7: C:\ProgramData\BOINC\

3) Restart BOINC service by reopening BOINC Manager.

That's it, you're done! You can open your task manager to see that it's really the new optimized app crunching your WUs.

BOINC will tell you that it found app_info.xml and is using an "anonymous platform".


Happy crunching!
8) Message boards : Number crunching : MilkyWay@Home v0.88 and MilkyWay@Home N-Body Simulation v0.66 (mt) (Message 50390)
Posted 26 Jul 2011 by ProfileSenilix
Post:
Here at mw there is no way to select which type of CPU work your pc gets - at least not in your account configuration.

But you can use an app_info.xml file to restrict your pc to wm@home apps only. The following message contains a download link to a SSE optimized exe, an appropriate app_info.xml and a textfile with instruction on how to install the exe and xml files.

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2473&nowrap=true#50045
9) Message boards : Number crunching : ps_separation and ps_test WUs all erroring out (Message 49644)
Posted 27 Jun 2011 by ProfileSenilix
Post:
All of the above mentioned WUs are erroring out on my ATI HD 5850. Same for my wingmen. As some of them are running nVidia cards, the issue seems to be WU related.
10) Message boards : Number crunching : Lastest Stock Apps - Optimized or Not (Message 49613)
Posted 26 Jun 2011 by ProfileSenilix
Post:
Here's a 'optimized' CPU app which was compiled using the Intel(R) C++ Compiler XE 12.0.4.196 for Windows.

A SSE2 compatible CPU is required (AMD & Intel)!
Difference is that we're using Intels LibM especially the exp(e^x) function, which is faster than the 'stock' SSE2 polyn. eval....

download -> MilkyWay Separation SSE2 Intel&AMD


I am getting a 404 when i'm trying to download that opti app.
11) Message boards : News : Any remaining major credit or application problems? (Message 49514)
Posted 23 Jun 2011 by ProfileSenilix
Post:
Weekend would be better!

+1
12) Message boards : News : assimilator back up (Message 45369)
Posted 31 Dec 2010 by ProfileSenilix
Post:
Yes, thanks, i guess you are right. The credit is missing in BoincStats only, my Milkyway account is showing the correct amount.
13) Message boards : News : assimilator back up (Message 45363)
Posted 31 Dec 2010 by ProfileSenilix
Post:
Looks like there are more issues:

I lost 200+K credits (which i may have earned due to the infamous assimilator/validator bug leading to duplicated credits for many WUs though)

Downloads are failing now
31.12.2010 22:29:10 Milkyway@home Giving up on download of de_separation_16_3s_fix_1_253969_1293575410_search_parameters: file not found
14) Message boards : Number crunching : Validator stuck? (Message 45062)
Posted 16 Dec 2010 by ProfileSenilix
Post:
Workunits waiting for validation are piling up.

And just to mention it: the issue with the assimilator doppelganger - with the effect of credits being double-counted - is still not solved.
15) Message boards : News : an update on the credit issue (Message 44801)
Posted 7 Dec 2010 by ProfileSenilix
Post:
Same here, am getting twice the usual credit for most WUs.

But no need to rush into it, Travis ... you can fix thee issue between the years ... or next year ... or even ... :)
16) Message boards : Number crunching : super charged? (Message 43841)
Posted 15 Nov 2010 by ProfileSenilix
Post:
Double counting of wus seems to have been re-installed ... and i'm not complaining ;)
17) Message boards : Number crunching : Feeder & validator need kicking (Message 38536)
Posted 10 Apr 2010 by ProfileSenilix
Post:
Validator needs kicking again ....
18) Message boards : Number crunching : de_11_3s_free_5... computation error (cuda23) (Message 37361)
Posted 15 Mar 2010 by ProfileSenilix
Post:
I just noticed that a couple of my wu's ended with a computation error. I found that ALL of them have been of the de_11_3s_free_5 type whilst every wu I crunched successfully has NOT been of that type.

Here's an example of the output of an erroneous wu.


Task 80201382

Name de_11_3s_free_5_1323519_1268608770_0
Workunit 75024904
Created 14 Mar 2010 23:19:33 UTC
Sent 14 Mar 2010 23:20:26 UTC
Received 15 Mar 2010 0:12:34 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xffffffffc0000005)
Computer ID 36488
Report deadline 22 Mar 2010 23:20:26 UTC
Run time 1065.359375
CPU time 8.203125
stderr out

<core_client_version>6.10.29</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
Device index specified on the command line was 0
Looking for a Double Precision capable NVIDIA GPU
The device GeForce GTX 260 specified on the command line can be used
Used 158268/917184 memory, 758915 remaining


Unhandled Exception Detected...

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

Engaging BOINC Windows Runtime Debugger...



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


BOINC Windows Runtime Debugger Version 6.7.0


Dump Timestamp : 03/15/10 01:10:48
Install Directory : H:\Programme\BOINC\
Data Directory : H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC
Project Symstore :
Loaded Library : H:\Programme\BOINC\\dbghelp.dll
Loaded Library : H:\Programme\BOINC\\symsrv.dll
Loaded Library : H:\Programme\BOINC\\srcsrv.dll
LoadLibraryA( H:\Programme\BOINC\\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC\slots\2;H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC\projects\milkyway.cs.rpi.edu_milkyway;srv*H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC\projects\milkyway.cs.rpi.edu_milkywaysymbols*http://msdl.microsoft.com/download/symbols;srv*H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC\projects\milkyway.cs.rpi.edu_milkywaysymbols*http://boinc.berkeley.edu/symstore


ModLoad: 00400000 000f2000 H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.24_windows_intelx86__cuda23.exe (-nosymbols- Symbols Loaded)
Linked PDB Filename : D:\milkyway\bin\Release\milkyway.pdb

ModLoad: 7c910000 000b9000 H:\WINDOWS\system32\ntdll.dll (5.1.2600.5755) (PDB Symbols Loaded)
Linked PDB Filename : ntdll.pdb
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 5.1.2600.5755

ModLoad: 7c800000 00108000 H:\WINDOWS\system32\kernel32.dll (5.1.2600.5781) (PDB Symbols Loaded)
Linked PDB Filename : kernel32.pdb
File Version : 5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 5.1.2600.5781

ModLoad: 10000000 02710000 H:\WINDOWS\system32\nvcuda.dll (6.14.11.9634) (-exported- Symbols Loaded)
Linked PDB Filename :
File Version : 6.14.11.9634
Company Name : NVIDIA Corporation
Product Name : NVIDIA CUDA 3.0.1 driver
Product Version : 6.14.11.9634

ModLoad: 7e360000 00091000 H:\WINDOWS\system32\USER32.dll (5.1.2600.5512) (PDB Symbols Loaded)
Linked PDB Filename : user32.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2105)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 77ef0000 00049000 H:\WINDOWS\system32\GDI32.dll (5.1.2600.5698) (PDB Symbols Loaded)
Linked PDB Filename : gdi32.pdb
File Version : 5.1.2600.5698 (xpsp_sp3_gdr.081022-1932)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5698

ModLoad: 77da0000 000aa000 H:\WINDOWS\system32\ADVAPI32.dll (5.1.2600.5755) (PDB Symbols Loaded)
Linked PDB Filename : advapi32.pdb
File Version : 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 5.1.2600.5755

ModLoad: 77e50000 00092000 H:\WINDOWS\system32\RPCRT4.dll (5.1.2600.5795) (PDB Symbols Loaded)
Linked PDB Filename : rpcrt4.pdb
File Version : 5.1.2600.5795 (xpsp_sp3_gdr.090415-1241)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5795

ModLoad: 77fc0000 00011000 H:\WINDOWS\system32\Secur32.dll (5.1.2600.5834) (PDB Symbols Loaded)
Linked PDB Filename : secur32.pdb
File Version : 5.1.2600.5834 (xpsp_sp3_gdr.090624-1305)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version : 5.1.2600.5834

ModLoad: 00340000 00048000 H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC\projects\milkyway.cs.rpi.edu_milkyway\cudart.dll (6.14.11.2020) (-exported- Symbols Loaded)
Linked PDB Filename :
File Version : 6,14,11,2020
Company Name : NVIDIA Corporation
Product Name : NVIDIA CUDA 2.2 Runtime
Product Version : 6,14,11,2020

ModLoad: 00390000 00057000 H:\Dokumente und Einstellungen\All Users\Anwendungsdaten\BOINC\projects\milkyway.cs.rpi.edu_milkyway\cutil32.dll (-exported- Symbols Loaded)
Linked PDB Filename : c:\Documents and Settings\All Users.WINDOWS\Application Data\NVIDIA Corporation\NVIDIA CUDA SDK\common\lib\cutil32.pdb

ModLoad: 76330000 0001d000 H:\WINDOWS\system32\IMM32.DLL (5.1.2600.5512) (PDB Symbols Loaded)
Linked PDB Filename : imm32.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: 00c60000 00110000 H:\WINDOWS\system32\nvapi.dll (6.14.11.9634) (-exported- Symbols Loaded)
Linked PDB Filename : d:\bld\r196_21\drivers\nvapi\_out\winxp_x86_release\nvapi.pdb
File Version : 6.14.11.9634
Company Name : NVIDIA Corporation
Product Name : NVIDIA Windows drivers
Product Version : 6.14.11.9634

ModLoad: 774b0000 0013d000 H:\WINDOWS\system32\ole32.dll (5.1.2600.5512) (PDB Symbols Loaded)
Linked PDB Filename : ole32.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 77be0000 00058000 H:\WINDOWS\system32\msvcrt.dll (7.0.2600.5512) (PDB 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

Get Product Name Failed.
ModLoad: 770f0000 0008b000 H:\WINDOWS\system32\OLEAUT32.dll (5.1.2600.5512) (PDB Symbols Loaded)
Linked PDB Filename : oleaut32.pdb
File Version : 5.1.2600.5512
Company Name : Microsoft Corporation
Product Name :
Product Version : 5.1.2600.5512

ModLoad: 77f40000 00076000 H:\WINDOWS\system32\SHLWAPI.dll (6.0.2900.5912) (PDB Symbols Loaded)
Linked PDB Filename : shlwapi.pdb
File Version : 6.00.2900.5912 (xpsp_sp3_gdr.091207-1454)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.00.2900.5912

ModLoad: 7e670000 00821000 H:\WINDOWS\system32\SHELL32.dll (6.0.2900.5622) (-exported- Symbols Loaded)
Linked PDB Filename : shell32.pdb
File Version : 6.00.2900.5622 (xpsp_sp3_gdr.080617-1319)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 6.00.2900.5622

ModLoad: 778f0000 000f4000 H:\WINDOWS\system32\SETUPAPI.dll (5.1.2600.5512) (PDB Symbols Loaded)
Linked PDB Filename : setupapi.pdb
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Company Name : Microsoft Corporation
Product Name : Betriebssystem Microsoft� Windows�
Product Version : 5.1.2600.5512

ModLoad: 77bd0000 00008000 H:\WINDOWS\system32\VERSION.dll (5.1.2600.5512) (PDB 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

ModLoad: 773a0000 00103000 H:\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: 5d450000 0009a000 H:\WINDOWS\system32\comctl32.dll (5.82.2900.5512) (PDB 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: 04d60000 00115000 H:\Programme\BOINC\dbghelp.dll (6.8.4.0) (PDB 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: 01550000 00048000 H:\Programme\BOINC\symsrv.dll (6.8.4.0) (PDB 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: 04e80000 0003b000 H:\Programme\BOINC\srcsrv.dll (6.8.4.0) (PDB 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



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

- I/O Operations Counters -
Read: 743, Write: 0, Other 418

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

- Paged Pool Usage -
QuotaPagedPoolUsage: 139188, QuotaPeakPagedPoolUsage: 152404
QuotaNonPagedPoolUsage: 3504, QuotaPeakNonPagedPoolUsage: 4480

- Virtual Memory Usage -
VirtualSize: 122544128, PeakVirtualSize: 253374464

- Pagefile Usage -
PagefileUsage: 82489344, PeakPagefileUsage: 215633920

- Working Set Size -
WorkingSetSize: 48369664, PeakWorkingSetSize: 181501952, PageFaultCount: 55776

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

- Information -
Status: Wait Reason: UserRequest, , Kernel Time: 3281250.000000, User Time: 79062496.000000, Wait Time: 2658823.000000

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

- Registers -
eax=0252eff0 ebx=00000000 ecx=04d5a030 edx=00000000 esi=00000000 edi=0252eff0
eip=00408036 esp=0012fc74 ebp=0012fdb4
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246

- Callstack -
ChildEBP RetAddr Args to Child
0012fdb4 00401bb5 024fef58 005e2f30 00000001 7ffdf000 milkyway_0.24_windows_intelx86_!+0x0
0012ff4c 00401d76 00000000 00000001 00000001 00000001 milkyway_0.24_windows_intelx86_!+0x0
0012ffc0 7c817077 005e2f30 00000000 7ffdf000 c0000005 milkyway_0.24_windows_intelx86_!+0x0
0012fff0 00000000 0041aa1f 00000000 78746341 00000020 kernel32!_BaseProcessStart@4+0x0

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

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

- Registers -
eax=00c5f890 ebx=00000000 ecx=00000006 edx=00000000 esi=00000000 edi=00c5ff70
eip=7c91e514 esp=00c5ff40 ebp=00c5ff98
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202

- Callstack -
ChildEBP RetAddr Args to Child
00c5ff3c 7c91d21a 7c8023f1 00000000 00c5ff70 00000000 ntdll!_KiFastSystemCallRet@0+0x0 FPO: [0,0,0]
00c5ff40 7c8023f1 00000000 00c5ff70 00000000 00000000 ntdll!_NtDelayExecution@8+0x0 FPO: [2,0,0]
00c5ff98 7c802455 00000064 00000000 00c5ffb4 00416b34 kernel32!_SleepEx@8+0x0
00c5ffa8 00416b34 00000064 00c5ffec 7c80b729 00000000 kernel32!_Sleep@4+0x0
00c5ffb4 7c80b729 00000000 00000000 00000000 00000000 milkyway_0.24_windows_intelx86_!+0x0
00c5ffec 00000000 00416b20 00000000 00000000 00905a4d 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 0.0450216793324415
Granted credit 0
application version MilkyWay@Home v0.24 (cuda23)

Home | My Account | Message Boards


Copyright © 2010 AstroInformatics Group


The wu's are running up to ~99.9%, then stopping for a while and eventually ending with a computation error.

I decided to abort any wu of that de_11_3s_free_5 type delivered to my box.


EDIT: This seems to be CUDA-related only as my wingmen's ATI boxes are crunching them successfully.
19) Message boards : Number crunching : NVidia 196.75 WHQL withdrawn - Causes Overheating (Message 37040)
Posted 8 Mar 2010 by ProfileSenilix
Post:
EDIT: Sorry double post.

The Collatz admin is recommending a fall back to version 196.21 but i found this in a Collatz thread from Zydor:

Anyone using the 196.75 WHQL driver should roll back to 196.21 WHQL to avoid issues. NVidia have released a statement acknowledging the problem, withdrawn the 196.75 WHQL driver from its Site, and recommend rolling back to 196.21 WHQL (However see below).

196.75 Withdrawn by NVidia

However, 196.21 has a bug stopping GPU overclocking. I personally rolled back to 196.34 which although formally a Beta driver, only has the GPU overclock bug fix as the difference with the bugged 196.21 WHQL

Regards
Zy
20) Message boards : Number crunching : NVidia 196.75 WHQL withdrawn - Causes Overheating (Message 37039)
Posted 8 Mar 2010 by ProfileSenilix
Post:
The Collatz admin is recommending a fall back to version 196.21 but i found this in a Collatz thread from Zydor:

Anyone using the 196.75 WHQL driver should roll back to 196.21 WHQL to avoid issues. NVidia have released a statement acknowledging the problem, withdrawn the 196.75 WHQL driver from its Site, and recommend rolling back to 196.21 WHQL (However see below).

196.75 Withdrawn by NVidia

However, 196.21 has a bug stopping GPU overclocking. I personally rolled back to 196.34 which although formally a Beta driver, only has the GPU overclock bug fix as the difference with the bugged 196.21 WHQL

Regards
Zy


Next 20

©2021 Astroinformatics Group