Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 62
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi J.C.S.
You're in the wrong project forum. I've altered the thread title post, so it's clear this one is about HPF2. Please repost in the HCMD2 forum (presuming your other science results are ok, i.e. it's science specific) --//-- |
||
|
J.C.S.
Cruncher Joined: Apr 10, 2008 Post Count: 21 Status: Offline |
ooh!! sorry i´ m error
----------------------------------------Regards ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm having a lot of wu ending up with that error.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I just had an error occur at the exact same time as another job finished.
Just wondering if it was just a fluke or is it something I should worry about ? oz029_ 00037_ 5-- 640 Pending Validation 12/17/11 00:23:27 12/17/11 09:11:17 8.54 163.1 / 0.0 oz037_ 00109_ 8-- 640 Error__________ 12/17/11 06:56:51 12/17/11 09:11:17 2.21 42.3 / 0.0 Result Log Result Name: oz037_ 00109_ 8-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> SIGSEGV: segmentation violation Stack trace (19 frames): [0x8789e9f] [0x877cfa4] [0xf7fb1400] [0x87dfb6f] [0x87badaa] [0x876d273] [0x822fc2f] [0x842d5c3] [0x874ba87] [0x8109c82] [0x810a40e] [0x85e9eb8] [0x85eb7c5] [0x805cf24] [0x8331f6b] [0x83f3cdd] [0x83f3f5c] [0x87ed062] [0x8048131] Exiting... </stderr_txt> ]]> |
||
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
!
----------------------------------------[Edit 1 times, last edit by skgiven at Jul 18, 2012 9:28:43 PM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yup, these \711 on HPF2 replaced the \401, but occur factor 10 less. Near immediate crash out at start and only on Windows. Why they happen to one and not the other remains a mystery.
--//-- |
||
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I havn't seen that error in awhile, by any chance are you running FA@H on the same system.. if so that still is a known issue that tends to cause this error. now as far as this error on AMD based chips all the time that I don't know.. running 20 threads off a quad and hex core systems here. hex one was a retrofit of a old dual core and so far no problems have popped up with this project.. my other system quad is doing FA@H. hope this helps you.. Yes, I just got the error on a Q8300 Quad running Win7 64-bit and BOINC 6.12.34 (64-bit also, which sometimes makes a difference). And I am running Folding@home also on that machine, but no betas.<core_client_version>6.12.34</core_client_version> I think that it is the first time that I have ever gotten it, and lost no time, so it is no big deal, but it is still around. |
||
|
Shaun August
Cruncher Joined: Jun 23, 2006 Post Count: 3 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Just had a couple of these happen to me on a machine that has been rock steady up to now. i7 machine running windows 7, 6.12.34(x64). I am also running FAAH.
|
||
|
Bernd Milmert
Cruncher Germany Joined: Aug 29, 2010 Post Count: 22 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Win 7, x64, (autoupdate), E8400,
----------------------------------------BOINC 7.0.25, running all projects + BETA -GPU Project Name: Human Proteome Folding - Phase 2 Created: 05/05/2012 03:40:54 Name: qe001_00262 My Result Status : Valid WU Status : 4 with Status ERROR Project Name: Human Proteome Folding - Phase 2 Created: 05/11/2012 19:52:15 Name: qe140_00097 My Result Status : Valid WU Status : 2 with Status ERROR Project Name: Human Proteome Folding - Phase 2 Created: 05/11/2012 19:52:31 Name: qe142_00059 My Result Status : Valid WU Status : 4 with Status ERROR Project Name: Human Proteome Folding - Phase 2 Created: 05/12/2012 17:04:58 Name: qe155_00046 My Result Status : Valid WU Status : all Valid , 1 In Progress Project Name: Human Proteome Folding - Phase 2 Created: 05/15/2012 20:06:47 Name: qe229_00011 Pending validaton Project Name: Human Proteome Folding - Phase 2 Created: 05/17/2012 14:35:39 Name: qe269_00253 My Result Status : ERROR (line 711) WU Status : 6 with ERROR Project Name: Human Proteome Folding - Phase 2 Created: 05/17/2012 14:35:25 Name: qe269_00048 My Result Status : ERROR (line 711) WU Status : 9 with ERROR Project Name: Human Proteome Folding - Phase 2 Created: 05/18/2012 20:18:29 Name: qe298_00022 My Result Status : In Progress Between the 2 ERROR 'wu's and the 'In Progress' 'wu' I checked the windows event log, shows 1 error. Online Help: http://social.technet.microsoft.com/wiki/cont...rosoft-windows-capi2.aspx I followed the instuctions under 'user action' Step 2 Result: Success I'm not sure if this help me with the 'wu's, but one windows error less ![]() [Edit 1 times, last edit by Bernd Milmert at May 21, 2012 4:42:39 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thnks for that. The 711 error is rare and random on HPF2 and not previously been associated to your observation. Can you please copy the actual event log entry where that CAPI2 certificate entry appeared and past in a reply. That would help to document for the techs to understand the relationship. Also the BOINC startup log, first 30 lines, so we have the device details as seen by BOINC.
thanks --//-- |
||
|
|
![]() |