Crappy 3DM03

[Highland3r]

Having huge issues with 3dmark 2003 atm (As Mr K404 knows.. lol) For some reason the score SUCKS. Mananged to "fix" GT1 with a few windows tweaks, but the rest of the score is poor.

Had hoped to be in the 4x k range, based on other peoples clocks and K's 8800GTS results it looks like it should be possible. However stuck around the 38.x k mark which frankly sucks imo.

Few people seem to be having issues with the G80's and 03, anyone got any tips at all? Tried the usual LOD, quality, services tweaks and non seem to have any effect.

http://service.futuremark.com/compare?2k3=5181811 <--- that's the score, GT1's about right but the rest frankly suck!

 

[maverik-sg1]

mmmmmm - 03 was always a funny one, my best scores were always one-offs and not very repeatable, maybe I was just lucky, I recall Gollum trying to get close to my scores, even with higher clocks (CPU and GPU) was left wanting.

iirc my best successes were from a cold boot first thing in the morning and it was never the same after that until the next cold boot from a fully cooled system that had not seen power for several hours.

Mav's tips:

Try assigning the affinity to one core (try both cores indivdually) or even dropping the clocks and increasing PCI-E frequencies - try running the cpu tests too, should give a boost on core2.

Retired but still has a few tricks

 

[K404]

Get yer ass out of retirement! You got a new toy, an EP is slipping these days....

-> How do you bench, Mr Phillips? Do you run directly after a restart (set GPU clocks then GO) or bench a load of things in one boot? I think its true that as RAM and/or cache is used as a boot is on longer, performance drops. When i`m benching for real, I bench one thing, then restart.

 

[stocky]

Good tips, keep them coming...

 

[Highland3r]

Cheers for the tips. I've played with dropping and increasing CPU and GFX clocks, the performance scales as you'd expect!

Bench wise, yup it's into windows, open program set clocks via riva and bench away.

Tried setting affinity and it doesnt work. You don't get any points for the CPU tests in 03, so don't bother running them usually.

<edit>

05 and 06 scores are about bang on, so looks like any tweaks/settings are working ok. Maybe a touch on the low side, but no where near as bad as 03 is. </edit>

 

[maverik-sg1]

Bad driver set?

 

[Highland3r]

Bad driver set?

Latest FM approved. Kenny tested on his "normal" install, they gave him a better score than his old drivers!

 

[maverik-sg1]

Bad install?

 

[Highland3r]

Could be yea. Would expect to see problems in other benches though and they seem to be about right.

 

[maverik-sg1]

Could be yea. Would expect to see problems in other benches though and they seem to be about right.

In my experience - test1 is cpu driven (iirc it's a DX7 test) thereafter its quite 3d orientated, maybe uninstall the drivers with drivercleaner or similar and re-install and see where it takes you.

Maybe it's an issue with the latest DX9 update - remember that 3DM03 is no spring chicken, might be worth considering a rollback, perhaps some of the other scores were using previous patches of 03?

Before we give up and put it in the 'too difficult' folder consider these:

Try different chipset drivers/Mobo BIOS?

Try BIOS flashing your clocks on the GPU?

Tru disabling fastwrites and sideband addressing using Riva.

Setting priority to realtime and running with explorer still open (some 3dmarks benefit from explorer being closed).

Mav

Old but scores still standing

 

[Highland3r]

In my experience - test1 is cpu driven (iirc it's a DX7 test) thereafter its quite 3d orientated, maybe uninstall the drivers with drivercleaner or similar and re-install and see where it takes you.

Maybe it's an issue with the latest DX9 update - remember that 3DM03 is no spring chicken, might be worth considering a rollback, perhaps some of the other scores were using previous patches of 03?

Before we give up and put it in the 'too difficult' folder consider these:

Try different chipset drivers/Mobo BIOS?

Try BIOS flashing your clocks on the GPU?

Tru disabling fastwrites and sideband addressing using Riva.

Setting priority to realtime and running with explorer still open (some 3dmarks benefit from explorer being closed).

Mav

Old but scores still standing

Will give the drivers a shot later, if that doesnt work then re-install.

Will give chipset drivers a go too, and bios if all else fails!

Would like to avoid hard flashing clocks if possible, bit of a wimp when it comes to that sorta thing, even more so with a card costing as much as the GTX lol.

Realtime didnt work, and didnt try f/w sideband (think these might have been disabled though) so will look there too.

Cheers for the tips mav. Still can't help but feel there's something I'm missing somewhere though. Even a totally untweaked system (ie Kenny's) seems to be scoring correctly, maybe its a driver setting wrong or something which is throwing things off!

 

[maverik-sg1]

I set the following for benching in NV Advanced driver settings:

All optimisations on

VSync off

Set for high performance (also try performance)

AA and AF disabled (but also try with them set to app controlled)

Try with multithread tweak on and off (do not leave in auto)

Virtual memory on different drive to that of the OS and is possible the 03 Installation also change priority of system to system cache instead of programs.

Enable CPU cache in registry.

Cheers

Mav

 

[Highland3r]

I set the following for benching in NV Advanced driver settings:

All optimisations on

VSync off

Set for high performance (also try performance)

AA and AF disabled (but also try with them set to app controlled)

Try with multithread tweak on and off (do not leave in auto)

Virtual memory on different drive to that of the OS and is possible the 03 Installation also change priority of system to system cache instead of programs.

Enable CPU cache in registry.

Cheers

Mav

All of those done (bar swapfile on another drive)

Was wondering if the multithreading support was what was killing the performance, need to try with it set to off and see if that helps.