gtx 970 stutters in all texture loadings!

FX8370E VARIANT have the thermal margin annouced at 71 in amd website in comparison to 8350 or 8370. And, as i said, with no overclock, the temps barely hit 55 and i still have the stutter

About the SSD, I dont have the money and dont think it is a much viable solution. With games always hitting the 30, 50gb mark, it will only resolve the problem in some cases. And the other problem is that the possibility of not being storage disk related is high, because the change of HDd that i did recently speed up my pc big time in gerenal usage, but the stutters remain the same

Interesting. But money is still a problem, especially being a brazilian student. I was afraid that could be gpu related because 2 of my friend have the same gpu but from zotac instead of galax, and not factory overclocked

yes. in pubg or rocket league, even when set on Low, it still happens

More tests done:
-switched PCIe slot. nothing.
-overvolted gpu. Nothing.
-overclocked +50Mhz (reaching a constant and stable 1442Mhz. Nothing........

I really don't know what to do.

i've made the test for 1.20 hours 2 times.
both messages received are the same. between the two, I have tried to lower the CPU clock to 4.0 and increase voltage, the temps didnt even reached 60 in CPU and same in motherboard. HWmonitor just registered a minimum clock of 3900MHz and the max CPU usage was 93%.

in the second attempt, i've activated HPC in bios, which prevents drop in clocks. all power saving features are disabled in BIOS and windows, that is running in high performance mode, with 100% min and max performaance of cpu.

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 1:26:53 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: JON
OS version: Windows 10 , 10.0, build: 17134 (x64)
Hardware: Gigabyte Technology Co., Ltd., 970A-UD3P
CPU: AuthenticAMD AMD FX-8370E Eight-Core Processor
Logical processors: 8
Processor groups: 1
RAM: 16350 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 4019 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 1158.527131
Average measured interrupt to process latency (µs): 12.870169

Highest measured interrupt to DPC latency (µs): 1148.190622
Average measured interrupt to DPC latency (µs): 6.040970


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 916.152028
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Highest reported total ISR routine time (%): 0.140490
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.181294

ISR count (execution time <250 µs): 5155534
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 231
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 1147.565812
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 398.11 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0.097522
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.499684

DPC count (execution time <250 µs): 22614108
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1456
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: tslgame.exe

Total number of hard pagefaults 28642
Hard pagefault count of hardest hit process: 14316
Number of processes hit: 45


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 527.935698
CPU 0 ISR highest execution time (µs): 916.152028
CPU 0 ISR total execution time (s): 61.491098
CPU 0 ISR count: 3669027
CPU 0 DPC highest execution time (µs): 1147.565812
CPU 0 DPC total execution time (s): 162.665820
CPU 0 DPC count: 19470903
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 211.836239
CPU 1 ISR highest execution time (µs): 565.971137
CPU 1 ISR total execution time (s): 13.958352
CPU 1 ISR count: 1469683
CPU 1 DPC highest execution time (µs): 570.933068
CPU 1 DPC total execution time (s): 38.460570
CPU 1 DPC count: 2593339
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 72.476160
CPU 2 ISR highest execution time (µs): 388.434685
CPU 2 ISR total execution time (s): 0.156318
CPU 2 ISR count: 16738
CPU 2 DPC highest execution time (µs): 386.374720
CPU 2 DPC total execution time (s): 1.183256
CPU 2 DPC count: 107997
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 66.965096
CPU 3 ISR highest execution time (µs): 409.787261
CPU 3 ISR total execution time (s): 0.000707
CPU 3 ISR count: 59
CPU 3 DPC highest execution time (µs): 212.769097
CPU 3 DPC total execution time (s): 0.668184
CPU 3 DPC count: 61970
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 80.025376
CPU 4 ISR highest execution time (µs): 26.832048
CPU 4 ISR total execution time (s): 0.000089
CPU 4 ISR count: 37
CPU 4 DPC highest execution time (µs): 233.540931
CPU 4 DPC total execution time (s): 1.788183
CPU 4 DPC count: 126202
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 77.869111
CPU 5 ISR highest execution time (µs): 4.857925
CPU 5 ISR total execution time (s): 0.000049
CPU 5 ISR count: 29
CPU 5 DPC highest execution time (µs): 289.153770
CPU 5 DPC total execution time (s): 1.057017
CPU 5 DPC count: 74711
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 83.123744
CPU 6 ISR highest execution time (µs): 3.789998
CPU 6 ISR total execution time (s): 0.000053
CPU 6 ISR count: 32
CPU 6 DPC highest execution time (µs): 220.367007
CPU 6 DPC total execution time (s): 1.717556
CPU 6 DPC count: 121764
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 74.493530
CPU 7 ISR highest execution time (µs): 8.332919
CPU 7 ISR total execution time (s): 0.000303
CPU 7 ISR count: 160
CPU 7 DPC highest execution time (µs): 212.283901
CPU 7 DPC total execution time (s): 0.848089
CPU 7 DPC count: 58679
_________________________________________________________________________________________________________

hello again!
Tried the above yesterday, did a clean install of just what was needed, but, unfortunately, the results were the same...
i've just finished to "repair" my windows - formating but maintaining apps and docs - (it is not a solution but there's so much things that i can't save right now to hard format again)
Another test that i've done is to unplug my old crappy 1.5 tb HDD. aaaaaaaaaaaaaand... same

sometimes i think that is something software related, because, randomly/usually the desktop tends to blink, like if it was refreshing or something like that. But I really don't know what more to do...
Maybe one day, with more time, i could try open the PC and reconect everything. but, after all of that, i just doubt that it would resolve anything

I've managed to record through my phone some clips where it happens very clearly - sorry for the bad image quality and the invertion in some clips -

https://www.youtube.com/watch?v=GYWsCvrc7V4&feature=youtu.be

currently i am playing at 1920x1080. but, i just tested now increasing the resolution through nvidia control panel, decreasing it to below full HD and even trying a VGA cable instead of HDMI. the results, if different, are almost unspottable

the sadest thing is that it is not exceeding. or, in some games that it exceeds, it not happens. Assetto corsa with ultra graphics and 20 cars on track, it doesnt happen. in others, like rocket league (even on lowest setting and with lower resolution) it happens

PS: just tested unpluging my mouse logitech, my usb headset. same results. Tried to convert disk, GDP to MBR. no luck.

i can't say for sure, because these stutters are so much predictable. it always happens at the same places and times.
These are some prints of exact moments when it occurred. the biggest drop is the "literal loading moment", when entering the match. the stutters are the spikes Just before the big drop.
http://prntscr.com/k8m5om
http://prntscr.com/k8m6fp
http://prntscr.com/k8m6j1