| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: I'm getting too many invalid results |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
I'm using windows xp 32 bit on my intel c2 duo e6750 2.66ghz cpu and nearly 20% of my results are invalid. Is there a problem with my cpu? or is there a problem with boinc? does anybody have the same problem? thanx |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
No, i fear you are the only one reporting this presently. 20% can point to a stability issue of your computer due e.g. overclocking and or temperature. Get speedfan or coretemp program to check on that and schedule a thorough clean out if your system has been crunching for longer. Memtest86 and a few other test utilities are listed in an FAQ of the WCG Start Here forum.
----------------------------------------Also please visit the Result Status page and find an invalid result. Click on the status column link and copy the content to this board so we can read. Further go through the message log of BOINC and see if there are any suspicious messages. ttyl
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This was one of the first programs i have installed when i bought a new machine for my home a week ago. I did not overclock the cpu or any other components and cpu temperature is fine. I didn't see any suspicious message in system log which i haven't seen before on my work computer.
here's the (invalid) result log of a work unit named: faah3041_ ZINC04293355_ xMut_ md19300_ 05_ 1-- thanx Result Log <core_client_version>5.10.30</core_client_version> <![CDATA[ <stderr_txt> World Community Grid AutoDock (projects/www.worldcommunitygrid.org/wcg_faah_autodock_5.42_windows_intelx86) version Failed to get VersionInfo size: 1812 Failed to get VersionInfo size: 1812 INFO: No state to restore. Start from the beginning. ERROR: Restoring checkpoint failed. Unable to restore state! INFO:[07:25:41] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[07:26:31] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 Setting maxGen to 6750 About to enter main loop...(dockings already completed: 0) call_glss(): pop_size: 200 num_evals: 10000000 start: [07:26:35] call_glss(): begin 2nd for loop over pop: [07:26:35] call_glss(): end 2nd for loop over pop: [07:26:35] call_glss(): end 1st do/while: [07:26:35] _maxGenSeenSoFar changed: 6750 call_glss(): end: [07:41:33] Updating Best Energy for WU: 0.00 call_glss(): pop_size: 200 num_evals: 10000000 start: [07:41:33] call_glss(): begin 2nd for loop over pop: [07:41:33] call_glss(): end 2nd for loop over pop: [07:41:33] call_glss(): end 1st do/while: [07:41:33] call_glss(): end: [07:56:28] call_glss(): pop_size: 200 num_evals: 10000000 start: [07:56:28] call_glss(): begin 2nd for loop over pop: [07:56:28] call_glss(): end 2nd for loop over pop: [07:56:28] call_glss(): end 1st do/while: [07:56:28] call_glss(): end: [08:11:48] Updating Best Energy for WU: -12.59 call_glss(): pop_size: 200 num_evals: 10000000 start: [08:11:50] call_glss(): begin 2nd for loop over pop: [08:11:50] call_glss(): end 2nd for loop over pop: [08:11:50] call_glss(): end 1st do/while: [08:11:50] call_glss(): end: [08:27:04] Updating Best Energy for WU: -13.30 call_glss(): pop_size: 200 num_evals: 10000000 start: [08:27:05] call_glss(): begin 2nd for loop over pop: [08:27:05] call_glss(): end 2nd for loop over pop: [08:27:05] call_glss(): end 1st do/while: [08:27:05] call_glss(): end: [08:42:04] call_glss(): pop_size: 200 num_evals: 10000000 start: [08:42:05] call_glss(): begin 2nd for loop over pop: [08:42:05] call_glss(): end 2nd for loop over pop: [08:42:05] call_glss(): end 1st do/while: [08:42:05] call_glss(): end: [08:56:54] call_glss(): pop_size: 200 num_evals: 10000000 start: [08:56:56] call_glss(): begin 2nd for loop over pop: [08:56:56] call_glss(): end 2nd for loop over pop: [08:56:56] call_glss(): end 1st do/while: [08:56:56] call_glss(): end: [09:11:56] Updating Best Energy for WU: -14.31 call_glss(): pop_size: 200 num_evals: 10000000 start: [09:11:59] call_glss(): begin 2nd for loop over pop: [09:11:59] call_glss(): end 2nd for loop over pop: [09:11:59] call_glss(): end 1st do/while: [09:11:59] call_glss(): end: [09:26:54] call_glss(): pop_size: 200 num_evals: 10000000 start: [09:26:56] call_glss(): begin 2nd for loop over pop: [09:26:56] call_glss(): end 2nd for loop over pop: [09:26:56] call_glss(): end 1st do/while: [09:26:56] call_glss(): end: [09:41:50] call_glss(): pop_size: 200 num_evals: 10000000 start: [09:41:52] call_glss(): begin 2nd for loop over pop: [09:41:52] call_glss(): end 2nd for loop over pop: [09:41:52] call_glss(): end 1st do/while: [09:41:52] call_glss(): end: [09:56:51] call_glss(): pop_size: 200 num_evals: 10000000 start: [09:56:52] call_glss(): begin 2nd for loop over pop: [09:56:52] call_glss(): end 2nd for loop over pop: [09:56:52] call_glss(): end 1st do/while: [09:56:52] call_glss(): end: [10:12:19] call_glss(): pop_size: 200 num_evals: 10000000 start: [10:12:19] call_glss(): begin 2nd for loop over pop: [10:12:19] call_glss(): end 2nd for loop over pop: [10:12:19] call_glss(): end 1st do/while: [10:12:19] call_glss(): end: [10:27:24] call_glss(): pop_size: 200 num_evals: 10000000 start: [10:27:24] call_glss(): begin 2nd for loop over pop: [10:27:24] call_glss(): end 2nd for loop over pop: [10:27:24] call_glss(): end 1st do/while: [10:27:24] call_glss(): end: [10:42:30] call_glss(): pop_size: 200 num_evals: 10000000 start: [10:42:31] call_glss(): begin 2nd for loop over pop: [10:42:31] call_glss(): end 2nd for loop over pop: [10:42:31] call_glss(): end 1st do/while: [10:42:31] call_glss(): end: [10:57:31] call_glss(): pop_size: 200 num_evals: 10000000 start: [10:57:31] call_glss(): begin 2nd for loop over pop: [10:57:31] call_glss(): end 2nd for loop over pop: [10:57:31] call_glss(): end 1st do/while: [10:57:31] call_glss(): end: [11:12:40] call_glss(): pop_size: 200 num_evals: 10000000 start: [11:12:40] call_glss(): begin 2nd for loop over pop: [11:12:40] call_glss(): end 2nd for loop over pop: [11:12:40] call_glss(): end 1st do/while: [11:12:40] call_glss(): end: [11:27:48] ________________________________________________________________________________ autodock4: Successful Completion on "World Community Grid device" ________________________________________________________________________________ </stderr_txt> ]]> |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
See nothing out of the ordinary in the result log. Those errors are really just benign warnings.
----------------------------------------Sorry if confusing, but the message log I meant was the one of BOINC. You can see them in either the Simple or Advanced Grid View of the BOINCmgr GUI (message tab). The older ones you can find in the stdoutdae.txt file e.g. If you open that file and go back to where that invalid result ran, there may be something. Also the other txt files in the BOINC program dir could hold info. New system, still could have faulty ram for instance needing some burn in. Crunching IS THE hardware test. Memtest86 would reveal some intermittency if ran for longer. Any AV or Firewall logs you could review if they interfered? ttyl
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Feb 9, 2008 10:46:30 AM] |
||
|
|
|