Overclock corrupted windows??? HELP!

[Boonesmi]

you can easily get corrupt data on a harddrive from overclocking past the point your hardware can handle (even when the pci bus is running in spec at 33mhz)

sounds like your going to have to reinstall windows

 

[DrZone]

Originally posted by: Boonesmi
you can easily get corrupt data on a harddrive from overclocking past the point your hardware can handle (even when the pci bus is running in spec at 33mhz)

sounds like your going to have to reinstall windows

Provided I take things slowly, is there a chance of permanent damage?

 

[Boonesmi]

Provided I take things slowly, is there a chance of permanent damage?

nah you dont need to worry about permanent damage... the corruption isnt from the harddrive failing... its from the system failing while the harddrive was in the process of being written to

personally i make a clone of my system (using nortons ghost) before trying to find the overclocking limit of my system... then if i screw up windows i can always restore it from the clone

hehe and believe me, its saved me more then once.... i think ive corrupted windows at least half a dozen times while trying to find the overclocking limit of a cpu (especially in winxp... it rarely happened with win98)

 

[Sid59]

=\ ..

i tried to up my multiplier from 11 to 11.5 x 200 and no boot, constantly rebooting. i couldn't even boot when i tried 11 x 205. I didn't relax my timings so i don't know if it's the cpu or the memory. Though im sure my corsair xms 3200 would be able to handle 2-3-3-6. Oh well. Im happy with 2200 ghz.

Good luck on getting windows to boot.

 

[DrZone]

Originally posted by: Sid59
=\ ..

i tried to up my multiplier from 11 to 11.5 x 200 and no boot, constantly rebooting. i couldn't even boot when i tried 11 x 205. I didn't relax my timings so i don't know if it's the cpu or the memory. Though im sure my corsair xms 3200 would be able to handle 2-3-3-6. Oh well. Im happy with 2200 ghz.

Good luck on getting windows to boot.

Thanks for the info... Well, i re-installed everything and running at 10.5x200 @ 1.675 on retail HS/fan. I'll scared to try for 11x200 since last time it corrupted EVERYTHING. Although i'm still confused why...

Thanks for all of your help!!!

 

[Boonesmi]

do you have a spare harddrive? if so you can easily make a clone of your current harddrive
then you wont need to worry about corrupt data, you can aways just restore from the clone

 

[bjc112]

Originally posted by: Cesar

Originally posted by: DrZone
Just the retail heatsink/fan. The temps don't go beyond 45 celsius in the bios. And from reading other posts, many users were able to go even further than 3200+ using the retail heatsink/fan.

there's your problem buy a better cooling than the stock cooling
SK-7 with SFII
SLK-947U excellent heatsink

I'm getting the SLK-947U with Vantec Tornado 92mm
well I'm overclocking my Athlon 1700+ to 2.4Ghz and I need Super cooling!
temperture must be under 40 idle if you want a stable system when overclocking!

Come on now Cesar...


Disregaurd that post Doc..

You do not need super cooling to hit fairly decent overclocks.. You should be able to attain 2.2Ghz with the stock HSF and a few case fans.

"temps under 40 idle for stable OC"

Where the hell did you hear that? AMD states it's CPU's are good and safe up till 94C.

Normally you won't see a stable overclock with anything of 65+C but it can happen..

I have overclocked several system on the retail HSF - Intel / AMD and both are fine if you keep the overclock resonable .. Anything under 60C is fine. ( Shoot for 50 )

 

[Soulkeeper]

dang i just corrupted windows too

bla

it gets too hot during the day

stable up to like 2.8 at night but only 2.4 during the day

 

[0roo0roo]

ghost is your friend

 

[Sid59]

Originally posted by: DrZone

Originally posted by: Sid59
=\ ..

i tried to up my multiplier from 11 to 11.5 x 200 and no boot, constantly rebooting. i couldn't even boot when i tried 11 x 205. I didn't relax my timings so i don't know if it's the cpu or the memory. Though im sure my corsair xms 3200 would be able to handle 2-3-3-6. Oh well. Im happy with 2200 ghz.

Good luck on getting windows to boot.

Thanks for the info... Well, i re-installed everything and running at 10.5x200 @ 1.675 on retail HS/fan. I'll scared to try for 11x200 since last time it corrupted EVERYTHING. Although i'm still confused why...

Thanks for all of your help!!!

Use GHOST to back up your current install. 2100 mhz from 1800 mhz is still a good oc.

 

[DrZone]

Yup 2100mhz is about 3000+ so i'm pretty pleased with that. But if i keep my FSB the same and just play around with the multiplier, could that corrupt my hard drive too? Keep in mind that my FSB and ratio's will be kept the same.

 

[CaptianAburrr]

how would you go about fixing this problem if you have SP1 installed.. I booted from my cd-rom and i usually just install over or "repair" the current windows xp installation.. but for some reason i dont see that option this time.. it tells me if i choose to install windows xp over the current installation that all users and files will be deleted and possibly the "My Documents" folder.. I have ALL my data on the drive as I just built the computer and haven't had a chance to create a backup yet.. I have two raptors in Raid 0 and two IDE drives in raid 0.. if I could somehow get in where i could copy all my data from drive C: to drive E: (i really wished i'd done this before this happened) i would just re-install windows without a care.. let me know what you think i can do

 

[Boonesmi]

Originally posted by: DrZone
Yup 2100mhz is about 3000+ so i'm pretty pleased with that. But if i keep my FSB the same and just play around with the multiplier, could that corrupt my hard drive too? Keep in mind that my FSB and ratio's will be kept the same.

yeah you can corrupt data even if you just raise the multiplier to high (leaving everything else in spec) corrupt data certainly doesnt happen all the time, but it is a risk

 

[ScissorClaw]

You run a chance of corrupting your data anytime that the computer decides to do a reboot right in the middle of windows loading. So, it doesn't really matter if it is the FSB, ration, multiplier, vcore or whatever you may happen to be doing at the time. It's the resulting rebopot that does the damage. It's the same thing as pulling the plug as windows is loading. You probably won't get a corrupted NTLDR file (or any other important sys file) everytime, but you will definetly have it happen more than you would like. I've corrupted plenty of OS's during overclocking, and it only seems to happen during an imprmptu reboot, they really suck. I cross my fingers and pray everytime it happens. I've learned since to make a ghost image before trying any serious overclocking. I have an extra HD I just ghost everything too, and should I corrupt the original, just switch the cables and I am good to go. Works like a charm and I'm right back to overclcoking like it never happened.