Jump to content

Nvidia Gtx 860M Driver Issue


4 replies to this topic

#1 Master Green Fox

    Member

  • Pip
  • Bad Company
  • Bad Company
  • 19 posts

Posted 15 December 2017 - 10:15 PM

As of the Fall creator's update 1709 for Win 10 I had the "Black-screen" error and had to go through and update my video drivers for the Intel HD 4600. In doing so I figured I would update the GTX 860M as well.

However in doing so the new drivers (388.59) for some unknown reason make playing MWO in specific almost impossible. Even on the lowest settings the graphics flicker, the frame rate drops, and there is a lot of tearing if I turn slightly fast in game. The game runs, I just can't effectively see what is going on.

For some reason I couldn't roll back the driver and have no idea what it was before (though it was probably very old) and I have spent way too many hours over the past few days trying to find a way to fix this.

I currently have a very bad workaround in that the game is playable without tearing or frame rate (still slightly flickering mechlab though) on the lowest settings when I installed the 378.66 drivers. If anyone has a better idea of a more stable build that is higher up, or has a better workaround of another type, that would be very much appreciated.

Also, has anyone else with a Nvidia GTX 860M and Win 10 been dealing with this issue? It would be nice to know if I'm not the only one. And if so and you still haven't managed to fix it hopefully you might be able to use the aforementioned idea to use the 378.66 to play.

#2 NARC BAIT

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • 518 posts
  • Twitch: Link
  • LocationAustralia

Posted 16 December 2017 - 01:15 AM

sounds to me like its lost your preferences during one of the upgrades, and is preferencing the HD4600, as opposed to the Nvidia card .... within the nvidia control panel, you want to check / create a profile for MWO and within there you should be able to tell it to always use the nvidia card ...

other than frame rate minimums, an 860 should play a reasonable resoluion fine ...

#3 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,824 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 16 December 2017 - 03:58 PM

By default Windows 10 updates all drivers but it does not always go well. Suggest turning off that feature.

Completely uninstall Nvidia drivers and all associated software. 388.59 or the one prior to that would have been installed.

http://www.nvidia.co...px/127669/en-us

The other option.. still uninstall all Nvidia drivers and software Geforce stuff.

Go to your laptop's mfg and download their GPU driver and install it. Then set 3D, Power Management Mode, from Adaptive to Max Performance.

Also, your system's power options, Settings, Power, change to High Performance.

Also, a can of compressed air, blow out the heatsinks of dust buildup.

Edited by Tarl Cabot, 16 December 2017 - 03:58 PM.


#4 Master Green Fox

    Member

  • Pip
  • Bad Company
  • Bad Company
  • 19 posts

Posted 18 December 2017 - 03:34 PM

I actually had already done both of the things that you two suggested in those prior two days trying to fix it. I would have put it all in the post but I didn't want to make the post incredibly long. None of those things worked at all.

My laptop is already set to High performance for power management and so was the GPU back then before I installed the 378.66

In order to even get the old driver 378.66 to install I had to completely uninstall Nvidia using the DDU so I could make a clean install of it, only after that did I manage to get anything functional. Of course then again It wasn't even a direct install of 378.66 because the Nvidia installer couldn't find the device, so I had to install an even earlier driver first just so that the 378.66 driver installer could actually find the device.

I also only came to that set of drivers after trying a clean reinstall of the 388.59 which changed nothing so I started to go back a few drivers at a time. Each time I went through and made them clean installs. Nothing worked all the way back to 385.41 which was all the way back in August. So then I had to look for another angel to attack from and looked up what was considered the last stable driver for a GTX 860M. To my dismay what was being stated was 355.98 which is way too old to run almost anything. I know because I tried that driver too. the last one mentioned by anyone was a 365.10 but also failed and that was the driver I used to get the 378.66 to find the hardware. Which finally worked, though I had to reduce MWO video settings to Low.

Also If I do use the 4600 the game is impossible to run where even menu buttons are not all visible and flicker, and the game usually crashes if I try to enter a game.

What gets me the most about all this is each of the drivers still worked for almost all my other games, some of which are pretty new (Prey, Divinity 2, etc) but for some reason crap out on MWO. I only say "almost" because I didn't sit down and start every game I own. That would take way too long. But still, it is really strange and a bit frustrating.

I think the next thing I'm going to try as dumb as it sounds is reinstalled the newest update and then attempt to run the game in windowed mode. Because for no reason I can figure, the game is running even better in windowed mode on the 378.66 driver than full screen. So much so that I can raise the graphics a whole quality grade and have no performance dips.

#5 SmoothCriminal

    Member

  • PipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 815 posts

Posted 28 December 2017 - 12:57 PM

Master Green Fox - any update on whether this is working?

I recently came back to the game and was having similar issues using a Nivdia 860M (essentially hitting loading screens that canned the game and forced a restart). I am now getting an error message (the fated graphics card not supported issue) - that will not let me even start the game. If this continues to be an issue i will start deleting/re-installing the game/drivers etc. to see if that might fix it...

Edited by SmoothCriminal, 28 December 2017 - 12:58 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users