Forum > Windows
2.4 Unrecoverable Errors ??
Gecko_R7:
I'll back Crunch3r's comments on 5.10.13 as it would not work w/ x32 -doze 2.4 SSSE3 on my T7200.
WUs would randomly slow by 75% and take 2-2.5 times as long to complete as they should. I was getting longer times than a P-M 1.7 running stock 5.27. NO WAY that is correct. in other cases, threads would start and freeze leaving only 1 thread running.
FWIW, this "stable" BOINC version also froze-up running 2.3 development aps and 2.2B.
I've tried resets, uninstalls/reinstalls, defrag/restart etc.
Once I went back to 5.4.11, everything ran perfect.
I also had issues w/ 5.10.13 on T7200 iMactel and "reverted" to 5.4.9. Problems went away.
IMO, 5.10.13 has problems and isn't a stable release. Actually, I've run Betas w/ less issues in the past than this "stable" one.
Not ranting on BOINC, but this one version is just particularly bad. :o
Gus:
Hi Simon,
I've been seeing the same errors as Richard. I'm running 2.4_Windows_x32_SSSE3 on Vista Home Premium. This is a Core 2 Duo (E6600). For me the WU's always blow up as soon as they start, either on a new WU or on one that was running normally and is being restarted by closing BOINC and restarting it.
After reading your suggestions in this thread I confirmed that .NET Framework 3.0 is installed on the system and I backloaded the CC to 5.8.16. It was running 5.10.13. But I am getting the same errors.
Here is the WU, and I'm attaching the original result file which I managed to save.
Regards,
Gus
More Info -
- This is not the same machine that I reported at the beginning of this thread. That was a Q6600 with Vista Home Basic.
- I just realized that WinZip truncated the attached file name which ends with 4.5.11
- The machine has all available Windoz Updates installed.
- I'm going to bed now before I pass out.
[attachment deleted by admin]
Richard Haselgrove:
Let one more run as a test.
http://setiathome.berkeley.edu/result.php?resultid=597127577 errored out under 3 seconds.
Suspending all SETI activity for the moment - I now have some spare WUs I can use for testing debug builds if you want.
Richard Haselgrove:
Maybe I should have been deleting them - didn't know there was a limit. Try again.
I'll try SSE3 quickly, then must break for food.
Gus:
--- Quote from: Haselgrove on 25 Aug 2007, 04:25:54 pm ---Maybe I should have been deleting them - didn't know there was a limit. Try again.
I'll try SSE3 quickly, then must break for food.
--- End quote ---
@Richard - Any luck running SSE3?
@Crunch3r - You've probably considered this already, and if it is a silly suggestion please forgive a novice.
If I understand it correctly, when the app starts it tries several techniques on the data to determine the best routines to use to crunch it. Since (for me at least) these always fail within seconds of starting, might the problem be within that routine? In other words, might the app sometimes try an illegal operation as part of these tests? Just a thought.
BTW, I offered earlier and I'll do so again. I'm available for help in testing this if you would like. gobermeyer at comcast dot net.
-Regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version