Welcome to MilkyWay@home

post milkyway_windows_intelx86 problems here


Advanced search

Message boards : Number crunching : post milkyway_windows_intelx86 problems here
Message board moderation

To post messages, you must log in.

1 · 2 · 3 · 4 · Next

AuthorMessage
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 6419 - Posted: 22 Nov 2008, 11:16:16 UTC
Last modified: 22 Nov 2008, 13:01:52 UTC

Please post any problems with the 32 bit windows binary here. Please provide details about your particular OS and architecture.
ID: 6419 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfilePhil
Avatar

Send message
Joined: 13 Feb 08
Posts: 1124
Credit: 46,740
RAC: 0
10 thousand credit badge10 year member badge
Message 6434 - Posted: 22 Nov 2008, 13:22:48 UTC - in response to Message 6419.  

Crashed because it appears not to talk to Boinc Manager when in Simple View mode:

<result>
<name>nm_test2_336_1227346550_1</name>
<final_cpu_time>645.062500</final_cpu_time>
<exit_status>1</exit_status>
<state>3</state>
<platform>windows_intelx86</platform>
<version_num>1</version_num>
<stderr_out>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
ID: 6434 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfilePhil
Avatar

Send message
Joined: 13 Feb 08
Posts: 1124
Credit: 46,740
RAC: 0
10 thousand credit badge10 year member badge
Message 6452 - Posted: 22 Nov 2008, 17:05:57 UTC

Here is a workunit failed by 2 hosts with your strange Error reading into background_parameters problem.
ID: 6452 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 6454 - Posted: 22 Nov 2008, 17:11:55 UTC - in response to Message 6452.  

Here is a workunit failed by 2 hosts with your strange Error reading into background_parameters problem.


It's funny, i did a grep of that over all of our code and it's nowhere to be found :) what i'm suspecting is that Dave didn't update a file or two in his windows project.
ID: 6454 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
James Nunley

Send message
Joined: 29 Nov 07
Posts: 39
Credit: 74,300,629
RAC: 0
50 million credit badge10 year member badge
Message 6457 - Posted: 22 Nov 2008, 18:27:55 UTC

No Idea what this means but I have a bunch like this



<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003)
</message>
<stderr_txt>
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1227507480.000000
Skipping: /computation_deadline
Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time
Skipping: /mod_time
Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct
Skipping: 100.000000
Skipping: /max_ncpus_pct
ERROR: Invalid parameter detected in function (null). File: (null) Line: 0
ERROR: Expression: (null)


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x76F77DFE

Engaging BOINC Windows Runtime Debugger...



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


BOINC Windows Runtime Debugger Version 5.10.45


Dump Timestamp : 11/22/08 07:22:03
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\ProgramData\BOINC\slots\0;C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway;srv*C:\Windows\TEMP\symbols*http://msdl.microsoft.com/download/symbols


ModLoad: 00400000 00041000 C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway\milkyway_0.1_windows_intelx86.exe (-nosymbols- Symbols Loaded)
ModLoad: 76f30000 00127000 C:\Windows\system32\ntdll.dll (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 757b0000 000db000 C:\Windows\system32\kernel32.dll (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 76830000 000c6000 C:\Windows\system32\ADVAPI32.dll (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 770c0000 000c2000 C:\Windows\system32\RPCRT4.dll (6.0.6001.18051) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 76d10000 0009d000 C:\Windows\system32\USER32.dll (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 758e0000 0004b000 C:\Windows\system32\GDI32.dll (6.0.6001.18023) (-exported- Symbols Loaded)
File Version : 6.0.6001.18023 (vistasp1_gdr.080221-1537)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18023

ModLoad: 77070000 0001e000 C:\Windows\system32\IMM32.DLL (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 76a50000 000c8000 C:\Windows\system32\MSCTF.dll (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6000.16386 (vista_rtm.061101-2205)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6000.16386

ModLoad: 76db0000 000aa000 C:\Windows\system32\msvcrt.dll (7.0.6001.18000) (-exported- Symbols Loaded)
File Version : 7.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 7.0.6001.18000

ModLoad: 76900000 00009000 C:\Windows\system32\LPK.DLL (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 76c30000 0007d000 C:\Windows\system32\USP10.dll (1.626.6001.18000) (-exported- Symbols Loaded)
File Version : 1.0626.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft(R) Uniscribe Unicode script processor
Product Version: 1.0626.6001.18000

ModLoad: 6db90000 000dc000 C:\Windows\system32\dbghelp.dll (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000

ModLoad: 74e40000 00008000 C:\Windows\system32\version.dll (6.0.6001.18000) (-exported- Symbols Loaded)
File Version : 6.0.6001.18000 (longhorn_rtm.080118-1840)
Company Name : Microsoft Corporation
Product Name : Microsoft� Windows� Operating System
Product Version: 6.0.6001.18000



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

- I/O Operations Counters -
Read: 2022, Write: 0, Other 590

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

- Paged Pool Usage -
QuotaPagedPoolUsage: 30560, QuotaPeakPagedPoolUsage: 30560
QuotaNonPagedPoolUsage: 2152, QuotaPeakNonPagedPoolUsage: 2152

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

- Pagefile Usage -
PagefileUsage: 8671232, PeakPagefileUsage: 8671232

- Working Set Size -
WorkingSetSize: 10338304, PeakWorkingSetSize: 10338304, PageFaultCount: 2529

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

- Information -
Status: Ready, Kernel Time: 0.000000, User Time: 2.000000, Wait Time: -2.000000

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x76F77DFE

- Registers -
eax=0000001a ebx=00000001 ecx=0040bc06 edx=76f89a94 esi=00439150 edi=00000000
eip=76f77dfe esp=0012fb30 ebp=0012fb60
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000216

- Callstack -
ChildEBP RetAddr Args to Child
0012fb60 0040fc55 00000000 00000001 000000a1 00439150 ntdll!DbgBreakPoint+0x0
0012fba4 00406a06 00000000 00000001 000000a1 00439150 milkyway_0.1_windows_intelx86!+0x0
019f1f80 01f40470 ffffffff 00000000 00000000 00000000 milkyway_0.1_windows_intelx86!+0x0
019f1f84 ffffffff 00000000 00000000 00000000 019f1fb8 milkyway_0.1_windows_intelx86!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = '01f40470'
01f40470 00000000 5124b96e 88000000 00000000 00000000 milkyway_0.1_windows_intelx86!+0x0 SymFromAddr(): GetLastError = '126' SymGetLineFromAddr(): GetLastError = '126' SymGetModuleInfo(): GetLastError = '126' Address = 'ffffffff'

*** Dump of the Timer thread (aec): ***

- Information -
Status: Waiting, Kernel Time: 0.000000, User Time: 0.000000, Wait Time: -2.000000

- Registers -
eax=018ffad8 ebx=00842db8 ecx=14cfc483 edx=00000000 esi=018fff08 edi=00000000
eip=76f89a94 esp=018ffec4 ebp=018fff2c
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202

- Callstack -
ChildEBP RetAddr Args to Child
018fff2c 757b1c7a 000003e8 00000000 018fff80 0040b76b ntdll!KiFastSystemCallRet+0x0
018fff3c 0040b76b 000003e8 00842db8 00410955 00000000 kernel32!Sleep+0x0
018fff80 004109fa 00000000 757f4911 00842db8 018fffd4 milkyway_0.1_windows_intelx86!+0x0
018fff94 76f6e4b6 00842db8 73524ebb 00000000 00000000 milkyway_0.1_windows_intelx86!+0x0
018fffd4 76f6e489 0041097b 00842db8 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0
018fffec 00000000 0041097b 00842db8 00000000 6c51f3c9 ntdll!RtlInitializeExceptionChain+0x0


*** Debug Message Dump ****


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

Exiting...

</stderr_txt>
]]>
ID: 6457 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileDave Przybylo
Avatar

Send message
Joined: 5 Feb 08
Posts: 236
Credit: 49,648
RAC: 0
10 thousand credit badge10 year member badge
Message 6458 - Posted: 22 Nov 2008, 18:55:56 UTC - in response to Message 6457.  

It seems you were still using version 1 we have since upgraded to 2. See if you still have the same problem
Dave Przybylo
MilkyWay@home Developer
Department of Computer Science
Rensselaer Polytechnic Institute
ID: 6458 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfilePhil
Avatar

Send message
Joined: 13 Feb 08
Posts: 1124
Credit: 46,740
RAC: 0
10 thousand credit badge10 year member badge
Message 6505 - Posted: 23 Nov 2008, 18:10:36 UTC - in response to Message 6419.  

nm_test8 workunits arent checkpointing:

APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0

If a job is exited before it completes it exits with

Error reading into stream_integrals
ID: 6505 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilebanditwolf
Avatar

Send message
Joined: 12 Nov 07
Posts: 2425
Credit: 524,164
RAC: 0
500 thousand credit badge10 year member badge
Message 6508 - Posted: 23 Nov 2008, 18:47:02 UTC

same here:
Name: nm_test8_381_1227457762_0
Workunit: 54601153

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<stderr_txt>
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0

</stderr_txt>
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.
ID: 6508 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfilePhil
Avatar

Send message
Joined: 13 Feb 08
Posts: 1124
Credit: 46,740
RAC: 0
10 thousand credit badge10 year member badge
Message 6512 - Posted: 23 Nov 2008, 18:55:35 UTC - in response to Message 6508.  

The checkpoint file is locked, which is odd because I recall taking a peek inside one on Saturday and that one wasnt.
ID: 6512 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilecaferace
Avatar

Send message
Joined: 4 Aug 08
Posts: 46
Credit: 8,255,900
RAC: 0
5 million credit badge10 year member badge
Message 6514 - Posted: 23 Nov 2008, 18:57:22 UTC - in response to Message 6505.  

nm_test8 workunits arent checkpointing:

APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0
APP: error writing checkpoint (flushing checkpoint file) 0

If a job is exited before it completes it exits with

Error reading into stream_integrals

Same here...

-jim
ID: 6514 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilebanditwolf
Avatar

Send message
Joined: 12 Nov 07
Posts: 2425
Credit: 524,164
RAC: 0
500 thousand credit badge10 year member badge
Message 6565 - Posted: 24 Nov 2008, 13:41:39 UTC

The test8 wu's don't like to be suspended and resumed. One errored out for me.
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.
ID: 6565 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileJLDun
Avatar

Send message
Joined: 17 Nov 07
Posts: 77
Credit: 117,183
RAC: 0
100 thousand credit badge10 year member badge
Message 6876 - Posted: 27 Nov 2008, 16:27:27 UTC - in response to Message 6565.  

Had a task error out after 104 seconds and a computer reboot with "Error reading into stream_integrals"; for app 0.04 series nm_test 26 on a Win32 1.4 GHz Celeron M using BOINC 6.1.9.
ID: 6876 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Brian Silvers

Send message
Joined: 21 Aug 08
Posts: 625
Credit: 558,425
RAC: 0
500 thousand credit badge10 year member badge
Message 7116 - Posted: 1 Dec 2008, 12:09:00 UTC

Checkpointing (or something else) does not seem to be simply "cosmetic"... The situation here is I shut my computer down during the night. Previously the application handled being shut down gracefully. Not now...

Task ID 56860667
Name nm_stripe86_1_2775_1228096449_0
Workunit 57084027
Created 1 Dec 2008 1:54:12 UTC
Sent 1 Dec 2008 2:12:54 UTC
Received 1 Dec 2008 12:02:32 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -1 (0xffffffffffffffff)
Computer ID 26452
Report deadline 4 Dec 2008 2:12:54 UTC
CPU time 1721.734375
stderr out <core_client_version>5.8.16</core_client_version>
<![CDATA[
<message>
- exit code -1 (0xffffffff)
</message>
<stderr_txt>
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
Error reading into stream_integrals

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 7.40839500198479
Granted credit 0
application version 0.04

ID: 7116 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileArion
Avatar

Send message
Joined: 10 Aug 08
Posts: 218
Credit: 41,846,854
RAC: 0
30 million credit badge10 year member badge
Message 7207 - Posted: 2 Dec 2008, 0:18:16 UTC
Last modified: 2 Dec 2008, 0:20:39 UTC

I'm having the same problem here. This isn't a test unit but one of the Stripe Units:

Task ID 56909816
Name nm_stripe79_1_660_1228157480_0
Workunit 57125386
Created 1 Dec 2008 18:51:23 UTC
Sent 1 Dec 2008 19:01:21 UTC
Received 1 Dec 2008 21:56:43 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -1 (0xffffffffffffffff)
Computer ID 36995
Report deadline 4 Dec 2008 19:01:21 UTC
CPU time 941.996438
stderr out <core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
- exit code -1 (0xffffffff)
</message>
<stderr_txt>
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
APP: error writing checkpoint (closing checkpoint file) 0
Error reading into stream_integrals

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 4.89181571567951
Granted credit 0
application version 0.04
ID: 7207 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 7214 - Posted: 2 Dec 2008, 1:12:27 UTC - in response to Message 7207.  

Yeah we're aware of the checkpointing problem on windows. It should be fixed as soon as Dave updates the windows app to 0.6
ID: 7214 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileArion
Avatar

Send message
Joined: 10 Aug 08
Posts: 218
Credit: 41,846,854
RAC: 0
30 million credit badge10 year member badge
Message 7222 - Posted: 2 Dec 2008, 2:47:42 UTC - in response to Message 7214.  

Yeah we're aware of the checkpointing problem on windows. It should be fixed as soon as Dave updates the windows app to 0.6



I saw that on on of my systems and everything seemed to be fine after that first one. I have a Windows Xp system with an XP 3000 AMD and I've had to shut it down as its getting non stop errors. Finally caught up with it after you extended the times that the results are online..


Will wait for the .06 app before I bring it back online with MW.




ID: 7222 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 7223 - Posted: 2 Dec 2008, 2:54:07 UTC - in response to Message 7222.  

Yeah we're aware of the checkpointing problem on windows. It should be fixed as soon as Dave updates the windows app to 0.6



I saw that on on of my systems and everything seemed to be fine after that first one. I have a Windows Xp system with an XP 3000 AMD and I've had to shut it down as its getting non stop errors. Finally caught up with it after you extended the times that the results are online..


Will wait for the .06 app before I bring it back online with MW.





0.6 should be available now.
ID: 7223 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileThe Ancient One

Send message
Joined: 28 Apr 08
Posts: 11
Credit: 3,128,430
RAC: 0
3 million credit badge10 year member badge
Message 7226 - Posted: 2 Dec 2008, 3:03:58 UTC

OS Vista 32bit x86 2 core 3.2GHz Intel 3GB Ram 6GB Virtual Status: Workstation/Server compliant.

I've noted that wu nm_stripe82_2_109_1228184198_0 is running as 'high priority' due to task manager registering it as follows:

CPU TIME; 0:3:30 PROGRESS; 3.989% TO COMPLETION; 443:50:30

I believe their is an error within the wu its self. Is this correct?



All man born has the right to life and no man born has the right to take that life.
ID: 7226 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTravis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
10 thousand credit badge10 year member badge
Message 7228 - Posted: 2 Dec 2008, 3:28:44 UTC - in response to Message 7226.  

OS Vista 32bit x86 2 core 3.2GHz Intel 3GB Ram 6GB Virtual Status: Workstation/Server compliant.

I've noted that wu nm_stripe82_2_109_1228184198_0 is running as 'high priority' due to task manager registering it as follows:

CPU TIME; 0:3:30 PROGRESS; 3.989% TO COMPLETION; 443:50:30

I believe their is an error within the wu its self. Is this correct?


This is a problem with the boinc manager actually. The time to completion should should sort itself out after a wu or two.
ID: 7228 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileArion
Avatar

Send message
Joined: 10 Aug 08
Posts: 218
Credit: 41,846,854
RAC: 0
30 million credit badge10 year member badge
Message 7238 - Posted: 2 Dec 2008, 10:39:33 UTC - in response to Message 7223.  

0.6 should be available now.



.06 did the trick. My XP+3000+ system is completing the workunits successfully again.

Thanks for the fast fix!




ID: 7238 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
1 · 2 · 3 · 4 · Next

Message boards : Number crunching : post milkyway_windows_intelx86 problems here

©2020 Astroinformatics Group