Today NVIDIA released the first driver from our new Release 265 driver branch. The new driver 266.35 is available for download from our beta download drivers page for NVIDIA Geforce desktop/notebook/ION GPUs. For a brief description of some of the changes in our new 266.35 display driver, please read the article below:

[b]The NVIDIA Control Panel User's Guide for display driver 266.35 is also available and can be downloaded from the URL below:[/b]
http://us.download.nvidia.com/Windows/266.35/266.35_NVIDIA_Control_Panel_Quick_Start_Guide.pdf

You may download the appropriate driver for your NVIDIA GPU by choosing the type and operating system from the links below:

Notes::
Notebooks supporting Hybrid Power technology with Intel chipsets are not supported by this release.
The following Sony VAIO notebooks are supported: Sony VAIO F Series with NVIDIA GeForce 310M, NVIDIA GeForce GT 335M and NVIDIA GeForce GT 425M. Other Sony VAIO notebooks are not supported at this time (please contact Sony for driver support).

Please provide feedback on these drivers here so that I may compile the information and pass it along to our software team. When you reply to this thread with your feedback, please include the following as best you can to help us reproduce the issue you are experiencing.

Step by step instructions if necessary on how to reproduce problem?
How long does it take for the problem to appear?
Does this problem occur with previous drivers (if not, which driver version were you previously using)?
If this is a monitor compatibility issue does it show up with other monitors?

Desktop make and model:
Graphics Cards/Processors used in your Desktop:
Amount of system memory installed:
Operating System:
If the problem only shows on external display(s), please list the monitor make and model used:
Other:

[b]*Note* If no system information is provided, I can not file a bug for your issue so please provide as much detailed information as you can so that our QA team has a better chance of reproducing your problem. Some of the bugs that were filed in the 260.99 thread may still be open so you do not need to file detailed description for these if you already filed it in the previous thread. Thank you for your time. [/b]

If you are reporting that your notebook GPU is not supported by this driver release, please provide the following info:

1) Make and model of notebook
2) NVIDIA GPU model
3) Device ID of GPU. To get the Device ID of your GPU, please do the following:
-Open your Windows Device Manager
-Double-click on the "Display Adapters" icon
-Right-click over the icon for your NVIDIA GPU
-Select "Properties"
-From the Properties window, select the "Details" tab
-From the drop down "Property" box, select "Hardware Ids"
-Copy the first line shown and paste it into your report. In the image shown below, you would paste:

Today NVIDIA released the first driver from our new Release 265 driver branch. The new driver 266.35 is available for download from our beta download drivers page for NVIDIA Geforce desktop/notebook/ION GPUs. For a brief description of some of the changes in our new 266.35 display driver, please read the article below:

Notebooks supporting Hybrid Power technology with Intel chipsets are not supported by this release.

The following Sony VAIO notebooks are supported: Sony VAIO F Series with NVIDIA GeForce 310M, NVIDIA GeForce GT 335M and NVIDIA GeForce GT 425M. Other Sony VAIO notebooks are not supported at this time (please contact Sony for driver support).

Please provide feedback on these drivers here so that I may compile the information and pass it along to our software team. When you reply to this thread with your feedback, please include the following as best you can to help us reproduce the issue you are experiencing.

Step by step instructions if necessary on how to reproduce problem?

How long does it take for the problem to appear?

Does this problem occur with previous drivers (if not, which driver version were you previously using)?

If this is a monitor compatibility issue does it show up with other monitors?

Desktop make and model:

Graphics Cards/Processors used in your Desktop:

Amount of system memory installed:

Operating System:

If the problem only shows on external display(s), please list the monitor make and model used:

Other:

*Note* If no system information is provided, I can not file a bug for your issue so please provide as much detailed information as you can so that our QA team has a better chance of reproducing your problem. Some of the bugs that were filed in the 260.99 thread may still be open so you do not need to file detailed description for these if you already filed it in the previous thread. Thank you for your time.

If you are reporting that your notebook GPU is not supported by this driver release, please provide the following info:

1) Make and model of notebook

2) NVIDIA GPU model

3) Device ID of GPU. To get the Device ID of your GPU, please do the following:

-Open your Windows Device Manager

-Double-click on the "Display Adapters" icon

-Right-click over the icon for your NVIDIA GPU

-Select "Properties"

-From the Properties window, select the "Details" tab

-From the drop down "Property" box, select "Hardware Ids"

-Copy the first line shown and paste it into your report. In the image shown below, you would paste:

PCI\VEN_10DE&DEV_0A2B&SUBSYS_9072104D&REV_A2

Attachments

Please send me a PM if I fail to keep up on replying in any specific thread or leave a driver feedback: Driver Feedback

hello my fellow nvidia users, i have been following the forums for quite some time and have finally decided to join. Anywho I just downloaded the beta drivers 266.35 and have been playing various games. Aliens vs Predator has been running alot better from the previous drivers that i have been testing. Flatout Ultimate Carnage runs pretty good but still needs a better SLi profile.

The only hitch that I have run into is Battlefield Bad Company 2. I started a match and the game plays for the most part flawless except for when I pressed the J key to start to chat to other players the game froze up and went right to a white screen in which I had to restart.
Settings for Bad Company 2 are:

1920x1080
HIGH settings
at the time of the incident 8x CSAA Anti-Aliasing (havent tried any other settings yet.) I have read that other people were having issues with the AA in BC2.

hello my fellow nvidia users, i have been following the forums for quite some time and have finally decided to join. Anywho I just downloaded the beta drivers 266.35 and have been playing various games. Aliens vs Predator has been running alot better from the previous drivers that i have been testing. Flatout Ultimate Carnage runs pretty good but still needs a better SLi profile.

The only hitch that I have run into is Battlefield Bad Company 2. I started a match and the game plays for the most part flawless except for when I pressed the J key to start to chat to other players the game froze up and went right to a white screen in which I had to restart.

Settings for Bad Company 2 are:

1920x1080

HIGH settings

at the time of the incident 8x CSAA Anti-Aliasing (havent tried any other settings yet.) I have read that other people were having issues with the AA in BC2.

Showing Ambient Occlusion "not supported in this application" when viewing in program settings despite release notes saying it is supported.

[i]"Visual Quality
Adds ambient occlusion support for one of the most popular games of the year: Starcraft II: Wings of Liberty. Ambient occlusion improves the quality of lighting, shadows, and depth perception in many parts of the game. Learn more on GeForce.com."[/i]

Showing Ambient Occlusion "not supported in this application" when viewing in program settings despite release notes saying it is supported.

"Visual Quality

Adds ambient occlusion support for one of the most popular games of the year: Starcraft II: Wings of Liberty. Ambient occlusion improves the quality of lighting, shadows, and depth perception in many parts of the game. Learn more on GeForce.com."

All in bootcamped Windows 7 on a 2010 Macbook Pro (all happening with driver versions 197, 198, 260 and now 265):

1) Constantly high DPC latencies in *all* 2D and 3D modes. Worse than the 9600M before (which only showed DPC misbehavior in 2D). Same happens for another user on 330M based Sony Vaio.

2) Scaling for external displays still does not work. Even though the scaling option is now saved (aka does not revert back to display scaling) there is no scaling happening, but the output is send to the display unscaled. Only the internal display of the laptop is scaled (has no hardware scaling anyway).

3) When an external display is used in *Single*-display mode the GPU does [u]not decrease clock-rates down to 2D mode ever[/u]. The lowest clock-rate is 405 MHz then. When the internal display is used (even with an external display connected) clock-rates function properly (105 MHz lowest).

To underline again, this happens in [u]Single[/u]-display mode.

Besides, the statement that "GPU Runs at a High Performance Level (full clock speeds) in Multi-display Modes" "...is a hardware limitation and not a software bug." is a plain lie or at least misinformation! It works properly with the very same hardware on OS X (tested with the 9600M GT on a 2009 Macbook Pro and a Watt meter), so it's a software/driver limitation, not a hardware limitation.

All in bootcamped Windows 7 on a 2010 Macbook Pro (all happening with driver versions 197, 198, 260 and now 265):

1) Constantly high DPC latencies in *all* 2D and 3D modes. Worse than the 9600M before (which only showed DPC misbehavior in 2D). Same happens for another user on 330M based Sony Vaio.

2) Scaling for external displays still does not work. Even though the scaling option is now saved (aka does not revert back to display scaling) there is no scaling happening, but the output is send to the display unscaled. Only the internal display of the laptop is scaled (has no hardware scaling anyway).

3) When an external display is used in *Single*-display mode the GPU does not decrease clock-rates down to 2D mode ever. The lowest clock-rate is 405 MHz then. When the internal display is used (even with an external display connected) clock-rates function properly (105 MHz lowest).

To underline again, this happens in Single-display mode.

Besides, the statement that "GPU Runs at a High Performance Level (full clock speeds) in Multi-display Modes" "...is a hardware limitation and not a software bug." is a plain lie or at least misinformation! It works properly with the very same hardware on OS X (tested with the 9600M GT on a 2009 Macbook Pro and a Watt meter), so it's a software/driver limitation, not a hardware limitation.

PCI\VEN_10DE&DEV_0A29&SUBSYS_00C8106B&REV_A2

Full system is listed in my signature.

Attachments

All of the below issues were solved by changing to an ATI based solution:

Hello Everyone! Well....i installed the new 266.35 beta and my GPU temperature are more elevated now. With the 260.99, the temp are always variate in 49Â°C - 55Â°C (Using the GPU-Z program). And now with 266.35 Beta are 55Â°C - 60Â°C.

This temperature is good and normal for my GPU? Im using a 9500GT here!

When will come the WHQL version? You guys will do something more after launch the WHQL version?

Hello Everyone! Well....i installed the new 266.35 beta and my GPU temperature are more elevated now. With the 260.99, the temp are always variate in 49Â°C - 55Â°C (Using the GPU-Z program). And now with 266.35 Beta are 55Â°C - 60Â°C.

This temperature is good and normal for my GPU? Im using a 9500GT here!

When will come the WHQL version? You guys will do something more after launch the WHQL version?

Tv out not working connected with DVI-D Windows 7 64, in Windows xp works fine.
Doesnt down 2d mode if using 120hz refresh rate on samsung 2233rz 110hz no prob. Last driver that dropped to 2d clocks was 258.96.
Tv: Samsung PS-42V4S EDTV
Card: Evga gtx 460
Connection: Both DVI-D

Experienced "display recovery"/nvlddmkm error with this set of drivers as well @ bc2 ... after about 10 minutes the screen goes white and event manager tells me something about "nv driver has to be recovered ... " NEVER had such problems with 260.99!

Experienced "display recovery"/nvlddmkm error with this set of drivers as well @ bc2 ... after about 10 minutes the screen goes white and event manager tells me something about "nv driver has to be recovered ... " NEVER had such problems with 260.99!