Having a problem with benchmarking my system and am hoping some of you folk can shed some knowledge on it for me.
My system is an Athlon 64 3700 San Diego with 2gig Corsair XMS3200 RAM and a PBY 7900GT on a Jetway 939GT Board.
CPU-Z dump - http://valid.x86-secret.com/show_oc.php?id=143111
Previously I was getting 4620 with 3D Mark 06 before I overclocked the CPU and had the card running at 468 MHz / 661 MHz.
So I overclocked my CPU to 2.5GHz with a FSB of 230MHz and my 3D Mark dropped to 4060???
Did futuremark do something to the tests with the latest revision of 3D Mark? Or can overclocking the FSB slow down your graphics card?
3D Mark compare URL: http://service.futuremark.com/compare?3dm06=698522
Any help would be most appreciated.
Overclocking & Benchmarking Problem
I wouldn't get to hung up on synthetic benchmarks like 3d mark as they mean very little in the real world but i can see your concern. On older AGP systems FSB was tied to the cpu and graphics card bus so if you altered it it affected both - that's why most overclocking boards and FSB locks so you could alter the CPU's FSB independently.
Yours is a newer PCI-E board though and these days changes in FSB don't affect the graphics cards speed so I'm not really sure why your benchies have gone down? Maybe your cpu/ram is showing errors at the increased speeds.
Yours is a newer PCI-E board though and these days changes in FSB don't affect the graphics cards speed so I'm not really sure why your benchies have gone down? Maybe your cpu/ram is showing errors at the increased speeds.
Last edited by fac51 on Mon Dec 04, 2006 12:22 pm, edited 1 time in total.

Wouldn't have thought so as they the latest Nvida drivers, if anything they should give a better result. saying that i don't use them as i can get coolbits working properly with them so I'm still using 91.47.
Have you tried dropping back you cpu to stock speeds and running 3dmark again - at least that would point to it being the drivers if the result is still low.
Have you tried dropping back you cpu to stock speeds and running 3dmark again - at least that would point to it being the drivers if the result is still low.
