Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 28
Posts: 28   Pages: 3   [ 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 6422 times and has 27 replies Next Thread
NixChix
Veteran Cruncher
United States
Joined: Apr 29, 2007
Post Count: 1187
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
MIP1 Tasks Fail During Shutdown

I have recently stopped running my computer 24x7 and have experienced that the WUs have errored-out upon restart, though not always all of them. I eventually checked the logs and realized that they are actually failing during shutdown, not restart. Last night I caught a fleeting glimpse of a pop-up message that I think stated "invalid instruction". Here is one of the logs (the others appear similar except for the addresses):

<core_client_version>7.2.47</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073741819 (0xc0000005)
</message>

Cheers coffee
<stderr_txt>
[2019-12-20 0: 4:38:] :: BOINC:: Initializing ... ok.
[2019-12-20 0: 4:39:] :: BOINC :: boinc_init()
INFO: result number = 0
BOINC:: Setting up shared resources ... ok.
BOINC:: Setting up semaphores ... ok.
BOINC:: Updating status ... ok.
BOINC:: Registering timer callback... ok.
BOINC:: Worker initialized successfully.
command: projects/www.worldcommunitygrid.org/wcgrid_mip1_rosetta_7.16_windows_intelx86 -in::file::zip MIP1_databasev2.zip @./MIP1_00257744.flags -out::file::silent result_silent.out -run:jran 873195579 -nstruct 6 -out::level 100 -run::no_scorefile true
Registering options..
Registered extra options.
Initializing broker options ...
Registered extra options.
Initializing core...
Initializing options.... ok
Options::initialize()
Options::adding_options()
Options::initialize() Check specs.
Options::initialize() End reached
Loaded options.... ok
Processed options.... ok
Initializing random generators... ok
Initialization complete.
Initializing options.... ok
Options::initialize()
Options::adding_options()
Options::initialize() Check specs.
Options::initialize() End reached
Loaded options.... ok
Processed options.... ok
Initializing random generators... ok
Initialization complete.
Setting WU description ...
Unpacking zip data: ../../projects/www.worldcommunitygrid.org/mip1.MIP1_databasev2.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
set_shared_memory_fully_initialized ...
abrelax ...
abrelax.run
Setting up folding (abrelax) ...
Beginning folding (abrelax) ...
BOINC:: Worker startup.
Starting work on structure: _0001


Unhandled Exception Detected...

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

Engaging BOINC Windows Runtime Debugger...



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


BOINC Windows Runtime Debugger Version 7.7.0


Dump Timestamp : 12/20/19 00:06:22
Install Directory : C:\Program Files (x86)\BOINC\
Data Directory : C:\ProgramData\BOINC
Project Symstore :
Loaded Library : C:\Program Files (x86)\BOINC\\dbghelp.dll
Loaded Library : C:\Program Files (x86)\BOINC\\symsrv.dll
Loaded Library : C:\Program Files (x86)\BOINC\\srcsrv.dll
LoadLibraryA( C:\Program Files (x86)\BOINC\\version.dll ): GetLastError = 126
Loaded Library : version.dll
Debugger Engine : 4.0.5.0
Symbol Search Path: C:\ProgramData\BOINC\slots\7;C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org


ModLoad: 0000000000370000 000000000342a000 C:\ProgramData\BOINC\projects\www.worldcommunitygrid.org\wcgrid_mip1_rosetta_7.16_windows_intelx86 (-exported- Symbols Loaded)
Linked PDB Filename :

ModLoad: 00000000770a0000 0000000000180000 C:\Windows\SysWOW64\ntdll.dll (6.1.7601.24384) (-exported- Symbols Loaded)
Linked PDB Filename : wntdll.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000075730000 0000000000110000 C:\Windows\syswow64\kernel32.dll (6.1.7601.24384) (-exported- Symbols Loaded)
Linked PDB Filename : wkernel32.pdb
File Version : 6.1.7601.18015 (win7sp1_gdr.121129-1432)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.18015

ModLoad: 0000000075f20000 0000000000047000 C:\Windows\syswow64\KERNELBASE.dll (6.1.7601.24384) (-exported- Symbols Loaded)
Linked PDB Filename : wkernelbase.pdb
File Version : 6.1.7601.18015 (win7sp1_gdr.121129-1432)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.18015

ModLoad: 0000000076030000 0000000000035000 C:\Windows\syswow64\WS2_32.dll (6.1.7601.23451) (-exported- Symbols Loaded)
Linked PDB Filename : ws2_32.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000075050000 00000000000ac000 C:\Windows\syswow64\msvcrt.dll (7.0.7601.17744) (-exported- Symbols Loaded)
Linked PDB Filename : msvcrt.pdb
File Version : 7.0.7601.17744 (win7sp1_gdr.111215-1535)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 7.0.7601.17744

ModLoad: 0000000075d90000 00000000000f0000 C:\Windows\syswow64\RPCRT4.dll (6.1.7601.24384) (-exported- Symbols Loaded)
Linked PDB Filename : wrpcrt4.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000747c0000 0000000000060000 C:\Windows\syswow64\SspiCli.dll (6.1.7601.24384) (-exported- Symbols Loaded)
Linked PDB Filename : wsspicli.pdb
File Version : 6.1.7601.24384 (win7sp1_ldr_escrow.190220-1800)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.24384

ModLoad: 00000000747b0000 000000000000c000 C:\Windows\syswow64\CRYPTBASE.dll (6.1.7601.24384) (-exported- Symbols Loaded)
Linked PDB Filename : cryptbase.pdb
File Version : 6.1.7601.24384 (win7sp1_ldr_escrow.190220-1800)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.24384

ModLoad: 0000000075a80000 0000000000019000 C:\Windows\SysWOW64\sechost.dll (6.1.7601.18869) (-exported- Symbols Loaded)
Linked PDB Filename : sechost.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000075100000 0000000000006000 C:\Windows\syswow64\NSI.dll (6.1.7601.23889) (-exported- Symbols Loaded)
Linked PDB Filename : nsi.pdb
File Version : 6.1.7601.23889 (win7sp1_ldr.170810-1615)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.23889

ModLoad: 0000000075450000 0000000000100000 C:\Windows\syswow64\USER32.dll (6.1.7601.23594) (-exported- Symbols Loaded)
Linked PDB Filename : wuser32.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.17514

ModLoad: 00000000751c0000 0000000000090000 C:\Windows\syswow64\GDI32.dll (6.1.7601.24234) (-exported- Symbols Loaded)
Linked PDB Filename : wgdi32.pdb
File Version : 6.1.7601.24234 (win7sp1_ldr.180813-0600)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.24234

ModLoad: 0000000076000000 000000000000a000 C:\Windows\syswow64\LPK.dll (6.1.7601.24231) (-exported- Symbols Loaded)
Linked PDB Filename : wlpk.pdb
File Version : 6.1.7601.24231 (win7sp1_ldr.180810-0600)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.24231

ModLoad: 0000000075690000 000000000009d000 C:\Windows\syswow64\USP10.dll (1.626.7601.23894) (-exported- Symbols Loaded)
Linked PDB Filename : usp10.pdb
File Version : 1.0626.7601.23894 (win7sp1_ldr.170816-0600)
Company Name : Microsoft Corporation
Product Name : Microsoft(R) Uniscribe Unicode script processor
Product Version : 1.0626.7601.23894

ModLoad: 0000000075aa0000 00000000000a1000 C:\Windows\syswow64\ADVAPI32.dll (6.1.7601.24384) (-exported- Symbols Loaded)
Linked PDB Filename : advapi32.pdb
File Version : 6.1.7601.24384 (win7sp1_ldr_escrow.190220-1800)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.24384

ModLoad: 0000000075160000 0000000000060000 C:\Windows\system32\IMM32.DLL (6.1.7601.17514) (-exported- Symbols Loaded)
Linked PDB Filename : wimm32.pdb
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7601.17514

ModLoad: 0000000075cb0000 00000000000cd000 C:\Windows\syswow64\MSCTF.dll (6.1.7601.23915) (-exported- Symbols Loaded)
Linked PDB Filename : msctf.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000071280000 0000000000021000 C:\Windows\system32\ntmarta.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : ntmarta.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 0000000075110000 0000000000045000 C:\Windows\syswow64\WLDAP32.dll (6.1.7601.23889) (-exported- Symbols Loaded)
Linked PDB Filename : wldap32.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385

ModLoad: 00000000742e0000 0000000000115000 C:\Program Files (x86)\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: 0000000074740000 0000000000048000 C:\Program Files (x86)\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: 00000000742a0000 000000000003b000 C:\Program Files (x86)\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: 0000000072f30000 0000000000009000 C:\Windows\system32\version.dll (6.1.7600.16385) (-exported- Symbols Loaded)
Linked PDB Filename : version.pdb
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 6.1.7600.16385



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

- I/O Operations Counters -
Read: 11737, Write: 0, Other 2798

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

- Paged Pool Usage -
QuotaPagedPoolUsage: 204112, QuotaPeakPagedPoolUsage: 204112
QuotaNonPagedPoolUsage: 9488, QuotaPeakNonPagedPoolUsage: 9488

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

- Pagefile Usage -
PagefileUsage: 94908416, PeakPagefileUsage: 94908416

- Working Set Size -
WorkingSetSize: 89989120, PeakWorkingSetSize: 89989120, PageFaultCount: 22775

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

- Information -
Status: Wait Reason: UserRequest, , Kernel Time: 156001.000000, User Time: 0.000000, Wait Time: 6702667.000000

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

- Registers -
eax=043e2761 ebx=00000015 ecx=00000000 edx=0382e188 esi=081c0020 edi=081c0020
eip=0146d380 esp=0c1ef6d4 ebp=0c1ef6d8
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202

- Callstack -
ChildEBP RetAddr Args to Child
0c1ef6d8 0146e55b 043e2761 081c0020 0c1ef6fc 01450aae wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::statements_cache+0x0
0c1ef6e8 01450aae 081c0020 081c0020 00000000 0c1ef710 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::statements_cache+0x0
0c1ef6fc 0145635f 081c0020 014562f0 00000000 0c1ef74c wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::statements_cache+0x0
0c1ef710 00864e0b 00000015 7c3a8794 00000001 00000006 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::statements_cache+0x0
0c1ef74c 757e7731 0312b13c 7e4e526e 00000000 00000000 wcgrid_mip1_rosetta_7!cppdb::atomic_counter::get+0x0
0c1ef7d8 7574344d 00000006 0c1ef824 770d9802 80000006 kernel32!CtrlRoutine+0x0
0c1ef7e4 770d9802 80000006 7d3d3283 00000000 00000000 kernel32!BaseThreadInitThunk+0x0
0c1ef824 770d97d5 757e757c 80000006 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0
0c1ef83c 00000000 757e757c 80000006 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0

*** Dump of thread ID 3668 (state: Running): ***

- Information -
Status: Base Priority: Above Normal, Priority: Above Normal, , Kernel Time: 15912102.000000, User Time: 933822016.000000, Wait Time: 6702665.000000

- Registers -
eax=00000001 ebx=0aa472f8 ecx=0a97f4d8 edx=0ac6fb58 esi=0ac6fb58 edi=0aa472ec
eip=014f0080 esp=0433ea84 ebp=0433ea8c
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202

- Callstack -
ChildEBP RetAddr Args to Child
0433ea8c 014ef4f9 09aaf4a4 0aa472f8 0aa472ec 0aa0cd68 wcgrid_mip1_rosetta_7!cppdb::shared_object::safe_sym+0x0
0433eaac 0233c6f1 0a38eaf0 0433eae0 014eff2c 00000001 wcgrid_mip1_rosetta_7!cppdb::shared_object::safe_sym+0x0
0433eab8 014eff2c 00000001 ffffffff 0a38eaf0 0a4ea968 wcgrid_mip1_rosetta_7!cppdb::version_number+0x0
0433eae0 0233c74b 74179bd8 0a438ba8 0a38eaf0 0433eb24 wcgrid_mip1_rosetta_7!cppdb::shared_object::safe_sym+0x0
0433eb00 00df876d 00000001 022dde33 74179be8 0ad26d38 wcgrid_mip1_rosetta_7!cppdb::version_number+0x0
0433eb30 022ddeeb 0823b070 0433eb74 00df876d 00000001 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
0433eb3c 00df876d 00000001 0094559d 74179bac 0a07d4b0 wcgrid_mip1_rosetta_7!cppdb::version_number+0x0
0433eb74 00942e8c 0a07d4b0 74179b7c ffffffff 0433ee48 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
0433eba4 00906be2 0a07d4b0 74179b34 04e44168 00000064 wcgrid_mip1_rosetta_7!cppdb::atomic_counter::get+0x0
0433ebec 01bc1e7d 04e2dbd0 0a471710 00001388 0433ee48 wcgrid_mip1_rosetta_7!cppdb::atomic_counter::get+0x0
0433ec0c 01bcd099 0433ee48 0823ab6c 00000000 3ff00000 wcgrid_mip1_rosetta_7!cppdb::version_number+0x0
0433ec38 01116e8c 0433ee48 74179c1c 0433ee48 0433ed24 wcgrid_mip1_rosetta_7!cppdb::version_number+0x0
0433ecc4 0110731c 0433ee48 74179d94 0aba2ac8 081c7708 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
0433ed4c 01116767 0433ee48 74179d4c 081c7708 02acfa40 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
0433ed94 0109faf9 0433ee48 741784e0 0433f69c 09a77ac0 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
0433f438 010a2c8a 0433f458 081c7708 09a77ac0 7417858c wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
0433f554 0085efa4 7417888c 00000000 00000000 00000000 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
0433f854 00862121 0000000e 04c4e168 04c7ff20 74178844 wcgrid_mip1_rosetta_7!cppdb::atomic_counter::get+0x0
0433f89c 7574344d 7efde000 0433f8e8 770d9802 7efde000 wcgrid_mip1_rosetta_7!cppdb::atomic_counter::get+0x0
0433f8a8 770d9802 7efde000 7510324f 00000000 00000000 kernel32!BaseThreadInitThunk+0x0
0433f8e8 770d97d5 0086219e 7efde000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0
0433f900 00000000 0086219e 7efde000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0

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

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

- Registers -
eax=00000000 ebx=0000000a ecx=00000000 edx=00000000 esi=069cf938 edi=00000000
eip=770bfdc1 esp=069cf8f4 ebp=069cf95c
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246

- Callstack -
ChildEBP RetAddr Args to Child
069cf95c 75f34667 00000064 00000000 069cfb98 01438ccb ntdll!NtDelayExecution+0x0
069cf96c 01438ccb 00000064 00000000 00000000 00000000 KERNELBASE!Sleep+0x0
069cfb98 7574344d 00000000 069cfbe4 770d9802 00000000 wcgrid_mip1_rosetta_7!cppdb::backend::statements_cache::active+0x0
069cfba4 770d9802 00000000 77bf3143 00000000 00000000 kernel32!BaseThreadInitThunk+0x0
069cfbe4 770d97d5 01438ca0 00000000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0
069cfbfc 00000000 01438ca0 00000000 00000000 00000000 ntdll!RtlInitializeExceptionChain+0x0


*** Debug Message Dump ****


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

Exiting...

</stderr_txt>
]]>

----------------------------------------

----------------------------------------
[Edit 1 times, last edit by NixChix at Dec 20, 2019 4:11:53 PM]
[Dec 20, 2019 3:49:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
hchc
Veteran Cruncher
USA
Joined: Aug 15, 2006
Post Count: 865
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

BOINC/WCG 7.2.47 came out in 2014. Wondering if you'll still get the same error messages on 7.14.2 (2018). And 7.16.x should come out as soon as the team finally gets their stuff together -- been teasing us since summer 2019.

To the specific error, sorry, no idea. I always tend to upgrade to the latest stable app release before spending too much time trying to figure out why something keeps breaking.
----------------------------------------
  • i5-7500 (Kaby Lake, 4C/4T) @ 3.4 GHz
  • i5-4590 (Haswell, 4C/4T) @ 3.3 GHz
  • i5-3570 (Broadwell, 4C/4T) @ 3.4 GHz

[Dec 20, 2019 7:27:37 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

"I have recently stopped running my computer 24x7 and have experienced that the WUs have errored-out upon restart, though not always all of them."

Look for one of my recent posts in a Windows topic describing the laborious workaround. It's very prominent since the W10 1903 build and worse since 1910 build.
[Dec 20, 2019 8:09:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
ca05065
Senior Cruncher
Joined: Dec 4, 2007
Post Count: 328
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

I have BOINC 7.14.2 on an up to date Windows 10 and have experienced similar problems since MIP began. I had not associated the calculation error as occurring on closing BOINC.
However even with all work units suspended before closing BOINC, several would end with 'computation error' as BOINC started and before I had resumed any work units. I could avoid closing BOINC for several days by using hibernate instead of shut down but eventually some software insisted on an operating system restart.
[Dec 20, 2019 8:47:24 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

Suspending, with LAIM on I dare guess.
[Dec 20, 2019 11:13:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
ca05065
Senior Cruncher
Joined: Dec 4, 2007
Post Count: 328
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

Yes. LAIM was on when I suspended the work units. Do you think it would avoid the computation error if LAIM was off? I will try it the next time I am forced to restart.
[Dec 21, 2019 12:29:22 AM]   Link   Report threatening or abusive post: please login first  Go to top 
NixChix
Veteran Cruncher
United States
Joined: Apr 29, 2007
Post Count: 1187
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

I'll try installing 7.14.2, but I doubt I will be able to do so for the coming week.

When I started my computer this evening, all 12 jobs had failed. I am not going to get many jobs processed this way.

Cheers coffee
----------------------------------------

[Dec 21, 2019 4:53:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Mike.Gibson
Ace Cruncher
England
Joined: Aug 23, 2007
Post Count: 12594
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

I would also try Hibernate rather than shutdown, especially if less than 24 hours down. I started doing that because of the infrequent checkpoints on arp1.

Mike
[Dec 24, 2019 1:21:59 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

I'll try installing 7.14.2, but I doubt I will be able to do so for the coming week.

When I started my computer this evening, all 12 jobs had failed. I am not going to get many jobs processed this way.

Cheers coffee

If I recollect correctly, there's a way to slow down the Windows shutdown to give BOINC time to close all files off properly without any dirty bits.

My recipe has been to first suspend all tasks, then exit BOINC and only then boot/shutdown Windows. I'm running a BOINC repair on startup before resuming the tasks. Cant control that though if Windows boots on some secret schedule or on power outage. For that I've set BOINC though to not start computing until 10 minutes after loading, also services allows to load BOINC with delay. When there it gives time to suspend the tasks and run the routine.
[Dec 24, 2019 12:24:09 PM]   Link   Report threatening or abusive post: please login first  Go to top 
ca05065
Senior Cruncher
Joined: Dec 4, 2007
Post Count: 328
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: MIP1 Tasks Fail During Shutdown

I had to re-boot my PC as my internet connection was misbehaving so I had the opportunity to test a restart with LAIM off and work units suspended.

I set LAIM off
I suspended one work unit but another started because I had not first suspended the 'ready to start' work units
I suspended the 'ready to start' work units
I suspended the running work units individually
I restarted the PC, logged in and waited a few minutes
I resumed each MIP work unit, but waited until the CPU time (as shown in BOINCTasks) began incrementing before starting the next
All restarted without error except for one which was just starting before the restart
I then set LAIM on
[Dec 24, 2019 11:09:41 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 28   Pages: 3   [ 1 2 3 | Next Page ]
[ Jump to Last Post ]
Post new Thread