- Aug 22, 2014
- 9
- 0
- 4,510
Hi all, a fresh member and a first-time PC-builder here! First of all, sorry for the long wall of text, but I'm trying to give out as much information as possible.
Last weekend I completed my first fully self-built computer. Surprisingly everything worked well, I installed Windows 7 64-bit, all my applications and a few games (which I tried for several hours on very high settings and the computer had no problems, CPU temp ~55-60, GPU ~50-60). All was well for ~5 days (PC was on ~90% of the time, downloading my steam library).
The problem started yesterday evening - first the PC just turned itself off. I turned it on again and it worked for a few minutes - during this time I managed to run AMD overdrive to see the CPU and GPU temperatures (I have not OC-d the CPU though, just use the program to measure temperatures. The temperatures were normal - around 30C CPU on idle and same for GPU. Anyway after a few minutes of idling the system locked up - the sound looped, mouse cursor did not move. Had to shut down the PC by holding the power button for several seconds.
The next time I tried to turn on the PC, the machine did not POST. All the fans turned on, and I could hear the HD also start up, but the red "CPU_Led" light stayed lit and nothing happened.
I figured maybe the processor is badly seated, since it is my first build. I removed the stock heatsink and the processor, removed the old thermal paste and applied some fresh paste (rouhghly the amount of a cooked grain of rice). Next time I ran the machine the PC told me that it detected a change of processor and booted into BIOS. From there I was able to boot into Windows and subsquently lock up in a few minutes again.
Now the PC is not booting at all, again stuck at red CPU_Led and working fans and HD. I obtained a Mobo speaker to learn the error code, but I'm not getting a single beep - even if I try to boot without any RAM present. I also rechecked all the connections, reseated RAM, GPU, etc, also reset the CMOS.
Could it be that the crashing somehow ruined the BIOS? The worse possibilities seem to be that either the CPU fried somehow, or the PSU developed a fault or that something is wrong on the motherboard. Or, I somehow managed to imperfectly seat the CPU heatsink. I'm hoping that it is BIOS. I have no equipment neither skills to test the PSU, but the rest of the components I'm going to try and "breadboard", to detect the fault more detailed, but since I am getting no Mobo speaker beeps at all, I'm not sure I'll be able to gather much information.
Writing from work at the moment, do not have a second PC at home, but I will monitor this thread on my phone and will try to present additional information when I have more (sent this post with the detailed description out before "breadboarding", because posting that kind of a text on a cellphone would take hours
Meanwhile, I hope that the description gives somebody a few ideas what might have happened and how I could fix it. Or at least an estimation about how probable it is that something fried.
If you need additional information, I will gladly provide it to the best of my ability.
My specs:
M5A99FX Pro 2.0 mobo
FX6300 CPU
R9 280 GPU (MSI 3gb version)
Samsung Evo 840 SSD for Windows, 1TB WD 7200 RPM drive for data
Random Apple Cinema Display (21")
8GB Kingston 1866mHz RAM (HX318C10FB/8)
Kind regards,
Kaarel
Last weekend I completed my first fully self-built computer. Surprisingly everything worked well, I installed Windows 7 64-bit, all my applications and a few games (which I tried for several hours on very high settings and the computer had no problems, CPU temp ~55-60, GPU ~50-60). All was well for ~5 days (PC was on ~90% of the time, downloading my steam library).
The problem started yesterday evening - first the PC just turned itself off. I turned it on again and it worked for a few minutes - during this time I managed to run AMD overdrive to see the CPU and GPU temperatures (I have not OC-d the CPU though, just use the program to measure temperatures. The temperatures were normal - around 30C CPU on idle and same for GPU. Anyway after a few minutes of idling the system locked up - the sound looped, mouse cursor did not move. Had to shut down the PC by holding the power button for several seconds.
The next time I tried to turn on the PC, the machine did not POST. All the fans turned on, and I could hear the HD also start up, but the red "CPU_Led" light stayed lit and nothing happened.
I figured maybe the processor is badly seated, since it is my first build. I removed the stock heatsink and the processor, removed the old thermal paste and applied some fresh paste (rouhghly the amount of a cooked grain of rice). Next time I ran the machine the PC told me that it detected a change of processor and booted into BIOS. From there I was able to boot into Windows and subsquently lock up in a few minutes again.
Now the PC is not booting at all, again stuck at red CPU_Led and working fans and HD. I obtained a Mobo speaker to learn the error code, but I'm not getting a single beep - even if I try to boot without any RAM present. I also rechecked all the connections, reseated RAM, GPU, etc, also reset the CMOS.
Could it be that the crashing somehow ruined the BIOS? The worse possibilities seem to be that either the CPU fried somehow, or the PSU developed a fault or that something is wrong on the motherboard. Or, I somehow managed to imperfectly seat the CPU heatsink. I'm hoping that it is BIOS. I have no equipment neither skills to test the PSU, but the rest of the components I'm going to try and "breadboard", to detect the fault more detailed, but since I am getting no Mobo speaker beeps at all, I'm not sure I'll be able to gather much information.
Writing from work at the moment, do not have a second PC at home, but I will monitor this thread on my phone and will try to present additional information when I have more (sent this post with the detailed description out before "breadboarding", because posting that kind of a text on a cellphone would take hours
Meanwhile, I hope that the description gives somebody a few ideas what might have happened and how I could fix it. Or at least an estimation about how probable it is that something fried.
If you need additional information, I will gladly provide it to the best of my ability.
My specs:
M5A99FX Pro 2.0 mobo
FX6300 CPU
R9 280 GPU (MSI 3gb version)
Samsung Evo 840 SSD for Windows, 1TB WD 7200 RPM drive for data
Random Apple Cinema Display (21")
8GB Kingston 1866mHz RAM (HX318C10FB/8)
Kind regards,
Kaarel
Facebook
Twitter
Instagram