About 6 months ago I fried an Athlon XP chip I use in my server/backup workstation. So I just put in an old Athlon T-Bird I had. I figured it had been fried because when I had originally messed it up the machine would start but I would get no beeps and the monitor would never "fire up" with the system. After a few days of swapping parts I finally figured out it was the CPU.
Yesterday I got the bright idea of trying the XP again to see if I really cooked it. I swapped the CPUs and got the same results from 6 months back. Then I put the good CPU back in and booted up to install XP again. When it booted, the keyboard wasn't acting right and after I pressed enter to boot from CD, it didn't want to work at all. Which means I couldn't partition the drive and format. So, I rebooted a few times with the same results. On the last try, I hit a weird key combo I guess and the system just cut off. When I tried to boot it up I got the same result from 6 months ago, no video and no post. What the hell is going on here? Did I really fry another CPU by rebooting?
Yesterday I got the bright idea of trying the XP again to see if I really cooked it. I swapped the CPUs and got the same results from 6 months back. Then I put the good CPU back in and booted up to install XP again. When it booted, the keyboard wasn't acting right and after I pressed enter to boot from CD, it didn't want to work at all. Which means I couldn't partition the drive and format. So, I rebooted a few times with the same results. On the last try, I hit a weird key combo I guess and the system just cut off. When I tried to boot it up I got the same result from 6 months ago, no video and no post. What the hell is going on here? Did I really fry another CPU by rebooting?
Facebook
Twitter