help on overclock w/ asus bios

[dualhybrid]

So, i have an ASUS pd5l2 (specs in sig). I want to run my cpu at 3.0 ghz... its currently oc'd to 2.77, at 45C load temps. I am using AI's 'easy overclock' type tool that lets you overclock to a certain percent.... currently 30. So when i go into manual mode to custom change the freq. i type in 375 (x 8) and it runs at 3.0 ghz........ but of course for some reason its not that easy. Temps are stable, but for some reason, NTLDR is missing, wont boot windows. I go into bios, and the default boot drive is now my IDE drive (secondary storage) and my raid array is missing from the list......
i go back to 'overclock 30%'...... and raid array pops back up
any ideas?

[hUMANbEATbOX]

that mobo has a i945p chipset. i think 375fsb is asking a bit much of it.

[dualhybrid]

it says input value to 450....
but would that cause the not-recognizing the drive problem?

[hUMANbEATbOX]

just because it says 450 in the bios, doesn't mean it will actually go that far. i think mine says 650 in the bios. :eek:

your chipset was originally not designed with the core2duo's in mind. it was designed for cpu's that had a stock fsb of 200. it really wasn't ever meant to go that high. to be honest, i'm surprised you can even post at 375fsb. ;)

and yeah, that could likely be the reason why your hd's are flaking out. i would make sure the pci-e speed is locked at 100mhz, and that the pci speed is locked at 33.3mhz, as that could be causing the problem as well.

[dualhybrid]

that didnt work, that last part. it didnt post after i took the pcie and pci freq's off auto. had to take the cmos batt. out

[hUMANbEATbOX]

that means that something is corrupt, and i think you will have to reformat, and set up your raid all over again. the pci-e speeds SHOULD be set 100, and the pci SHOULD be locked to 33.3 from the start to avoid this happening again.

[Will Eatforfood]

? It shouldnt be more stable at auto. Because then it would go up as FSB goes up and that causes HD corruption and all types of mess. In general/most cases, motherboards are crappy at making decisions. Check if there is a "Hyper****" option on the ram. I don't remember exactly what it's called. But disable that. Set your ram to loose timings.

When it can't detect NTLDR after an overclock, the mobo can't handle the FSB. Has nothing to do with the hard drive's boot sector.

For running higher than whatever stable fsb u have right now, try to increase your mch voltage and fsb term v. Other than that, your mobo has reached its limit.

[dualhybrid]

For running higher than whatever stable fsb u have right now, try to increase your mch voltage and fsb term v.

can you un-abbreviate that? and tell me what volts i should try running?

[BMac420]

can you un-abbreviate that?


for running front side bus than whatever front side bus you have right now, try to increase your MCH (north bridge) voltage, and your front side bus termination (FSB TERM) voltage. those are both settings in your bios and upping the voltage on them allows them to handle higher frequencies. as does the ICH voltage (south bridge).

EDIT: i honestly couldn't tell ya recomendations for voltages on that board. sorry.

[dualhybrid]

for running front side bus than whatever front side bus you have right now, try to increase your MCH (north bridge) voltage, and your front side bus termination (FSB TERM) voltage. those are both settings in your bios and upping the voltage on them allows them to handle higher frequencies. as does the ICH voltage (south bridge).

Thanks....
any idea in what incriments i should increase them?
and should i increase them at the same intervals.. or?