I got in on the latest CompUSA deal for the PNY 6800 and it showed up the very next day!
I decided to install it and see what it would do in my current system. My system consists of an AMD Mobile 2600 running at 12.5X200, 2X512 meg Samsung pc3500 ram, Shuttle AN35N-Ultra mobo, Thermal take 480 watt powersupply, 80 gig WD HD, and misc fans and temperature monitors.
First day out of the box stock settings (325-700) and using the 66.93 drivers
3dmark03 8,770
3dmark05 rev1.0 3,339
3dmark05 rev 1.10 3,313
Decent enough scores I guess to start things out.
Second day, I installed Riva tuner to see if I could unlock the extra pipelines; no dice. I have to wait for Rivatuner 15.3 to come out. Anyways, I spent all my time trying to unlock so no benchmarks or clocking done. I changed drivers to the Omega 66.71 drivers so it would be compatible with Riva Tuner.
Third day, I wanted to get a fresh days benchmark to compare everything else to.
First Stock speeds using Omega 66.71 drivers
3dmark03 8,591
3dmark05 2,576
These scores were a considerable drop from my first evenings attempts. I decided since I could not use the Riva Tuner to unlock the card anyway that I would revert to the 66.93 drivers and retest.
Stock speeds 66.93 drivers
3dmark03 8,712
3dmark05 3,240
These drivers definitely scored better than the Omega 66.71 drivers did although the score still wasn't as good as the first night I got it. I decided to give overclocking a try to see what sort of numbers I could get. I fired up Riva Tuner, but could not figure out how to enable overclocking. I decided to download Coolbits instead. Got Coolbits installed and rebooted the machine to get a fresh dektop to start my days benchmarks.
Hit auto-detect for overclocking speed. Came back 332-714, well that didn't seem like much of an increase from 325-700, so I hit auto-detect again. This time it came back with 358-766, which seemed a lot better to me. I hit auto detect a third time and it came out with 394-838 which sounded like a winner. I forgot to hit "take effect on restart" though so when it rebooted it was at stock speeds. Back through auto-detect again. First was 331-712 which was really close to what it detected first run. Second auto-detect was 394-838 again so I decided to try this one again. Hit apply and take effect on restart.
Reboot time. Everything powers up great and I go into Nvidia properties to verify clock speeds. It shows up as 394-838 which is awesome. I decide to check Riva Tuner as well to see what it says. Riva Tuner has the core still at stock 324 and the memory is at 841! Hmmm, well I decide to simply see what it spits out benchmark wise.
Coolbits set to 394-838 using 66.93 drivers
3dmark03 10,178
POW! I wanted a 10k+ card and this got it for me. I noticed something though as I scrolled through the project details, it had the core listed at 324 and the memory at 842. Well that was rather shocking to me. I knew I had the core set to 394, so I went back and checked it. I decided to reboot and see if it would hit again.
Reboot time and I decide to see what I get out of 3dmark05
Coolbits set to 394-838 using 66.93 drivers
3dmark05 3,890
I scrolled through the project details and it showed up with 395-842. I figured that it must have taken the upgraded speeds. Since the first run through 3dmark03 did not show the core overclocked any, I decided to reboot again and run that test.
Coolbits set to 395-839 using 66.93
3dmark03 10,177
I scrolled down the project details and it showed up at 395core and 842memory. Well now the core was registering as overclocked, but the score was vertually identical. Was the first score a valid score with overclocking and the core speed simply didn't register?
Anyways, enough rambling by me. I thought I would toss out some scores and let everyone know my experiences.
Zard
AMD Mobile 2600+ at 12.5X200
Shuttle AN35N-Ultra
PNY 6800 at 395/842
2X512 Samsung PC3500
I decided to install it and see what it would do in my current system. My system consists of an AMD Mobile 2600 running at 12.5X200, 2X512 meg Samsung pc3500 ram, Shuttle AN35N-Ultra mobo, Thermal take 480 watt powersupply, 80 gig WD HD, and misc fans and temperature monitors.
First day out of the box stock settings (325-700) and using the 66.93 drivers
3dmark03 8,770
3dmark05 rev1.0 3,339
3dmark05 rev 1.10 3,313
Decent enough scores I guess to start things out.
Second day, I installed Riva tuner to see if I could unlock the extra pipelines; no dice. I have to wait for Rivatuner 15.3 to come out. Anyways, I spent all my time trying to unlock so no benchmarks or clocking done. I changed drivers to the Omega 66.71 drivers so it would be compatible with Riva Tuner.
Third day, I wanted to get a fresh days benchmark to compare everything else to.
First Stock speeds using Omega 66.71 drivers
3dmark03 8,591
3dmark05 2,576
These scores were a considerable drop from my first evenings attempts. I decided since I could not use the Riva Tuner to unlock the card anyway that I would revert to the 66.93 drivers and retest.
Stock speeds 66.93 drivers
3dmark03 8,712
3dmark05 3,240
These drivers definitely scored better than the Omega 66.71 drivers did although the score still wasn't as good as the first night I got it. I decided to give overclocking a try to see what sort of numbers I could get. I fired up Riva Tuner, but could not figure out how to enable overclocking. I decided to download Coolbits instead. Got Coolbits installed and rebooted the machine to get a fresh dektop to start my days benchmarks.
Hit auto-detect for overclocking speed. Came back 332-714, well that didn't seem like much of an increase from 325-700, so I hit auto-detect again. This time it came back with 358-766, which seemed a lot better to me. I hit auto detect a third time and it came out with 394-838 which sounded like a winner. I forgot to hit "take effect on restart" though so when it rebooted it was at stock speeds. Back through auto-detect again. First was 331-712 which was really close to what it detected first run. Second auto-detect was 394-838 again so I decided to try this one again. Hit apply and take effect on restart.
Reboot time. Everything powers up great and I go into Nvidia properties to verify clock speeds. It shows up as 394-838 which is awesome. I decide to check Riva Tuner as well to see what it says. Riva Tuner has the core still at stock 324 and the memory is at 841! Hmmm, well I decide to simply see what it spits out benchmark wise.
Coolbits set to 394-838 using 66.93 drivers
3dmark03 10,178
POW! I wanted a 10k+ card and this got it for me. I noticed something though as I scrolled through the project details, it had the core listed at 324 and the memory at 842. Well that was rather shocking to me. I knew I had the core set to 394, so I went back and checked it. I decided to reboot and see if it would hit again.
Reboot time and I decide to see what I get out of 3dmark05
Coolbits set to 394-838 using 66.93 drivers
3dmark05 3,890
I scrolled through the project details and it showed up with 395-842. I figured that it must have taken the upgraded speeds. Since the first run through 3dmark03 did not show the core overclocked any, I decided to reboot again and run that test.
Coolbits set to 395-839 using 66.93
3dmark03 10,177
I scrolled down the project details and it showed up at 395core and 842memory. Well now the core was registering as overclocked, but the score was vertually identical. Was the first score a valid score with overclocking and the core speed simply didn't register?
Anyways, enough rambling by me. I thought I would toss out some scores and let everyone know my experiences.
Zard
AMD Mobile 2600+ at 12.5X200
Shuttle AN35N-Ultra
PNY 6800 at 395/842
2X512 Samsung PC3500
