Deuce65 :
Well maybe, maybe not. Lets start from scratch and not assume anything. What exactly happened? segmentation fault errors do not typically indicate a problem with the CPU or mb, but could be memory. What exactly happened, what is happening now, and what diganostics if any have you run?
What PSU is it?
Well, I came home to the smell of burning plastic.
I have several machines dedicated to CPU mining and this one machine probably needed better cooling.
After narrowing down the smell to one of my machines I checked it's status from a terminal (it's headless) and found it wasn't connected to the network.
Powered it down and back up to find it wouldn't boot.
Hooked it up to a monitor/keyboard/mouse then booted it to find that it couldn't find the SATA hard drive.
Reset the cmos and was unable to find a hard drive to boot from.
BIOS indicated that the drive capacity was incorrect.
Connected the hard drive to another PC and found it was bad.
Connected an older hard drive to the IDE port which worked, so I re-installed Debian.
Everything seemed to work fine.
Logged back in using SSH and tried to get it to start mining again, but got a segmentation fault error.
Attempted to run a few other programs and each returned a seg fault error.
Pulled each stick of RAM one at a time to see if I could narrow it down to a single stick, but I kept getting the same error.
Pulled the CPU which seemed as if it were welded to the heatsink, cleaned and reapplied thermal paste then reinstalled the CPU and still got the same error.
The PSU is a Rosewill Green Series RG530-S12 530W.
Motherboard is a Gigabyte GA-880GA-UD3H.
CPU is an AMD 910e.