Message boards :
Number crunching :
invalid results
Message board moderation
Author | Message |
---|---|
Send message Joined: 23 Jan 22 Posts: 5 Credit: 499,763 RAC: 0 |
Keep getting invalid results for wu's. Never seen this on other projects. CPU time 0.000000 <core_client_version>7.16.20</core_client_version> <![CDATA[ <stderr_txt> 23:15:09 (4572): wrapper (7.17.26016): starting 23:15:09 (4572): wrapper: running build\cmdock.exe (-c -j 1 -r target.prm -p "D:\ProgramData\slots\7\data\scripts\dock.prm" -f htvs.ptc -i ligands.sdf -o docking_out) 10:18:05 (9804): wrapper (7.17.26016): starting 10:18:05 (9804): wrapper: running build\cmdock.exe (-c -j 1 -r target.prm -p "D:\ProgramData\slots\7\data\scripts\dock.prm" -f htvs.ptc -i ligands.sdf -o docking_out) 18:35:38 (8360): wrapper (7.17.26016): starting 18:35:38 (8360): wrapper: running build\cmdock.exe (-c -j 1 -r target.prm -p "D:\ProgramData\slots\7\data\scripts\dock.prm" -f htvs.ptc -i ligands.sdf -o docking_out) 18:49:02 (9588): wrapper (7.17.26016): starting 18:49:02 (9588): wrapper: running build\cmdock.exe (-c -j 1 -r target.prm -p "D:\ProgramData\slots\7\data\scripts\dock.prm" -f htvs.ptc -i ligands.sdf -o docking_out) 18:49:04 (9588): build\cmdock.exe exited; CPU time 0.000000 18:49:04 (9588): called boinc_finish(0) |
Send message Joined: 11 Oct 20 Posts: 337 Credit: 25,677,139 RAC: 9,236 |
Hello! I have looked at few results and they look really weird and incorrect. Could you perform a project reset? Can work of application be blocked by antivirus or another tools? Than you for participation! |
Send message Joined: 23 Jan 22 Posts: 5 Credit: 499,763 RAC: 0 |
A project reset was done still the same problem. I don't think Kaspersky is responsible or blocking. nothing in the logs Nothing wrong with computer (Dell ), diagnostic test ok including extended memory test, win11 memory test. memtest86-usb Data drive ckecked Boinc Checkpoint set 120 sec. I don't keep boinc running at night or during important internet activity ( banking,shopping etc.) No running in background Boinc services Sidock@home seems to be running ,uploading ok, no error messages The problems seems to be when restarting boinc after a pause some wu's upload Some run run a few hours terminate 100% and uploads all normal but some seem to be a shorter computing time. Running: cosmology,denis ,einstein, LHC,milkyway @ home no such problems. Strong internet cable system connection. Looks more like checkpoint problem |
Send message Joined: 23 Jan 22 Posts: 5 Credit: 499,763 RAC: 0 |
Doubled checked boinc data drive chkdsk /r and solidigm (intel) utilities and found nothing Looks that the problem is on your side >> application or network |
Send message Joined: 11 Oct 20 Posts: 337 Credit: 25,677,139 RAC: 9,236 |
Yes, it's not a hardware problem. Can you remember in detail what was done? Thank you! |
Send message Joined: 23 Jan 22 Posts: 5 Credit: 499,763 RAC: 0 |
"Can you remember in detail what was done?" Sorry, not sure what you are asking |
Send message Joined: 11 Oct 20 Posts: 337 Credit: 25,677,139 RAC: 9,236 |
"Can you remember in detail what was done?" We want to repeat these steps in test environment. |
Send message Joined: 23 Jan 22 Posts: 5 Credit: 499,763 RAC: 0 |
If you want to test wu just redo the last ones I finished. Let then run 2-6 hours depending on the estimated completion time ( I have a Alienware R10 gaming computer so depending on the one you are using it may be different) From what I've seen the problem occurs if BOINC is exited, or project sidock is suspended and then ,after some time, BOINC is restarted or project is resumed the ( sidock) wu's will resume work, (nothing unusual seen) after some time, units will upload then others will do the same with no indication of problems except shorter time than estimated. I'm always on the lookout for bad units I always check the website to see if any bad units reported, that's how I found bad invalid results . For other projects I'm running it's only occasional ones ,often, not the only computer because of bad wu's The only thing else I could do is uninstall and re install BOINC. Windows 11, BIOS, etc are always update, computer tested so I don't see anything causing this. |
©2024 SiDock@home Team