6800 performance problems

[imported_Stormbringer]

I don't know where to start. I've had a 9500 for 2 years, and yesterday upgraded to a eVGA 6800. Uninstalled old drivers, ran Driver Cleaner, installed new drivers, everything seemed fine. Ran a few games, the FPS seemed a little better. Then I ran Aquamark and 3DMark03.

After digging around on a few benchmark sites out there, my results seem FAR lower than they shoud be. Here's my specs:

P4 @ 3.0 GHz
1024 MB Corsair XMS RAM
eVGA 6800
using 66.93 Nvidia drivers

AA is set to off, AF is set to application preference.

CPU:
core speed - 3105 MHz
mulitplier - 18.0
FSB - 172.5 MHz
Bus Speed - 690 MHz

Also, I'm using an Abit IT7-MAX2 motherboard, 4x AGP, 256MB aperture size. I've seen some things about fast write needing to be off, but I can't find that anywhere in my BIOS, so I'm assuming I don't have it.

Ram is Corsair XMS, PC3200. Running at 215MHz, 2.5-3-3-7.

Ran 3DMark03 twice, and got 6200.
Ran Aquamark3 twice, got 33,000.

This seems to be 50% less than the benchmarks I see out there with comparable systems.

Does anyone have the slightest idea where I should start looking to try and fix this? Do you need other stats of my system? Is it just me, or do those numbers seem off to anyone else?

Thanks for any and all information, I'm at a loss as to what might be going on.

 

[MidasKnight]

Update to the Forceware 71.25 drivers. Set AA to " off " set AF to " off " / set Preformance & Quality settings to " High Preformance " make sure V sync it set to " off "

Then run the 3DMark03 / 05 and see what you get.

 

[Machine350]

It may be caused by your motherboard being only 4x AGP. That card is AGP 8x, which does allow for more bandwidth. Also, try turning down you AGP Aperture to like 128, I don't know if it'll make a difference, but you might try it.

 

[imported_Stormbringer]

Okay, changed settings to High Performance, they were set to High Quality. Changed vsync, it was on Application Preference, changed to Off. AA and AF are set to off. Ran it with the same drivers, 66.93, and got 7300 in 3DMark03, 36000 in Aquamark03. Slight improvement, but not where it should be.

Uninstalled the drivers, installed 71.25. Made sure the settings were the same, and this time got 7000 in 3DMark03 (?) and 38000 in Aquamark03. Not a lot of difference, and 3DMark went down for some reason. Probably within tolerance levels, though.

I'm stumped. For comparison, most benchmark sites I see with rigs at least similar to mine are showing 54000 or so on Aquamark03, and 12500 on 3DMark03. That sound about right?

It just seems I'm missing something basic here. I have no idea what.

Thanks for the help, folks. I need it. =)

 

[Regs]

CPU:
core speed - 3105 MHz
mulitplier - 18.0
FSB - 172.5 MHz
Bus Speed - 690 MHz

Your FSB is at 172.5. So why in the 2nd part of your post you stated that your ram is running at 215MHz?

Am I missing something here?

Your FSB should be 800 MHz +.

 

[imported_Stormbringer]

Hmmmm. I don't know. I'm just taking the numbers off of CPU-Z.

It's showing FSB of 172.5, and Bus Speed of 690.0. Under the Memory tab, it's showing a 4:5 FSB : DRAM ratio, and a Frequency of 215.6.

Is there a deeper problem? Or am I just not as technically inclined in regards to memory bus speeds? Which is more than possible. =)

 

[Regs]

Originally posted by: Stormbringer
Hmmmm. I don't know. I'm just taking the numbers off of CPU-Z.

It's showing FSB of 172.5, and Bus Speed of 690.0. Under the Memory tab, it's showing a 4:5 FSB : DRAM ratio, and a Frequency of 215.6.

Is there a deeper problem? Or am I just not as technically inclined in regards to memory bus speeds? Which is more than possible. =)

Are you trying to run a overclock? A 100 MHz overclock is useless with that divider. It's actually worse off! Try a 1/1 divider at stock speeds. 3.0 GHz and benchmark. Did you deliberately set the divider to 4:5?

 

[imported_Stormbringer]

Yes, the CPU is a 2.4 running at 3.1. As far as the divider, I don't think I set it to that, but it's been a long time since I set this machine up. I'll try it at a 1:1 and see what happens.