trepoo

I haven't seen a post about this yet in this thread, sorry if it was already posted though.

Core clock doesn't seem to downclock anymore using only one monitor. It will downclock when the monitor is turned off though. So right now, using only one monitor, i get idle temperatures of 80C with core clock at 405mhz while i was getting ~48C at 51mhz with 258.** drivers.

Anybody else noticed it ?

I know it's beta but just wondering if i'm the only one with this problem.

Regards,

trepoo

Yes - me too!
No downclock below 405 - 0% GPU Load - both Cards
Also BsoD after 2 Minutes BC2 - with Vision 3D on - Mafia 2 runs fine(no 3D Vision tested, because I only play 3D Shoter and Racer with 3D Vision on)
I´m back on 259.32

Kamarad

Rat-Boy

jackvancouver

The fan fell back to 40% while I was gaming and STAYED THERE... Temps rose to 103C!!! Immediately exited the game so that I don't fry the card.

Now I can't game until WHQL comes out... It's 196.75 all over again.

Yes you can, if you make a own fan profile at Afterburner, than it works great.

Yea, they also have fan controls in the new Precision which I really like.

Are you all saying I need to upgrade Precision? Fine. Peer pressure wins again...

If anything, I just make a single plot fixed on 86% so that it's that fan speed on all but the hottest temperatures.

No one else is experiencing sudden drops of fan speed back to auto with these drivers? I must be the only one in the world...

nvidia are using a lower quality form of TrMSAA in Release 256/260 >.>

noticed it after loading up SM64 with 32xS (the SS component boosts TrMSAA) to find jaggies all over the fences.

squall-leonhart

nvidia are using a lower quality form of TrMSAA in Release 256/260 >.>

noticed it after loading up SM64 with 32xS (the SS component boosts TrMSAA) to find jaggies all over the fences.

i was under the impression that TRMA has always sucked since it doesn't work inside the textures. i guess nvidia wants higher performance for their gpus. 

I was disappointed with the drivers.. i had a freeze when playing bfbc 2. I think i highly agree with everyone heartly that we need to wait for the WHQL version. I was so disappointed cuz i liked it and how it sweeps the drivers for you and most of all i saw much fps increase. Hopefully they can fix out the kinks. I had to revert back to my other drivers. I have a question though.. i took pictures to make sure everything is installed and i am wondering why physx doesn't show checked on this list? Can someone tell me if i need to reinstall the drivers or?


You can click on the picture and it takes you straight to imageshack and double click it to get a bigger view.
Uploaded with ImageShack.us

I tried the clean install option but that did not work very well.When my pc rebooted nvidia controll panel would not open.I finally uninstalled the drivers and dug the left over pieces out of my registry then installed using the custom option with just the drivers and physics.All is working well now.

If you need to drop back to a previous version do a system restore.  That's what I have always done and had to do with this beta. Works great and is quick. No issues after the system restore, again.

carrera997

If you need to drop back to a previous version do a system restore.  That's what I have always done and had to do with this beta. Works great and is quick. No issues after the system restore, again.

Sorry, but thats absurd and potentially system ruining advice. System restore was not meant for trivial things like driver downgrades.

Well that sucked... I reinstalled 258.96 and had issues! First I started Crysis after I reinstalled the driver and the same thing happened. It froze with little white tiles on the screen. So I downclocked my GPU to stock settings but when I would press the reset button to reset my clocks I got the BSOD. So I uninstalled again only this time I deleted all nVidia files and uninstalled PhysX from remove programs because when I would start GPU-Z the little PhysX check box wasn't checked.

I thought that was odd and looked at my PhysX software in programs and it was dated from a few days ago when I installed 260.63. So I removed all that I could find with nVidia display and PhysX then ran driver sweeper in safe mode and cleaned my registry with CCleaner and rebooted and installed 258.96.

Checked in my programs and PhysX was then dated for today and GPU-Z was also correct with the PhysX box checked this time. Played Crysis with no issues and Batman Arkham Asylum for a little while and good to go.

So now I'm wondering if my overclocks weren't stable causing the white tile/game freeze or if all along it was 260.63. When overclocking my 460 I ran OCCT for 30 minutes with NO errors and same with Evga OC Tool stress test.

I guess now that things seem back to normal with 258.96 I can try and overclock my card again and see what happens.

gamernut78

These beta drivers work great for me playing Star Trek Online, i do notice a bit smooth play when rotating camera but i need to do some benchmarks. There used to be flickers with the current released drivers but with the beta it took them away and now my gameplay is good and i don't get those strange flickers from time to time in STO. BUT however..I had a problem i hope you guys can help me. After reinstalling the new drivers (The Beta) and sweeping the left overs.. i rebooted my pc and for some odd reason i cannot prevent this coming back but it seems to give me an error!

DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"

Did the drivers do something to my pc causing this? This never happened to me before. I find it odd.

WHY did this happen? So i restarted and pressed F8 and i booted my second hard drive and it booted. i WONDER what caused that after the driver install? Is my boot not set right? Strange.. advice?

Gamernut, I would bet the farm that your system didn't know where the boot manager was.  I, too, run two harddrives (a boot drive, and a storage drive).  When I first hooked it up, everything ran fine.  Then one day, POW "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER".  After doing some research, I found out that the boot manager still resided on my hdd, not my solid state boot drive.  So all I had to do was go into my bios, set the hdd to boot first (instead of the ssd) and everything was okay.  Not necessarily the driver's fault ^_^

Ooooooook, something veeeeeeeeery hardcore: had DPC Latency Checker now running for about 2h. Result: highest peak was around 7000µs(!!!!), so the problem still exist :-( Went now also back to 258.96, because till now i didn't had to much positives from the 260.xx (automatic fan didn't work well, games don't run smooth, etc.). Now i'm running again the DPC Checker on same websites like before and see, that now highest peak is 457µs :-(
So i hope really, that NV will fix that little (big) problem also, would be cool and nice.

Nice speed test numbers, how did you get them?

squall-leonhart

HRPuffnstuff

Just copy bootmgr to the ssd to solve the problem.

lol, i guess you're a newbie to bootsectors and stuff.

Not really as I've had to do it lots of times to restore a hd or edit boot.ini to restore the proper boot path.

outlawedmatrix

beta drivers working great so far! but does anyone know what the new process "nvxdsync.exe" does and if it needs to be running?

It deals with 3D somehow

"Nvidia User Experience Driver Component"

Filename: %PROGFILES64%\NVIDIA Corporation\Display\NvXDSync.exe MD5: 297165BF59AFB569E00AA55A37C9DAE4 Size: 1176168 Version: 7.17.12.6052 Product: NVIDIA User Experience Driver Component Company: NVIDIA Corporation Operating System: Windows 7 Description: NVIDIA User Experience Driver Component

squall-leonhart

carrera997

If you need to drop back to a previous version do a system restore.  That's what I have always done and had to do with this beta. Works great and is quick. No issues after the system restore, again.

Sorry, but thats absurd and potentially system ruining advice. System restore was not meant for trivial things like driver downgrades.

Grasshopper,
 
Sorry but it works. I have been at this for years and no issues.   Driver restores are not trivial.....