Alongside the release of the Oculus Touch controllers from Oculus VR, and the fifty-or-so games that launched with it, NVIDIA has published another graphics driver. The GeForce Game Ready 376.19 WHQL drivers also resolve one of two SLI issues in No Man’s Sky (the other bug, which involves temporal anti-aliasing, is still being worked on) and also fixes two issues with G-Sync for laptops.
Since it affects a few of our readers: the Folding@Home bug is not yet fixed, but it’s now classified as a top-priority bug, though. Personally, I’m guessing that it will be fixed soon, now that there’s a little down-time before and after the holidays, after and before the game release rushes. Otherwise, it seems pretty stable and smooth for me. One user is complaining about Windows 10 UI freezes and crashes, starting with 376.09, but it’s otherwise relatively quiet.
As for the contests
NVIDIA is hosting two giveaways: one on their social media sites (Twitter and Facebook) and the other on GeForce Experience. The first contest runs from Tuesday to Friday, where they are giving away a GTX 1080, game codes, and one grand prize of a custom PC, accessorized with an Oculus Rift and Oculus Touch. The other contest runs until December 30th, where NVIDIA will give away a bundle of Oculus Rift, Oculus Touch Controllers, and a GTX 1070 to ten people, at random, who log in to GeForce Experience.
Check out their blog post for details on how to enter, as well as get the new driver (if GeForce Experience hasn’t already started begging).
They jacked up the Windows 10
They jacked up the Windows 10 start menu…again.
Scott will tell you its a
Scott will tell you its a user error and you need to reboot your computer.
Your eyes deceive you.
Or… I actually mentioned it
Or… I actually mentioned it in the post. o.o
Its kind of silly to post
Its kind of silly to post that only one user has Win 10 corruption at the time your posting it as news not alert your readers their is a driver.
It could mean that by the time you posted this news one person already has issues popping up and sure enough its 12hrs later and several more people are complaining about Win 10 issues that were supposedly solved in prior releases.
There was literally only one
There was literally only one user in the eight pages (at the time of publication) of the GeForce Forums thread who complained about it. They seemed like they knew what they were talking about, so I mentioned it.
In fact, the thread is now ten pages, and there still is only one person complaining about it (although he made several posts and several people tried helping him). Quest4Glory's comment to this thread is only the second person I've seen complain about it, and the comment below is the third.
So… what's the problem with my writing?
i see you ignored all the
i see you ignored all the ones that complained and said they rolled back to previous drivers.
I guess in your book if they
I guess in your book if they don’t stick around and write up how they trouble shoot they don’t know what they are talking about. He only posted because the other person was skeptical on what he was complaining about and he got proved wrong.
After all why do the common sense thing of rolling back to a driver that works. Apparently that doesn’t qualify you as knowing what your talking about.
Link to a single
Link to a single post that I "ignored" in the first eight pages that claims someone (besides zig11727) rolled back to a previous driver for the Windows UI lockup issue, specifically, that you're referring to.
If I ignored "all the ones", then link one. Any one. Remember, you're talking about Windows 10 UI stability, so link a post specifically to Windows 10 UI stability.
Also, if you say this guy, he was talking about previous versions. In fact, he says this driver release was the best he's seen for a while on the next page.
So yeah. Please, link to a single post I "ignored" that claims someone had Windows 10 UI stability issues, so they rolled back to a previous driver. I know there isn't any. I just double-checked through all of them in case I missed any the first time around.
I wasnt but if you want to
I wasnt but if you want to use him as an example.
Actually he says
So if your using him as an example this is the first driver that appear to solve his issue where all this time since hes had his 1080 hes been dealing with.
This is what you said in one of your post LAST WEEK!!!
The very same person your using as an example according to you wouldn’t be having problems and be dismissed and ignored.
Unfortunately you and PCPerspective haven’t followed up on it. I believe someone mentioned prior in one of the driver releases and you dismissed it here as well.
Let me be clear i’m not against posting your opinion but being dismissive is an issue especially now that you used this as an example.
Can you see the problem?
Can you see the problem?
If you're upset at the way I report on an issue, making false accusations (like I "ignored" posts regarding people rolling back to a previous driver for Windows UI stability issues) isn't giving me feedback to solve your actual issue. Clearly you have an actual issue, because you wouldn't waste your time otherwise, but, at this point, I have no clue what it is.
I try to pull feedback wherever it's given, good or bad, but you're not conveying anything real or actionable. For all I know, it could be a general beef with the site, or even a general beef with NVIDIA, and there's nothing I, personally, can do better.
Or maybe there is something wrong with my writing. I don't know, but, again, I haven't been able to pull anything out of this sort of feedback to flag problems. I'm not going to change they way I report to consciously make one company look better or worse, but I might be doing that without realizing it.
In fact, I've been concerned that I was pointing out bugs in NVIDIA driver announcements more than AMD driver announcements because I've been experiencing several lately, whereas I don't have an AMD card to compare against. (I only have one work machine.) Should I assume, based on your comments, that I haven't been AMD-slanted lately?
it is indeed causing crashes,
it is indeed causing crashes, starting with 376.09.
yep windows is freezing at
yep windows is freezing at startup
soon as I click a button or icon explorer crashes