Subject: General Tech | March 29, 2019 - 06:55 AM | Jim Tanous
Tagged: ryzen, podcast, Optane, microphone, hyperx, graphics drivers, corsair, Cinebench, asus, anthem
PC Perspective Podcast #538 - 3/27/2019
Join us this week as we review a new quiet case from Corsair, a high-end gaming headset from ASUS, the first standalone microphone from HyperX, and more!
Subscribe to the PC Perspective Podcast
Check out previous podcast episodes: http://pcper.com/podcast
00:05 - Intro
02:04 - Review: Corsair Carbide 678C Case
08:43 - Review: ASUS ROG Delta Gaming Headset
16:25 - Review: HyperX QuadCast USB Microphone
22:51 - News: AMD Ryzen 2000 Price Drops
27:43 - News: Cinebench R20 Standalone Release
30:41 - News: Anthem DLSS & GeForce Highlights Update
33:58 - News: GeForce Game Ready Drivers 419.67
38:01 - News: Intel vs. Micron
43:10 - Picks of the Week
53:04 - Outro
Subject: Graphics Cards | March 25, 2019 - 02:14 PM | Scott Michaud
Tagged: nvidia, graphics drivers, geforce
Five days after they released the Creator Ready 419.67 drivers, NVIDIA has published their Game Ready equivalent, which is also version 419.67. It can be downloaded from GeForce Experience, or you can get it from their website (alongside the release notes).
In terms of features: this is another entry in the R418 branch. Often, but not always, major new features are merged in at the start, and subsequent releases add game-specific optimizations, bug fixes, and so forth. This is one of those drivers. It adds two new G-SYNC compatible monitors, the ASUS VG278QR and the ASUS VG258, as well as “Game Ready” tweaks for Battlefield V: Firestorm, Anthem, Shadow of the Tomb Raider, and Sekiro: Shadows Die Twice.
Also, if you have multiple GSYNC compatible displays, NVIDIA now also supports using them in Surround on Turing GPUs.
There are also several bug fixes, although most of them are relatively specific. They do have fixes for DaVinci Resolve and multiple Adobe applications, which I believe were first introduced in the Creator Ready driver. If you’re concerned about “missing out” on fixes, it looks like they’re intending to keep Game Ready up-to-date with Creator Ready, just with less QA on professional applications and timed to game releases (versus professional software releases).
Subject: Graphics Cards | March 20, 2019 - 04:03 PM | Scott Michaud
Tagged: nvidia, graphics drivers
At the ongoing Game Developers Conference, GDC 2019, NVIDIA has announced a “Creator Ready Driver” program. This branch targets the users that sit between the GeForce and Quadro line, who use GeForce cards for professional applications – such as game developers.
Both Game Ready Drivers and the Creator Ready Drivers will support all games and creative applications. The difference is that Creator Ready drivers will be released according to the release schedule of popular creative tools, and they will receive more strict testing with creative applications.
The first release, Creator Reader Drivers 419.67, lists a 13% performance increase with the Blender Cycles renderer, and an 8% to 9% increase for CINEMA 4D, Premiere Pro CC, and Photoshop CC, all relative to the 415-branch GeForce drivers.
You can choose between either branch using the GeForce Experience interface.
Image Credit: NVIDIA
As for supported products? The Creator Ready Drivers are available for Pascal-, Volta-, and Turing-based GeForce and TITAN GPUs. “All modern Quadro” GPUs are also supported on the Creator Ready branch.
Personally, my brain immediately thinks “a more-steady driver schedule and some creative application performance enhancements at the expense of a little performance near the launch of major video games”. I could be wrong, but that’s what I think when I read this news.
Subject: Graphics Cards | February 28, 2019 - 11:25 PM | Scott Michaud
Tagged: nvidia, graphics drivers, security
Normally, when we discuss graphics drivers, there are a subset of users that like to stay on old versions. Some have older hardware and they believe that they will get limited benefits going forward. Others encounter a bug with a certain version and will refuse to update until it is patched.
In this case – you probably want to update regardless.
NVIDIA has found eight security vulnerabilities in their drivers, which have been corrected in their latest versions. One of them also affects Linux... more on that later.
On Windows, there are five supported branches:
- Users of R418 for GeForce, Quadro, and NVS should install 419.17.
- Users of R418 for Tesla should install 418.96.
- Users of R400 for Quadro and NVS should install 412.29.
- Users of R400 for Tesla should install 412.29.
- Users of R390 for Quadro and NVS should install 392.37.
Basically, you should install 419.17 unless you are using professional hardware.
One issue is being likened to Meltdown and Spectre although it is not quite the same. In those cases, the exploit took advantage of hardware optimizations leak system memory. In the case of CVE-2018-6260, however, the attack uses NVIDIA’s performance counters to potentially leak graphics memory. The difference is that GPU performance counters are a developer tool, used by applications like NVIDIA Nsight, to provide diagnostics. Further, beyond targeting a developer tool that can be disabled, this attack also requires local access to the device.
Linux users are also vulnerable to this attack (but not the other seven):
- Users of R418 for GeForce, Quadro, and NVS should install 418.43.
- Users of R418 for Tesla should install 418.39.
- Users of R400 for GeForce, Quadro, NVS, and Tesla should install 410.104.
- Users of R390 for GeForce, Quadro, NVS, and Tesla should install 390.116.
- Users of R384 for Tesla should install 384.183.
Whether on Windows or Linux, after installing the update, a hidden option will allow you to disable GPU performance counters unless admin credentials are provided. I don’t know why it’s set to the insecure variant by default… but the setting can be toggled in the NVIDIA Control Panel. On Windows it’s Desktop then Enable Developer Settings then Manage GPU Performance Counters under Developer then Restrict access to the GPU counters to admin users only. See the driver release notes (especially the "Driver Security" section) for more info.
The main thing to fix is the other seven, however. That just requires the driver update. You should have received a notification from GeForce Experience if you use it; otherwise, check out NVIDIA’s website.
Subject: Graphics Cards | February 18, 2019 - 12:07 PM | Scott Michaud
Tagged: nvidia, graphics drivers, geforce
Apparently the latest WHQL driver, 418.81, can cause random application crashes and TDRs (“Timeout Detection and Recovery”) issues on Windows 7 and 8.1. NVIDIA has followed up with a hotfix driver, 418.99, that addresses the issue.
Hotfix drivers do not undergo full testing, so they should not be installed unless you are concerned about the specific issues they fix. In this case, because the bug does not affect Windows 10, a Windows 10 driver is not even provided.
In case you’re wondering what “Timeout Detection and Recovery” is, Windows monitors the graphics driver to make sure that work is being completed quickly (unless it is not driving a monitor – Windows doesn’t care how long a GPU is crunching on compute tasks if it is not being used for graphics). If it hangs for a significant time, Windows reboots the graphics driver just in case it was stuck in, for example, an infinite loop caused by a bad shader or compute task. Without TDR, the only way to get out of this situation would be to cut power to the system.
Subject: Graphics Cards | October 5, 2018 - 08:06 PM | Scott Michaud
Tagged: nvidia, pc gaming, graphics drivers
Another major version bump has occurred in NVIDIA’s Game Ready Drivers over the span of around two weeks. Typically, although there has been a couple of exceptions, NVIDIA has branches that contain major new features once every two-or-so major version numbers. They then push maintenance releases along the number line, which are probably cherry-picked into various branches. In this case, the 410-series branch, which was embodied in 411.63 and 411.60, brought in support for the RTX 20-series of cards.
This has been superseded by the 415-series branch with 416.16. (Oddly enough, the root branch has an odd version number. This is the first time I remember seeing that, although I have not been paying too much attention.)
What has changed? Even though it is a Game Ready driver, it is not associated with a game launch per se. Instead, it is for Windows 10 version 1809, which includes support for DirectX Raytracing (DXR). It also adds a handful of fixes, such as removing black-square glitches from Quake HD Remix mod and improving the performance of TXAA in Rainbow 6: Siege. So basically, the main advantage of this driver will be for those who are using the RTX 20-series cards when games such as Battlefield V launch, which should have been two weeks from now but has, instead, been pushed back to November 20th. (I don’t know if they said that raytracing would be supported at launch, though.)
As always, feel free to refresh GeForce Experience and update your drivers.
Subject: Graphics Cards | June 26, 2018 - 10:01 PM | Scott Michaud
Tagged: nvidia, graphics drivers, geforce
NVIDIA aligns their graphics driver releases with game launches, and today’s 398.36 is for Ubisoft’s The Crew 2. The game comes out on Friday, but the graphics vendors like to give a little room if possible (and a Friday makes that much easier than a Tuesday). NVIDIA is also running a bundle deal – you get The Crew 2 Standard Edition free when you purchase a qualifying GTX 1080, GTX 1080 Ti, GeForce gaming desktop, or GeForce gaming laptop. Personally, I would wait for new graphics cards to launch, but if you need one now then – hey – free game!
Now onto the driver itself.
GeForce 398.36 is actually from the 396.xx branch, which means that it’s functionally similar to the previous drivers. NVIDIA seems to release big changes with the start of an even-numbered branch, such as new API support, and then spend the rest of the release, and its odd-numbered successor, fixing bugs and adding game-specific optimizations. While this means that there shouldn’t be anything surprising, it also means that it should be stable and polished.
This brings us to the bug fixes.
If you were waiting for the blue-screen issue with Gears of War 4 to be fixed on Pascal GPUs, then grab your chainsaws it should be good to go. Likewise, if you had issues with G-SYNC causing stutter outside of G-SYNC games, such as the desktop, then that has apparently been fixed, too.
When you get around to it, the new driver is available on GeForce Experience and NVIDIA’s site.
Subject: Graphics Cards | May 3, 2018 - 08:41 PM | Scott Michaud
Tagged: nvidia, graphics drivers
The previous set of drivers, version 397.31 that was released last week, had a few bugs in them… so NVIDIA has released a hotfix (397.55) to address the issues (without waiting for the next “Game Ready” date). Of course, these drivers also went through a reduced QA process, so they should be avoided unless one of the problems affect you.
And the fixed bugs are:
- Device Manager may report Code 43 on certain GTX 1060 models
- Netflix playback may occasionally stutter
- Added support for Microsoft Surface Book notebooks
- Driver may get removed after PC has been idle for extended periods of time
The last issue manifests in a couple of different forms. The forum page specifically mentions Windows 10, although users with Windows 7 and Windows 8 could also be affected by the bug, just with different symptoms. I experienced it, and for me (on Windows 10) it was just a matter of force-quitting all processes prefixed with “nv” in task manager. My symptoms were that GeForce Experience would attempt to re-download the drivers and StarCraft II would fail to launch. If you’re experiencing similar issues, then you’ll probably want to give this driver a shot.
You can download it from their CustHelp page.
Subject: Graphics Cards | April 25, 2018 - 08:27 PM | Scott Michaud
Tagged: nvidia, graphics drivers, rtx, Volta
It’s quite the jump in version number from 391.35 to 397.31, but NVIDIA has just released a new graphics driver. Interestingly, it is “Game Ready” tied to the Battletech, which I have been looking forward to, but I was always under the impression that no-one else was. Apparently not.
As for its new features? The highlight is a developer preview of NVIDIA RTX Technology. This requires a Volta GPU, which currently means Titan V unless your team was seeded something that doesn’t necessarily exist, as well as 396.xx+ drivers, the new Windows 10 update, and Microsoft DXR developer package. Speaking of which, I’m wondering how much of the version number bump could be attributed to RTX being on the 396.xx branch. Even then, it still feels like a branch or two never left NVIDIA’s dev team. Hmm.
Moving on, the driver also conforms with the Vulkan 1.1 test suite (version 220.127.116.11). If you remember back from early March, the Khronos Group released the new standard, which integrated a bunch of features into core, and brought Subgroup Operations into the mix. This could allow future shaders to perform quicker by being compiled with new intrinsic functions.
Also – the standalone installer will apparently clean up after itself better than it used to. Often I can find a few gigabytes of old NVIDIA folders when I’m looking for space to save, so it’s good for NVIDIA to finally address at least some of that.
Pick up the new drivers on NVIDIA’s website or through GeForce Experience.
Subject: Graphics Cards | March 4, 2018 - 02:02 PM | Scott Michaud
Tagged: nvidia, hotfix, graphics drivers
NVIDIA has published a hotfix driver, 391.05, for a few issues that didn’t make it into the recently released 391.01 WHQL version. Specifically, if you are experiencing any of the following issues, then you can go to the NVIDIA forums and follow the link to their associated CustHelp page:
- NVIDIA Freestyle stopped working
- Display corruption on Titan V
- Support for Microsoft Surface Book notebooks
While improved support for the Titan V and the Microsoft Surface Book is very important for anyone who owns those devices, NVIDIA Freestyle is an interesting one for the masses. NVIDIA allows users to hook the post processing stage of various supported games and inject their own effects. The feature launched in January and it is still in beta, but lead users still want it to work of course. If you were playing around with this feature and it stopped working on 390-based drivers, then check out this hotfix.
For the rest of us? Probably a good idea to stay on the official drivers. Hotfixes have reduced QA, so it’s possible that other bugs were introduced in the process.