Quote:
Originally Posted by opt33Â 
The only WHEA errors I have correspond to runs where prime failed/stopped/error and stopped. I assume you guys when running prime 95 go to advanced tab and put check beside 1) sum (inputs) error checking as well as 2) round off checking.
Since version 26 of prime95..., quote "Some of the new, faster FFTs don't let us do as much error checking on each iteration. If you don't want to lose this error checking, choose "SUM(INPUTS) error checking" from the Options menu. This will slow down your tests by about 2-5%".
So my question is are you guys saying you have prime checking for both those error types, and you are still getting WHEA errors that prime program is missing....or do you not have both of those checked hence getting whea errors only?
I cant tell from looking at my logs, since all my stable runs, have no whea errors during those time frames, and I did not specifically look for WHEA errors if they exactly corresponded to prime errors.
The only WHEA errors I have correspond to runs where prime failed/stopped/error and stopped. I assume you guys when running prime 95 go to advanced tab and put check beside 1) sum (inputs) error checking as well as 2) round off checking.
Since version 26 of prime95..., quote "Some of the new, faster FFTs don't let us do as much error checking on each iteration. If you don't want to lose this error checking, choose "SUM(INPUTS) error checking" from the Options menu. This will slow down your tests by about 2-5%".
So my question is are you guys saying you have prime checking for both those error types, and you are still getting WHEA errors that prime program is missing....or do you not have both of those checked hence getting whea errors only?
I cant tell from looking at my logs, since all my stable runs, have no whea errors during those time frames, and I did not specifically look for WHEA errors if they exactly corresponded to prime errors.
yes I was still getting internal CRC WHEA errors even with those options enabled ...
it makes sense as to why Prime95 would not see these as errors as these internal errors should be transparent - the CPU is recovering itself and giving a proper answer - it just is taking slightly longer to respond as it's having to re-calculate ..
What happened to the first chip?
