problema audio che salta e/o lag nei giochi

[van-hallow]

Salve da pochissimo tempo ha iniziato a dare questi sintomi , su you tube audio che salta per una manciata di secondi e nei giochi invece si ha un mega laggone guardando da afterburner si vede proprio l'utilizzo della gtx 970 che passa da 99% al 10 % se non erro comunque si vede proprio che "salta" da 60 fps si passa a 25 . I giochi di steam stanno su un altro disco , ma per esclusione dove ho il problema che salta anche su firefox che sta su ssd non credo siano problemi di dischi malfunzioananti. Aggiornato driver scheda video al 26/11/2019. Alimentatore credo proprio da scartare ho un evga g2 750w . windows 8.1 con chiave originale e aggiornato.
Cosa può essere ? :(

[aled1974]

che altri programmi stanno lavorando in background?

anche quelli magari a tua insaputa, per dire, potrebbe anche essere un miner che utilizza il tuo pc per minare cryptovalue per altri

controlla ad ogni modo lo stato di salute di tutti i dischi tramite crystaldiskinfo, valori decimali, ci perdi pochi secondi e ti togli i dubbi definitivamente ;)

ciao ciao

[van-hallow]

che altri programmi stanno lavorando in background?

anche quelli magari a tua insaputa, per dire, potrebbe anche essere un miner che utilizza il tuo pc per minare cryptovalue per altri

controlla ad ogni modo lo stato di salute di tutti i dischi tramite crystaldiskinfo, valori decimali, ci perdi pochi secondi e ti togli i dubbi definitivamente ;)

ciao ciao

Salve , fatto una passata di malwarebytes su ssd e hdd dove sono i giochi nessun problema rilevato , monitorato in background e niente nessun processo anomalo . Usato cristaldiskinfo e lo stato dei dischi da buono sia ssd che hdd giochi . Poco fa ho giocato a mgsv e nessun lag ma la scheda video veniva usata massimo all'80% non è un gioco pesante , mafia 3 invece va al 99% quindi sfrutta di più . Ma non credo sia problema di scheda video no ? come la posso provare per vedere se il clock sotto stress scende ? o è problema di windows ?

[FulValBot]

prendi superantispyware free


ricorda che malwarebytes nella versione free ha qualche mancanza nelle scansioni


sarebbe da controllare se i vari dischi siano in modalità ultra dma e non pio (quest'ultima provoca caricamenti lunghissimi, audio gracchiante e mouse che scatta)

[van-hallow]

prendi superantispyware free


ricorda che malwarebytes nella versione free ha qualche mancanza nelle scansioni

Ok grazie proverò questo programma , in idle comunque siamo al 0% massimo 2 % di utilizzo cpu . fatto stessa scansione anche con avast e anche li zero minacce rilevate.

[FulValBot]

meglio evitare avast con windows 10

[van-hallow]

meglio evitare avast con windows 10

Non ho windows 10 , ma 8.1 . Windows 10 sino a quando non avrò il pc nuovo l'anno nuovo(e li per forza devo avere quel sistema per hardware nuovo)se lo posso evitare lo evito . Fatto partire la scansione con superantispyware.
Curiosità come mai evitare avast con windows 10 ?

[van-hallow]

aggiorno eseguito la scansione con superantispyware free ha trovato solo 14 adware sulle cache di firefox e qualcosa nei temp nulla di più . Gli altri dischi puliti . Stasera gioco e vediamo come si comporta.

[van-hallow]

Niente da fare ancora drop fps nei giochi , mi sono accorto in quelli meno esosi ad esempio lol salta l'audio ma gli fps sono stabili al contrario dove la scheda video è messa sotto stress drop fps ma audio non salta . Provato anche a deframmentare i dischi nulla si è risolto . Mi rimane a questo punto la formattazione per forza uff.

[Blue_screen_of_death]

Salve da pochissimo tempo ha iniziato a dare questi sintomi , su you tube audio che salta per una manciata di secondi e nei giochi invece si ha un mega laggone guardando da afterburner si vede proprio l'utilizzo della gtx 970 che passa da 99% al 10 % se non erro comunque si vede proprio che "salta" da 60 fps si passa a 25 . I giochi di steam stanno su un altro disco , ma per esclusione dove ho il problema che salta anche su firefox che sta su ssd non credo siano problemi di dischi malfunzioananti. Aggiornato driver scheda video al 26/11/2019. Alimentatore credo proprio da scartare ho un evga g2 750w . windows 8.1 con chiave originale e aggiornato.
Cosa può essere ? :(

E' un problema legato alla gestione delle procedure DPC / ISR da parte del kernel di Windows, che porta a sottoutilizzare le risorse disponibili.
Le cause possono essere diverse: bug in un driver installato, hardware danneggiato, virus, incompatibilità hardware o software.

Per scoprire la causa, scarica LatencyMon https://www.resplendence.com/latencymon, che è un tool che monitora i driver e alcuni parametri del sistema operativo.
Avvia il monitoraggio (tastino play in alto)
Lascialo aperto, e usa il PC normalmente / gioca.
Al primo lag, ferma il monitoraggio di LatencyMon, salva il report e mandamelo.

P.S. Che componenti monta il PC?

[van-hallow]

E' un problema legato alla gestione delle procedure DPC / ISR da parte del kernel di Windows, che porta a sottoutilizzare le risorse disponibili.
Le cause possono essere diverse: bug in un driver installato, hardware danneggiato, virus, incompatibilità hardware o software.

Per scoprire la causa, scarica LatencyMon https://www.resplendence.com/latencymon, che è un tool che monitora i driver e alcuni parametri del sistema operativo.
Avvia il monitoraggio (tastino play in alto)
Lascialo aperto, e usa il PC normalmente / gioca.
Al primo lag, ferma il monitoraggio di LatencyMon, salva il report e mandamelo.

P.S. Che componenti monta il PC?
Ottimo , subito nel dopo pranzo provo . Componenti sono msi big bang xpower 2 4960x stock gtx 970 g1 gaming (cpu e gou raffreddate a liquido custom) ssd ci sta windows e giochi stanno su un hdd meccanico. Ho questo pc da 4 anni cosi e con queste impostazioni mai avuto problemi di nessun tipo anzi solo soddisfazioni . Tutto questo è capitato da circa una settimana .
Edit: Dimenticavo se faccio partire degli stress test non so ad esempio firestrike o ungine nessun problema :O .

[van-hallow]

E' un problema legato alla gestione delle procedure DPC / ISR da parte del kernel di Windows, che porta a sottoutilizzare le risorse disponibili.
Le cause possono essere diverse: bug in un driver installato, hardware danneggiato, virus, incompatibilità hardware o software.

Per scoprire la causa, scarica LatencyMon https://www.resplendence.com/latencymon, che è un tool che monitora i driver e alcuni parametri del sistema operativo.
Avvia il monitoraggio (tastino play in alto)
Lascialo aperto, e usa il PC normalmente / gioca.
Al primo lag, ferma il monitoraggio di LatencyMon, salva il report e mandamelo.

P.S. Che componenti monta il PC?

Ecco il risultato su lol di questo salto audio , su mafia 3 non me lo ha fatto (sempre cosi quando uno vuole che si presenti il difetto ahah non esce) ieri era ogni due tre.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. 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 0:21:07 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: 4960X
OS version: Windows 8.1 , 6.3, build: 9600 (x64)
Hardware: MS-7737, MSI, Big Bang-XPower II (MS-7737)
CPU: GenuineIntel Intel(R) Core(TM) i7-4960X CPU @ 3.60GHz
Logical processors: 12
Processor groups: 1
RAM: 16297 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 2354,633790
Average measured interrupt to process latency (µs): 5,963284

Highest measured interrupt to DPC latency (µs): 2352,073787
Average measured interrupt to DPC latency (µs): 0,701152


_________________________________________________________________________________________________________
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): 150,670
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,108363

ISR count (execution time <250 µs): 1510752
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
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): 1617,835833
Driver with highest DPC routine execution time: USBPORT.SYS - Driver porta USB 1.1 & 2.0, Microsoft Corporation

Highest reported total DPC routine time (%): 0,036589
Driver with highest DPC total execution time: USBPORT.SYS - Driver porta USB 1.1 & 2.0, Microsoft Corporation

Total time spent in DPCs (%) 0,12710

DPC count (execution time <250 µs): 5472975
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 28
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: firefox.exe

Total number of hard pagefaults 3140
Hard pagefault count of hardest hit process: 2029
Number of processes hit: 12


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 19,240647
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 792,463333
CPU 0 DPC total execution time (s): 2,080233
CPU 0 DPC count: 2107632
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 49,244703
CPU 1 ISR highest execution time (µs): 150,670
CPU 1 ISR total execution time (s): 13,796296
CPU 1 ISR count: 928825
CPU 1 DPC highest execution time (µs): 488,876667
CPU 1 DPC total execution time (s): 7,337925
CPU 1 DPC count: 1862639
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 36,884261
CPU 2 ISR highest execution time (µs): 107,845556
CPU 2 ISR total execution time (s): 2,657578
CPU 2 ISR count: 576849
CPU 2 DPC highest execution time (µs): 1617,835833
CPU 2 DPC total execution time (s): 9,685657
CPU 2 DPC count: 1449803
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 8,218514
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 205,135556
CPU 3 DPC total execution time (s): 0,005153
CPU 3 DPC count: 1298
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 9,00970
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 139,560833
CPU 4 DPC total execution time (s): 0,053608
CPU 4 DPC count: 17411
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 8,586763
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 56,398333
CPU 5 DPC total execution time (s): 0,003507
CPU 5 DPC count: 878
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 7,766445
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 67,254167
CPU 6 DPC total execution time (s): 0,103282
CPU 6 DPC count: 17447
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 7,164206
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 73,35250
CPU 7 DPC total execution time (s): 0,002743
CPU 7 DPC count: 621
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 7,141245
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 40,889167
CPU 8 DPC total execution time (s): 0,011778
CPU 8 DPC count: 3064
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 9,472270
CPU 9 ISR highest execution time (µs): 29,550833
CPU 9 ISR total execution time (s): 0,022572
CPU 9 ISR count: 5067
CPU 9 DPC highest execution time (µs): 81,844444
CPU 9 DPC total execution time (s): 0,015105
CPU 9 DPC count: 6379
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 8,424238
CPU 10 ISR highest execution time (µs): 12,960
CPU 10 ISR total execution time (s): 0,00010
CPU 10 ISR count: 11
CPU 10 DPC highest execution time (µs): 120,834167
CPU 10 DPC total execution time (s): 0,016928
CPU 10 DPC count: 3270
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 9,392503
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 103,009722
CPU 11 DPC total execution time (s): 0,009598
CPU 11 DPC count: 2562
_________________________________________________________________________________________________________

[Blue_screen_of_death]

OK, la causa dovrebbe essere il driver USB o una periferica collegata ad una porta USB, che tiene impegnato il processore per troppo tempo.

- Che periferiche USB hai?
- Che driver USB hai installato? Quello fornito dal vendor della scheda madre, il driver di Windows o il driver fornito dal produttore del controller USB? E' aggiornato all'ultima versione disponibile?

[van-hallow]

OK, la causa dovrebbe essere il driver USB o una periferica collegata ad una porta USB, che tiene impegnato il processore per troppo tempo.

- Che periferiche USB hai?
- Che driver USB hai installato? Quello fornito dal vendor della scheda madre, il driver di Windows o il driver fornito dal produttore del controller USB? E' aggiornato all'ultima versione disponibile?

Allora alle porte usb della scheda madre c'è il microfono- joypad -pen drive wifi- mouse - un hub usb con attaccato un altro mouse . Adesso faccio dei test con un hub usb staccato . Per il driver delle porte usb c'è quello di default di windows per le 3.0 quello della scheda madre ma non c'è collegato niente li solo una piccola prolunga che la uso alla bisogna.

[van-hallow]

Questo e con mafia 3 si è finalmente mostrato il problema l'utilizzo gpu dal 99% può scendere al 50 con minimi di 20 % . ecco il report


_________________________________________________________________________________________________________
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 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 0:03:58 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: 4960X
OS version: Windows 8.1 , 6.3, build: 9600 (x64)
Hardware: MS-7737, MSI, Big Bang-XPower II (MS-7737)
CPU: GenuineIntel Intel(R) Core(TM) i7-4960X CPU @ 3.60GHz
Logical processors: 12
Processor groups: 1
RAM: 16297 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 1868,517682
Average measured interrupt to process latency (µs): 4,496487

Highest measured interrupt to DPC latency (µs): 1866,242123
Average measured interrupt to DPC latency (µs): 0,554181


_________________________________________________________________________________________________________
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): 116,601667
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,045868

ISR count (execution time <250 µs): 74962
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
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): 252,730833
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 441.41 , NVIDIA Corporation

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

Total time spent in DPCs (%) 0,049241

DPC count (execution time <250 µs): 424906
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 0
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: mafia3.exe

Total number of hard pagefaults 23
Hard pagefault count of hardest hit process: 12
Number of processes hit: 3


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 2,593544
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 139,220833
CPU 0 DPC total execution time (s): 0,157552
CPU 0 DPC count: 234673
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 8,820221
CPU 1 ISR highest execution time (µs): 116,601667
CPU 1 ISR total execution time (s): 1,294198
CPU 1 ISR count: 70600
CPU 1 DPC highest execution time (µs): 252,730833
CPU 1 DPC total execution time (s): 1,106973
CPU 1 DPC count: 141675
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,804752
CPU 2 ISR highest execution time (µs): 106,750
CPU 2 ISR total execution time (s): 0,001704
CPU 2 ISR count: 219
CPU 2 DPC highest execution time (µs): 139,619167
CPU 2 DPC total execution time (s): 0,013922
CPU 2 DPC count: 4952
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1,611703
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 33,826667
CPU 3 DPC total execution time (s): 0,003690
CPU 3 DPC count: 3077
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1,486055
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 42,57750
CPU 4 DPC total execution time (s): 0,009924
CPU 4 DPC count: 5078
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1,413871
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 24,8050
CPU 5 DPC total execution time (s): 0,001589
CPU 5 DPC count: 1087
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,923920
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 85,413333
CPU 6 DPC total execution time (s): 0,068177
CPU 6 DPC count: 15779
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,329346
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 55,640833
CPU 7 DPC total execution time (s): 0,003098
CPU 7 DPC count: 4025
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 1,307521
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 40,708889
CPU 8 DPC total execution time (s): 0,003329
CPU 8 DPC count: 2008
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 1,906549
CPU 9 ISR highest execution time (µs): 29,678889
CPU 9 ISR total execution time (s): 0,015714
CPU 9 ISR count: 3833
CPU 9 DPC highest execution time (µs): 60,631667
CPU 9 DPC total execution time (s): 0,024656
CPU 9 DPC count: 7063
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,393917
CPU 10 ISR highest execution time (µs): 14,83250
CPU 10 ISR total execution time (s): 0,002413
CPU 10 ISR count: 310
CPU 10 DPC highest execution time (µs): 42,56750
CPU 10 DPC total execution time (s): 0,013660
CPU 10 DPC count: 4142
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1,231621
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 35,10250
CPU 11 DPC total execution time (s): 0,004103
CPU 11 DPC count: 1348
_________________________________________________________________________________________________________

[Blue_screen_of_death]

L'ultimo report cattura il lag? Ovvero latency mon era in play quando si è verificato il lag?
Chiedo perché vedo che ha girato solo 3 minuti.
Quanto durano questi lag nei giochi?

[van-hallow]

L'ultimo report cattura il lag? Ovvero latency mon era in play quando si è verificato il lag?
Chiedo perché vedo che ha girato solo 3 minuti.
Quanto durano questi lag nei giochi?

Si latency mod era aperto e ha catturato quel fastidiosissimo lag .Quindi ho visto che mi ha riprodotto il lag (durano un secondo circa) ne ha fatti un 4/5 ho chiuso il gioco fatto stop su latency mod e copiato il report qui .

[Blue_screen_of_death]

ok, dai log vedo due potenziali problemi:
- un driver o periferica USB tiene impegnata la CPU per troppo tempo
- il numero di hard page fault è alto, considerando che hai monitorato solo per 3 minuti

I task da compiere sono questi:
- Aggiornare i driver USB
- Scollegare tutte le periferiche USB e vedere se il problema sparisce; in particolare, verifica che non dipende dal joypad
- Disabilitare il risparmio energetico delle periferiche USB in Gestione dispositivi
- Verificare che la RAM utilizzabile e RAM disponibile coincidono (WIN+PAUSA -> Accanto alla RAM disponibile viene riportata anche una voce RAM utilizzabile?)
- Provare a disattivare il file di paging e verificare se il problema sparisce

[van-hallow]

ok, dai log vedo due potenziali problemi:
- un driver o periferica USB tiene impegnata la CPU per troppo tempo
- il numero di hard page fault è alto, considerando che hai monitorato solo per 3 minuti

I task da compiere sono questi:
- Aggiornare i driver USB
- Scollegare tutte le periferiche USB e vedere se il problema sparisce; in particolare, verifica che non dipende dal joypad
- Disabilitare il risparmio energetico delle periferiche USB in Gestione dispositivi
- Verificare che la RAM utilizzabile e RAM disponibile coincidono (WIN+PAUSA -> Accanto alla RAM disponibile viene riportata anche una voce RAM utilizzabile?)
- Provare a disattivare il file di paging e verificare se il problema sparisce

Allora partiamo con ordine , intanto cosa sono i hard page fault ?

-come faccio ad aggiornare i driver usb ? sulla pagina della scheda madre dal sito produttore non c'è nessun driver relativo alle usb e/o 3.0
- ok proverò a lasciare solo il mouse e il microfono
-da gestione dispositivi come perifierica viene vista periferica xbox , se guardiamo controller usb ci sono tante voci.
-accanto alla ram disponibile che è 16 gb non risulta utilizzabile (se non erro quella voce c'è quando si ha una scheda video inegrata alla cpu)
-il file di paging lo avevo disabilitato ma per forza di cose lo dovuto riattivare per i giochi dove davano errori in merito proprio a questo file di paging nonostante tutto abbia 16 gb di ram . Stasera provo a giocare ma senza hub attaccato vediamo cosa cambia , se vedo che gli hard page sono ancora alti rimango con il mouse e microfono.
Intanto grazie tante dell'aiuto che mi stai dando :) , se posso evitare la formattazione è un grande sollievo . Anche perchè mi sa tanto un problema software , l'hardware sta bene.

[van-hallow]

oggi il problema si è presentato in maniera molto marcata su lol e ho catturato tutto sul report di latency , lo stesso programma dice che ci sono problemi infatti. Allego il report. Se non erro sono un 17 min con lol e lo ha fatto un sacco di volte il "salto dell'audio" e qualche lagghettino sporadico.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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 0:16:41 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: 4960X
OS version: Windows 8.1 , 6.3, build: 9600 (x64)
Hardware: MS-7737, MSI, Big Bang-XPower II (MS-7737)
CPU: GenuineIntel Intel(R) Core(TM) i7-4960X CPU @ 3.60GHz
Logical processors: 12
Processor groups: 1
RAM: 16297 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 2459,023621
Average measured interrupt to process latency (µs): 5,395695

Highest measured interrupt to DPC latency (µs): 2456,748064
Average measured interrupt to DPC latency (µs): 0,651302


_________________________________________________________________________________________________________
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): 819,45750
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,130885

ISR count (execution time <250 µs): 1497288
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 28
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): 1039,228333
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

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

Total time spent in DPCs (%) 0,137040

DPC count (execution time <250 µs): 4620902
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 51
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: aswidsagent.exe

Total number of hard pagefaults 29098
Hard pagefault count of hardest hit process: 11299
Number of processes hit: 21


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 9,668553
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 176,40250
CPU 0 DPC total execution time (s): 0,840952
CPU 0 DPC count: 1051044
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 43,562759
CPU 1 ISR highest execution time (µs): 819,45750
CPU 1 ISR total execution time (s): 13,234104
CPU 1 ISR count: 935690
CPU 1 DPC highest execution time (µs): 611,289167
CPU 1 DPC total execution time (s): 7,179081
CPU 1 DPC count: 1884386
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 29,362865
CPU 2 ISR highest execution time (µs): 55,535833
CPU 2 ISR total execution time (s): 2,411304
CPU 2 ISR count: 547325
CPU 2 DPC highest execution time (µs): 1039,228333
CPU 2 DPC total execution time (s): 7,745569
CPU 2 DPC count: 1522221
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 6,082787
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 62,13750
CPU 3 DPC total execution time (s): 0,003640
CPU 3 DPC count: 3073
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 7,213569
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 50,944167
CPU 4 DPC total execution time (s): 0,007107
CPU 4 DPC count: 4881
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 5,634447
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 47,210
CPU 5 DPC total execution time (s): 0,003178
CPU 5 DPC count: 3091
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 6,167212
CPU 6 ISR highest execution time (µs): 313,146667
CPU 6 ISR total execution time (s): 0,005933
CPU 6 ISR count: 57
CPU 6 DPC highest execution time (µs): 335,5650
CPU 6 DPC total execution time (s): 0,316933
CPU 6 DPC count: 85610
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 5,655314
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 53,520833
CPU 7 DPC total execution time (s): 0,002283
CPU 7 DPC count: 2826
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 4,534107
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 318,410
CPU 8 DPC total execution time (s): 0,021507
CPU 8 DPC count: 8123
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 9,023113
CPU 9 ISR highest execution time (µs): 47,172222
CPU 9 ISR total execution time (s): 0,070214
CPU 9 ISR count: 14199
CPU 9 DPC highest execution time (µs): 62,439167
CPU 9 DPC total execution time (s): 0,302152
CPU 9 DPC count: 41242
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 5,659483
CPU 10 ISR highest execution time (µs): 12,675833
CPU 10 ISR total execution time (s): 0,000388
CPU 10 ISR count: 45
CPU 10 DPC highest execution time (µs): 54,340
CPU 10 DPC total execution time (s): 0,010661
CPU 10 DPC count: 5549
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 8,517690
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 103,17750
CPU 11 DPC total execution time (s): 0,028195
CPU 11 DPC count: 8908
_________________________________________________________________________________________________________

[Blue_screen_of_death]

Che antivirus stai usando?
Nei post precedenti avevi parlato di Avast, ma nell'ultimo report vedo aswidsagent, che dovrebbe essere l'agent di AVG.

[van-hallow]

Che antivirus stai usando?
Nei post precedenti avevi parlato di Avast, ma nell'ultimo report vedo aswidsagent, che dovrebbe essere l'agent di AVG.

Si sto usando avast , aswidsagent è proprio avast ho cercato poco fa ma è anche riconducibile a avg . Non so ma vedo la formattazzione sempre più vicina :S

[Blue_screen_of_death]

Disattiva tutti i programmi in Gestione attività -> scheda Avvio e tutti i servizi non Microsoft in msconfig -> Scheda Servizi (spunta Nascondi i servizi Microsoft), incluso Avast.

Riavvia il PC e vedi se il problema sparisce.

Se il problema persiste, prova a disabilitare il pagefile.


Il consumo di RAM mentre giochi com'è?

[van-hallow]

Disattiva tutti i programmi in Gestione attività -> scheda Avvio e tutti i servizi non Microsoft in msconfig -> Scheda Servizi (spunta Nascondi i servizi Microsoft), incluso Avast.

Riavvia il PC e vedi se il problema sparisce.

Se il problema persiste, prova a disabilitare il pagefile.


Il consumo di RAM mentre giochi com'è?

Il consumo di ram è nella norma quando gioco sono a 8 gb occupati , provato anche ad avere un avvio pulito e i servizi necessari . PEr disperato ho formattato ho perso giusto 30 min (qualche rogna la sto avendo con il codice di attivazione) e appena installo tutto tutto (ieri ho giocato un 30min e pare tutto ok) vedo dopo gli aggiornamenti di windows se riesco ad attivare il mio codice .
grazie tantissimo dell'aiuto , a lol lo installato a sto giro nell'ssd . gli altri giochi steam sempre sul hdd

[van-hallow]

aggiorno giusto per far sapere come è andata . Per il codice di attivazione nulla da fare lo dovuto ricomprare -_- . Per il resto funziona tutto come prima :) . Grazie a tutti dell'aiuto .