HD Corruption when overclocking

[GRiMMi]

Wasn't sure where to post this - excuse me if it's the wrong place
Many of the times I have been overclocking - when I have pushed it to where windows won't even load (low voltage) the next time I start up, the C drive is corrupt - C is the boot drive. D is a partition of the same drive, but doesn't corrupt.
Every time it corrupts I can make scandisk recover the files and use them - but then they are file00001.chk etc. so the boot files are useless, but I can recover my most important documents. Sometimes when overclocking I restart it even tho it hasn't really crashed - I'm gonna stop doing that, dunno if that's it.
My system as of now :
Asus A7V-E
Duron 800@880
256mb pc133 SDRAM
SB Live 1024
Western Digital 20,5 GB
3d Prophet 2 MX
Plextor 8/4/32x
AOpen 48x
Windows ME Corporate

 

[n2]

recently, i learned that having your PCI clock set too high causes the corruption of files. could that be your issue?

 

[GRiMMi]

It could, it could.. The fsb affects pci speed right ?

 

[Goldwing]

Right the PCI bus is a multiple of the FSB. On my motherboard it is 1/3 of FSB up to a FSB of 132 and 1/4 of FSB at a FSB of 133 and over.

Some brands handle high PCI settings better than others.

 

[GRiMMi]

I can't up the FSB over 111 without files corrupting, tested it thoroughly now.

 

[Rav]

I had a similar problem with an old Maxtor 11GB when my FSB was over 105. The fix was to turn of DMA for that drive (which was fine for me because it was just a storage drive and didnt need performance). My newer Maxtors 30GB and 27GB are doing fine at 113.

 

[GRiMMi]

Damnit - turning off dma...that works - but ffs, it like drops the performance to one thirdth . So who's problem is this - Western Digital or Asus ?

 

[Oni]

When you push the FSB hugely out of spec, everything runs faster. There aren't many board that support a PCI divisor over 4. So you have to remember that every Mhz that you push your FSB over 133, it only divides that by 4 to obtain how fast the PCI bus should run, which includes videocards, modems, nic cards, and Hard Drives. There are other variables, like running your FSB at 120. 120 only divides by 3, so your PCI runs at 40, which is 7 Mhz over what it is supposed to be running at (33). These are good to keep in mind when overclocking w/ FSB. You can really only go so fast. Most devices don't mind going about 3 or 4 Mhz over, but after that it gets sketchy. Just be careful, and remember to back up your system.

 

[Kramerica]

My 50 gig hd did the same thing when I continously screwed with the multiplyers. Lost 1,500 mp3s and 50 or so DVD RIPS

 

[GRiMMi]

Today I had it at 111 mhz thinking peace and quiet - but no. Right now I'm in 110 mhz and with a crippled winMe full of dll errors.

 

[Wega!]

GRiMMi (Jun 14, 2001 12:16 a.m.):
Today I had it at 111 mhz thinking peace and quiet - but no. Right now I'm in 110 mhz and with a crippled winMe full of dll errors.

Have u tried another OS?

 

[GRiMMi]

No not together with upping the fsb - isn't really worth the hassle yet (need noise isolation), and I doubt it will work - as it normally hangs before winme is even started. I dunno I spose I could try it.

 

[Oni]

Try Windows2000 Professional. It works great.

 

[SickBoy]

Your IDE controllers run at the speed of your PCI bus, so if your PCI bus is out of spec (less than 31 MHZ or more than 35) your hard drives connected to those IDE's might have problems. HD corruption is a sign that you need to back off FSB or increase it so that you get a /4 PCI divisor.

SickBoy

 

[GRiMMi]

I think I got that part - but is it normal to have problems already by 110 fsb ? (10 mhz over standard)

 

[Justice]

Are you using generic memory? If you are try some crucial or corsair.

 

[GRiMMi]

Well yes I am, but I'm also trying to hold my budget
Why would memory be the problem ? I can run the memory high, already tried that. It's pc133, and if I put it at 100 mhz default and then up the fsb, it won't even go to 133...

 

[sfa ok]

On the Abit KT7A, does the CPU FSB box that adds mhz to the cpu and memory also affect pci and agp?

 

[Goldwing]

sfa ok (Jun 16, 2001 09:21 a.m.):
On the Abit KT7A, does the CPU FSB box that adds mhz to the cpu and memory also affect pci and agp?

Absolutely, PCI and AGP speeds are fractions of the FSB. PCI=1/3 of FSB between 100-132 mhz FSB and 1/4 of FSB >=133mhz. AGP is twice PCI bus speed with 1x, 2x, and 4x multipliers available.

So 132Mhz FSB = 44Mhz PCI and 88Mhz AGP (and with a 4x Multiplier 352 Mhz). 100 & 133 Mhz FSB = 33Mhz PCI and 66Mhz AGP (and with 4x Multiplier 266MHZ)

 

[Justice]

When I OC'ed my 750 to 825 via FSB cranking the generic memory went all to sh!t. any system i put it in it just f'ed up. Use CTSPD to determine if your memory is still functional. My dads laptop also had BSOD's from bad memory.. A 128mb fix from crucial, and no more BSOD. No More DLL errors. Athlons don't due well with generic memory because of background signal noise(?) messes up the 200mhz FSB.. Intels like it better because the run @ 100 or 133 mhz FSB and the noise doesn't affect the signals as much. Cas2 Crucial stuff fixed me up slick.