[SOLVED] Half-second stutter when loading in real-time in a lot of games

synthsequece

Prominent
Jun 30, 2017
4
0
520
Hi everyone,

I've been having this issue for a while and I'm really starting to lose my mind over it. Basically, in some games (about 30% of games I play at least, and I play a lot of different games), regardless of how demanding or old or optimised they may be, whenever something is loaded in real-time (ie, not during a loading screen, but say, a voice line that someone says) the game will stutter the first time it's loaded. Here's a few examples:

Killing Floor 2: Without fail, the first time I blow up an enemy's head it will ALWAYS stutter. It will also always stutter when I finish a game (as in win, I'm using the tutorial to test this as it's only 2 waves long).
Monster Hunter World: Will always without fail stutter whenever ANYONE faints, myself or otherwise. In fact I look for stutter now to see if someone's fainted rather than looking for messages. It's quite sad.
Resident Evil 6: It'll just stutter when someone says a voice line as part of the story.
Resident Evil Revelations 2: same as above.
Darksiders Warmastered Edition: It'll stutter when loading a new area.
Racedriver GRID (a game from 2007!): It'll stutter when my co-driver says something for the first time or when music begins to start playing. REALLY irritating as dramatic music always kicks in during the last 3 minutes of Le-Mans, which is a 24-minute race and it nearly always causes me to mess up.
The Longest Journey (FROM 1999!): Lags like every 3 or 4 voice lines, especially if I'm skipping them before they finish. In a game that's 80% listening to dialogue, it's irritating as hell.
Puyo Puyo Tetris: Whenever a new song starts playing. Incredibly frustrating in a game that needs to be stable at all times.
World of Final Fantasy: when opening some menus and when loading some voice lines.

When I say "loading" voice lines or music, I mean right before they play in the game. These are just some examples. These are tiny stutters, I'd say like a quarter to half of a second, but they're so damn frustrating. These are all different types of games from a nearly 20 year period. I could understand if it was just some of the later games, but The Longest Journey?!

The thing that annoys me the most is that it seems just random if a game will have this problem or not. I don't have any stutter in GRID 2, but in GRID 1 which is far less demanding I do? I can play Final Fantasy XIV, a modern MMO without a single sliver of lag, yet a POINT AND CLICK GAME FROM 1999 will lag on every third or fourth voice line? It never happens in Overwatch either, but it happens in Resident Evil 6 which is far less demanding.
NOTE: this is NOT a performance issue. I can run all these games on max settings and (with the exception of MHW) get framerates into triple digits consistently. It's the stuttering that's the issue.

DXDIAG: http://m.uploadedit.com/bbtc/1541159515797.txt

My specs:

GPU: Nvidia GTX 1070
RAM: 8GB
CPU: i5 4690K
HDD: 500GB SSD with OS, 3.6 GB HDD for storage
OS: Windows 10 Pro 64-bit 17134
MOBO: Gigabyte H97N WiFi
Monitor: ViewSonic VX2257

Honestly, I've tried so many different things that I've forgotten what I've tried, but here goes:


  • Defragging the drive the games are on (majority are on my HDD for storage reasons)
    Moving the games to my SSD to see if it's my HDD that's the problem (issue still happens)
    Replacing HDD (my current HDD is now less than 2 months old)
    Disabling all my sound devices (seeing as most of the lags are audio streaming related, didn't work)
    Using RAMMap to empty standby list (as suggested here https://www.reddit.com/r/Windows10/comments/8cdzsb/are_your_games_stuttering_lately/)
    Checking my temps - my CPU never goes over 70 and my GPU never goes over 80 (most demanding game is Monster Hunter World at the moment), I monitor my temps with GPUTemp and CoreTemp
    Making sure any power saving settings are turned off in BIOS, Windows 10 itself (Power Saving profiles have everything at max) and Nvidia control panel (ie using prefer maximum performance instead of power saving mode, et cetera)
    Fresh install of Windows 10
    Got a new aftermarket cooler for CPU and applied new thermal paste to CPU
    Video card drivers are up to date
    Turning adaptive vsync on and off
    Messing around with different Vsync options in general
    Changing my refresh rate to 60hz (default is 75hz)
    Turned off game DVR and all other Xbox garbage
    Run sfc scannow with all its variatins like a billion times
    Turned off diagnostic services
    Reinstalling the games
    I am definitely using my GPU and not my integrated graphics card (again, not a performance issue)
    DirectX runtime libraries are up to date
    Performing a clean boot - disabling all optional startup programs
    Trying safe mode

I'm willing to try anything else. If there's any other diagnostics I can run please let me know. If someone can troll through my dxdiag and spot something out of the ordinary that would be wonderful. Thanks in advance for the help.
 
Solution
Well, it's been 6 months and no-one's replied, but I haven't stopped trying. And I managed to resolve the issue. Please ignore above where I stated I tried moving games from my HDD to the SSD and it not fixing the issue. I don't think I tried this because the hitches went away when I moved games to my SSD.

The source of my issue was my HDD, but not a cable or age or damage or bad sectors or any of that usual garbage. If you have a WD blue this is a fault with HDD itself due to unwarranted hard baked power saving garbage, which as usual, completely f***s with gaming.

I fixed this using the solution from this thread:

But I also added my own bit...
Well, it's been 6 months and no-one's replied, but I haven't stopped trying. And I managed to resolve the issue. Please ignore above where I stated I tried moving games from my HDD to the SSD and it not fixing the issue. I don't think I tried this because the hitches went away when I moved games to my SSD.

The source of my issue was my HDD, but not a cable or age or damage or bad sectors or any of that usual garbage. If you have a WD blue this is a fault with HDD itself due to unwarranted hard baked power saving garbage, which as usual, completely f***s with gaming.

I fixed this using the solution from this thread:

But I also added my own bit. I managed to get the fix to run completely hidden using Task Scheduler. I didn't want an ugly CMD Window to be in the background constantly and also out of fear of closing it by accident.

1. If you choose to run it directly from your HDD (ie. double clicking the bat file from your HDD) it automatically changes the directory to where you're running it from. If you don't mind the black CMD window then you can ignore the rest of this fix.

2. Be sure to add the letter of the hard drive to the first line of the linked batch file code. In my case, my HDD is D:, so my code looks like this:

d:
:repeat
@Echo %RANDOM% > tmp.txt
ping -n 8 127.0.0.1 > NUL
goto repeat

The letter will be different depending on your setup so make sure you change it accordingly! This is important because if you run the task through Task Scheduler, it will run the code, but on your C: drive unless specifically stated otherwise. In other words, in my case it was executing this code on my SSD (C:), causing the issue to come back and frustrating me greatly.

3. Follow these instructions to run a task invisibly:
Scroll down to: Run A Silent Batch Script Using A Scheduled Task and follow the instructions.

Make sure you check the "Run whether user is logged on or not" check box or it will not hide the window, even if you have the "Hidden" box checked.

Hopefully if someone else has this issue it helps them. Just goes to show if you don't give up trying to fix something you'll get it eventually.

Thanks to Tom's Hardware user Solandri (https://forums.tomshardware.com/members/solandri.646978/) who offered a solution based on a wealth of personal experience and through actually listening to the original poster, instead of just listing useless generic fixes like "update your graphics driver" or "get another SSD lol".
 
Solution
Just keep in mind that your HDD is build to specific specs and it's circuitry might not be so cool with working all the time,also this does increase your writes on the disk although that should not be a big difference.

Cheers for your reply. Yeah, I figure having this run all the time will probably mean the hdd will die sooner. But hdds aren't that expensive nowadays and now I know to avoid WD blues and greens. I'll probably get a 7200rpm drive next time as well instead of a 5400rpm drive like the one I have now.

Thankfully there's nothing crucial on my hdd, just games which I can re download if something were to happen.