PDA

View Full Version : question with AGP OC'ing:p3bf


Stogierogy
01-25-01, 09:17 AM
hey,
i have an asus p3bf and
i cant run my games when i run my p3 700@933. plenty of cooling keeps ME stable, but my games freeze upon startup. all of them. i switched the voltage back and forth to no avail(between 1.65-1.80 and its fine). 256 Generic ram pc133, 100. i have an asus v6600 pure, sgram, no tv out running nvidia drivers. got a golden orb,themal paste. vid card cooler, and 2 case fans.
any ideas???? please help. thanx in advance

Stogie

ps. i normally run at 933 under 95F(cpu) and my V6600 reports its running fine, not too hot either. could it be this card??

Matthew A.
01-25-01, 04:16 PM
Stogierogy (Jan 25, 2001 09:19 a.m.):
hey,
i have an asus p3bf and
i cant run my games when i run my p3 700@933. plenty of cooling keeps ME stable, but my games freeze upon startup. all of them. i switched the voltage back and forth to no avail(between 1.65-1.80 and its fine). 256 Generic ram pc133, 100. i have an asus v6600 pure, sgram, no tv out running nvidia drivers. got a golden orb,themal paste. vid card cooler, and 2 case fans.
any ideas???? please help. thanx in advance

Stogie

ps. i normally run at 933 under 95F(cpu) and my V6600 reports its running fine, not too hot either. could it be this card??Even though I also have an Asus V6600 pure w/sgram, I cannot say if it could or could not be the v.card. However, I know this made a difference with games that did not like to run when o.c. with my computer. Did you install the games when your machine was o.c.. I found many games not running correctly or at all when they were installed when my machine was o.c.. Just a thought.

Stogierogy
01-25-01, 09:31 PM
nope, i wish that was it. its a clean install of ME and i had it running at the default 700 1.65V

****! ****!!!!! ****!

Ericsson
02-01-01, 06:28 PM
i don't think installing programs while the cpu is overclocked would cause any problems...unless the cpu is unstable at that speed...but then again, if it is unstable, you'd crash upon installation.

not all vid cards overclock the same...how 'bout raising the I/O voltage to 3.5V or higher? i run all my vid cards at that speed, specially when i'm running my BX at 133 and higher...actually i never put it below 3.5 anymore...heheheehehhe

try it...it could help. btw...i also tried a V6600...i stopped at BX133...no BX150 or higher. if all else fails, reduce the AGP aperture size to 64MB, switch to AGP1X. that could help.

Daniel ~
02-01-01, 07:09 PM
Can't help directly, But to add to your list of clues:
My 1st. P3B-F is set to V-core 195. my FSB is at 140 (800E)
No problems with my Gladiac in UT or Q-3. My other setup is the same but for My Asus Pure and The fact that I have real trouble in games at 124 FSB and above. I always though it was a difference in CPU chips, maybe not. Good luck!

Stogierogy
02-01-01, 08:28 PM
Ericsson (Feb 01, 2001 06:28 p.m.):

not all vid cards overclock the same...how 'bout raising the I/O voltage to 3.5V or higher? if all else fails, reduce the AGP aperture size to 64MB, switch to AGP1X. that could help.

how can i change the i/o voltage? in bios? and where would i be able to change to agp 1x rather than the default 2x? ive tried messing with the aperture but it made no difference
Stogie

jmsandrsn
02-01-01, 08:39 PM
These ideas may be longshots but you you may want to consider them. I've run 2 different P3B-F's up to 150 FSB and have not had problems(using G400's and several different GeForce's). I have a feeling it could be your memory... even though it is PC-133. Do you have another stick you could try. Another idea is that if your video card has sidebanding enabled, that could be a problem. I have a V6800 and the original BIOS did not have sidebanding enabled. I upgraded the BIOS and sidebanding seemed to prevent 3D apps from running at all. Good Luck getting this figured out. My guess would be that it's not the video card or motherboard.

Ericsson
02-02-01, 12:11 AM
wait...
256 Generic ram pc133, 100

what's 100? PC100? how 'bout removing it and if it does run...that might be the culprit...

but not being able to play 3d games only means that it's the vid card...try looking around more in the bios...there's gotta be a way to change I/O voltage and the agp setting...otherwise...it's another thing to keep me away from asus boards...they generally lack tweaks and options when compared to other boards in their own class...

Stogierogy
02-02-01, 06:41 AM
yeah, i have pc 100, and pc 133. i tried just running w/ the 133 to no avail. i even tried my friends rage fury maxx last night and it worked for as bit then froze as usual. i gotta look around bios a little more i guess. my next mobo im sure will not be an intel based board. thats for sure.

Stogie

sneakyfart
02-02-01, 07:48 PM
how bout a different approach? what version Direct=X? are your video drivers the latest availible? i had a problem similar to yours with a v-5 i once had...i upgraded DX and Vid Drivers and it fixed it...just a thought

Stogierogy
02-02-01, 11:45 PM
****, i WISH that was the case. i have direct x 8 and im running nvidias 6.31 drivers.(for stability)
whats weird is that if i put my fsb at 124 my cpu gets way too frigin hot...like 125 F but if i go to 133 (933 mghz) it stays cooler like around 93-100F.
i defintely DONT think its the memory considering i dont get protection faults when running windows while oc'd. IMHO its the agp bus, or the BX chipset.......who knows.....
Stogie

vox
02-04-01, 09:31 AM
I had a similar problem with my previous system ( Coppermine on a BX chipset mb, asus v6800 pure, generic pc133 cas3 Ram) with 3d games locking up upon startup but stable on win98se. Tried all kinds of different vid drivers to no avail. ..the fact that it was oc'd had no bearing on the problem - it was still locking up at stock speed.

Initially I thought it was anything from my vid card, then my mb, then the agp ., then the PS ( I was using 235W)..used to drive me crazy. I tested each component - vid card , HD etc on a separate system to isolate the problem. Upon further investigation I found that it would lockup when agp aperture was set at or above 32M. 16M aperture would stop the lockups but at a price in performance.
Turns out it was the system RAM. I changed it and reset the agp aperture back to 64M it has been fine since then zero lockups even at 133 fsb :)

Stogierogy
02-04-01, 10:43 PM
well, i guess im gonna bug my friend for a stick of his pny memory.......too bad its pc100...but its worth a shot to just try that one stick dont you think??
my ram is generic
Thanx

Stogie