I've never heard of undervolting hurting motherboards. I would reset your bios (unplug from wall, remove battery, switch cmos switch, wait 30, reverse) and try system restore or last-known good on bootup. Should fix the issue.
So, reset bios, reinstalled drivers. Teseted all GPUs to see if they could hash for 10m stock (probably not a long enough test to determine health): 7 passed, 1 causes system to boot to some 'corrupted' / must repair mode; I don't remember specificly but I've never seen it before - sounds dead.
For the motherboard, I get 4 slots that recognize 'passed' cards, and 3 only recognizing them as 'standard VGA adapter'. Ideas?
Also, I took two 'passed' cards at stock, set to mine over night. One crashed at ~2 hours, another at ~3 hours. So frustrating.
In a few hours I'll be able to start QC on my other rig and can cross-compare gpu's on that one
+1 This is where I would start as well, unless the real issue is the SO jamming a fork into it while he is a work...
Good thinking, but 1) I know she was out of town, 2) I trust her.
I'm using cgminer directly on a headless machine running xubuntu 12 with catalyst 13.3 drivers. You can try adding the --gpu-powertune 20 to the cgminer parameters but it seems like GUIMiner is already doing this since you're hitting 635 and if you\re using GUIMiner I'm assuming you have a screen connected - which intensity 20 that might be causing the errors. Try using cgminer directly by unplugging the monitor and sshing into the machine and running it. or maybe just run guiminer and unplug the monitor and see if your pool results change
I unplug the monitor once the system start hashing. I'm in the process of trying to decide on a good headless method I can monitor remotely. Your system sounds reasonable. Do you use anything to monitor remotely?
I'll keep doing my research as I haven't sshed before and am new to networking, but I already run mint on my main system so crossing over to linux wouldn't be too bad.