Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by Mott, Apr 3, 2018.
You made them aware.
@Mico thank you so much dude I love you. Spent thousands upgrading and 100s of hours chasing bugs, this solved all of my issues across 10 of my most problematic games. Insurgency, squad, ac odyssey, far cry 5, div 2, Blair witch, destiny 2 all butter smooth. Control and Kingdom Come which i bought this morning and spent 3 hours trying to fix the stutter instead of playing it are 95% stutter free which is magnitudes better than it was, the stutter is very minor now which ill chalk up to the game engine. I upgraded to all the best trying to solve this ongoing hitching problem 2080ti nvme ryzen 3600 x570 gigabyte master tridentz etc etc with no change. All along I thought it was hardware somehow, because almost every game did that damn 1/2 second stutter. Thanks again.
edit: the update from icue that just released solved the rest of the spikes on control and kc deliverance 100 percent stutter free now, unreal.
You're welcome. Glad this is working for others too!
Awesome work m8. Kudos to you.
This sounds like something that should be reported to Microsoft...
Good luck with that they dont even work together within the company. I gave up reporting to them a while ago. They just dont care about gaming performance or bug fixing, just adding useless feature after useless feature. If they truly cared about gaming they wouldnt load the system with bloat or apps we cant shut down, or give us a gaming version of windows 10.
Understandably, Microsoft doesn't have time to look at every report sent their way. But if reports were sent on mass, or if tech news sites (like guru3d) pick it up, I'd expect a fix pretty quickly.
Yep, if this is solving the issue for everyone, an in-depth article by some Guru or other reliable tech news sites would definitevely raise the problem.
Little update: after turning off ASLR related settings only i was noticing heavier cpu loads in some game (AC Odyssesy and The Division 2 mostly) and way longer loading times in almost all games. This compared to all settings off. So i basically returned to all setting off, and everything is fine again. Possibly on my machine is more noticeable due to my old cpu (i7 4770 + hdd, ssd for system only), since my friends with faster cpus + ssd are not having this.
So ASLR with high entropy (which is disabled when you turn off ASLR bottom-up), ASLR bottom-up and CFG all cause stutters in games and lead to measurable (at least for CFG) less performance, as we have seen in the past (I think it was something regarding Chrome or Chromium based browsers taking longer to load sites because of CFG).
I opted with turning off ASLR globally and CFG on per program basis, including Nvidia services and other stuff that runs in the background.
Not for everyone. IBM PC platform + Windows + user mentality create a universe of diversity.
Sorry my english faults again. Could you explain this in a less compressed way?
He's just saying there could easily be computers where these settings do not effect performance, we have a small sample size here.
Also Microsoft may consider the penalty worth it for non-power users, where security is more important. Most people never open a single settings window.
I would say most of computers do not suffer from security mitigations. Even in this thread we saw haw many gurus reported solving stutters by disabling security mitigations - 3, 4 ?
PS My home rig has no problems neither with standby list nor with CFG and ASLR.
On this particular ASLR protection, what scenario would this be able to be exploited? I read MS doc on it and it seems to change memory address each time an app is run. So to me, that would be most important with servers/VM's compared to a home user. I mean hacker would need to be at the system or have remote access to it?
I mean, at least regarding CFG: https://www.zdnet.com/article/windo...-huge-chromium-performance-issues-fix-coming/
And as no one knows that Microsoft fixed, I just assume they whitelisted Chrome or developed a heuristic to detect browsers.
So.. fully disable CFG and ASLR exploit protections globally and install ISLC on top for the ultimate W10 experience? (trying to sift through and get an accurate summary here for those like me who can't keep up with all the posts sometimes)
With CFG disabled and ISLC it's been pretty smooth.. but I'm always looking to eliminate any further potential stutters.
Yes. Same here, CFG on per program basis has been pretty smooth in the past (without ISLC as well), but I guess "better less-safe than rage" is the way to go with ASLR
I failed to create beautiful text, so here are the thoughts:
Bugs are always there.
Windows Defender gives users a way to toy with settings.
The article you linked is about test script - not the live user experience.
Also even 100 times slower CreateProcess function is still needed to be executed only one time to launch a game, after that it can`t be a cause for in game problems (until you launch tens or hundreds of processes on the background).
Edit: Also do not forget that exe-file should be compiled with CFG support for this mitigation to be active for the process. And IIRC gurus failed to find games with exe-files compiled with CFG support.
Not really. In server scenario main processes (database engine, WWW server engine, for example) are started at the start of the server to serve the queries/calls from clients. Some children processes can be launched for each client request but the life span of such children processes can be very short.
Also server scenario is more likely to get professional security solutions.
It would be nice if someone could benchmark disabling ASLR globally vs disabling ALSR game .exe
Did you just volunteer?