How bad is it when OC fails?

J

Jedimoto

Limp Gawd
Joined
Sep 11, 2004
Messages
144
I mean, does anything REALLY bad happen often? If I OC too much and it crashes, does it still boot up to BIOS alright? I'm really new at this and really don't know what to expect.
 
I OCed my 3500 on the fly using OCGuru, a feature of ABIT AV8 mobos, i wanted to see what would happen if i tried to oc to 2400 with my junk stock cooler and it hung around for a bit, then decided to lock up, then crash and reboot, when i reloaded and tried it a second time, it went off and the mobo started beeping at me, so i just killed the power and let it sit for a minute then booted in bios and downclocked it to sustainable speeds through bios itself and it didnt give me problems since, so i had it at like 2300 mghz with no problems, but i decided to go stock speed until i get my new HSF. You shouldnt have anything to worry about as long as your mobo/cpu have some kind of auto-shutdown feature, which im almost positive all new amd and intel processors have.
 
If something really goes wrong and you can't get into your bios then you have to reset your cmos. Check your mobo manual to tell you how. That should fix any problem you might have with OC'ing.
 
With your XP 120 I really wouldn't worry about it, I'm sure you can go far with it and not have any problems, just don't go overboard.
 
If you fail an overclock, there is almost a 0 percent chance of hardware damage. The only way hardware can be damaged is if you overvolt components too much. When your system crashes from an overclock, just reset the CMOS jumper. Quick and painless.
 
That wasn't so bad.
Oc'd to 2530mHz on the CPU with the mem @1:1, and 405mHZ/1100 on the GPU. First 3DMark03 and 01 kept hanging and so I rebooted. Bossted the Voltage to the AGP and started it back up. Then the PC lept trying to boot, but was going to a screen I had never seen before. Something about nVIDIA and about looking for an array or something. I dunno. It would try to boot, go to that screen and then try and boot again. So I loosened the timings up a bit and lowerd the 6800GT to 385/1000. Worked like a charm. 750+ gain on 3DMark03 scores and 400+ gain on 3DMark05. :D
I know those benchmarks aren't the end all be all, but it feels good to tinker around and make the PC faster. And you guys were right, when the OC fails, you just gotta back off a bit and try something else. :)
Thanks
 
overclocking only stresses components.... running them as fast as there capable of going will make them die marginaly faster
 
I OC'ed my chip pretty harsh the other day. Now I get random times when it wont even post when not over clocked.... I dont know what to replace now.
 
Glad your OC worked.

On my FX53, I left the CPU voltage at stock, and tried for 2700 by changing the multiplier. The system didn't boot, and then I couldn't get to the bios page to change it back. I had to reset the Cmos, which is a pain in the butt. Had to remove the battery, do the jumper, then put the battery back in. No more of that, I installed Clockgen and let it change the multiplier.

The higher you attempt to OC the CPU, the more voltage you'll need. The cost of this is heat. If you set your voltage to 1.8, your temps will sky rocket. I tried this on my water cooled machine at 2800, and it simply shut down. After waiting a minute, it came back to life. You may be able to up your voltage to 1.725, but I wouldn't go above that.

I have read of an older story where this guy OCed an Athlon 1.7 to 2.2, with raised voltage, started Prime95, went to the movie theater, and when he came back, his computer was dead. You may want to set the auto shutdown temp limits in your MB just in case you go above 65 or 70c.
 
The only think i have heard of an OC screwing up is data on a HD.
But that was in the old days where you didn't have locked pci bus speeds.

Shouldn't hurt anything these days.
 
Talonz said:
If you fail an overclock, there is almost a 0 percent chance of hardware damage. The only way hardware can be damaged is if you overvolt components too much. When your system crashes from an overclock, just reset the CMOS jumper. Quick and painless.
Click to expand...

well mostly true, except if you have a soltec 75fnblabla MB. I killed mine, lol, what a pos that board was
 
Well I've reset my jumper a few times pulled the CMOS battery put it back in. Now everything will power on but wont get post. My power switch wont even work properly it acts like a reset button.... sigh whats going on?
 
titanium said:
Well I've reset my jumper a few times pulled the CMOS battery put it back in. Now everything will power on but wont get post. My power switch wont even work properly it acts like a reset button.... sigh whats going on?
Click to expand...


sounds like nothing ;) . sorry but it doesn't sound good
 
mobiux said:
The only think i have heard of an OC screwing up is data on a HD.
But that was in the old days where you didn't have locked pci bus speeds.

Shouldn't hurt anything these days.
Click to expand...

hahah well i wish my gigabyte k8n pro nforce150 was like that :( :p
 
You must log in or register to reply here.
Back
Top