High end build, stuttering in every game

djanthony93 said:

Have you read about Rocket League? I'm getting 250 fps without Vsync, never go under 180~, why would the Vsync makes my fps unstable and cause that occasional stuttering? Also GTA V is giving me some random freezes even when Vsync is disabled, also when the stutter occurs it will not be recorded as an fps drop

I actually edited my response have you tried other GPU's in your machine to seeif it does the same ?

Another 1060 ?

solarstarshines said:

I actually edited my response have you tried other GPU's in your machine to seeif it does the same ?

Another 1060 ?

I have no other GPU or any other build unfortunally, is there any test to exclude it is a faulty hardware issue?

djanthony93 said:

I have no other GPU or any other build unfortunally, is there any test to exclude it is a faulty hardware issue?

Stuttering pretty much equals input lag there is bad communication between the Gpu and monitor so i would either test a solo monitor again none of the one's you have for gaming

Also the card could be starved for Power as well i would crank all voltages to max and see what it does

GPU Voltage and target voltage

slicendice said:

NOOO! DON't crank up your voltages to MAX...you could blow your GPU or something else too if not careful. But yes, monitor the voltages, as I have mentioned repeatedly. If you get a lot of swings then there might be some PSU issues or cable connection issues.

Do you even know what i am talking about ?

I am talking about GPU voltages that are safe to boost to max he can take his locked voltage and max it out as the same with his target voltage i know what i am talking about

Now as i was saying if you look at the photo of my Auros 1080ti i have it cranked to max it might need some extra juice and this will help with stability and possibly a undervolted card and make sure to use max power in Nvidia settings as well

slicendice said:

Yes I know exactly what I am talking about! As electrical engineering as a secondary hobby, I know that cranking up voltages can work, but you can also blow up your system, including the PSU. Start by monitoring the voltages at heavy load and ALWAYS increase them carefully. If there is a problem with the PSU or some cabling you might end up in completely fried computer, including PSU, MB, HDDS, GPU and CPU.

More of something is not always better, unless it is justified, but we have not seen any proof of more juice needed as of yet.

Depending on the board it should handle it and you know as a engineer which i am not you know there is a shut down protection before something goes haywire and that is actually dependent on the hardware he is using so far from his specs he is using a asus mobo and good ram

His psu shouldn't overload if it is a good one

slicendice said:

We need facts for this particular system. A trustworthy brand or PSU is not a fact for 100% of all devices with exactly the same configuration as the OP computer. There is variance in everything. First we need to collect all available stats, and then we can start adjusting something if justified.

A simple 3.3V reference can be anything from 3.2 - 3.4V at heavy load and can cause a lot of instability if it varies a lot. But we need proof of stability before we go into adjusting all parameters. It is just a matter of eliminating things that do work and focus on things that do not work.

Since the OP has no issue running benchmarks, the problem is most likely somewhere else.

Benchmarks don't have to run choppy to have a issue

Sometimes a Benchmark can be choppy due to non updated system files

Anyway the OP has tried pretty much everything besides that

Voltages are fine, there's no fluctuations.
From the DxDiag:

Windows Error Reporting:+++ WER0 +++:Bucket errato 129394945817, tipo 5Nome evento: RADAR_PRE_LEAK_WOW64Risposta: Non disponibileID CAB: 0Firma problema: P1: RocketLeague.exeP2: 1.0.10897.0P3: 10.0.15063.2.0.0P4: P5: P6: P7: P8: P9: P10: File allegati:\\?\C:\Users\Antonio\AppData\Local\Temp\RDR9E73.tmp\empty.txt\\?\C:\ProgramData\Microsoft\W indows\WER\Temp\WER9E74.tmp.WERInternalMetadata.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER 9E83.tmp.csv\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9E84.tmp.txtI file potrebbero essere disponibili qui:Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: 616993ab-0dce-44b5-afcd-85ef8b2b1022Stato rapporto: 268435456Bucket con hash: ebe64b0a75b297ebe8532d84b0080735+++ WER1 +++:Bucket errato 129552180573, tipo 5Nome evento: RADAR_PRE_LEAK_64Risposta: Non disponibileID CAB: 0Firma problema: P1: chrome.exeP2: 61.0.3163.79P3: 10.0.15063.2.0.0P4: P5: P6: P7: P8: P9: P10: File allegati:\\?\C:\Users\Antonio\AppData\Local\Temp\RDR43AE.tmp\empty.txt\\?\C:\ProgramData\Microsoft\W indows\WER\Temp\WER43BE.tmp.WERInternalMetadata.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER 43B9.tmp.csv\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER43CA.tmp.txtI file potrebbero essere disponibili qui:Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: d4c160c3-8483-419a-ae63-021e54b3e3c1Stato rapporto: 268435456Bucket con hash: 451b6ef6feac83e3532c3f00bc9a9c7c+++ WER2 +++:Bucket errato 129395444517, tipo 5Nome evento: RADAR_PRE_LEAK_WOW64Risposta: Non disponibileID CAB: 0Firma problema: P1: wmplayer.exeP2: 12.0.15063.0P3: 10.0.15063.2.0.0P4: P5: P6: P7: P8: P9: P10: File allegati:\\?\C:\Users\Antonio\AppData\Local\Temp\RDR7E79.tmp\empty.txt\\?\C:\ProgramData\Microsoft\W indows\WER\Temp\WER7E7A.tmp.WERInternalMetadata.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER 7E96.tmp.csv\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7E97.tmp.txtI file potrebbero essere disponibili qui:Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: e8312019-6940-4586-8e90-6ce77be616caStato rapporto: 268435456Bucket con hash: c045866e010ff04791926a9b8b8c577c+++ WER3 +++:Bucket errato 129545445456, tipo 5Nome evento: RADAR_PRE_LEAK_64Risposta: Non disponibileID CAB: 0Firma problema: P1: GTA5.exeP2: 1.0.1180.2P3: 10.0.15063.2.0.0P4: P5: P6: P7: P8: P9: P10: File allegati:\\?\C:\Users\Antonio\AppData\Local\Temp\RDR68B.tmp\empty.txt\\?\C:\ProgramData\Microsoft\Wi ndows\WER\Temp\WER69C.tmp.WERInternalMetadata.xml\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER69 B.tmp.csv\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AC.tmp.txtI file potrebbero essere disponibili qui:Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: cad407a4-29d2-4cfb-9c1b-c14d8cff0ae5Stato rapporto: 268435456Bucket con hash: 467e7553454fef33f964dbd1627a7538+++ WER4 +++:Bucket errato , tipo 0Nome evento: PnPDriverNotFoundRisposta: Non disponibileID CAB: 0Firma problema: P1: x64P2: USB\VID_1B1C&PID_0C09&REV_0100P3: P4: P5: P6: P7: P8: P9: P10: File allegati:I file potrebbero essere disponibili qui:C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_651e4c17bcfedffac615dfdfb3362fe 363257e7b_00000000_1d2840f1Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: 2d325147-84bb-4ce2-8ab6-ab58de2c37c7Stato rapporto: 4Bucket con hash: +++ WER5 +++:Bucket errato 109064257455, tipo 1Nome evento: APPCRASHRisposta: Non disponibileID CAB: 0Firma problema: P1: ATKEX_cmd.exeP2: 0.0.0.0P3: 00000000P4: KERNELBASE.dllP5: 10.0.15063.502P6: c3955624P7: 0eedfadeP8: 000eb802P9: P10: File allegati:\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD98D.tmp.WERInternalMetadata.xmlI file potrebbero essere disponibili qui:C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b7549db517dd2abcd2e932 dafc9814b938cb90_3ae784bb_151ede02Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: 3865d038-517b-440c-b2f7-218db50143e4Stato rapporto: 268435456Bucket con hash: d02eb9a273ef4b09b3ba965b989e98a4+++ WER6 +++:Bucket errato 109064257455, tipo 1Nome evento: APPCRASHRisposta: Non disponibileID CAB: 0Firma problema: P1: ATKEX_cmd.exeP2: 0.0.0.0P3: 00000000P4: KERNELBASE.dllP5: 10.0.15063.502P6: c3955624P7: 0eedfadeP8: 000eb802P9: P10: File allegati:\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B0.tmp.WERInternalMetadata.xmlI file potrebbero essere disponibili qui:C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b7549db517dd2abcd2e932 dafc9814b938cb90_3ae784bb_1bb1079cSimbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: 1be7412e-c0ff-41f8-8822-98cd1269441fStato rapporto: 268435456Bucket con hash: d02eb9a273ef4b09b3ba965b989e98a4+++ WER7 +++:Bucket errato 109064257455, tipo 1Nome evento: APPCRASHRisposta: Non disponibileID CAB: 0Firma problema: P1: ATKEX_cmd.exeP2: 0.0.0.0P3: 00000000P4: KERNELBASE.dllP5: 10.0.15063.502P6: c3955624P7: 0eedfadeP8: 000eb802P9: P10: File allegati:\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER144.tmp.WERInternalMetadata.xmlI file potrebbero essere disponibili qui:C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b7549db517dd2abcd2e932 dafc9814b938cb90_3ae784bb_1bb10421Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: 0fd0fd79-6935-47cb-afc2-8fdaf7f42676Stato rapporto: 268435456Bucket con hash: d02eb9a273ef4b09b3ba965b989e98a4+++ WER8 +++:Bucket errato 109064257455, tipo 1Nome evento: APPCRASHRisposta: Non disponibileID CAB: 0Firma problema: P1: ATKEX_cmd.exeP2: 0.0.0.0P3: 00000000P4: KERNELBASE.dllP5: 10.0.15063.502P6: c3955624P7: 0eedfadeP8: 000eb802P9: P10: File allegati:\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFD99.tmp.WERInternalMetadata.xmlI file potrebbero essere disponibili qui:C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ATKEX_cmd.exe_b7549db517dd2abcd2e932 dafc9814b938cb90_3ae784bb_1bb100b6Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: 2276818d-6a62-4810-a41a-ec6c65054467Stato rapporto: 268435456Bucket con hash: d02eb9a273ef4b09b3ba965b989e98a4+++ WER9 +++:Bucket errato , tipo 0Nome evento: APPCRASHRisposta: Non disponibileID CAB: 0Firma problema: P1: ATKEX_cmd.exeP2: 0.0.0.0P3: 00000000P4: KERNELBASE.dllP5: 10.0.15063.502P6: c3955624P7: 0eedfadeP8: 000eb802P9: P10: File allegati:I file potrebbero essere disponibili qui:C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ATKEX_cmd.exe_b7549db517dd2abcd2e932da fc9814b938cb90_3ae784bb_1be0fdb9Simbolo analisi: Nuova ricerca di soluzioni: 0ID rapporto: 3865d038-517b-440c-b2f7-218db50143e4Stato rapporto: 4Bucket con hash: