355.98 WHQL is out
 US Nvidia link All versions found here -- http://www.nvidia.com/download/find.aspx
 
http://www.nvidia.com/download/driverResults.aspx/91812/en-us Win 10 64

 
old links removed
Full release notes PDF 
http://us.download.nvidia.com/Windows/355.98/355.98-win10-win8-win7-winvista-desktop-release-notes.pdf
 
 
Release notes
This new GeForce Game Ready driver ensures you'll have the best possible gaming experience in Killing Floor 2. This driver is also aligned with the new flagship gaming GPU for notebooks, the GeForce GTX 980. In addition, this Game Ready driver also includes updated features and functionality for the GameWorks VR software development kit (SDK).

Game Ready
Best gaming experience for Killing Floor 2

New GeForce GPU
Supports the new GeForce GTX 980 for notebooks, based upon the second-generation Maxwell architecture

GameWorks VR Support
Updated driver support for GameWorks VR SDK, adding notebook support, VR SLI enhancements, and bug fixes. Learn more at developer.nvidia.com/vr.
 
Changes and Fixed Issues in Version 355.98
The following sections list the important changes and the most common issues resolved
in this version. This list is only a subset of the total number of changes made in this driver
version. The NVIDIA bug number is provided for reference.

Windows 10 Fixed Issues
***61557; [355.82] Memory clock reported as 0 MHz if P-state is P0. At times, same report with
P2 P-state. [200135032]
***61557; [353.62, GM204] Thunderbird mail client is choppy when G-Sync windowed mode is
enabled. [1673997]
***61557; [SLI, Stereo] Batman: Arkham Origins crashes when launched from task bar following
an Alt+Tab. [1673119]

Windows 8.1/Windows 8/Windows 7/Windows Vista Fixed Issues
***61557; [355.82] Memory clock reported as 0 MHz if P-state is P0. At times, same report with
P2 P-state. [200135032]
***61557; [Star Wars: Battlefront SLI Profile] Reflection envmaps flicker. [1676284]
***61557; [353.62, GM204] Thunderbird mail client is choppy when G-Sync windowed mode is
enabled. [1673997]
Release 355 Graphics Drivers for Windows, Version 355.98 RN-W35598-01v01 | 12
Open Issues in Version 355.98 WHQL
Open Issues in Version 355.98 WHQL
As with every released driver, version 355.98 WHQL of the Release 355 driver has open
issues and enhancement requests associated with it. This section includes lists of issues
that are either not fixed or not implemented in this version. Some problems listed may
not have been thoroughly investigated and, in fact, may not be NVIDIA issues. Others
may have workaround solutions.
For notebook computers, issues can be system-specific and may not be seen on your
particular notebook.
***61557; “Windows 10 Issues” on page 12
***61557; “Windows 8.1 Issues” on page 12
***61557; “Windows 8 Issues” on page 13
***61557; “Windows 7/Windows Vista Issues” on page 13

Windows 10 Issues
***61557; [VR Direct]: Tearing/corruption may occur when playing VR content while changing
display resolutions on the non-VR display, or after opening several VR applications in
succession.[1687875]
To work around, go to the Microsoft Component Services panel, then stop and then restart the
“Oculus VR Runtime service”.
***61557; [355.82, Surround, 2 × GTX Titan Black] Metro apps are throwing error
0xc00d11cd(80004005) when playing any video. [200135012]
***61557; [355.82, Multi-GPU] No content seen in Windows Media Player. [200134689]
***61557; [SLI, Batman: Arkham Knights] Severe stuttering seen, especially in indoor scenes,
when the game is running at 4K resolution and NVIDIA Gameworks settings are
turned on. [200116722]
***61557; [SLI, Batman: Arkham Knights] Random flickering occurs in the game if SLI is
enabled. [200116717]
***61557; [GM206, SLI, Batman: Arkham Knights] Stuttering occurs and performance drops
after shadow quality settings are toggled. [200116694]
***61557; [347.09, GM204] Blank screen observed on an ASUS Tiled display when system
resumes from shutdown or hibernation with Fast boot option enabled from BIOS.
[1591053]

Windows 8.1 Issues
***61557; [VR Direct]: Tearing/corruption may occur when playing VR content while changing
display resolutions on the non-VR display, or after opening several VR applications in
succession. [1687875]
Release 355 Graphics Drivers for Windows, Version 355.98 RN-W35598-01v01 | 13
Open Issues in Version 355.98 WHQL
To work around, go to the Microsoft Component Services panel, then stop and then restart the
“Oculus VR Runtime service”.
***61557; With a 3DTV connected and the resolution set to an HD3D resolution through the
NVIDIA Control Panel, the display flickers constantly after installing the driver via
INF over driver version 320.49. [1315116]
***61557; [3DVision] While a stereoscopic 3D video with stereoscopic 3D enabled is played, the
monitor refresh rate switches to 60 Hz after changing the resolution using the
Windows control panel. [1314811]

Windows 8 Issues
***61557; [VR Direct]: Tearing/corruption may occur when playing VR content while changing
display resolutions on the non-VR display, or after opening several VR applications in
succession. [1687875]
To work around, go to the Microsoft Component Services panel, then stop and then restart the
“Oculus VR Runtime service”.
***61557; [Optimus, Notebook] After installing the driver, the Device Manager includes an entry
for the NVIDIA Virtual Audio Device but the entry has a yellow bang.
The NVIDIA Virtual Audio Device is not needed nor used on Optimus notebooks, so there is no
effect on your notebook function. To remove the yellow bang, reboot your notebook.
***61557; With a 3DTV connected and the resolution set to an HD3D resolution through the
NVIDIA Control Panel, the display flickers constantly after installing the driver via
INF over driver version 320.49. [1315116]
***61557; [Video, Notebook, Hulu Desktop] When attempting to play videos using Hulu
Desktop, there is audio but no video. [1000017]
***61557; [Video, Notebook, Internet Explorer, YouTube] The NVIDIA Control Panel video
color settings have no effect on YouTube flash video playback within Internet Explorer
10. [999485]
***61557; [SLI, GeForce 500 series, DirectX 11, Dragon Age II] Shadows flicker in the cutscene
when SLI is enabled. [849235]

Windows 7/Windows Vista Issues
***61557; [VR Direct]: Tearing/corruption may occur when playing VR content while changing
display resolutions on the non-VR display, or after opening several VR applications in
succession. [1687875]
To work around, go to the Microsoft Component Services panel, then stop and then restart the
“Oculus VR Runtime service”.
***61557; [3DVision] While a stereoscopic 3D video with stereoscopic 3D enabled is played, the
monitor refresh rate switches to 60 Hz after changing the resolution using the
Windows control panel. [1314811]
Release 355 Graphics Drivers for Windows, Version 355.98 RN-W35598-01v01 | 14
Open Issues in Version 355.98 WHQL
***61557; [GeForce 500 series, Need for Speed: The Run] During the race the sun flickers and
there are bright blips and black patches. [909577]
***61557; [SLI, Company of Heroes: Tales of Valor] With SLI enabled, there is heavy flickering
in the game after switching from windowed mode to full-screen mode. [892264]
***61557; NVS 4200M, Optimus, F1 2011] The game hangs while selecting Quit To Main Menu
during gameplay. [879537]
***61557; [SLI, GeForce 500 series, DirectX 11, Dragon Age II] Shadows flicker in the cutscene
when SLI is enabled. [849235]
***61557; [GeForce 400 series, Total War: Shogun 2] The sun and surrounding area within the
game flicker. [807036]

Nice score, BioHazardSperm. I've been looking for new drivers all week. I'll have to give these a shot later this morning. I reflashed my stock BIOS to my video boards since it was crashing Fallout 3 with voltages being too low so I guess 1600 MHz clock speeds are out of the question for now. Time to so some benchmarking at 1500 MHz and see what kind of scores I get.

Has the overclocking issues been fixed with these drivers? I am downloading it and going to see myself, but was wondering if any of you have tested it. The only stable driver I have found out thanks to Sajin is 353.62

NVM

Sajin
Good news for me & others running the X99 chipset with 4-way sli Titan X. From nvidia customer support...
 
Hi Jeremy,

Our lab is finally able to replicate the failure using the ASUS Rampage V Extreme MB, which is also based on X99 chipset. The faulting application/module name and exception code were the same, so I believe we've replicated the same failure. Bug has been escalated to our development team to assign resource to debug this failure.

Best regards,
Ray
 
NOTE: This is in regards to the error I posted above when running heaven 4.0 in 4-way sli.

Nice

cdc-951

Sajin
Good news for me & others running the X99 chipset with 4-way sli Titan X. From nvidia customer support...
 
Hi Jeremy,

Our lab is finally able to replicate the failure using the ASUS Rampage V Extreme MB, which is also based on X99 chipset. The faulting application/module name and exception code were the same, so I believe we've replicated the same failure. Bug has been escalated to our development team to assign resource to debug this failure.

Best regards,
Ray
 
NOTE: This is in regards to the error I posted above when running heaven 4.0 in 4-way sli.

Nice

Yep, nice indeed. I reported the issue to them on the 13th of august and have been giving them all the info they requested from me up until this point. Glad they were able to reproduce it in their lab at nvidia. 

I really want to start a twitter hash tag @nvidia FIX YOUR DRIVERS!  I am sick to death of worrying if my system is going to crash while playing STO or Minecraft.  And that damnable Error Code 8 (OpenGL detected problem with display driver) bug is really getting old.  And it was old two years ago!  Why is it that Nvidia WON'T FIX THEIR DRIVERS?
 
NVidia FIX YOUR DRIVERS!!!!!!

xorbe
This 355.98 driver gives TDRs while playing TF2.  I had to revert to 355.82 driver.  Win 8.1 x64, Titan X (no oc), 4790K, Hero VII, 32GB ram, 144Hz g-sync, etc.  Titan X + Maxwell driver has never been as stable as my old og Titan + Kepler driver.  And I tried 2 different Titan X cards, rams, cpus, psus, underclocking+overvolting, you name it I tried it.  The root cause is Maxwell vs Kepler, whether hw or sw driver I don't know.

Pretty much dark times are ahead with both NVidia and AMD drivers... because of the launch of Windows 10. The devs for the drivers on both companies are trying to get it together with all the other versions of windows, fixing bugs, teaking the code.The hard part is that they have to be able to recreate the situation in their lab to see what issues need  to be  fixed with the bugs in code of the driver. Driver 355.98 is giving me crashes such as "this game has stopped responding" etc etc..... crashed in titan fall so far, BF4(sooo many times with this driver), star citizen, Killing floor 2 and GTA v.
 
The NVidia GeForce forums are full of people having issues and we can only wait for Nvidia to fix these issues.
 
Also It has crashed on stock on my gpu. I have ran DDU, Prime95 my cpu for 24 hours, memtest to test my ram stability, and my temps are fine. No crashes and all is stable on my system.... Everything after 350 on drivers has been wonky. If I roll back to something under 350.xx for my 780 ti on the side. Then it works perfectly fine, like I get 0 issues.  

Fallout 3 only stopped responding once using these with Windows 7 and GTX-980 in SLI. The biggest difference I have seen is that now BF4 hits my voltage limit where it didn't do that before with older drivers. I guess that's a performance improvement since it requires more voltage, isn't it?

I went shooting my mouth off and then I got 3 app crashes in Fallout 3 yesterday. Probably not drivers fault or is it?

If I enabled sli, every game eventually crashes although it runs absolutely fantastic until the crash. I usually get the "Mad Max has experienced an issue and closed"