PDA

View Full Version : How come I can't get my ABIT Siluro GF2 to overclock over 100MHz Memory?


ZeroAquaduct
10-21-01, 02:25 PM
I tried to overclock my ABIT Siluro GF2 T400 64MB, but it doesn't allow me to go over 100MHz Memory Clock Frequency. Why is that? I'm using WinXP and the Detonator XP drivers.

I have Coolbits enabled through the registry. When I go to the clock frequency adjustment screen, it'll allow me to go to a maximum or 250MHz for the Core Clock Frequency and 100MHz for the Memory Clock Frequency. I read that other users are able to go 240MHz Core and 230MHz Memory. How do I do that?

Also, sometimes when I run my 3-D games (without having my video card overclocked), I get these beeps coming from my PC. It's not a high pitch beep like what the mobo gives, but it's a low, electronic-like beep. I think it's coming from my video card. Does that mean it's too hot? What's going on?

Monaco
10-21-01, 10:38 PM
Wow that's a weird problem. GF2 cards are either 200core\333DDR mem for GTS cards, or 200\400 for Pro cards I believe. I've seen OC utilities report the memory as 166 or 200,ignoring the DDR, but not 100!! Is that an MX card, or a GTS\Pro type card?

Either way, I know MX cards have a memory clock higher than 100mhz. Try clicking around the end of the memory slider bar, sometimes you can change the slider range.

As for the beeping, I've never seen a vid card with a built in speaker before. Could be the vid card fan dying a slow, squeaky death I guess. I't probably the case speaker just making a weird noise- mine gives off weird beeps when I start getting heat related errors.

Good luck!

Maximus Nickus
10-22-01, 04:16 AM
i had the same problem with coolbits saying my mem was 0mhz!!!! and when oc'ed it was 100mhz!!!
i used nv max and it reported the mem as 360mhz!!!!! when its not ddr its actually 175mhz! weird still cant oc it!!!! it could be my board though....does anyone else have a hrecules 3d prophet 2mx 64mb and oc'ed it? or had same probs?

ZeroAquaduct
10-25-01, 04:05 AM
I tried NVmax and it seems to work. I'm able to overclock higher than 100MHz now. I guess the Coolbits program is messed up.

I e-mailed ABIT tech support about the beeps and the rep said it can't be coming out of the Siluro because it doesn't have speakers. He suggested it might be a heat problem with my PC. Thanks for the reply Monster of Rock. I better go get myself some cooling before it damages my PC.

Monaco
10-25-01, 03:54 PM
Word, glad I could help!

Personally I've never liked the Coolbits hack- it always seems to screw something up. Besides, who likes mucking about in their registry? Not me!!:D NVmax, etc work much better IMHO!

Coolbits also have known problems working with certain nVidia driver sets- especially the newer XP drivers, they don't work with Coolbits at all.

Hope you get the beeping thing straightened out- if it is heat, it must be pretty darn hot to sound an alarm! Maybe throw some more fans in there, or just glue a small one right to the cards heatsink- that should help it! One good thing about it is that it takes quite a while for heat to damage a vidcard- usually it cxrashes before to long. But it WILL destroy your card if you ignore it and keep it OCed- happened to me!!