Bad SMP 2652s?
Qeldroma
Arid ZoneAh Member
Hi all- hope you're all having a great holiday
I checked my logs this evening and noted this from just this morning-
It completes a 2653 OK, then EUEs on a 2652 at the SAME place 3 times, then I think it "throws in the towel" and downloads the core again and and starts up a 2653 which is running fine.
Normally this is a system stability error from overclocking, but an EUE three times in the same spot of execution is normally a software bug (or possibly a bad CPU instruction?). So I'm wondering if any of you choked on this WU lately [specifically around 2652 (Run 0, Clone 236, Gen 23)].
I'm about to troubleshoot this under-achieving system again, so this could be a clue.
Thanks.
I checked my logs this evening and noted this from just this morning-
It completes a 2653 OK, then EUEs on a 2652 at the SAME place 3 times, then I think it "throws in the towel" and downloads the core again and and starts up a 2653 which is running fine.
Normally this is a system stability error from overclocking, but an EUE three times in the same spot of execution is normally a software bug (or possibly a bad CPU instruction?). So I'm wondering if any of you choked on this WU lately [specifically around 2652 (Run 0, Clone 236, Gen 23)].
I'm about to troubleshoot this under-achieving system again, so this could be a clue.
Thanks.
0
Comments
But to be fair, there are many overclockers out there who refuse to believe that their computer clocks are unstable when they are only 98% stable. WinSMP will quickly reveal an instability.
I go through fits and starts with Folding Forum. It's a great place for information, but I can't take it in large dosages.
just EUE'd on frame 3 D:
I didn't get flamed for bringing it up and I think this problem is not only us & has got their attention. I know from programming that recognizing a pattern of behavior can be critical.
Thanks-
EDIT ADDED: Oh, and BTW- Happy New Year!