Best fix I found so far for shuttering and crashing.

[Ed_]

Get Process Hacker

Process Hacker is the super-powered version of your windows task managaer.
Link: http://processhacker.sourceforge.net/

Ok here is what you want to do:

Start up process hacker and prepare your computer for GTA V.
In process Hacker go to the view tab on the top left of the menu bar and select the view option.
Under view select system information a new menu should pop up with various graphs and numetrics.
Go under memory and select the more option on the bottom right that right above the close button a bit to the left.
in the new window that pops up go to empty and select Emtpy Standby List.

Now start up GTA V. When you get to the main menu screen of the game, alt tab out and go back to process hacker.

FInd the GTA V process and right click it. Under the menu options select priority, make it high and use the save to GTAV.exe option. Same goes for i/o priority. Do the same thing agian for the GTA V launcher except make it below normal and low priority

Under Miscellaneous, go to page priority and set it to one. This will deter GTAV from using the virtual memory that has ussally caused people to have massive shuttering. Next go back under Miscellaneous and select Reduce Working Set.

My steam guide for GTAV: http://steamcommunity.com/sharedfiles/filedetails/?id=431245552

[effmoo =☺_☺= 7]

thanks for this - i'll try and get it direct i dont like sforge always seems to have snidey ads = when i used it was a while back though

[Fabio]

I'm currently testing this. One hour has passed and I had no stuttering issues (online mode).

I'll report back if changes occur.

[Azarad0]

can anyone confirm this and also test this for Self radio suttering issues?

[Fabio]

Originally posted by Zard:

can anyone confirm this and also test this for Self radio suttering issues?

I tested the game for an entire hour. I can't confirm or deny if this works as a fix for crashes, but as far as stuttering goes, I had no more problems (for an hour, then a game bug messed up a mission and I had to turn off the game).

I'll test this again tomorrow.

By the way Ed94:

Originally posted by Ed94:

in the new window that pops up go to empty and select standby memory

The underlined option didn't show, so I selected another one, a similar one.

[Azarad0]

ok thanks if anyone here has the same problem as me with self radio massive stuttering in game since its a known problem can anyone test this and use self radio to see if it works?

[Ed_]

@Fabio sorry about that, its actually Empty Standby List not standby memory, I used the more common term than what was displayed for the same thing. I'll update the post with the correct term.

[GrandNoodleLite]

Originally posted by Ed94:

My steam guide for GTAV: http://steamcommunity.com/app/271590/guides/#scrollTop=200

Clicking on this link leads to the guides page for GTA V, not any specific guide. Just fyi.

[Ed_]

Originally posted by GrandNoodleLite:

Originally posted by Ed94:

My steam guide for GTAV: http://steamcommunity.com/app/271590/guides/#scrollTop=200

Clicking on this link leads to the guides page for GTA V, not any specific guide. Just fyi.

Fixed thx.

[Fabio]

Originally posted by Ed94:

@Fabio sorry about that, its actually Empty Standby List not standby memory, I used the more common term than what was displayed for the same thing. I'll update the post with the correct term.

No problem! That was the option I selected anyway, it only occured to me that it could mislead other people who read the guide.

[Ben]

what even is "shuttering"

[gsw mer]

i wrote a ticket to r* about the stuttering, and they replied telling me to disable my firewall... what a joke amazing how my other games dont ask for this

[Buck]

Originally posted by Ed94:

Next go back under Miscellaneous and select Reduce Working Set.

Why would you want to do this? This just lowers the amount of data the game can keep resident in main memory. This would directly increase the game's need to utilize paged pool space (Paged memory != page file usage). And if you take THAT away from it, well the process is most likely going to crash due to running out of resources,

I don't quite understand the purpose of this program. I haven't downloaded or played with it yet, but it looks like nothing more than a clone of Sysinternals Process Explorer, which was written by Mark Russinovich (If you don't know who he is and why you should listen to him, google the name).

It's not a good idea to mess with the paged memory pool either. Doing that will just increase the use of non-paged memory pool space. At worst, it could cause it to exhaust the non-paged pool which can possibly affect ervices and other kmm (Kernel mode memory) processes such as drivers which could potentially lead to instability and crashes.


Look, I know people find the stuttering annoying, but mucking around with stuff you don't understand with tools you don't understand because some random guy on a forum said "HEY TRY THIS!" is not a good idea. I doubt you can cause any real serious harm by doing so, but imo it's not something people should be playing with if they don't at least have a general idea of what they are doing. We can probably safely assume that the guys who actually built the RAGE engine and the game know more about it and and how it needs to work than anyone else possibly could.

Personally, I think any perceived benefit is just that, perceived, and is likely a placebo effect. The only way to truly tell whether or not any mucking done to the game with this program is having any effect would be to do a double blind study. Something I doubt anyone really wants to actually be bothered to do.

[Fabio]

Originally posted by Buck:

Why would you want to do this? This just lowers the amount of data the game can keep resident in main memory. This would directly increase the game's need to utilize paged pool space (Paged memory != page file usage). And if you take THAT away from it, well the process is most likely going to crash due to running out of resources,

I don't quite understand the purpose of this program. I haven't downloaded or played with it yet, but it looks like nothing more than a clone of Sysinternals Process Explorer, which was written by Mark Russinovich (If you don't know who he is and why you should listen to him, google the name).

It's not a good idea to mess with the paged memory pool either. Doing that will just increase the use of non-paged memory pool space. At worst, it could cause it to exhaust the non-paged pool which can possibly affect ervices and other kmm (Kernel mode memory) processes such as drivers which could potentially lead to instability and crashes.


Look, I know people find the stuttering annoying, but mucking around with stuff you don't understand with tools you don't understand because some random guy on a forum said "HEY TRY THIS!" is not a good idea. I doubt you can cause any real serious harm by doing so, but imo it's not something people should be playing with if they don't at least have a general idea of what they are doing. We can probably safely assume that the guys who actually built the RAGE engine and the game know more about it and and how it needs to work than anyone else possibly could.

Personally, I think any perceived benefit is just that, perceived, and is likely a placebo effect. The only way to truly tell whether or not any mucking done to the game with this program is having any effect would be to do a double blind study. Something I doubt anyone really wants to actually be bothered to do.

This is why I'm testing this and if in reality the stutter begins, I'll just say that this guide does not work. No harm done.

[Ed_]

I'm not posting something I havent tired. Its something I used for at least 15 hours with moderate sucesss the only place I get a frame drop now is when driving at top speed through Grapeseed due to the sheer number of reasources conglomerated into one area. its easily one of the most heavily densest areas of the game.

If in anyway you find a configuration with processhacker that you have found to keep shuttering even further away than this by all means post it. I would love to be able to acutally enjoy playing this game fully for once like I did back on ps3. The reason I bought the pc version was to have the best experience and I am not.

Here was my what I found happened with those settings, Emptying standby memory early on frees up memory from programs that are not going to be needed when playing GTA V, it also allows it to have greater priority on that free memory compared to when it had been influced by other programs. Putting the games priority at high and I/O priority at high gave the game less of a lag time when acessing the cpu and HDD. The purpose in putting page priority to 1 or idle was to keep GTA V from ever wanting to really use the memory(It half worked). It drasticly reduced shuttering but when looking at the numetrics while playing I saw that the game was still using at least 100mb. Normally I'd be fine with that till I found that it was using some pretty large reasources in the 100mb instead of using it for something light on performance like shaders. So I tried other options till I came accross Reduce Working set. At first I was skeptical it would work since of course it would make GTA V use less of the ram which would then incline it to use the page file, but for some reason that did not happen, oddly enough it acutally allowed GTA V to not go over 4gbs of ram use like it usually does and made the gpu have access to the shared memory option.

SO I finnally was able to get no shuttering on minimum specs. From here I put my settings slowly back up till I found the breaking point and tested areas to further refine it. Then I became satisfed with mid to high settings with only Grapeseed having shutter. Close to the kind of performance I used to have with only my old fixes before the last 2 patches.

P.S. My settings before allowed me to run this game almost on all high with no shutter using previous fixes at about 45 to 50 frames per second.

[Dysstatic]

Originally posted by Ed94:

Putting the games priority at high and I/O priority at high gave the game less of a lag time when acessing the cpu and HDD.

I have had to do this since last patch (was smooth as before), set the GTA exe to high/high, while it has't fixed it 100%, its mostly smooth again (occasional stutter but nothing like it was).

I have also turned off my pagefile completely which definitely helps overall performance on a machine with a mechanical drive (i dont care about BSOD logs, if need be and the machine starts playing up, I'll just turn it back on to get logs). With 16gb RAM the machine copes fine with no page, GTA uses very little anyway.