Overclocking Help

[Brodly]

While testing my FSB for my computer i got to that point where i couldnt get into windows. So i knocked my FSB down about 5 and i still couldnt get it. another 5 then 10 then 20 and i still couldnt get in. Finally i reset my CMOS put everything to default and still no luck getting in. Any help would be greatly appreciated. Thanks

Athlon XP 2500+
Abit AT7-MAX2
Samsung 512 PC2700
Maxtor 200 gig and 80gig
BFG 5900Ultra
Enermax 430w

[airoh69]

When you say you couldn`t get into windows what do you mean. the computer freezes,restarts by itself or what????
also what are your temps.

[Nive11en]

I heard that if you clock yer FSB too high, and your hard drive isnt of too good quality, some data may get corrupted, thus causing such a problem.
I don't have experience in that problem though, lets wait until someone knowledgeable will post about it.

[GnomeWizardd]

first off u know FSB UP not down. Second what error are you getting?

[lordbean]

I heard that if you clock yer FSB too high, and your hard drive isnt of too good quality, some data may get corrupted, thus causing such a problem.
I don't have experience in that problem though, lets wait until someone knowledgeable will post about it.

I can see where someone might make that mistake. Data errors are never going to be the HD's fault, no matter what quality the HD is, as long as it is in working condition. The HD will always read/write properly, but the data that it reads and writes passes through your RAM / CPU caches at some point. Since CPU/RAM are the first things to destabilize while overclocking, errors start flying, and the HD can appear to both be producing read errors, and can actually write bad data to the drive if errors are made in data to be written.

Keep in mind, the key point here is none of this is the HD's fault. It's just doing what it's been told to.

[kanezfan]

your windows install is fried. you need to run a repair install. it's happened to me, and i was pissed, but i got over it.

[Nive11en]

I can see where someone might make that mistake. Data errors are never going to be the HD's fault, no matter what quality the HD is, as long as it is in working condition. The HD will always read/write properly, but the data that it reads and writes passes through your RAM / CPU caches at some point. Since CPU/RAM are the first things to destabilize while overclocking, errors start flying, and the HD can appear to both be producing read errors, and can actually write bad data to the drive if errors are made in data to be written.

Keep in mind, the key point here is none of this is the HD's fault. It's just doing what it's been told to.
That's right. It sometimes is the chipsets fault that data gets corrupted on HD's then?

[lordbean]

Well, any data being written to the HD passes through system RAM first, and if you're overclocked to the point where the RAM is unstable, there are going to be mistakes in the data, which the HD will write to disk. So because the CPU or RAM screwed up, the HD writes bad data.

[Zuntar]

first off u know FSB UP not down............

? WTH this no make sence to me! :loco: