SATA drive not working while FSB is raised?

[DyslexicHobo]

I've really been trying to overclock my Athlon 64 3500 (13nm) to 2.5-2.6GHz. I got it stable at 2.5GHz, but then I went to open my E drive and it said it was corrupted! That had me scared, but after a reboot and turning my FSB back down it was fine.

Why is this happening? I've got the latest bios (1009). Is there anyway I can prevent this?

 

[fixxxer0]

I think if thats happening, its not really stable

What tests are you running to define it as stable at that speed?

 

[DyslexicHobo]

I ran Prime95 for ~2 hours. Is that not long enough? *Is new to OCing*

 

[BlueWeasel]

What revision board is that? I've read that the Revision 2.0 A8V boards have a AGP/PCI lock, but the earlier A8V boards don't have a lock.

With no lock, raising the FSB could certainly cause hard drive instability when overclocking.

 

[DyslexicHobo]

Crap I have the Revision 1 board... The Asus site says that the 1005 BIOS fixes that problem, apparently not. Both of my IDE drives work fine though.

 

[crazyjeeper]

Originally posted by: DyslexicHobo
I've really been trying to overclock my Athlon 64 3500 (13nm) to 2.5-2.6GHz. I got it stable at 2.5GHz, but then I went to open my E drive and it said it was corrupted! That had me scared, but after a reboot and turning my FSB back down it was fine.

Why is this happening? I've got the latest bios (1009). Is there anyway I can prevent this?

What fsb are you running?

 

[DyslexicHobo]

230 x 11

 

[BlueWeasel]

Originally posted by: DyslexicHobo
Crap I have the Revision 1 board... The Asus site says that the 1005 BIOS fixes that problem, apparently not. Both of my IDE drives work fine though.

Oh, that may not be the problem then. I don't have a A8V, but did remember reading about the lack of a AGP or PCI lock. I did a quick Google search and found that the Rev. 2 boards are supposed to have the lock. I don't know if Asus added the lock as part of a BIOS update.

Given what you described, though...it really sounds like corruption from a PCI bus overclocked too far.

 

[Inappropriate4AT]

Null.

 

[Sardian]

Did you go into the bios and manually set the agp/pci bus to 66/33. I know you have a rev.1 board and it may not lock for you but even though I have a rev.2 board I still must manually set the bus to 66/33 or it isn't locked. You can use the program ClockGen to check if it is locked or not.