Possible fix for stuttering....worked for me anyway :D

Associate
Joined
26 Aug 2009
Posts
1,299
First off, you need at least 12GB of RAM for this fix, if you have less there really is no point in trying as running out of memory is going to cause you more issues. Well, actually it may not given the nature of the fix and the way Windows works.

So, the fix.....putting the page file into a RAMDISK. For me, it releived all of the stuttering in BF3 and Skyrim.

Why? As some/most of you may know a large amount of stuttering is caused by slow I/O's from the page file which is normally located on a hard disk or these days a solid state drive. Even the fastest solid states (single) can only achieve around 520MB/s throughput, and latency is still high enough for you to notice it in game.

How? RAM, being on the fastest BUS in the system can achieve more than 18 times the throughput than PCI-E can (SATA controllers use a PCI-E bus), in the range of 8GB/s to well, anything. This massive bandwidth coupled with nanosecond access times allows windows to cache files extremely fast, and load them equally fast as and when needed, thus alleviating the stuttering we see in games.

So for those who didn't figure it out yet, a RAMDISK is a virtual drive that is located in your systems RAM, and it is for this reason you need such a large amount. A typical page file should be at least 4GB in size to allow Windows to allocate that space to multiple programs, and games are pretty hungry in this area. On my rig, playing BF3 @ 2560x1440 with a 4GB RAMDISK, I see RAM usage get to around 10GB-11GB, which leaves me with a comfortable amount of space for say a web browser and what ever else I want to remain in memory and not hog up the precious page file.

So, how to do it? You will need a piece of software from Microsoft called "SuperSpeed RAMDISK Plus". A google search will bring up the correct Microsoft page for the download. Once you have it installed, press the small green + sign in the top left. This will start the wizard. Enter the size drive you would like (try for 4GB+ if possible, and smaller and I advise using multiple page files), and also check the option to write the RAMDISK to the hard drive on shutdown. Because RAM is volatile, on shutdown all data in the RAMDISK will be lost so this step is important. Once everything is done, you should see the disk under windows explorer, feel free to run a standard SSD benchmark to get an idea of what speeds you are achieving (overclocking will increase this).

Now, right click on my computer and "properties" and then "Advanced System Settings". Now under the "Advanced" tab, select "Settings" under "Performance". Select "Advanced" again, and here you will see the page file settings, click "Change". Uncheck "Auto manage page file....." at the top, and follow by setting ALL drives to have no page file by selecting the drive, clicking "no pagefile" and pressing "Set" (pressing "Set" MUST be done for each drive with a pagefile). Once you have done this, select the RAMDISK drive, and enter an amount and press "Set". You will need to reboot your system for these changes to take effect. That's it, your set.

Moving back to the last part of my first paragraph, there is a reason this MAY work even with small amounts of memory (It's worth a try and it won't do any harm). When your RAM is full, Windows proceeds to dump the oldest data to be accessed into the page file, where it can be recalled when needed. Now, allocating most of your spare RAM (above the minimum Windows needs to load + 1GB space) could yield the same benefits.

To expand, what could POSSIBLY happen is this: You load a game, Windows will detect that the memory is full and begin to write to the page file (unknowingly to memory). Now when the game requests data windows will attempt to load it into the 1GB you left spare. Due to the extremely fast speeds, you shouldn't notice any lag, if you do this won't work for you.

Feel free to ask questions and I will try answer them the best I can. I give credit to "Motherboards.org" for the tip on the software.
 
When I suggested this in another subforum, I was told it wouldn't work because it's addressing things that need to go to the RAM... to the RAM. Although I'm sure you're right, you just need plenty of RAM to do it. I can't find a source but some games like BF3 do use a given amount of Page File arbitrarily.


Could you perhaps post some bench results?

Also Perma is right.
 
When I suggested this in another subforum, I was told it wouldn't work because it's addressing things that need to go to the RAM... to the RAM. Although I'm sure you're right, you just need plenty of RAM to do it. I can't find a source but some games like BF3 do use a given amount of Page File arbitrarily.


Could you perhaps post some bench results?

Also Perma is right.

Yes, disabling the page file is always an option, but if my memory serves me correctly all Windows does instead of writing to the page is to drop the data from memory, thus still requiring a read from the drive anyway....but I could be wrong about that, maybe a more tech savvy person than myself could tell us.

I can run the heaven bench if you like, although I don't think there will be any difference in performance. Will post back tomorrow once I get heaven installed, I'll also try and grab a few other benchmarks.

As for addressing things that need to be in RAM from RAM, this makes no difference to windows as it is unaware the drive is located in memory and treats it like a physical drive. All it knows is that they are under the same IRQ, but beyond this is will simply issue the command to move data from one block to another, something which happens in the GB/s. Where the advantage comes is the sheer I/O performance the page file now has, and given many of us have 12-16GB of memory (and given it only costs £100~ for that too) keeping the page file here should at the very least allow you to think you're not wasting half of it :D

[Super Edit] I was just looking into RAMDISK based Pagefiles and bumped into this, see post #3 at this link:
http://www.overclock.net/t/1193401/why-it-is-bad-to-store-the-page-file-on-a-ram-disk/20

He doesn't elaborate as to whether it fixed the stuttering in games, but it does fix video stuttering issues he has been having as well as stutter in game. I also cannot find an definitive information on how Windows 7 x64 manages memory without a pagefile other than speculations from various sources that data (pages) is only removed from memory upon request of the CPU/Program. I find this hard to believe, loading even a game such as BF3 or Skyrim would chomp up stupid amounts of memory. If anyone reading this thread knows, please let us know :)
 
Last edited:
Wow I was not expecting that to work as I tried so many drivers and tweaks to fix my Skyrim stutter but that actually did it! Thanks for the advice, great tip.
 
I doubt the fix is a result of the pagefile and this is just masking over another weak link in your system or misconfgiuration that affects your disk access.

What AV apps are you running?
SSDs or Crappy non-defragmented HDDs?
What SATA controllers are you using?
Are those controllers configured correctly? (AHCI instead of IDE f.ex)
 
Even if that's the case, one could argue that masking over the weak link (lets say it is crappy HDDs) is no bad thing if it improves performance at no cost.
 
This fix doesn't make sense =/ a pagefile is just used when there's no room left in ram. So putting the pagefile into the ram is just circular.... Disabling the pagefile would have the same result.
 
I'd assume most games can't address all your RAM though? I've tried disabling it before and the stutter was still there. At any rate I've no idea why this worked, my specs if anyone's interested in finding out why:

i7 950 @ 4.0
Asus p6x58d-e
Samsung 128 SSD running in ACHI on Sata 300
5970
12gb Dominator
AVG AV
 
I doubt the fix is a result of the pagefile and this is just masking over another weak link in your system or misconfgiuration that affects your disk access.

What AV apps are you running?
SSDs or Crappy non-defragmented HDDs?
What SATA controllers are you using?
Are those controllers configured correctly? (AHCI instead of IDE f.ex)

- No AV, no personal details are ever entered onto this machine and any sign of a virus it simply gets a full format
- 3x SSD's in Raid0 getting around 600MB/s read 450Mb/s write
- Jmicron controller in AHCI
 
This fix doesn't make sense =/ a pagefile is just used when there's no room left in ram. So putting the pagefile into the ram is just circular.... Disabling the pagefile would have the same result.

Actually the page file is used when a 4KB chunk of data in RAM (Known as a page) has not been accessed for a given amount of time, or is specifically requested by the CPU and/or program to be moved.
 
I doubt the fix is a result of the pagefile and this is just masking over another weak link in your system or misconfgiuration that affects your disk access.

What AV apps are you running?
SSDs or Crappy non-defragmented HDDs?
What SATA controllers are you using?
Are those controllers configured correctly? (AHCI instead of IDE f.ex)

non-defragmented -> fragmented ;)


I put a small pagefile on my main SSD, the access times are minimal so there's is no stuttering associated with reading from the drive.

There's been quite a few articles on why disabling the pagefile entirely is a bad idea.
 
I was getting a lot of stuttering in bf3, downloaded a user.cfg file with the following.

Renderdevice.forcerenderaheadlimit 1
renderdevice.triplebufferingenable 0

Cured the stuttering, game is now running as smooth as silk. From googling, it seems that stuttering is pretty common on both skyrim and bf3, particularly with the current nvidia 300 series beta drivers.
 
I was getting a lot of stuttering in bf3, downloaded a user.cfg file with the following.

Renderdevice.forcerenderaheadlimit 1
renderdevice.triplebufferingenable 0

Cured the stuttering, game is now running as smooth as silk. From googling, it seems that stuttering is pretty common on both skyrim and bf3, particularly with the current nvidia 300 series beta drivers.

Triple Buffering should be disabled by default anyway, unless you have vsync on.
 
I'd assume most games can't address all your RAM though? I've tried disabling it before and the stutter was still there. At any rate I've no idea why this worked, my specs if anyone's interested in finding out why:

i7 950 @ 4.0
Asus p6x58d-e
Samsung 128 SSD running in ACHI on Sata 300
5970
12gb Dominator
AVG AV

You're spot on, the vast majority of games are 32 bit and cannot address much more than 4GB of RAM, although they are often large address aware to compensate for being allocated memory above the 4GB range.

It's for this reason I think having a RAMDISK paging file in empty memory that will never/rarely be used on a gaming machine has to be worth a try in the least.

Just going to get the Heaven Benchmark now guys, I have a few dozen results from when I was doing my water cooling trials to compare too. I'm not expecting any sort of a drastic change.
 
Some very interesting Heaven results, I'm going to have to double check these because a 200 point boost with a lower cpu overclock makes no sense to me. If it is the RAMDISK pagefile, removing it will cause me to loose points. I'll post back in a half hour with the results of that test.

No RAMDKISK: i7 @ 4Ghz
i74GhzNoRAMDISK.png


RAMDISK: i7 @ 3.8Ghz
i738GhzRAMDISK.png


I will say this now however, there was no stuttering in this benchmark. In the 90+ runs I did over 4 months of trials with Mayhem Aurora coolants, I never once had this benchmark run without stuttering. Again, just to make sure this isn't a driver related fix, I will disable the RAMDISK and see what happens :D

[ninja edit]

Just ran it again with no RAMDISK Pagefile, the stuttering was back, but admittedly less than a few months ago so drivers probably have a lot to play with this benchmark, which stands to reason given the release of the 7k cards the drivers right now are heavily optimised for benchmarks :D.

No RAMDISK: i7 @ 3.8Ghz
i738GhzNoRAMDISK.png


[final edit] Just been playing BF3, can confirm that the stuttering returned once I removed the RAMDISK Pagefile.
 
Last edited:
Triple Buffering should be disabled by default anyway, unless you have vsync on.
No vsync on, nvidia driver 301.24 beta, fxaa on through nvidia inspector, i have 12gb of ram here, even before when i was using 6gb, never had ram issues.
 
- No AV, no personal details are ever entered onto this machine and any sign of a virus it simply gets a full format
- 3x SSD's in Raid0 getting around 600MB/s read 450Mb/s write
- Jmicron controller in AHCI

How can you be running RAID0 SSDs on a controller in AHCI mode? Software RAID?

Not really sure how good the Jmicron controller is but I am not sure I would want to run RAIDes SSDs on it. Not something I would even do now on an INtel controller until the latest ICH/Intel RST updates to support TRIM on them.

What SSDs are they? I would expect 3 in RAID-0 to outperform a single Current Gen SATA-III SSD.
 
Nvidia members have confirmed stuttering with 301 drivers and recommend the 300's not all suffer from this though and mainly the 580's and 680's
 
Back
Top Bottom