NVIDIA ForceWare 169.04 Beta


Recommended Posts

NVIDIA has new beta drivers up for download!

Release highlights:

* Beta driver for GeForce FX, 6, 7, and 8 series GPUs including GeForce 8800 GT.

* Recommended driver for Crysis single player game demo and TimeShift.

* Several game and application compatibility fixes. Please read the release notes for more information on product support, features, driver fixes and known compatibility issues.

* If you would like to be notified of upcoming drivers, please subscribe to the newsletter.

* Please read the driver installation hints before you install this driver.

Download for Windows Vista

English: 32-bit | 64-bit

International: 32-bit | 64-bit

Download for Windows XP

English: 32-bit | 64-bit

International: 32-bit | 64-bit

Link to comment
https://www.neowin.net/forum/topic/597548-nvidia-forceware-16904-beta/
Share on other sites

Hopefully this will solve the 64-bit Crysis demo freeze issue I'm having. About five seconds after Crysis starts in full screen, it becomes unresponsive - I have to go into Task Manager and kill it. 32-bit works fine.

I've heard that there supposedly is a 20% performance benefit if you run it in 64-bit mode vs. 32-bit, and am anxious to test it out.

again? That's a lot of beta releases in a short period. Will have to install when I get home.

No kidding! They released the 169.01 driver on Friday, the 169.02 driver on Monday, and the 169.04 driver today.

Nate,

There are several reasons why the 64bit may not work.

The first was the leaked pre-order version of the SP Demo. It had 64 bit executable issues.

It is recommended to use the rereleased public version.

The second was the 169.01 drivers. They apparently have done more harm than good, and their main focus was to help optimize some GPU hardware that had fallen by the wayside, which was a concern given that the SP demo is considerably old; rather than particularly increase performance, which, is a bit of a moot point, given the age of the demo. They also do not work with RivaTuner. And I suspect these new ones do not as well, as even the 2.06 version of Riva only covers the 163.7X series and older.

The third was some users, especially those using Nhancer, had multiple profiles in their Nvidia control panel or Nhancer database. Also, if you do not have duplicate or multiple profiles, you should at least remove the executable that the profile points to, and replace it with the newly installed 64 bit one.

There is another quirky suggestion that seem to have 'done the trick for some. That was to set GPU to default clocks, run the game in 32bit mode, set your visuals, save and exit, reboot, then run in 64bit. If it works, then modify clock settings.

What we know, is that the public release of the demo, using 163.69 Vista 64 drivers is confirmed as working, without flaws.

General FPS reports (1280X1024, no AA, Very High (a.k.a. DX10)) settings are:

high teens - high twenties for GTX users and mid teens-mid twenties for GTS users (roughly speaking).

The 64 bit will help processing, but it won't necessarily return better frame rates.

Edited by hopeful

Vsync and AF are non existent in the demo. And indeed it might be an issue, which is why checking the nvidia/nhancer profiles is a good idea, to ensure everything is disabled until you secure the stability first.

I'll add that to the notes, thank you.

And I'm not surprised the drivers give less performance with UT3, it was already performing great. These are just shoddy beta drivers, that have no need.

If you want drivers for Crysis, just wait a few days till after it's gone retail.

Vsync and AF are non existent in the demo. And indeed it might be an issue, which is why checking the nvidia/nhancer profiles is a good idea, to ensure everything is disabled until you secure the stability first.

I'll add that to the notes, thank you.

And I'm not surprised the drivers give less performance with UT3, it was already performing great. These are just shoddy beta drivers, that have no need.

If you want drivers for Crysis, just wait a few days till after it's gone retail.

This fix is for those who are having the 5 second fullscreen freeze, or that are unable to progress past the first ad screen in fullscreen mode.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop data 'Google Chrome' is downloading for Chrome without you agreeing to it. Fun right? Sure, the way Microsoft is pushing 'Microsoft Edge' on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!