Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by Astyanax, Sep 10, 2019.
what happens if you make a profile for MS Edge in RTSS and set application detection level to none?
I don't have RTSS installed, I just use MSI Afterburner, I don't use the overlay. If I disable hardware acceleration of IE11, which also disables it in Edge, then I don't have the issue with Twitter being open
I just tried with the Sli indicator on, and this will always shows its working, but if you view the clock speeds and gpu usage in MSI Afterburner, the 1 card is not being used. With Twitch closed, both cards are running at the same speed and the usage is identical for both cards.
Purpspyk is not the only person experiencing this, I have seen others on reddit reporting it too.
Nice to know, I was not ware of this, I was about to reformat.
For me it is Borderland 3. Up then down too often for my liking.
@ManuelG another reddit user has reported that much like Darrens case, exiting Afterburner and RTSS together stopped the GW502 crashes.
This driver fixed the occasional hitching i had in R6: Siege with ultra low latency mode.
I got one 2k 165hz & one 1080p 144hz on my GPU and my 3rd monitor (1080p 60hz) on my Cpu (Mainboard hdmi).
Can you guys please bring back the non-vsync'd borderless mode?
After 391.something drivers it's always forced on, regardless of the Control Panel setting and many games nowadays implement borderless as fullscreen and they're laggy.
I'm still on 391.29 Tesla drivers because of this.
That was not a feature of the driver, it was a driver model behavior that microsoft are accepting feedback on.
Thanks very very much my friend.
So from my understanding, WDDM something introduced this behavior and NVidia driver 392.x needed to comply with it, that's why it's forced.
I`ve confirmed this is not a driver related issue, since it happens with other drivers (happens less often with older drivers), also, not a bios problem since I changed my Bios and also happens.
Here is a video about my problem:
Can you check your pc with malwarebytes?
It`s been like.... 10 years, maybe more, since I had a anti virus or something like that in my pc... But since I`m clueless, I ran this Malwarebytes, it found 4 things related to chrome and... I still have the problem...
Next step, format...
Clean Windows and still have the problem...
Hi @ManuelG This is using the Express Installation during driver install.
I have a dual boot system, Windows 7 and Windows 10 and I'm using a RTX 2070 graphics card and I can no longer get super sampling anti aliasing to work using Nvidia Inspector on either Battlefield 2 and battlefield 2142 using the 430. drivers under Windows 10 . I really hate jaggies, but what's even more annoying is that I'm getting awful graphical glitches and stuttering in both BF2 and BF2142 (smoke effects flashing on and off).
Windows 10: BF2 & BF2142: I can't get AA to work at all using Nvidia Inspector. Nvidia Control Panel works. Graphical glitches, smoke and shadows flickering on and off.
Windows 7: BF2 & BF2142: AA works fine using Nvidia Inspector, but I get awful graphical glitches with smoke and fire effects flashing on and off all over the place and really bad stuttering even though the FPS is 90+.
I never had any of these problems with my old graphics card, a GTX 770 when using Windows 10 and Windows 7, or even Widows XP. These games ran fine in any OS.
Is Nvidia no longer bothered about older games not working and instead is just concentrating on new games?
Does anyone else with an RTX graphics card experience these problems? Or maybe there's something wrong with my graphics card? The highest temp while playing was only 45C. Are these artifacts caused by a faulty GFX card, Nvidia driver bugs or game related bugs. I never noticed these glitches with my GTX 770.
After further experimentation it appears that the glitches are caused by activating any kind of AA, either in game or through the Nvidia control panel. NO AA= no graphics glitches, smoke and shadows work, so it looks like it must be a Nvidia driver problem because the game ran fine with AA turned on when I was using a GTX 770 with older drivers. With my GTX 770 I used to play this game with 8XSuperSampling with no graphical glitches whatsoever.
Seems that with the arrival of their premature RTX cards (with arguably minor performance improvments over theprior generation GTX cards and the mining craze business decision tree of nvidia), that anything after driver 399.40 its been major suckage. Granted my opinion is biased because I bought 2 RTX Titans and returned them for lackluster performance as they compared poorly compared to Volta and HBM2 mem dies/GPUs (and because the RTX non HBM2 die has better production line yield). At the time of purchase I was comparing Volta on the 399.40 driver and the 418.xx and 416.xx performance.
All 400.xx series drivers have only lessened Titan XP and Titan V performance for me. As I've beem reminded kindly by other knowledgeable members of this community: the RTX line is meant to power Ray Traced games at 1920x1080. This may be true, but after 399.40 at 4K and 5K and current drivers (especially the 430.xx+/and above) its been major suckage for my cards.
So IMHO, with Volta and Titan XP --- YES!, nVidia drivers have really started to suck
(not to mention driver downloads in excess of .5 GB in size with a lot of telemetry and non-user-selectable OPT out/ OPT in functions, in addition id doesnt help that there is NO COMPETITION from AMD-RADEON on halo card performance vs performance rather than the price point marketing by AMD, sorry...it is the truth)
nothing to do with the drivers,
you can't make it work because under 10 they aren't actually in exclusive fullscreen and the SSAA modes need a game to be in a pure exclusive fullscreen.