![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Åndhrimnir
Limp Gawd
- Joined
- Nov 28, 2009
- Messages
- 323
Long story short: there was a power flicker that took my computer down yesterday. This happens from time to time, seemingly always when I was in the middle of something important, but this time was really bad - I was defragging the system folders.
When the power came back on I powered up, but the system didn't POST. I reset the CMOS and tried again. This time it booted. My OC settings were back to stock, but I figured I'd deal with it later. The system booted fine, no issues at all. I thought if it acted funny I would do a restore but it was fine.
Today I went to re-OC my CPU (which is a Phenom 9850 BE). My last OC was simple - I cranked the multiplier up to 17, where it ran hot at 3.4 GHz, then dropped it back to a comfy 3 GHz.
This time I set the multiplier to 15 (3 GHz) to start. I ran a visualizer and several 2d games at the same time for an impromptu stress test - worked fine. CPU load was at about 60% and temps were in the low 40s.
Then I jumped to 3.2GHz. This is where it got bad. Ten seconds later the machine crashed - hardcore BSOD, first one I've had in a year of owning the machine. It rebooted with stock settings - even though I didn't touch the CMOS jumper.
To put it simply, it acts funny now. Even after clearing the CMOS, the computer doesn't work. It boots to windows, but windows is broken - I tried to open the control panel to do a system restore and it just opened and froze. half my programs do this - CPU-Z, Zune, Windows Live Mail, etc.
I anticipate having to replace components - that's not a problem. My confusion is on these two points:
1) Did I damage the processor (seems more likely) or maybe the mobo (an ASRock K10N780SLIx3-Wifi)?
2) If the processor is damaged, as I am inclined to suspect, then why does the machine still boot? I figured a processor was pretty much either functional or a paperweight with no middle ground - am I wrong?
Thanks in advance for any help. I just joined this community, and I hate to be bugging people for help already, but this was just bad timing and I don't really know what to do.
-Åndhrimnir
When the power came back on I powered up, but the system didn't POST. I reset the CMOS and tried again. This time it booted. My OC settings were back to stock, but I figured I'd deal with it later. The system booted fine, no issues at all. I thought if it acted funny I would do a restore but it was fine.
Today I went to re-OC my CPU (which is a Phenom 9850 BE). My last OC was simple - I cranked the multiplier up to 17, where it ran hot at 3.4 GHz, then dropped it back to a comfy 3 GHz.
This time I set the multiplier to 15 (3 GHz) to start. I ran a visualizer and several 2d games at the same time for an impromptu stress test - worked fine. CPU load was at about 60% and temps were in the low 40s.
Then I jumped to 3.2GHz. This is where it got bad. Ten seconds later the machine crashed - hardcore BSOD, first one I've had in a year of owning the machine. It rebooted with stock settings - even though I didn't touch the CMOS jumper.
To put it simply, it acts funny now. Even after clearing the CMOS, the computer doesn't work. It boots to windows, but windows is broken - I tried to open the control panel to do a system restore and it just opened and froze. half my programs do this - CPU-Z, Zune, Windows Live Mail, etc.
I anticipate having to replace components - that's not a problem. My confusion is on these two points:
1) Did I damage the processor (seems more likely) or maybe the mobo (an ASRock K10N780SLIx3-Wifi)?
2) If the processor is damaged, as I am inclined to suspect, then why does the machine still boot? I figured a processor was pretty much either functional or a paperweight with no middle ground - am I wrong?
Thanks in advance for any help. I just joined this community, and I hate to be bugging people for help already, but this was just bad timing and I don't really know what to do.
-Åndhrimnir