Quote Originally Posted by AgentGOD View Post
Just in-case you guys are curious, here is my system's current status:

I wanted to lower the vcore two notches (from previously known IntelBurnTest stable configuration), and it resulted in a BSOD after the first iteration (MACHINE_CHECK_EXCEPTION).

Even after lowering the vcore two notches, it was still hot. I turned off ThermalThrottling (CPU TM) in the BIOS for the most accurate testing.

Guess this Xigmatek is getting dusty.

P.S.: I only look at the maximum CPU temperature, not averaging them. I'm using RealTemp v2.77, and it uses 100*C Tjunction value.
Hi AgentGOD,

thanks for replying. I am rather happy to see that there is something like Intelburntest. It dawned on me in the last 24h that the GFLOPs cannot only depend on the raw CPU power....

I am currently facing some issues here since I changed to an ASUS P5Q3 deluxe mainboard.

My current settings for CPU PLL Voltage, GPU Ref 0/2, 1/3, NB Voltage, and some others are so razor's edge that partially only one step up or down will make my system prime-unstable. Intelburntest however is a lot more tolerant and allows for a much wider range of settings without showing calculation errors.

What's the common opinion here? Can one dismiss Prime/Orthos/OCCT's errors? Priming has always been a neccessary evil to me and I would like to have it replaced by a better solution.

I saw Leghoof'd's opinion here, what is stable for you is stable enough. True. But I have seen effects at tiems on m operating systems that led me to believe that errors in the background that noone notices is slowly affecting th e reliability of one's OS overall, as in causing problems in the long shot that others would easily blame on Microsoft's incompetence. <g>