Update:
I ran a bunch of tests this weekend. Reinstalled original graphics card, pulled PCI cards, pulled my SSD and 4TB HD, and clean installed 10.13.6 onto the original HD that came with the machine. I tested all kinds of RAM configurations and this is what I have figured out:
Two sticks of my OWC 4GB 1333 RAM cause no crashing when running the Terminal "yes" stress test of all 24 cores (12 physical, 12 virtual, activity monitor reports 99–100% CPU usage) and GB5 benchmark test. I kept the same stick in slot 1 and alternated all 3 others through slot 5. No crashes. As soon as I add the remaining two OWC sticks into slots 2 and 6, GB5's benchmark test causes a crash, BUT there's still no crash during the Terminal stress test. Here's where it gets more interesting: I found two of the original 1GB RAM sticks and there's no crash during either GB5 or the Terminal test. I had been wondering if the 2 and 6 RAM slots were defective but this test would seem to indicate that's not the case. For the hell of it I threw my two remaining 4GB sticks into slots 3 and 7, for a total of 34 GB of RAM and GB5 still triggers a crash. Does it seem strange that individually when I test the 4GB RAM sticks #1 + #2., #1 + #3. #1 + #4, they all work, but when used together the system crashes? I can't figure out what that means.
I then reinstalled the CPUs, carefully scraping off as much of the gunked-up black residue as possible and applying as thin of a coat of thermal paste as I could. Still crashing the same as before. See photos below.
I'm very confused on why GB5's benchmark test crashes the system but the Terminal "yes" command does not. I tested GB4—same result. Prior to removing my SSD and 4TB drive, I ran a baseball simulation using a game called Out of the Park Baseball to simulate years of baseball games and statistics the computer didn't crash/restart, it just froze after a 15 or so minutes of processing that data. I'm seriously dumbfounded at this point. None of the hardware I pulled out to get down to a bare bones system caused anything to change so I'm fairly confident that those elements are not the problem. Is there some other troubleshooting methodology that would better serve me?