Quote:
Originally Posted by Iketh 
"Internal parity error" means the processor checked its own work and got different results. So the processor has to rerun the calculation from scratch to find out which result (if either) was correct. Once it's done rerunning the calculation, it reports the situation to the OS for logging. It goes without saying that these errors are a sign of instability and lower performance.
What I find most intriguing is that I can't get these errors to show up at all on my 2600k no matter how unstable I make it... with all the playing with overclocks and the 1000 or so BSODs over the past several months, I don't have a single whea 19 warning...

"Internal parity error" means the processor checked its own work and got different results. So the processor has to rerun the calculation from scratch to find out which result (if either) was correct. Once it's done rerunning the calculation, it reports the situation to the OS for logging. It goes without saying that these errors are a sign of instability and lower performance.
What I find most intriguing is that I can't get these errors to show up at all on my 2600k no matter how unstable I make it... with all the playing with overclocks and the 1000 or so BSODs over the past several months, I don't have a single whea 19 warning...
Ya I am in the same boat as you. I never seen these errors on previous chips... Q9550, E7200, P4...
Interestingly when I looked back at the log file I saw a massive 170+ WHEA errors from when I was still getting my overclock figured out.
The settings I have now I have not seen one in the newest record date, and the log is slowly decreasing in reported as the time frame grows.
It must be a new instruction the CPU is giving the OS to be reported.

























