Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by dr_rus, Apr 14, 2017.
This is fixed in our next driver
And this driver tdr while browsing?
Reminds me of old 280.xx driver that had similar bug, but back then it affected mostly gf104/114 460/560gtx, very rare on full gf110 chip.
Took driver team until 290.xx to fix completely. Please don't let it be the same now
Just got my very first driver overran stack buffer BSOD.
The weird part was it happened during browsing, rather then intensive GPU usage.
Why dont you fix the display port monitor issues
some times i get black screen with mouse curser that i can move about but thats it black screen
my lg b6 oled tv does not work with the hdmi port, hdr is messed up causes the graphics driver to become unresponsive.. and bsod or get stuck in a display loop of trying to detect and redetect about 8 times then bsod.
this is with 2x 1080ti` Fe`s.
then there is monitor detection,, even my monitors will not detect properly every time, sometimes black screen again or driver crashes and tries to recover over and over again......
i also run multi monitor so some of the issues could be tied into multimonitor issues aswell... but clearly something is broken...
same reason sli still doesnt work in the config they suggest/advertise expect you to use on their site with multiple displays.
of all the configs listed, none suggest to use only 1 card for connections. mods on the forums have said thats an unsupported config, yet theres a 20 page long thread of people all saying their options are either use a top card only config or use the old bridge at a performance loss.
off topic a bit though as for these drivers, yea i get some peeeerty weird lock ups w/ them myself although i also moved to creators update so who knows what nonsense is going on now.
Thanks & greatly appreciated. :banana:
Good! But we are already on 22th of April and the 25th will be released Sniper: Ghost Warrior 3 that is optimized for Nvidia's graphics card....
The eta for the new drivers?
I'm guessing new Game ready driver for Prey on May 5th.
Wondering myself here I'm still using LTSB build 1607. Don't wanna come near regular windows versions My guess it's the same as 381.65 whql...
Most likely around the corner. I guess might release the end of this month.
I get boot to black screen quite often with Win10 Creators and this driver.
Anyone else, or just me?
Yup, every second boot, have to force restart all the time.
Cool! I'm going to install this today.
Glad to hear it's not just me then. I don't know if it's Creators or nVidia or both. Hopefully it'll be fixed before long.
For my friend on his laptop Asus G752VS we can't even install Windows 1703 upgrade from 1607. it just freeze on black screen after finishing the first windows downloading and updating..
If you use custom refresh rates in your games, don't update to Win 10 Creators.
Creators breaks the use of custom refresh rates in game while it works in the desktop.
I've tried this driver and 3 others before it and this issue is not resolved.
I've also tried disabling, game mode, GameDVR and game bar without any success.
My desktop runs at 2560 x 1440 @75hz but it reverts to 2560 x 1440 @60hz (native res) during gaming.
Games that have a setting that specifies the res and refresh rate to use can't see my desktop's custom refresh rate.
Hopefully either Nvidia or Microsoft can resolve this issue since I play with vsync on so that there is a vast difference between 75 fps and 60 fps in terms of gaming experience.
^ custom refresh rate works just fine here with this driver and CU (15063.138). Recently clean installed though.
Using CRU to create 1920x1080@75 Hz (default 60 Hz).
Tried using CRU but it seems that I can't set my custom res and refresh rate with it.
I'm using a display port cable with my monitor.
Can you give me the steps to set it up? Maybe I'm missing a step or two.
I got a black screen after a reboot today. Well, what do you know!
If you just want to add the higher refresh rate to your native res you needn't create a separate custom res at all. The new refresh rate is available after resetting display driver.
If I understood correctly. Just create a new detailed resolution in CRU with 75 hz refresh, save and reset driver. The new refresh rate is selectable with your native res now.
Though check nv cpl as there are separate entries for HD and PC often depending on your cable/monitor. If you don´t see it immediately check alternative section for the same resolution.
Have it set up like this: