help...my XP 1900 and crappy OCing

[cloud10ten]

I have just unlocked my AXP 1900 and at 13x (12.5 is what is says after i select 13x) wont go above 133 at all...windows will boot but will lock up when i try and run something like 3dmark...and at the default 12x i can only get it to 140...both of those numbers come up as xp 2000+ ...i have a epox 8kha+ (flashed to newest bios as of end of Nov) , 512 crucial pc2100, and a sparkle 400w...so i dunno if i my chip just sucks or what

[cloud10ten]

oh yeah those setting run stable at +.025v and i tried all the voltage settings up to + .1 and still nothing above 13x133 or 12x140

[Placid]

What are your cpu temps?
What voltage are you using for the memory?

[cloud10ten]

my temp right now is at 38c at load its like at 42c i think and the mem voltage is whatever is defaulted in bios

[Placid]

Try 2.7 for the memory then lower the multiplier to 10 and see if you can run the fsb @ 155mhz.
Then let us know if you can.

[cloud10ten]

nope i couldnt do that either...tried to up my chip V to +.1 too still didnt work

[Placid]

Ok sounds like might be either your memory or another component not liking the fsb as the cpu should do 1.5ghz no problem.

Try using the same fsb and memory voltage but set the memory timings to their slowest settings.

There is also a known problem with the 8KHA+ that when the fsb is set high it won't reboot without pushing the restet button a few times, the beta bios for it is supposed to fix this problem so if you get a no boot at all its probably the board bug but if you lock while the os is loading or past that point then thats what I am talking about above.

If you want to try the new beta bios you can find a link to it here:

http://forums.overclockers.ws/vb/showthread.php?s=&threadid=49558

[cloud10ten]

ok it booted at dram clock 100mhz...but what does that mean then? my ram is not good?

[cloud10ten]

oh yeah i changed the dram but i left the timing at 2.5-3-3

[Placid]

Sorry, I did not mean dram clock 100 I meant set it to 133 but use manual timings and set the cas to 2.5,trdc 3,trd 3.

So you still lock up with these settings?

[cloud10ten]

yep it wont boot with those setting at all...i have to power it down all the way and power it back up for it to work

[Placid]

Its the board bug causing that, try the beta bios.

[cloud10ten]

ok ill see what i can do with that bios...thanks for all the help :)

[Placid]

Ok you need to use 2.7v usually with 512mb of the crucial to get a decent fsb stable.
Goodluck :)

[cloud10ten]

ok ill keep that in mind :)

[cloud10ten]

well i did all that and still nothing...im stumped as to what it is now

[Placid]

Try 150fsb x 10.
I am very surprised you don't even get a boot from it maybe the cpu unlock is not working.
Test that, use wcpuid and 133fsb and set the multiplier to 10 and see if you really get 1333mhz.

If the unlock is good and you can't run 150fsb x 10 then its time to look at your add in cards as possible fsb stoppers.
You will have to remove them and test to find out if one of them is the problem or not.
The most common problem card is the nic.

[cloud10ten]

yeah it comes up as 1333 but when i try 150x10 i get a steady beep from the comp and a black screen

[cloud10ten]

i think im just gonna mess with the bios setting for now with most of my PCi card out cept my scsi one since my HD is on there :)