| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: New (I think) BOINC error found today |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Again, apologies for the long post but it's a copy and paste. Very strange... looks like the client flopped over, died and did a dump of some sort. This client has been running for days with little or no issue (two "error" conditions before this, but plenty of "valid", too)
Any thoughts? This is the first time I've seen ANYTHING like this... <core_client_version>5.4.9</core_client_version> <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> [18:33:36] [INFO] Checkpoint complete [18:42:20] [INFO] Checkpoint complete [18:49:35] [INFO] Checkpoint complete [18:58:38] [INFO] Checkpoint complete [19:07:55] [INFO] Checkpoint complete [19:16:52] [INFO] Checkpoint complete [19:26:10] [INFO] Checkpoint complete [19:34:01] [INFO] Checkpoint complete [19:42:48] [INFO] Checkpoint complete [19:52:27] [INFO] Checkpoint complete [20:00:35] [INFO] Checkpoint complete [20:07:35] [INFO] Checkpoint complete [20:14:38] [INFO] Checkpoint complete [20:24:45] [INFO] Checkpoint complete [20:35:55] [INFO] Checkpoint complete [20:44:21] [INFO] Checkpoint complete [20:52:49] [INFO] Checkpoint complete [21:00:21] [INFO] Checkpoint complete [21:08:15] [INFO] Checkpoint complete [21:14:55] [INFO] Checkpoint complete [21:22:22] [INFO] Checkpoint complete [21:30:38] [INFO] Checkpoint complete [21:39:53] [INFO] Checkpoint complete [21:48:49] [INFO] Checkpoint complete [21:56:35] [INFO] Checkpoint complete [22:07:09] [INFO] Checkpoint complete [22:19:02] [INFO] Checkpoint complete [22:26:11] [INFO] Checkpoint complete [22:33:54] [INFO] Checkpoint complete [22:45:33] [INFO] Checkpoint complete [22:54:33] [INFO] Checkpoint complete [23:00:47] [INFO] Checkpoint complete [23:09:38] [INFO] Checkpoint complete [23:19:00] [INFO] Checkpoint complete [23:26:27] [INFO] Checkpoint complete [23:35:23] [INFO] Checkpoint complete [23:44:55] [INFO] Checkpoint complete [23:52:31] [INFO] Checkpoint complete ERROR Exception occurred while running Rosetta: Exception code: 0xc0000005 Exception address: 0x00488EB6 Operating System: Windows XP Service Pack 1 Build #: 2600 BOINC Windows Runtime Debugger Version 5.4.9 Dump Timestamp : 07/11/06 23:56:18 Debugger Engine : 4.0.5.0 Symbol Search Path: C:\Program Files\BOINC\slots\0;C:\Program Files\BOINC\projects\www.worldcommunitygrid.org;srv*C:\DOCUME~1\admin\LOCALS~1\Temp\symbols*http://msdl.microsoft.com/download/symbols;sr...inc.berkeley.edu/symstore ModLoad: 00400000 00b63000 C:\Program Files\BOINC\projects\www.worldcommunitygrid.org\wcg_hpf2_rosetta_5.07_windows_intelx86 (5.0.6.0) (-nosymbols- Symbols Loaded) File Version : 5, 0, 6, 0 Company Name : New York University Center For Comparative Functional Genomics in collaboration with the University of Washington and IBM Corporation Product Name : Rosetta ab-initio World Community Grid client Product Version: ModLoad: 77f50000 000a7000 C:\WINDOWS\System32\ntdll.dll (5.1.2600.1217) (PDB Symbols Loaded) File Version : 5.1.2600.1217 (xpsp2.030429-2131) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.1217 ModLoad: 77e60000 000e6000 C:\WINDOWS\system32\kernel32.dll (5.1.2600.1560) (PDB Symbols Loaded) File Version : 5.1.2600.1560 (xpsp2_gdr.040517-1325) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.1560 ModLoad: 76b40000 0002c000 C:\WINDOWS\System32\WINMM.dll (5.1.2600.1106) (PDB Symbols Loaded) File Version : 5.1.2600.1106 (xpsp1.020828-1920) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.1106 ModLoad: 77d40000 0008d000 C:\WINDOWS\system32\USER32.dll (5.1.2600.1634) (PDB Symbols Loaded) File Version : 5.1.2600.1634 (xpsp2.050301-1526) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.1634 ModLoad: 7f000000 00042000 C:\WINDOWS\system32\GDI32.dll (5.1.2600.1789) (PDB Symbols Loaded) File Version : 5.1.2600.1789 (xpsp2.051228-1438) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.1789 ModLoad: 77dd0000 0008d000 C:\WINDOWS\system32\ADVAPI32.dll (5.1.2600.1106) (PDB Symbols Loaded) File Version : 5.1.2600.1106 (xpsp1.020828-1920) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.1106 ModLoad: 78000000 00087000 C:\WINDOWS\system32\RPCRT4.dll (5.1.2600.1361) (PDB Symbols Loaded) File Version : 5.1.2600.1361 (xpsp2.040109-1800) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.1361 ModLoad: 04ed0000 00118000 C:\Program Files\BOINC\dbghelp.dll (6.5.3.7) (PDB Symbols Loaded) File Version : 6.5.0003.7 (vbl_core_fbrel(jshay).050527-1915) Company Name : Microsoft Corporation Product Name : Debugging Tools for Windows(R) Product Version: 6.5.0003.7 ModLoad: 77c10000 00053000 C:\WINDOWS\system32\msvcrt.dll (7.0.2600.1106) (PDB Symbols Loaded) File Version : 7.0.2600.1106 (xpsp1.020828-1920) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 7.0.2600.1106 ModLoad: 05100000 00046000 C:\Program Files\BOINC\symsrv.dll (6.5.3.8) (PDB Symbols Loaded) File Version : 6.5.0003.8 (vbl_core_fbrel(jshay).050527-1915) Company Name : Microsoft Corporation Product Name : Debugging Tools for Windows(R) Product Version: 6.5.0003.8 ModLoad: 05150000 00031000 C:\Program Files\BOINC\srcsrv.dll (6.5.3.7) (PDB Symbols Loaded) File Version : 6.5.0003.7 (vbl_core_fbrel(jshay).050527-1915) Company Name : Microsoft Corporation Product Name : Debugging Tools for Windows(R) Product Version: 6.5.0003.7 ModLoad: 77c00000 00007000 C:\WINDOWS\system32\version.dll (5.1.2600.0) (PDB Symbols Loaded) File Version : 5.1.2600.0 (xpclient.010817-1148) Company Name : Microsoft Corporation Product Name : Microsoft® Windows® Operating System Product Version: 5.1.2600.0 *** UNHANDLED EXCEPTION **** Reason: Access Violation (0xc0000005) at address 0x77F83905 write attempt to address 0x0000002D *** Dump of the Worker(offending) thread: *** eax=0000002c ebx=003f0000 ecx=0000002d edx=0aba4960 esi=0aba4a80 edi=0aba4960 eip=77f83905 esp=0022f9bc ebp=0022f9c8 cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010297 ChildEBP RetAddr Args to Child 0022f9c8 77f58cca 003f0000 0aba4a80 0022fa68 00000000 ntdll!_RtlpCoalesceFreeBlocks@16+0x0 0022fa9c 00c25c30 003f0000 00000000 0aba4a88 07e31f1c ntdll!_RtlFreeHeap@12+0x0 0022fad8 0066c7fa 0aba4a88 07885878 00000000 0022fb24 wcg_hpf2_rosetta_5!+0x0 07e31f10 00000000 0aba4a88 00000080 000f000f 000c0105 wcg_hpf2_rosetta_5!+0x0 *** Dump of the Timer thread: *** eax=ab2e554e ebx=00000000 ecx=0000002d edx=00000000 esi=00000001 edi=00c33300 eip=7ffe0304 esp=066aff08 ebp=066aff40 cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202 ChildEBP RetAddr Args to Child SymFromAddr(): GetLastError = '126' Address = '7ffe0304' SymGetModuleInfo(): GetLastError = '126' Address = '7ffe0304' 066aff04 77f5c524 76b49dbe 00000002 066aff6c 00000001 !+0x0 066aff08 76b49dbe 00000002 066aff6c 00000001 00000001 ntdll!_NtWaitForMultipleObjects@20+0x0 FPO: [5,0,0] 066affb4 77e7d28e 00000000 00c33300 00000000 00000000 WINMM!_timeThread@4+0x0 FPO: [1,35,1] 066affec 00000000 76b49d87 00000000 00000000 00000008 kernel32!_BaseThreadStart@8+0x0 Exiting... </stderr_txt> |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hmm.... either I've stumped everyone around here, or everyone's whispering behind my back "I wish this guy would just go away!"
 Just an update... this one instance of this LONG error is the only one I've received so far, but yesterday alone every one of my BOINC machines threw at least one error, saying "invalid environment" or some such thing. I'm still getting valids, pendings, inconclusives, etc so I'm not JUST throwing errors. Perhaps this is normal? Do errors just naturally occur? If so, could this be why people are talking behind my back? Just kidding...-John Scottsdale, AZ |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
] Yes, you got 30 readers stumped (so far) or ......why not do a thorough hardware test and a Windows Repair run. Also there is another thread, hence the possible silence, which has a similar error in there to your "Reason: Access Violation (0xc0000005) at address 0x77F83905 write attempt to address 0x0000002D"
----------------------------------------PS: Plz check your post formatting...missing [/...] somewhere
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jul 14, 2006 2:04:29 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
] Yes, you got 30 readers stumped (so far) or ......why not do a thorough hardware test and a Windows Repair run. Also there is another thread, hence the possible silence, which has a similar error in there to your "Reason: Access Violation (0xc0000005) at address 0x77F83905 write attempt to address 0x0000002D" PS: Plz check your post formatting...missing [/...] somewhere Wow... thanks for the "friendly" post, Sekerob. Sorry to have interrupted your slumber. Please return to your regularly scheduled sarcastic response and forget this thread exists. -jk Phoenix, AZ USA |
||
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges: 
|
Sorry to have interrupted your slumber. Please return to your regularly scheduled sarcastic response and forget this thread exists. Yet, here it is.Access violation, hmm. What else is going on on the same machine? Perhaps one of the techs will see this thread and comment. The HPF2 project does some strange things now and then. If it becomes too large of a problem on that particular computer, try just running FAAH for awhile. As a result, my own BOINC is well behaved and is not doing anything like this.
SUPPORT ADVISOR
----------------------------------------Work+GPU i7 8700 12threads School i7 4770 8threads Default+GPU Ryzen 7 3700X 16threads Ryzen 7 3800X 16 threads Ryzen 9 3900X 24threads Home i7 3540M 4threads50% [Edit 2 times, last edit by retsof at Jul 15, 2006 11:28:09 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As Sekerob so tactfully reminded us, this is an error we have seen before (quite frequently). At the moment, it looks like it is caused by a bug in the Rosetta code (not one introduced during porting this version for Rosetta for WCG). As such, it is taking a little time to track down and WCG will provide the fix as son as it is available.
|
||
|
|
|