Why Can't I get over 134-137 FSB

[TunaBoo]

No matter what I do, I cannot get over 137 FSb, what am I doing wrong?

System:

Win2k
AXIA 1Ghz@Up to 1.47GHz
2 x 256 MB Crucial DDR
Epoc8k7a
Enermax 350 watt whisper.
Netgearfa311(nice conflicts)
kyro2

No matter WHAT I do, I cannot get over 137, that is so retarded.

I can drop multiplier to 7, and still no luck.
I have my RAM voltage at max, no luck.

I can try either stick fo crucial by itself, no luck. Considering most sticks go to 160 or more, you would think 1 out of 2 would make it to 140 with the LEAST aggressive memory settings, right?

I dont get it. I recently added a promise IDE controller, but I had no luck before this also. I haev the newest bios and tried to run at 166 (So pci was not stressed). Started to work and then got graphical crapage, I guess my Kyro2 didnt like that speed.

But honestly, what is holding me back. This is making me so mad. 137FSB is pretty crapp. A lot of days I can only do 135 normal cas 2.5 without errors.

I know I beed a bigger PSU to OC more, but that shouldnt hold me back. My 12V is around 12.8V and my 5V is around 4.91V. My VCore is at 1.8V


What should I do next? Remove all my PCI cards? Is my HD crappping out? Or is my mobo bunk? ARGH


I posted this on the |h|ard, and someone said it sounds like a bunk motherboard because his died after acting like this. I have had board over a month, doesn't feel dead.

 

[LuNoTiCK]

Maybe you can try it without all your pci cards just to see if one of the pci cards are holding you back. Than you can also try the ram one stick at a time, maybe one is holding you back. Raise the i/o voltage also.

 

[TunaBoo]

<< Maybe you can try it without all your pci cards just to see if one of the pci cards are holding you back. Than you can also try the ram one stick at a time, maybe one is holding you back. Raise the i/o voltage also. >>



I tried 1 ram at a time. I also tried an old skool rage128 pro graphics card.

Where do I raise my i/o voltage?

I will try PCI card thing tonight.

 

[Kill_Phil]

toasty or just a lemon of a motherboard would make sence

 

[TunaBoo]

^

 

[RedShirt]

Quote from you:

&quot;boot up in dos.

Type format c: /q \y

Works wonders&quot;

 

[TunaBoo]

<< Quote from you:

&quot;boot up in dos.

Type format c: /q \y

Works wonders&quot; >>



Hehe

naw, I dont use ME

But for ME users, it will

 

[Insane3D]

One thing to remember with the Epox is that while it implements a 1/5 PCI divisor after 166mhz, I am pretty sure the AGP divisor (1/2) stays the same. So while your memory may work @ 166mhz, you got the graphical garbage because the Kyro can't handle the 83mhz AGP speed. You might want to either try a PCI vid card if you have it, or try to disable AGP Fast Writes and drop it from AGP 4X to 1X/2X and give it another go. I would also try memory timings of 8872222, or even try the default &quot;Normal&quot; settings. Also, while it's known the Netgear card conflicts with the AMD 761 chipset, I don't know if that also might be affecting you FSB overclocking.

 

[Cooltech2k]

If you go straight to the bios on a post what are the temps at at the max you can post?

 

[TunaBoo]

Max temp at max speed I can post is 37C

Tried mem timings.

AGP is on 2X

Fastwrites are off.

*UGH*

But even 137, I SHOULD be able to do that no matter what. Nothing is stressing very much. Lately boards hasnt been botting up right. I know my netgear nic makes a warmboot issue, but it USED to cold boot fine. I think mobo is going bunko.

 

[TunaBoo]

^

 

[JohnBlack007]

Because it wasn't designed to go past 133mhz.

 

[helloedchen]

..ermm maybe ur chip just can't do it?

 

[TunaBoo]

<< ..ermm maybe ur chip just can't do it? >>



Im backing off my multiplier. I back it down to like 1200 MHz when it can go up to 1470 MHz.

 

[primeosu2]

TunaBoo,
I'm also having problems raising my fsb but to over 145 mhz. I have the same motherboard, amount/type of ram, video card, and operating system. I too lowered my multiplier, used least aggressive ram timings, increased ram voltage, etc. Nothing seems to work. I can post higher fsb's (up to 170 is what I tried), although sometimes I would get a BIOS Checksum error. But most of the time my errors would occur when attempting to boot into win2k. I either get an error at the very beginning saying that it can not find the file ntoskrnl.exe, or in the middle of booting I get a BSOD saying hard disk failure. I have a IBM 60GXP hard drive which supposedly doesn't like high fsb's, but if the 1/5 pci divider kicks in at 166 mhz, the hard drive shouldn't be having any problems. I really have no clue what's wrong, but if I'm able to miracously fix it, I'll let you know. You do the same for me!