• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Nvidia GeForce 359.06 WHQL driver

N

nvgpu

Senior member
 
Last edited:
 
Unless something odd is going on with my machine, this driver is not WHQL. Not that it matters, but both the driver from Geforce.com and from within the GFE app are not WHQL signed even though they say it is on the download.

Driver works fine for R6S though, but GFE gets the optimal playing settings horribly wrong.
 
I'm reading reports that custom resolutions (refresh overclocking) is still broke.

358.50 still for me 🙁
 
Anyone else having system lockup issues with MPC-BE with these or the previous drivers? I also have it using MadVR and the Black editions built in WASAPI driver. Also have the maximum Klite codecs installed.

Sometimes when I load a video, it loads up and plays for a bit, sometimes with a blank screen, sometimes with the video. This happens more often if I load a video before the previous one closes. After a few seconds it locks up, I can't close it from Task manager with either end task or end process tree.

My only option is to shut down, but even then it prevents the system from doing so without eventually turning the power off manually.

Just trying to narrow it down as so many factors could be affecting it.
 
I'm still getting some texture flickering in JC3 (all settings maxed out @ 1080p) on my EVGA GTX 980 with these new drivers. Stock settings, nothing overclocked including my i7 4790K.
 
Anyone tried Fallout 4 with these drivers and seeing crashes? I keep getting random driver crashes and I'm trying to determine if it is my OC or if it a problem with the game/driver. Anywhere between 5 to 30 minutes the driver will crash. No artifacts or any signs of instability before it does. Seems to be quite stable in Uningine Valley & Heaven, but crashes in FO4.

Apparently this was a wider spread problem shortly after release and I'm not sure if it was fixed or not.

1 - https://www.reddit.com/r/Nvidiahelp/comments/3spngb/nvidia_display_driver_stopped_responding_while/
2 - https://www.reddit.com/r/Nvidiahelp/comments/3t1hep/fallout_4_is_unplayable_driver_crash_after/
3 - https://www.reddit.com/r/Nvidiahelp...lay_driver_stopped_working_and_has_recovered/
4 - https://www.reddit.com/r/Nvidiahelp/comments/3u195d/graphics_card_crashing_during_fallout_4_help/

I will try stock clocks later today to isolate driver versus overclock, but I wanted to see if anyone else was running into this issue.
 
I've had several issues with that, and what seems to have worked for me oddly enough was disabling DP 1.2 on my monitor and having the 980 output DP 1.1.

Not sure if it is the monitor, the driver, or Windows not liking DP 1.2, but things are running smoother via DP 1.1 signal.
 
Thanks for sharing that. I am using HDMI 2.0 so DisplayPort isn't a problem. I'll keep digging around. I can't test the OC right now but I'll mess with it when I get home.
 
It is possibly your OC. Nvidia was rather strict with the power limit. You are probably hitting the power limit.

I can run Firestrike any flavor at 1515mhz on the core without issue, but then FFXIV would crash, but if I drop it down a peg to 1504mhz, I get no issues.
 
Thanks. Not ruling out the OC being the problem at all, something I will test when I am home.

The weird thing about this is I would expect Unigine to be more power hungry than Fallout 4. Unigine is 100% load the entire time, while Fallout 4 is a bit more variable (80-100% range). Oh well.
 
No issues for me outside of a rock stable overclock on my 770 simply crashing my rig within seconds now.1241 has been rock solid till now,where i get immediate artifacts then a crash moments later.

I can't even hold 1202,1241 barely was worth noticing in my games so i went back to stock.The 770 already is a oced 680,i didn't expect much anyways lol.
 
Actaeon said:
Thanks. Not ruling out the OC being the problem at all, something I will test when I am home.

The weird thing about this is I would expect Unigine to be more power hungry than Fallout 4. Unigine is 100% load the entire time, while Fallout 4 is a bit more variable (80-100% range). Oh well.
Click to expand...

I have a suspicion it could be vdroop related as well. Also, you have to take into account when factoring in card power that Unigine does not stress the Vram very much whereas most games will. As a result, that will cause the card to use more overall power and as a result.
 
Teizo said:
I have a suspicion it could be vdroop related as well. Also, you have to take into account when factoring in card power that Unigine does not stress the Vram very much whereas most games will. As a result, that will cause the card to use more overall power and as a result.
Click to expand...

Good points. Also agree that benchmarking software isn't the same as a game, so its possible they are both stressed in different ways.

Was really hoping to figure it all out yesterday so I can get some gaming in today, but looks like I'll have to keep playing with it.
 
Do I need this driver? I'm not use to having 3-4 driver updates in a month. This is just for Just Cause 3, correct?
 
Had a couple of random game crashes, so decided to do a complete reinstall using DDU and now the driver is reading as WHQL...so obviously Nvidia updated the driver file.

Just a FYI for those who may be interested.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top