FSB & Hard Drive Corruption

[dmdstar]

I can't seem to get my FSB over 140 without the hard drive corrupting. (Get an error about Winxp system file missing or corrupted). Lowering it back down to 133 causes it to boot normal again.

Is there something I'm missing here? I know there are supposed to be dividers on this board, but where are they?

I really want to max out this RAM, but this durned hard drive problem is holding me back...

Thanks for your help.

[Holst]

140 seems a bit low for HDD corruption.

What speed is the ram running at when the board is at 140 ?
What timings ?
What voltage ?

It sounds more like the ram wont go any faster to me...and is causing problems with windows.

[dmdstar]

I got the OCZ PC3000... I sure hope that isn't the problem...

I tried with the ram at both 166 and 133. When oc'ed, i had vdimm voltage at 2.7 (ocztech website says anything higher would damage it). Settings are at cas2.5-3-6-3.

Thanks.

[Holst]

Originally posted by dmdstar
I got the OCZ PC3000... I sure hope that isn't the problem...

I tried with the ram at both 166 and 133. When oc'ed, i had vdimm voltage at 2.7 (ocztech website says anything higher would damage it). Settings are at cas2.5-3-6-3.

Thanks.

I just read another thread on here that says that the memory will allways run in 166mhz mode untill the fsb reaches 166.

So even if you set it to 133 it will be at 166 and at 140 it will be at 175

If your ram is at 175mhz that would explain the HDD corruption.

As your CPU is unlocked try dropping the multiplyer down to say 9 and then run 167fsb.

Post back with the results.

Good luck.

[dmdstar]

I'll try that tonight and post back with the results, but this RAM should be able to hit 190 FSB easy... at least that's how it was advertised.

[dmdstar]

I am writing this now, running 9.5x multiplier at 167Mhz FSB!!! ... I've never experienced things moving so fast! ...can't wait to see how far I can take this bugger.

Thanks for the suggestion.

[Holst]

Originally posted by dmdstar
I am writing this now, running 9.5x multiplier at 167Mhz FSB!!! ... I've never experienced things moving so fast! ...can't wait to see how far I can take this bugger.

Thanks for the suggestion.

Cool.

Now try this.

Drop the multi back to 9X (8.5 if you realy want to push hard) then increase the FSB as far as it will go.

If that ram is as good as they claim it is then you might get well past 167.

You might also have to play with voltages and timings to get stability.

Once you have sucssesfully found the max FSB you can increase the multiplyer to the chips maximum.

Glad I could help.

[nikhsub1]

Just so you know, that windows error is NOT HD CORRUPTION!! I get that when I OC the system to far with multi and a low FSB. That is just the CPU freaking out. BTW, Im running this sucker at 183x10! Rocking Fast!

[dmdstar]

When I got into Windows, it was horribly unstable. Kept crashing,, and couldnt keep it up for more than a few minutes. Ah well... Thinking maybe I had some bridges crossed, I wiped away the conductive grease, locking the processor once again... after rebooting, with the bios back to normal, I got that crazy message again... guess it's time to reinstall windows... hope i didnt cause some kind of permanent damage.

[EPoX Tech]

Your symptoms are not of HDD corruption but of unstable overclock. In your particular case I would not attempt to overclock in order to overt any unexpected damage to any peripheral from unknown causant factors.

[Holst]

Originally posted by dmdstar
When I got into Windows, it was horribly unstable. Kept crashing,, and couldnt keep it up for more than a few minutes. Ah well... Thinking maybe I had some bridges crossed, I wiped away the conductive grease, locking the processor once again... after rebooting, with the bios back to normal, I got that crazy message again... guess it's time to reinstall windows... hope i didnt cause some kind of permanent damage.

Like epox tech says your overclock isnt stable.

Go back to default speed and try booting windows again...if its dead reinstall at stock speed

If you think your unlocking is not good do it again....and test it throughly running 133fsb with various multiplyers.

Next download "memory stuff" from www.aoafiles.com
That zip includes memtest86 a DOD memory tester.

Use it to test your memory stability with the HDD unplugged (no chance of corruption) Once you have found a FSB where you can pass memtest try windows (with the CPU multiplyer low)

Then run the other part of memtest "superPI" if you can pass a 5m superpi then your memory is stable.

Increase the CPU voltage a bit and increse the CPU multiplyer by .5 run to see if its stable (3dmark is good) then increase another.5 and so on.
Hopefully moving slowly will show you slight instablity in 3dmark before windows gets damaged.

[Caper]

Originally posted by dmdstar
I got the OCZ PC3000... I sure hope that isn't the problem...

I tried with the ram at both 166 and 133. When oc'ed, i had vdimm voltage at 2.7 (ocztech website says anything higher would damage it). Settings are at cas2.5-3-6-3.

Thanks.

I am running OCZ PC300 on 8K3A 200 fsb cas2 4way, 2.8 DDR voltage.

[dmdstar]

Yeah, I don't think it was my ram... I'm fairly certain these problems were due to a bad unlock.

[xgman]

Is it harddrive corruption if you get a message something like windows/sytem config damages try to run "r" repair, and you can't get into windows at any speed even default settings and safe mode after a high overclock in the 200fsb range?

[dmdstar]

That's what happened to me. Only way around it was to reinstall windows.

At first, It fixed itself when I went back to default speed, but I upped the fsb one too many times, and it went splat.

[xgman]

curious what fsb did it happen and which hard drive? Did it run for a while and then give out or happen as soon as you pushed it to far?

[dmdstar]

Happened immediately. Windows wouldnt even load.