saer.

Any idea how long it should take until these are WHQL'd ?

There is going to be more beta's probably before there is going to be WHQL
*waits five months*

saer.

Any idea how long it should take until these are WHQL'd ?

Have a look at NV forum, than you know more: Any news on when the successor to 260.63 is going to be WHQL?.

I'm having problems with AA at Battlefield BC2. Is anybody else having the same issue?

squall-leonhart

"so i decided to go back to 258.96 release driver. its been 2hours since install never had a problem. wish nvidia will fix that issue once they release it."

thats not explicitly a driver issue anyway.

since u said its not driver issue what is it then since ive tested both precision and msi afterburner both have issue on fan controller? pls explain otherwise dont say things u cant proved.
i notice most of ur post in this thread is negative why not answer it right or dont say a word instead.
not because u never experience the issue doesnt make it has no problem. lots of guys here already complain already about the issue ur one of the few who never or havent had experience with the issue . doesnt mean its not a driver issue..

squall-leonhart

lots of guys cause their own problems by keeping temp monitoring and fan controlling apps running.

Fan controller is there to help our video card keep it cool. and the temp monitoring is to avoid problem to our system. are you normal?? do u even owned a gaming pc or ur just here to troll...

dmoheban

Guys,

I noticed that my second 480GTX Temp went climbed up to 105 degrees because the fan speed was locked at 44% in Metro2033 with these beta drivers. I used Precision 2.0 to monitor fps and temps and fan speeds. Every thing is back to normal after a complete driver uninstall and reinstall of the previous 258.96 whql drivers. I used driver cleaner to remove every last trace of these dangerous betas.

Nvidia not cool...

So people stay away from these! Luckily I barely put my gpus under much load. Only gamed for an hour max until I realized. If anyone else with a similar config please verify and spread the word.

Thanks.

same thing happened to me man so i decided to go back to old release driver. btw dont listen to that guy name =squall-leonhart
 he doesnt know what his talking about i dont even know why i wasted my time replying to him.

zer0byte
same thing happened to me man so i decided to go back to old release driver. btw dont listen to that guy name =squall-leonhart
he doesnt know what his talking about i dont even know why i wasted my time replying to him.

While people were blaming 196.75 for the fan speed issue, i was finding the actual cause, which btw happened to be caused by the RmThermalProviderInfo and RmThermalProviderNum reg keys not updating properly, which oh so happens to be the same keys that would cause issues in precision with certain drivers.
 
When my fan speeds invert/revert or fail to ramp up, i don't dump the drivers, i look at the applications running. in 100% of cases i have had conflicting applications running, like gpu-z and everest at the same time.
 
Stop trolling, you haven't posted anything valid as to why the driver is the issue, just making assumptions.  I on the other hand, make educated statements through point experiences having to test setups with different configurations all the time trumps your testing a driver for 5 mins, finding the fan kicks down with 4 temp monitoring apps running and reverting because you don't know how to run a clean config.
 

dmoheban

squall-leonhart

you are the troll, and not worth a comment.
the nvd already allows device and fan rules, adding more via third party apps just adds more points of issue that can result in problems occuring.

eleet and precision can screw the fan controlling up when used along side other apps that keep the temp monitored, gpu-z for instance, or everest.

Then is there anyway to monitor gpu temps and fan rpms without 3rd party apps? I personally hadn't created any fan rules with Precision to cause the 2nd gpu fan to stay at 40%. Not that I would want to reinstall the 260.63 to prove a point that it was nvidias' fault or precisions. It doesn't matter. They're beta drivers. Use at your own risk...

Did you clean install the new drivers?, they revert the RMThermal keys under normal upgrade install circumstances which have control over the temperature ramped fan speeds, but in multigpu setups it can update them incorrectly.
 
if ever you get a fan or temperature issue, search for and delete RmThermalProviderInfo and RmThermalProviderNum in regedit and reboot. Almost all of the 25x drivers have been extra sensitive to what sensor monitoring apps i have running, the newest speedfan or gpu-z when run next to everest causes the temp sensor to report 0 or screw the fan up even if its manually set and the only fix is to reset the device (hibernate works here).
eleet has been known to cause this regardless of driver or other apps running. precision should be pretty safe to run along side everest atleast.

NVMd...

HeavyHemi
You mean the debug info I provided to Unwinder before you even knew there was an issue? LOL

 
You never reported the RMThermal keys for 196.75 :P, you reported them for a slightly older kit, one of the 195 kits wasn't it, heck probably older, like 192 or something?, but i found the same keys that you found effected precisions temp monitoring also effects the automatic fan controlling on 196.75.
 
I purposely installed a "bugged" driver to figure it out lol. got the same fan speed locked at 40% issue, then clean installed to find it didn't have the issue.
 
went back to the previous kit, and upgrade installed again to reproduce it(which i did) then went through nvidia reg entries to find the culprit.  Tbh, i probably just should've deleted those keys in the first place, but i wanted to be entirely sure.

you obviously aren't using the latest then. the beta adds nvidia sensor support and logs continuous smbus collisions when using it alongside another monitoring app.

smbus collisions happen alot, but its only graphic cards that seem to suffer fan controller and probe collisions that cause function issues.

I experienced a slight case of it in SC2 the other day, but seeing as I'm not convinced that game engine is 100% yet I shrugged it off as a one time occurrence.  I'll be keeping an eye on it to see if it happens again, and if necessary, rollback and re-test.  Beyond that I have no complaints with the beta driver to this point.

I guess we will have to just wait for the full version for the time being..

squall-leonhart

SeaShells

I'm a bit of a newb to this so... Anyone know of a list of monitoring apps that should not be run concurrently?  Some that are obviously monitoring the same things seem clear, but there is also overlap with some apps that monitor different things- for instance, RealTemp also indicates GPU temp, both OC Scanner and Precision monitor GPU temp, etc.

Is there a rule of thumb for determining what should/not be run together?

I'm not sure what method gpu-z implemented its sensors with, but it causes fan controller issues when run alongside everest (though is fine for short usage)
Precision and any other RT based apps should work fine alongside everest afaik.

Realtemp however, i have had experience with that locking up computers when run alongside other monitoring apps.

I haven't had any problems with real temp running with anything.......but honestly I LOVE EVGA but all their monitors are glitchy....iv only had these problems with eleet and precision just cause problems for me....whenever i have my computer running I now have MSI Afterburner, realtemp, and gpuz running and havent had any glitches with that combo, plus you can edit voltages simply in afterburner.

eleet has been blamed for fan speed issues alot in numerous threads here