Why do my files corrupt any time i overclock

[foges]

I just upgraded my motherboard and CPU and now every time that i overclock and it gets unstable, some file on my computer will become corrupt so windows wont boot and the windows repair function on the windows install CD wont work (it will always halt somewhere). Why is this? It isnt normal is it?

This time when i run the install CD the problem is:

L:\I386\asms Parameter is incorrect

anyone have any clue how to fix it, before i go reformatting again???

Im running linux right now, but i deffenetally dont love it, its just too complicated for what an os should be, especially when it comes to installing stuff, i really dont like the terminal.

 

[Smilin]

Dude, a stable overclocked system is generally an illusion. What appears stable is usally just bitflips, missed clock edges and all sorts of trouble that simply hasn't hit anything critical to cause a crash. It's luck.



Yes, the behavior you are seeing is perfectly normal. If you redlined your car all the time it might not blow the engine but would you be surprised to see it burning a bit more oil?




(before anyone jumps...yes it's an exageration. You can get stable - but most people overclocking don't really know one way or the other).

 

[RebateMonger]

File corruption is one of the potential consequences of overclocking. You can have problems with the disk controller, Windows System files, or the Windows Registry.

There's a reason why components are given a clock rating by the maker. Often, it's because the manufacturer tested the component at higher speeds (using very strict tests) and found problems.

Originally posted by: Smilin
Dude, a stable overclocked system is generally an illusion. What appears stable is usally just bitflips, missed clock edges and all sorts of trouble that simply hasn't hit anything critical to cause a crash. It's luck.

I agree. The last TOTALLY STABLE overclock I performed was the Celeron 300/450 around 2000. Every other significant overclocking I've done has eventually displayed instabilities. Sometimes it just takes a while to find them. I'll take total reliability over a small speed boost any time.

 

[foges]

Damn, i didnt know overclocking was that bad, with my last 3500+ it would run unstable and hot, but never screw around with the files.

 

[RebateMonger]

It could depend on the drive controller. Some might handle overclocking nicely, and some might not. Data corruption is a definite possiblity when overclocking. I've never SEEN it happen, but I've read of it happening. The most common corruption problem is probably in the Windows Registry.

 

[Smilin]

Originally posted by: foges
Damn, i didnt know overclocking was that bad, with my last 3500+ it would run unstable and hot, but never screw around with the files.

Data corruption on disk from overclocking is pretty rare. You could get there by writting something from corrupted memory to disk, or having your controller incorrectly execute an instruction... again very rare though. More often data corruption occurs in o/c systems simply because of a dirty shutdown due to a crash. unstable & hot = asking for a dirty shutdown.

 

[Shawn]

It is because you are overclocking the hard drive controller as well. If your bios supports it you need to adjust the pci bus speed seperately. If you can't then you are SOL.

 

[Smilin]

Originally posted by: RebateMonger
It could depend on the drive controller. Some might handle overclocking nicely, and some might not. Data corruption is a definite possiblity when overclocking. I've never SEEN it happen, but I've read of it happening. The most common corruption problem is probably in the Windows Registry.

Yep. The registry files are constantly in use and being touched (go TRY to delete system32\config\system 😛 ). If you get a bad shutdown the probability of corruption is actually pretty high. Windows does all sorts of crap to try and minimize this (.log & .sav files. double copies etc) but there is only so much that can be done.

 

[bob4432]

if you lock the pci and pci-e bus and the only thing that gets messed with is the fsb and your machine is both memtest stable for 12+hrs, orthos stable for 12+hrs and can loop any video benchmark for 12hrs+ how is this not a stable o/c?

 

[ebaycj]

Originally posted by: Shawn
It is because you are overclocking the hard drive controller as well. If your bios supports it you need to adjust the pci bus speed seperately. If you can't then you are SOL.