Random shut downs, kernel reports CPU2 caller

Thank you Dan for sharing your awesome knowledge, I very much appreciate you being so willing to share. Heaven is all have known so far for stressing GPUs and RAM, and it works for me to divide the good GPUs and RAM macs from those which fail under stress. Do you have a better tool up your sleeve for me to use for that purpose? Also, just guessing here with my still marginal understanding : The CPU failing means : replace or repair logic board,or the chip, right? I was just about to disable SIP and try again with my Heaven, because I also have a 2013 15"which tends to shut down: I have been told by various sources that by disabling SIP in that model I can get it to stop doing this: Apparently there is a glitch in the Thunderbolt circuit in that model which causes the shut downs, and disabling SIP can act as a work around. Is this true, according to your experience? And if so, is there a better solution?

I haven't found any tool which stresses a GPU helpful. These tools are useful for a hardware designer to push the limits of the given system design to see if one design is better than another.

For us as repair techs they only weaken the logic if we go too far. And that's the nut! What is too far! Each generation of GPU's have improved so what I would run on a newer 2019 top of the line system will be very different than what I could run on an older 2011 system.

Think of it this way... You likely remember the 1960's Indy500 races. You remember the engine, transmission, brake failures these racers would have. Now you rarely see a racer loose an engine or trans or even brake failure! Thats because over the years they improved the racers! Many of that tech also went into your car you are driving around today!

So what we can achieve today is a lot different than what the older system (car) could do. So stressing a system really doesn't tell us much.

I focus on simple diagnostics and a 30min video rendering if I need to push a system to find something.