Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Beta Testing Forum: Beta Test Support Forum Thread: New Beta starting Aug 23, 2011 |
No member browsing this thread |
Thread Status: Locked Total posts in this thread: 164
|
Author |
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: |
"The GPU was sent into and infinite loop and then caused a blue screen
I have a copy of the error message" What was the message? |
||
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: |
In such circumstances I would recommend Exiting Boinc before clicking "Programma afsluiten" and then restarting the system - often saves the task. I know, even a reset of the computer (without proper shutdown) could save the task, but because this is beta and it should functioning without user interception, I did't want to save the task (not important for me neither for the project), because that's not what you can ask from an average cruncher. |
||
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: |
Also with version 6.17 a WIN APPCRASH and computation error.
----------------------------------------The crashes appear when the application just finished a job and wants to start a new wcg_beta13_vina_6.17_windows_intelx86.exe for the next job. The vina's aren't crashing, it is the wcg_wrapper*.exe loosing control. Workunit Status Project Name: Beta Test Created: 08/27/2011 15:51:00 Name: BETA_BETA_00002025_0000003_0167 Minimum Quorum: 2 Replication: 3 Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit BETA_ BETA_ 00002025_ 0000003_ 0167_ 3-- - In Progress 29/08/11 07:17:48 30/08/11 21:41:48 0.00 0.0 / 0.0 BETA_ BETA_ 00002025_ 0000003_ 0167_ 2-- 617 Error 29/08/11 03:23:50 29/08/11 07:17:22 0.15 2.9 / 0.0 BETA_ BETA_ 00002025_ 0000003_ 0167_ 0-- 616 Inconclusive 27/08/11 18:03:15 28/08/11 04:14:12 3.66 100.7 / 0.0 BETA_ BETA_ 00002025_ 0000003_ 0167_ 1-- 616 Inconclusive 27/08/11 18:03:15 29/08/11 03:23:15 7.85 144.8 / 0.0 |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
@skgiven
----------------------------------------"The GPU was sent into an infinite loop and then caused a blue screen I have a copy of the error message" What was the message? ati2dvag infinite loop stop: 0x000000EA (0x892729430, 0x89682B08, 0xF78FACBC, 0x00000001) [Edit 2 times, last edit by Former Member at Aug 29, 2011 9:31:24 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My results for the 6.17 Beta are worst than previous rounds.
3 errors with exit code -1073741819 (0xc0000005); 2 on windows 7 64bit and 1 on Vista 32 bit which also caused a windows error window. 2 Valid 10 pending validation |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's hard to say where -107341819 comes from. The FAQ previously hinted at http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=16468 suggests a systemic issue. On the other hand, if all tasks in a quorum fail on this, it would suggest something finicky in the science app that kicks of some general weakness in an OS family, maybe a domino effect... a bug that sets of the next dependency. What I do when encountering this error, I'll boot.
Not much help, I know, but still. Over the past 3 days 14,672 Beta tasks validated. Don't know how many showed failure. The 6.17 for Mac and Linux from 6.16 had no changes and lacking significant reports of failure for this platform, even Kremmen happy on stability and speed, which is Thé seal of approval ;>), these 2 platforms have seemingly reached a stable state. Let's hope the techs iron out the last >5% bug occurrences out soonest. --//-- |
||
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: |
... Let's hope the techs iron out the last >5% bug occurrences out soonest. On Windows 64bits narrowed down to versions 6.16 and 6.17:--//-- Total 45 returned: 5 Errors, 8 Pendings and 32 Valids. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the link; I followed it up when you mentioned it earlier. It looks like the wingman will complete the units that showed an error ok.
As the error is not particularly precise and both computers have been extremely reliable, I have set both computers to test the memory, just on the slight chance there is a problem. What I do when encountering this error, I'll boot. I expect that is the best option. |
||
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: |
I noticed that the runtime memory size of the 6.17 "wrapper" program was 2.something MB, down about 1MB from the 6.16 version.
Maybe they deleted debugging code - but then 1MB seems like a lot of printf()s :) --- @Sekerob: "It's hard to say where -107341819 comes from". It's the weirdo decimal representation of hexadecimal c0000005. The latter is a lot easier to recognise for the programmers who wrote the software that produced it. (Sek probably knows this, but our non-technical readers may not). I have no idea of what it means, either. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
My results for 6.16 and 6.17:
----------------------------------------Windows 7 64-bit 24 WU's, 9 Pending, 15 Valid, No errors, no instability or performance issues. [Edit 1 times, last edit by Former Member at Aug 29, 2011 12:22:41 PM] |
||
|
|