nVIDIA ForceWare 174.93

Did you get it to work? I must have missed something since it didn't make any difference. I even checked the name of the files but noticed that it was referring to what I assume is the SysWOW64 folder, where the files are still using the old names. The name of the section probably refers to the System32 ones which have the changed name. Doesn't matter that much though. Using driver emulation everything works fine. Just shows what a great piece of software it is.

 

Ok I finally registered:thumbup: Greetings everyone :cheers:

My monitor goes into standby in XP when I enable SLI too. No probs w/Vista. I've tried the reg keys that F_L_C posted with no luck. How do I try enabling SLI w/Nhancer? I see no SLI options in there unless SLI is enabled through the nvidia CP 1st?

 

Welcome and good luck
I prefer avoiding nhancer atm.

 

Just got some time to test these out, nice drivers so far.
I've tried a few games, performance wise no big difference was noticed though, but at least everything is running as it should. I'm on Vista x32 with SP1 btw.

Oh and OC with RivaTuner is working just fine (someone complained about that a few pages back), just ignore the 'this driver is not supported' message as it actually means nothing crucial as it's just a warning.

 

does this driver have the CUDA runtime in it, cuz nvidia alredy released the list of CUDA enabled gpu list?

http://www.nvidia.com/object/cuda_learn_products.html

 

Okay I just installed these and I see that I'm not able to change the scaling. Is there a fix for this or am I going back to the old 169.21s

 

WHY DOES GURU3D ALWAYS SKIP the XP x64 drivers..

Here ya go..
Geforce 174.93 WinXP x64

We XP x64 users are gaming to..

 

I just got a pair of EVGA 9800GTX and figured I give these drivers a try. I have XP and both Vista 32 and 64 bit Home Premium all on there own drives. In Vista I lost around 100 points in 3DMark06, which I could live with if they were stable. But using XP they crash my system when I try to enable SLI and after a restart XP tells me they are incompatible with my video cards. They may have a workaround, but why bother. These Drivers suck.

 

@Pyr0,

I have a HR-03 Plus with a 92mm/70 CFM fan. I have never seen over 65° (Everest Ultimate) even after hours of gameplay, mostly Oblivion, or a couple hours of rthdribl at max settings.

I will check out the DTek unit, but I am somewhat unsure about doing the voltmod.

Thanks for the reply.

 

if your card jumps from 621 up to 648, flashing the bios may help fine tune your clocks too

 

Does anybody know if UT2004 still stutters with these in XP32?

 

these drives crashed my TDU game when enabling SLi.

Back to the 174.74's.

 

and what code for driver 174.93?

what 444d mean? I don't understand could you explain a bit?

btw, thanks for your help!

 

You guys who always have issues with Rivatuner and OC'ing? Why dont you just use Nibitor and edit youre bios so you have the OC all the time? There you can also mod voltage and so on. Much better than be always dependant of Rivatuner or other OC programs to work??? Its pretty risk free if you know what you are doing and not so hard to do either!?

 

thats what i do once i found the most stable overclock on my cards ,i then do as you say with nibitor and its much easier that way.

 

I decided to stick with 174.74 for now... waiting for a newer rivatuner or a new driver build.

 

If you actually read what Unwinder (the creator of RivaTuner) wrote you would see that in Vista 64bit (don't know about XP 64) they have renamed some files which means RivaTuner can't detect any ForceWare at all. This means you can't do anything (without the fixes above), not just the normal "unsupported driver version" which you get with most other driver releases and just like you say doesn't matter much.

As already explained, 0x444D is 17485 in base 10 (the normal base you use every day). You can read more about it here: http://en.wikipedia.org/wiki/Hexadecimal

What the above means is that you tell RivaTuner that it should emulate the supported 174.85 driver, which enables it to communicate with the driver in the same way, more or less. That's why all functions work again. To put it short, you should tell RivaTuner to emulate a supported driver like 174.85, not the unsupported 174.93.

 

Rivatuner 2.08 works fine with the XP/Vista-Drivers of 174.93. Had no problems with it.

Results are very good in 3DMark06 in XP and also with Vista with these drivers, the fastest i ever archieved on my GF8800GTS.

Both Windows versions has a increase of about +70 3DMarks06 Points

XP - Forceware 174.93 - 9166 3DMarks 06
XP - Forceware 169.44 - 9095 3DMarks 06
XP - Forceware 169.21 - 9092 3DMarks 06
XP - Forceware 169.13 - 9097 3DMarks 06
XP - Forceware 169.09 - 9096 3DMarks 06
XP - Forceware 169.04 - 9091 3DMarks 06
Vista - Forceware 174.93 - 8936 3DMarks 06
Vista - Forceware 169.09 - 8865 3DMarks 06
Vista - Forceware 169.04 - 8917 3DMarks 06
Vista - Forceware 169.13 - 8863 3DMarks 06
Vista - Forceware 174.85 - 8891 3DMarks 06

I tell you, performance-wise these drivers are the best in 3DMark06 :banana:.
I always use default settings, no OC or anything like that.
Just some minor standard performance settings in Rivatuner.

 

Hm missed that part, my bad. I thought that it's one of those 'omg RivaTuner shows the driver unsupported message so it doesn't work with this driver' comments. Will try to look more closely next time, thanks for your correction

 

The issue with 174.93 / Rivatuner is Vista x64 ONLY!

As for 3dmark 06, nice jump but no one plays 3dmark 06 online anymore ..:3eyes: