View Full Version : Piccoli freeze durante uso del pc
Buonasera,
scrivo qui ma non so è la sezione giusta. Ho un problema con il mio pc:
AMD ryzen 5 1600
RX 580 8gb
Gygabyte ax370 k3 gaming.
Praticamente ogni tanto mi vengono dei mini freeze di anche un secondo o meno in cui si blocca l'audio e video e poi riparte (suono tipo gracchiante). anche quando navigo normalmente o guardo video. Cosa può essere? ho 3 hard disk sata collegati e il principale ssd. Ho notato che quando aprivo CrystalDiskInfo me lo faceva quindi ho pensato fosse un problema di qualche disco è possibile? grazie mille
Blue_screen_of_death
03-10-2019, 21:13
Una routine DPC o ISR lenta. Dobbiamo capire a quale driver o periferica appartiene.
Scarica LatencyMon
Clicca su Start Monitor per avviare il monitoraggio dei driver
Attendi che si verifica un freeze (se riesci puoi anche replicare le operazioni che lo causano)
Clicca su Stop
Edit -> Copy report text to clipboard
Incolla il report in un messaggio di risposta
allora ho provato per un'oretta ma non mi ha fatto niente comunque copio lo stesso.
_________________________________________________________________________________________________________
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 1:20:38 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 100776,30
Average measured interrupt to process latency (µs): 7,814270
Highest measured interrupt to DPC latency (µs): 100763,40
Average measured interrupt to DPC latency (µs): 4,299982
_________________________________________________________________________________________________________
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): 306,080
Driver with highest ISR routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Highest reported total ISR routine time (%): 0,008869
Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Total time spent in ISRs (%) 0,014508
ISR count (execution time <250 µs): 4344987
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 2
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): 1052,250
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Highest reported total DPC routine time (%): 0,017558
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,054327
DPC count (execution time <250 µs): 10743975
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1506
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: gamebar.exe
Total number of hard pagefaults 7015
Hard pagefault count of hardest hit process: 3683
Number of processes hit: 34
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 164,136135
CPU 0 ISR highest execution time (µs): 306,080
CPU 0 ISR total execution time (s): 8,391763
CPU 0 ISR count: 4330295
CPU 0 DPC highest execution time (µs): 1052,250
CPU 0 DPC total execution time (s): 28,923236
CPU 0 DPC count: 10373649
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 65,461988
CPU 1 ISR highest execution time (µs): 16,940
CPU 1 ISR total execution time (s): 0,025582
CPU 1 ISR count: 10092
CPU 1 DPC highest execution time (µs): 303,750
CPU 1 DPC total execution time (s): 0,052265
CPU 1 DPC count: 8062
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 35,833792
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 242,990
CPU 2 DPC total execution time (s): 0,176115
CPU 2 DPC count: 33804
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 33,175892
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): 297,030
CPU 3 DPC total execution time (s): 0,031001
CPU 3 DPC count: 7054
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 31,033964
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): 218,450
CPU 4 DPC total execution time (s): 0,085970
CPU 4 DPC count: 15950
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 30,910317
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): 187,30
CPU 5 DPC total execution time (s): 0,027941
CPU 5 DPC count: 6162
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 35,233412
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): 403,840
CPU 6 DPC total execution time (s): 0,839686
CPU 6 DPC count: 119593
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 31,094520
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): 225,210
CPU 7 DPC total execution time (s): 0,028786
CPU 7 DPC count: 5108
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 37,574432
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): 305,090
CPU 8 DPC total execution time (s): 0,730383
CPU 8 DPC count: 104402
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 33,839061
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 172,450
CPU 9 DPC total execution time (s): 0,020843
CPU 9 DPC count: 3415
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 36,158694
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 260,960
CPU 10 DPC total execution time (s): 0,470784
CPU 10 DPC count: 50361
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 36,962506
CPU 11 ISR highest execution time (µs): 7,140
CPU 11 ISR total execution time (s): 0,005175
CPU 11 ISR count: 4602
CPU 11 DPC highest execution time (µs): 396,570
CPU 11 DPC total execution time (s): 0,153389
CPU 11 DPC count: 17922
_________________________________________________________________________________________________________
Blue_screen_of_death
04-10-2019, 02:35
Assicurati che nel BIOS è attivato High Precision Event Timer
Nel report si legge Reported CPU speed: 320 MHz, che potrebbe indicare che qualcosa sta limitando la velocità del processore oppure è un errore di misurazione del software.
Nelle impostazioni avanzate risparmio energia di Windows assicurati che il Livello massimo prestazioni del processore è impostato al 100%
Inoltre scarica CPU-Z e verifica che il processore sta lavorando alla sua frequenza.
Aggiorna driver di rete all'ultima versione disponibile sul sito del produttore.
Se i problemi persistono, avvia il monitoraggio con LatencyMon, lascialo girare finché si verificano i freeze e manda il nuovo report.
Mi aspetto che negli istanti dei freeze audio / video c'è qualcosa che schizza in alto, e non sono sicuro che nel report che hai postato sia stata catturata.
Per questo dovresti cercare di catturare i freeze prima di mandare il report.
Assicurati che nel BIOS è attivato High Precision Event Timer
Nel report si legge Reported CPU speed: 320 MHz, che potrebbe indicare che qualcosa sta limitando la velocità del processore oppure è un errore di misurazione del software.
Nelle impostazioni avanzate risparmio energia di Windows assicurati che il Livello massimo prestazioni del processore è impostato al 100%
Inoltre scarica CPU-Z e verifica che il processore sta lavorando alla sua frequenza.
Aggiorna driver di rete all'ultima versione disponibile sul sito del produttore.
Se i problemi persistono, avvia il monitoraggio con LatencyMon, lascialo girare finché si verificano i freeze e manda il nuovo report.
Mi aspetto che negli istanti dei freeze audio / video c'è qualcosa che schizza in alto, e non sono sicuro che nel report che hai postato sia stata catturata.
Per questo dovresti cercare di catturare i freeze prima di mandare il report.
ok allora provo tutto, poi ti allego un video per mostrarti l'errore che mi viene abbastanza frequentemente non nello stesso giorno però ogni tanto si ripresenta, e il rumore è quello che mi fa sempre però che dura quel secondo o meno. Grazie mille spero di essermi spiegato
https://vimeo.com/user103598545/review/364382006/f8e5268503
Blue_screen_of_death
04-10-2019, 20:59
Non riesco ad aprire il link
"Sorry, we couldnt find that page"
Blue_screen_of_death
04-10-2019, 21:10
OK, trovato il video.
Quella schermata dice ben poco.
I dettagli dell'errore vengono scritti in file con estensione .dmp, salvati per default nella cartella C:\Windows\Minidump
Analizzando il contenuto di quei file possiamo capire la causa del problema.
Carica tutti i file che trovi in quella cartella su un sito di hosting o su un sistema di cloud storage (Google Drive, Dropbox, ...) e manda il link.
OK, trovato il video.
Quella schermata dice ben poco.
I dettagli dell'errore vengono scritti in file con estensione .dmp, salvati per default nella cartella C:\Windows\Minidump
Analizzando il contenuto di quei file possiamo capire la causa del problema.
Carica tutti i file che trovi in quella cartella su un sito di hosting o su un sistema di cloud storage (Google Drive, Dropbox, ...) e manda il link.
ok ho caricato su dropbox vedi se riesci, grazie mille.
https://www.dropbox.com/s/mw6y6kmmz9xt77f/100419-328953-01.dmp?dl=0
Blue_screen_of_death
04-10-2019, 21:45
Si riesco a scaricare
Ne hai solo uno? Se ne hai anche altri manda tutta la cartella.
Blue_screen_of_death
04-10-2019, 21:53
OK, allora il sistema è configurato per eliminare i vecchi dump.
Prosegui comunque con quello che ti avevo scritto, in particolare questo:
Se i problemi persistono, avvia il monitoraggio con LatencyMon, lascialo girare finché si verificano i freeze e manda il nuovo report.
Mi aspetto che negli istanti dei freeze audio / video c'è qualcosa che schizza in alto, e non sono sicuro che nel report che hai postato sia stata catturata.
Per questo dovresti cercare di catturare i freeze prima di mandare il report.
Appena riesco (credo in serata / nottata) ti aggiorno per quanto riguarda le schermate blu.
:)
OK, allora il sistema è configurato per eliminare i vecchi dump.
Prosegui comunque con quello che ti avevo scritto, in particolare questo:
Appena riesco (credo in serata / nottata) ti aggiorno per quanto riguarda le schermate blu.
:)
grazie mille si non ti preoccupare quando hai tempo gentilissimo. :)
Blue_screen_of_death
05-10-2019, 10:06
Ho analizzato il dump.
Il problema è stato causato dalla corruzione in una page table. Le page table mappano lo spazio di indirizzamento virtuale nello spazio di indirizzamento fisico. In parole più semplici, contengono informazioni che servono ai processi per leggere o scrivere in RAM.
Si dovrebbe vedere a quale processo appartiene la memoria corrotta, e da questo si potrebbe risalire al nome del driver che la corrompe. Ma purtroppo questo non riesco a farlo perché il dump non contiene queste informazioni.
Dovremmo configurare Windows per creare dump più grandi che includono anche queste informazioni e attendere il prossimo crash.
Ma per evitare di perdere altro tempo, aggiungiamo altre due cose alla lista di cose da fare :)
- Nelle impostazioni avanzate risparmio energia di Windows assicurati che il Livello massimo prestazioni del processore è impostato al 100%
- Scarica CPU-Z e verifica che il processore sta lavorando alla sua frequenza.
- Testa la RAM con MemTest86+
- Testa i driver con driver verifier, come descritto di seguito
- Lascia avviato LatencyMon in background e al primo mini-freeze, manda il report
Procedura per testare i driver
Apri verifier (strumento incluso in Windows),
seleziona Crea impostazioni standard
Seleziona automaticamente tutti i driver installati in questo computer
Fine
Ora riavvia.
Al riavvio, Windows fa tiene sotto controllo tutti i driver, quindi potrebbe essere più lento del solito.
Attendi il prossimo crash, manda una foto e manda il minidump. Questa volta dovrebbe contenere informazioni più dettagliate incluso il nome del driver incriminato.
Se non riesci più ad avviare Windows a causa dei crash (perché magari si verificano in fase di avvio), avvia Windows in modalità provvisoria e disattiva Driver Verifier scegliendo Elimina impostazioni esistenti.
Ho analizzato il dump.
Il problema è stato causato dalla corruzione in una page table. Le page table mappano lo spazio di indirizzamento virtuale nello spazio di indirizzamento fisico. In parole più semplici, contengono informazioni che servono ai processi per leggere o scrivere in RAM.
Si dovrebbe vedere a quale processo appartiene la memoria corrotta, e da questo si potrebbe risalire al nome del driver che la corrompe. Ma purtroppo questo non riesco a farlo perché il dump non contiene queste informazioni.
Dovremmo configurare Windows per creare dump più grandi che includono anche queste informazioni e attendere il prossimo crash.
Ma per evitare di perdere altro tempo, aggiungiamo altre due cose alla lista di cose da fare :)
- Nelle impostazioni avanzate risparmio energia di Windows assicurati che il Livello massimo prestazioni del processore è impostato al 100%
- Scarica CPU-Z e verifica che il processore sta lavorando alla sua frequenza.
- Testa la RAM con MemTest86+
- Testa i driver con driver verifier, come descritto di seguito
- Lascia avviato LatencyMon in background e al primo mini-freeze, manda il report
Procedura per testare i driver
Apri verifier (strumento incluso in Windows),
seleziona Crea impostazioni standard
Seleziona automaticamente tutti i driver installati in questo computer
Fine
Ora riavvia.
Al riavvio, Windows fa tiene sotto controllo tutti i driver, quindi potrebbe essere più lento del solito.
Attendi il prossimo crash, manda una foto e manda il minidump. Questa volta dovrebbe contenere informazioni più dettagliate incluso il nome del driver incriminato.
Se non riesci più ad avviare Windows a causa dei crash (perché magari si verificano in fase di avvio), avvia Windows in modalità provvisoria e disattiva Driver Verifier scegliendo Elimina impostazioni esistenti.
allora ho fatto la maggior parte delle cose, tra l'altro ho pure aggiornato il bios, o provato con driver verifier ma purtroppo mi crashava subito al logo di windows.
poi il processore è al 100%
la ram la ritesterò ma già lo feci a uno degli ultimi crash con lo stesso errore e non venne fuori nessun problema.
per verificare i driver ed evitare che mi crashi devo fare qualcos'altro?
grazie mille per l'aiuto sei gentilissimo :)
Blue_screen_of_death
05-10-2019, 21:32
allora ho fatto la maggior parte delle cose, tra l'altro ho pure aggiornato il bios, o provato con driver verifier ma purtroppo mi crashava subito al logo di windows.
poi il processore è al 100%
la ram la ritesterò ma già lo feci a uno degli ultimi crash con lo stesso errore e non venne fuori nessun problema.
per verificare i driver ed evitare che mi crashi devo fare qualcos'altro?
grazie mille per l'aiuto sei gentilissimo :)
Guarda se a seguito del crash avvenuti durante l'avvio ti ha generato il dump, nella cartella C:\Windows\Minidump. Puoi capire se è un dump nuovo o vecchio guardando data e ora di creazione, ma anche osservando il nome del file .dmp (che infatti contiene proprio la data e l'ora :) ).
Se sì, manda il file che do un'occhiata
Se no, allora fai una foto alla schermata blu e manda, e speriamo che c'è l'informazione che ci serve
Guarda se a seguito del crash avvenuti durante l'avvio ti ha generato il dump, nella cartella C:\Windows\Minidump. Puoi capire se è un dump nuovo o vecchio guardando data e ora di creazione, ma anche osservando il nome del file .dmp (che infatti contiene proprio la data e l'ora :) ).
Se sì, manda il file che do un'occhiata
Se no, allora fai una foto alla schermata blu e manda, e speriamo che c'è l'informazione che ci serve
niente file dump.. :( la schermata dell'errore era: thread stuck in device driver
Blue_screen_of_death
06-10-2019, 00:55
niente file dump.. :( la schermata dell'errore era: thread stuck in device driver
ok, compare anche il nome del driver?
ok, compare anche il nome del driver?
no solo il nome dell'errore
Blue_screen_of_death
06-10-2019, 14:20
OK
Con driver verifier abiliti la verifica soltanto su un sottoinsieme di driver. Ovvero li testi a gruppi, finché non individui il driver che impedisce l'avvio.
Ad esempio potresti partire testando i driver non Microosft, poi abiliti il test solo sui driver con lettera iniziale compresa tra A e E, poi F e L, ...
Quando individui il gruppo di driver che impedisce l'avvio, selezioni un sottoinsieme di quel gruppo e così via, fino a rimanere con un solo driver.
A quel punto provi ad aggiornarlo, e ti accerti che l'aggiornamento ha risolto il problema all'avvio con verifier attivato.
So che richiede un po' di tempo. :)
In alternativa, potresti provare ad aggiornare tutti i driver
- Audio
- Video
- Scheda di rete wireless
- Scheda di rete Ethernet
- Chipset
- Controller USB
Ma così stiamo andando a tentativi e non è detto che riesci a individuare e risolvere il problema.
Scegli tu come procedere.
OK
Con driver verifier abiliti la verifica soltanto su un sottoinsieme di driver. Ovvero li testi a gruppi, finché non individui il driver che impedisce l'avvio.
Ad esempio potresti partire testando i driver non Microosft, poi abiliti il test solo sui driver con lettera iniziale compresa tra A e E, poi F e L, ...
Quando individui il gruppo di driver che impedisce l'avvio, selezioni un sottoinsieme di quel gruppo e così via, fino a rimanere con un solo driver.
A quel punto provi ad aggiornarlo, e ti accerti che l'aggiornamento ha risolto il problema all'avvio con verifier attivato.
So che richiede un po' di tempo. :)
In alternativa, potresti provare ad aggiornare tutti i driver
- Audio
- Video
- Scheda di rete wireless
- Scheda di rete Ethernet
- Chipset
- Controller USB
Ma così stiamo andando a tentativi e non è detto che riesci a individuare e risolvere il problema.
Scegli tu come procedere.
ok proverò intanto a vedere di aggiornare tutto poi inizio con la verifica, poi mi ha ridato il crash con memory management ma non mi ha creato il nuovo file nella cartella minidump...
Blue_screen_of_death
06-10-2019, 15:03
Forse è impostato per creare un dump completo della memoria, ovvero il file C:\Windows\MEMORY.DMP
c'era ho riavviato il pc e ora non c'è più forse la pulizia?
poi in un altro HD ho 3 file DUMP26c1, DUMP2625, DUMP2626 e tutti pesano sui 25 gb con estensione .tmp
Blue_screen_of_death
06-10-2019, 15:18
OK, 30 GB è difficile da inviare.
Ma puoi fare così:
WIN+PAUSA
Impostazioni di sistema avanzate
Impostazioni sotto Avvio e ripristino
Imposta Dump della memoria kernel
Così dovrebbe crearti il minidump, che pesa qualche megabyte.
Poi se vuoi, riprova con Driver Verifier abilitando la verifica su tutti i driver. Se viene scritto il minidump puoi mandarmelo e dovremmo beccare il nome del driver in un attimo.
Altrimenti, ignora questo post e continua con l'aggiornamento driver.
A tua scelta.
OK, 30 GB è difficile da inviare.
Ma puoi fare così:
WIN+PAUSA
Impostazioni di sistema avanzate
Impostazioni sotto Avvio e ripristino
Imposta Dump della memoria kernel
Così dovrebbe crearti il minidump, che pesa qualche megabyte.
Poi se vuoi, riprova con Driver Verifier abilitando la verifica su tutti i driver. Se viene scritto il minidump puoi mandarmelo e dovremmo beccare il nome del driver in un attimo.
Altrimenti, ignora questo post e continua con l'aggiornamento driver.
A tua scelta.
ok imposto subito, i driver usando driver easy mi dice tutti aggiornati. provo a fare quello che hai detto ora
allora il dmp lo ha fatto ti linko tutto è di 800 mega il file.
https://www.dropbox.com/s/4uo8p353o7zkxgq/MEMORY.DMP?dl=0
Blue_screen_of_death
06-10-2019, 16:26
Beccato :)
Il driver che impedisce l'avvio (e che probabilmente è anche causa dei freeze) è ScpVBus, ovvero Virtual USB Bus.
E' un driver usato da joystick, controller PS4, Xbox, o cose simili. (Hai uno di questi dispositivi?)
La versione del driver installata risale al 2013, due anni prima del rilascio di Windows 10. Quindi potrebbe essere incompatibile con Windows 10.
Dovresti aggiornare quel driver.
si uso i joystick per giocare ogni tanto come faccio ad aggiornare?
usavo il programma ds4 perchè ogni tanto alcuni giochi il joystick non lo leggeva, e questo emula il driver del controller di xbox 360 potrebbe essere?
Blue_screen_of_death
06-10-2019, 16:43
Marca / modello dei joystick?
_________________________________________________________________________________________________________
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:00:19 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 3436,20
Average measured interrupt to process latency (µs): 8,553457
Highest measured interrupt to DPC latency (µs): 3431,20
Average measured interrupt to DPC latency (µs): 4,965094
_________________________________________________________________________________________________________
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): 46,380
Driver with highest ISR routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Highest reported total ISR routine time (%): 0,095639
Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Total time spent in ISRs (%) 0,104814
ISR count (execution time <250 µs): 151398
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): 100868,490
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0,062182
Driver with highest DPC total execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Total time spent in DPCs (%) 0,240834
DPC count (execution time <250 µs): 136264
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 58
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: tiworker.exe
Total number of hard pagefaults 566
Hard pagefault count of hardest hit process: 297
Number of processes hit: 15
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0,982381
CPU 0 ISR highest execution time (µs): 46,380
CPU 0 ISR total execution time (s): 0,237280
CPU 0 ISR count: 149793
CPU 0 DPC highest execution time (µs): 654,210
CPU 0 DPC total execution time (s): 0,380497
CPU 0 DPC count: 120062
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,259422
CPU 1 ISR highest execution time (µs): 9,540
CPU 1 ISR total execution time (s): 0,000758
CPU 1 ISR count: 321
CPU 1 DPC highest execution time (µs): 87,910
CPU 1 DPC total execution time (s): 0,013835
CPU 1 DPC count: 882
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,251673
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 625,090
CPU 2 DPC total execution time (s): 0,024260
CPU 2 DPC count: 10413
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,130216
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): 20,110
CPU 3 DPC total execution time (s): 0,000158
CPU 3 DPC count: 52
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,154943
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): 24,040
CPU 4 DPC total execution time (s): 0,001178
CPU 4 DPC count: 225
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,120851
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): 165,690
CPU 5 DPC total execution time (s): 0,001274
CPU 5 DPC count: 238
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0,195983
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): 83,540
CPU 6 DPC total execution time (s): 0,004517
CPU 6 DPC count: 646
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0,158261
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): 19,160
CPU 7 DPC total execution time (s): 0,000198
CPU 7 DPC count: 55
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,550784
CPU 8 ISR highest execution time (µs): 6,360
CPU 8 ISR total execution time (s): 0,000896
CPU 8 ISR count: 1074
CPU 8 DPC highest execution time (µs): 100868,490
CPU 8 DPC total execution time (s): 0,116971
CPU 8 DPC count: 2763
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,180135
CPU 9 ISR highest execution time (µs): 1,30
CPU 9 ISR total execution time (s): 0,000013
CPU 9 ISR count: 13
CPU 9 DPC highest execution time (µs): 113,450
CPU 9 DPC total execution time (s): 0,000404
CPU 9 DPC count: 53
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0,196084
CPU 10 ISR highest execution time (µs): 1,770
CPU 10 ISR total execution time (s): 0,000058
CPU 10 ISR count: 57
CPU 10 DPC highest execution time (µs): 86,690
CPU 10 DPC total execution time (s): 0,005298
CPU 10 DPC count: 794
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0,171310
CPU 11 ISR highest execution time (µs): 5,780
CPU 11 ISR total execution time (s): 0,000159
CPU 11 ISR count: 140
CPU 11 DPC highest execution time (µs): 76,720
CPU 11 DPC total execution time (s): 0,000944
CPU 11 DPC count: 140
_________________________________________________________________________________________________________
ti mando anche il tab con un piccolo freeze
Marca / modello dei joystick?
dualshock 4 quello normale della ps4
Blue_screen_of_death
06-10-2019, 16:52
Cerca il game controller in Gestione Dispositivi. E da lì puoi aggiornarlo.
Non avendo a disposizione joystick, non so dirti esattamente com'è chiamato.
Forse Controller di gioco compatibile HID o qualcosa del genere.
Cerca il game controller in Gestione Dispositivi. E da lì puoi aggiornarlo.
Non avendo a disposizione joystick, non so dirti esattamente com'è chiamato.
Forse Controller di gioco compatibile HID o qualcosa del genere.
ho provato ma niente mi dice sempre che è aggiornato ora provo a disinstallare il driver, per verificare che l'ho tolto devo fare la provo con verifier e vedere se mi si avvia giusto?
Blue_screen_of_death
06-10-2019, 16:55
ho provato ma niente mi dice sempre che è aggiornato ora provo a disinstallare il driver, per verificare che l'ho tolto devo fare la provo con verifier e vedere se mi si avvia giusto?
Si esatto
Si esatto
ok provato e niente mi da sempre quell'errore, quindi rimane qualcosa dentro? ti rimando il dmp?
Blue_screen_of_death
06-10-2019, 17:00
ok, manda
Blue_screen_of_death
06-10-2019, 17:06
Hai installato qualcosa per far funzionare il joystick? Ad esempio un software di gestione.
Qui sto lavorando di immaginazione. Non avendone mai visto uno, non so quali step hai fatto per installarlo e cosa si porta dietro l'installazione del joystick :D
Quindi vorrei capire cosa ha installato quel driver ScpVBus, che di default in Windows non è presente.
Questo spiega le mie domande.
Hai installato qualcosa per far funzionare il joystick? Ad esempio un software di gestione.
Qui sto lavorando di immaginazione. Non avendone mai visto uno, non so quali step hai fatto per installarlo e cosa si porta dietro l'installazione del joystick :D
Questo spiega le mie domande.
si l'ho installato su un hard disk esterno però mi installa i driver sul sistema principale si chiama DS4 e sto guardando un pò e dice sia un problema levarlo. :(
Blue_screen_of_death
06-10-2019, 17:12
Secondo me conviene scollegare il joystick, rimuovere tutto software e driver relativo al joystick
Ripetere il test con Driver Verifier.
E se è tutto OK, cercare versioni aggiornate dei driver, certificate per funzionare con Windows 10.
Questo dovrebbe andare, è datato 2017
https://sourceforge.net/projects/scptoolkit.mirror/
Secondo me conviene scollegare il joystick, rimuovere tutto software e driver relativo al joystick
Ripetere il test con Driver Verifier.
E se è tutto OK, cercare versioni aggiornate dei driver, certificate per funzionare con Windows 10.
il problema è che il joystick io non lo collego quasi mai.. poi nel pannello di controllo non c'è nemmeno il software ho eliminato la cartella ma sicuramente i driver sono rimasti... ti linko il dump
https://www.dropbox.com/s/t925dkejwejtc22/MEMORY.DMP?dl=0
Blue_screen_of_death
06-10-2019, 17:26
Sto scaricando il dump.
C'è una periferica Scp Virtual Bus Driver in gestione dispositivi?
Sto scaricando il dump.
C'è una periferica Scp Virtual Bus Driver in gestione dispositivi?
no non lo vedo
Blue_screen_of_death
06-10-2019, 17:37
il problema è che il joystick io non lo collego quasi mai.. poi nel pannello di controllo non c'è nemmeno il software ho eliminato la cartella ma sicuramente i driver sono rimasti... ti linko il dump
https://www.dropbox.com/s/t925dkejwejtc22/MEMORY.DMP?dl=0
Colpa di Kaspersky questa volta. Rimuovi anche lui, e rilancia Driver Verifier.
Qui c'è una procedura per la rimozione di ScpVbus.
https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal
Si tratta di rimuovere 3 cose: il servizio, il driver del virtual USB e il driver libusbK
Era questo il tool che avevi installato per la gestione del joystick?
Se quel servizio e quelle periferiche non ci sono è stato rimosso.
P.S. Avevi aggiornato da Windows 7 o 8, senza formattare?
Colpa di Kaspersky questa volta. Rimuovi anche lui, e rilancia Driver Verifier.
Qui c'è una procedura per la rimozione di ScpVbus.
https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal
Si tratta di rimuovere 3 cose: il servizio, il driver del virtual USB e il driver libusbK
Era questo il tool che avevi installato per la gestione del joystick?
Se quel servizio e quelle periferiche non ci sono è stato rimosso.
P.S. Avevi aggiornato da Windows 7 o 8, senza formattare?
ok rimuovo anche lui, allora il dirver di libusbk lo uso per la nintendo switch
no ho formattato facendo un avvio pulito, più che altro ora mi deve arrivare l'ssd nuovo e volevo clonare l'hard disk cosi da avere tutto già pronto però se da tutti questi problemi... io addirittura pensavo a problemi con scheda madre e processore
Blue_screen_of_death
06-10-2019, 17:47
ok rimuovo anche lui, allora il dirver di libusbk lo uso per la nintendo switch
Rimuovi Kasperski, e rimuovi il driver libusbk.
Per libusbk, disinstalla prima da Installazione applicazioni, se c'è la voce.
Poi elimina i residui a mano, https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal
Cerchiamo di arrivare a una situazione funzionante, poi puoi reinstallare tutto quello che hai rimosso, versioni compatibili con Windows 10.
Rimuovi Kasperski, e rimuovi il driver libusbk.
Per libusbk, disinstalla prima da Installazione applicazioni, se c'è la voce.
Poi elimina i residui a mano, https://github.com/nefarius/ScpToolkit/wiki/Manual-driver-removal
Cerchiamo di arrivare a una situazione funzionante, poi puoi reinstallare tutto quello che hai rimosso, versioni compatibili con Windows 10.
rimosso kaspersky e ho fatto verifier ed è partito tutto senza eliminare libusbk, anche perchè ho provato ma non c'è la voce di gestione dispositivi perchè la periferica non ce l'ho connessa.
ora che è partito con verifier?
Blue_screen_of_death
06-10-2019, 17:57
Se ti serve, reinstalla Kaspersky. E vedi se il sistema parte con verifier.
Se ti serve, reinstalla Kaspersky. E vedi se il sistema parte con verifier.
diciamo che lo tenevo cosi tanto per sicurezza in più dice che conviene?
Blue_screen_of_death
06-10-2019, 18:02
diciamo che lo tenevo cosi tanto per sicurezza in più dice che conviene?
Alla fine dipende dai gusti.
Io uso da anni l'antivirus integrato in Windows 10.
Crea sicuramente meno conflitti, in quanto è di Microsoft ed è integrato perfettamente in Windows.
E se non è compatibile lui allora non so quale antivirus potrebbe esserlo :D
Alla fine dipende dai gusti.
Io uso da anni l'antivirus integrato in Windows 10.
Crea sicuramente meno conflitti, in quanto è di Microsoft ed è integrato perfettamente in Windows.
E se non è compatibile lui allora non so quale antivirus potrebbe esserlo :D
mi sembra la cosa più giusta :D :)
per il resto ora che mi manca di fare?
Blue_screen_of_death
06-10-2019, 18:19
Aggiornare i driver obsoleti (sto vedendo se ce ne sono dal dump)
E poi attendere, cioè usare il PC normalmente per vedere se i problemi (crash e freeze) sono spariti.
ok uso driver easy va bene? o c'è di meglio? comunque devo ripristinare il tutto eliminando da verifier perchè ora il pc è stra lento è normale giusto?
Blue_screen_of_death
06-10-2019, 18:26
si, con driver verifier è normale che è lento, perché Windows disabilita alcune ottimizzazioni ed attiva procedure di verifica sui driver, che consumano risorse.
Per i driver, meglio verificare a mano. Quei software che aggiornano in automatico non sono affidabilissimi.
Quindi, prendere la lista dei driver che trovi sul sito della scheda madre (https://www.gigabyte.com/Motherboard/GA-AX370-Gaming-K3-rev-10/support#support-dl-driver-usb31)
E per ogni driver guardare se la versione installata nel PC (che puoi vedere in gestione dispositivi) è >= di quella presente sul sito.
Sembra laborioso, ma non sono tanti.
si, con driver verifier è normale che è lento, perché Windows disabilita alcune ottimizzazioni ed attiva procedure di verifica sui driver, che consumano risorse.
Per i driver, meglio verificare a mano. Quei software che aggiornano in automatico non sono affidabilissimi.
Quindi, prendere la lista dei driver che trovi sul sito della scheda madre (https://www.gigabyte.com/Motherboard/GA-AX370-Gaming-K3-rev-10/support#support-dl-driver-usb31)
E per ogni driver guardare se la versione installata nel PC (che puoi vedere in gestione dispositivi) è >= di quella presente sul sito.
Sembra laborioso, ma non sono tanti.
ok faccio subito, ma lo devo disabilitare ora verifier?
Blue_screen_of_death
06-10-2019, 18:32
Non sarebbe male tenerlo ancora attivato, perché se trova altri problemi, li rileva ti salva il dump e puoi rimandarmelo.
Però mi rendo conto che così potrebbe essere inutilizzabile.
Se è inutilizzabile allora disattivalo.
Al limite lo riabilitiamo successivamente, se i problemi persistono.
ok per ora lo tengo
comunque ti ringrazio perchè sei stato gentilissimo e disponibile :) speriamo di aver risolto magari quel memory managment era errore del driver perchè anche quello c'era un periodo che me lo dava spesso
comunque tutto aggiornato ho provato anche un altro riavvio con verifier abilitato ed è andato
Blue_screen_of_death
06-10-2019, 18:56
Si, probabile che è la causa era quel driver :sperem:
E siccome è stato scritto 6 anni fa (nell'informatica sono veramente tanti) non stupirebbe più di tanto
Non resta che attendere qualche ora (o giorno, a seconda della frequenza con cui si presentavano i problemi) per vedere se il problema è sparito.
Si, probabile che è la causa era quel driver :sperem:
E siccome è stato scritto 6 anni fa (nell'informatica sono veramente tanti) non stupirebbe più di tanto
Non resta che attendere qualche ora (o giorno, a seconda della frequenza con cui si presentavano i problemi) per vedere se il problema è sparito.
ancora grazie! ti farò sempre se tutto andrà bene, anche latency mon prima mi dava rosso ora sembrerebbe stabile
Si, probabile che è la causa era quel driver :sperem:
E siccome è stato scritto 6 anni fa (nell'informatica sono veramente tanti) non stupirebbe più di tanto
Non resta che attendere qualche ora (o giorno, a seconda della frequenza con cui si presentavano i problemi) per vedere se il problema è sparito.
già che ci sono ti posso fare una domanda?
allora io ho un case con 3 porte usb nel pannelo frontale una 3.0 e le altre due 2.0, quando collego anche una pennina la rimozione sicura non mi appare devo per forza andare in computer ed espellerla da li invece la 3.0 senza problemi appare come mai?
Blue_screen_of_death
08-10-2019, 02:30
Dipende dal modo in cui il driver in uso gestisce il controller USB.
Collega una pen drive a una porta USB 2.0
Apri Gestione disco.
La pen drive viene vista come Rimovibile come in questa figura?
https://www.windowsblogitalia.com/wp-content/uploads/2019/04/Windows-10-criteri-rimozione-sicura-hardware-dispositivi-USB-860x484.jpg
(da https://www.windowsblogitalia.com/2019/04/sicuro-rimuovere-pendrive-pc-windows-10/)
Inoltre, apri le proprietà, scheda Criteri, qual è il Criterio di rimozione impostato?
Se è impostato Rimozione rapida prova a mettere Prestazioni migliori. In questo modo compare la rimozione sicura?
Dipende dal modo in cui il driver in uso gestisce il controller USB.
Collega una pen drive a una porta USB 2.0
Apri Gestione disco.
La pen drive viene vista come Rimovibile come in questa figura?
https://www.windowsblogitalia.com/wp-content/uploads/2019/04/Windows-10-criteri-rimozione-sicura-hardware-dispositivi-USB-860x484.jpg
(da https://www.windowsblogitalia.com/2019/04/sicuro-rimuovere-pendrive-pc-windows-10/)
Inoltre, apri le proprietà, scheda Criteri, qual è il Criterio di rimozione impostato?
Se è impostato Rimozione rapida prova a mettere Prestazioni migliori. In questo modo compare la rimozione sicura?
fai conto che si disconnette in continuazione non riesco nemmeno ad aprire proprietà..
Blue_screen_of_death
08-10-2019, 13:13
Quindi non riesci ad usare tutte le periferiche USB? O solo una pen drive?
Quindi non riesci ad usare tutte le periferiche USB? O solo una pen drive?
per esempio nell'altra porta 2.0 ho una chiavetta per un mouse wireless e nell'altra volevo provare la pen drive ma ogni tanto si disconnette oppure non va proprio e devo riavviare il pc. se provo ad andare nelle proprietà mi si disconnette, e appena regge per un attimo provo quella cosa che mi dicevi di fare e non la vedo e poi si disconnette. (la vede come pen drive 3.0) può essere per quello?
Blue_screen_of_death
08-10-2019, 13:28
Disinstalla i driver del controller USB e riavvia.
Lasciagli installare i driver che vuole lui e vedi se il problema scompare.
provato ma niente ti faccio vedere cosa vedo io
https://ibb.co/CJbRSdh
Blue_screen_of_death
09-10-2019, 07:51
Intanto dobbiamo capire se il problema è software o hardware, perché potrebbe
Sai usare Linux? Potresti avviare Linux in modalità live e vedere se lì le periferiche USB funzionano.
Intanto dobbiamo capire se il problema è software o hardware, perché potrebbe
Sai usare Linux? Potresti avviare Linux in modalità live e vedere se lì le periferiche USB funzionano.
si una cosa normale lo usavo qualche annetto fa ahahah appena riesco ti faccio sapere!
Blue_screen_of_death
09-10-2019, 22:45
ok, tanto basta che avvii la live Linux, provi a collegare ed usare una periferica USB per un po'.
I problemi di freeze e schermate blu sono spariti?
ok, tanto basta che avvii la live Linux, provi a collegare ed usare una periferica USB per un po'.
I problemi di freeze e schermate blu sono spariti?
con il lavoro rientro la sera e provo per quel che posso però per ora i freeze sembrerebbe di si e le schermate blu uguale anche se quelle erano più rare
Blue_screen_of_death
10-10-2019, 20:21
Ok
Ok
allora ora come ora c'è stato veramente un millesimo di secondo il freeze ma ovviamente non avevo abilitato latency :muro:
Blue_screen_of_death
10-10-2019, 22:11
ho ripreso l'ultimo log che mi hai mandato di LatencyMon, che mi era sfuggito.
C'è un rallentamento causato dal driver storport, che gestisce lo storage.
Controlliamo i dischi, manda uno screenshot di CrystalDiskInfo.
Se non sbaglio hai detto che all'apertura di CrystalDiskInfo freeza, giusto?
ho ripreso l'ultimo log che mi hai mandato di LatencyMon, che mi era sfuggito.
C'è un rallentamento causato dal driver storport, che gestisce lo storage.
Controlliamo i dischi, manda uno screenshot di CrystalDiskInfo.
Se non sbaglio hai detto che all'apertura di CrystalDiskInfo freeza, giusto?
si ho un disco vedrai che fa fare i capricci, menomale avevo latency aperto mentre aprivo crystal ti mando tutto.
_________________________________________________________________________________________________________
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:28:47 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 253,80
Average measured interrupt to process latency (µs): 4,914504
Highest measured interrupt to DPC latency (µs): 249,80
Average measured interrupt to DPC latency (µs): 1,597891
_________________________________________________________________________________________________________
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): 201,830
Driver with highest ISR routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Highest reported total ISR routine time (%): 0,003562
Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Total time spent in ISRs (%) 0,005634
ISR count (execution time <250 µs): 858479
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): 100867,450
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0,015914
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 0,053936
DPC count (execution time <250 µs): 3632334
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 77
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: diskinfo32.exe
Total number of hard pagefaults 3432
Hard pagefault count of hardest hit process: 2123
Number of processes hit: 31
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 53,258470
CPU 0 ISR highest execution time (µs): 201,830
CPU 0 ISR total execution time (s): 0,971462
CPU 0 ISR count: 700829
CPU 0 DPC highest execution time (µs): 100867,450
CPU 0 DPC total execution time (s): 10,290083
CPU 0 DPC count: 3512087
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 37,999045
CPU 1 ISR highest execution time (µs): 44,470
CPU 1 ISR total execution time (s): 0,131718
CPU 1 ISR count: 58421
CPU 1 DPC highest execution time (µs): 209,710
CPU 1 DPC total execution time (s): 0,198258
CPU 1 DPC count: 17388
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 30,953961
CPU 2 ISR highest execution time (µs): 13,620
CPU 2 ISR total execution time (s): 0,009801
CPU 2 ISR count: 5349
CPU 2 DPC highest execution time (µs): 297,480
CPU 2 DPC total execution time (s): 0,165380
CPU 2 DPC count: 45239
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 37,919980
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): 269,380
CPU 3 DPC total execution time (s): 0,011504
CPU 3 DPC count: 1691
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 28,439876
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): 291,910
CPU 4 DPC total execution time (s): 0,056631
CPU 4 DPC count: 8019
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 39,243234
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): 179,240
CPU 5 DPC total execution time (s): 0,006070
CPU 5 DPC count: 859
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 20,688717
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): 308,340
CPU 6 DPC total execution time (s): 0,277979
CPU 6 DPC count: 26415
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 23,749721
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): 86,380
CPU 7 DPC total execution time (s): 0,006993
CPU 7 DPC count: 1758
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 20,520389
CPU 8 ISR highest execution time (µs): 14,540
CPU 8 ISR total execution time (s): 0,047048
CPU 8 ISR count: 84063
CPU 8 DPC highest execution time (µs): 307,840
CPU 8 DPC total execution time (s): 0,095765
CPU 8 DPC count: 12323
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 22,73040
CPU 9 ISR highest execution time (µs): 5,160
CPU 9 ISR total execution time (s): 0,000696
CPU 9 ISR count: 1193
CPU 9 DPC highest execution time (µs): 183,280
CPU 9 DPC total execution time (s): 0,003121
CPU 9 DPC count: 411
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 18,875902
CPU 10 ISR highest execution time (µs): 6,20
CPU 10 ISR total execution time (s): 0,001032
CPU 10 ISR count: 1249
CPU 10 DPC highest execution time (µs): 261,750
CPU 10 DPC total execution time (s): 0,031345
CPU 10 DPC count: 3153
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 21,675216
CPU 11 ISR highest execution time (µs): 15,330
CPU 11 ISR total execution time (s): 0,005894
CPU 11 ISR count: 7375
CPU 11 DPC highest execution time (µs): 287,040
CPU 11 DPC total execution time (s): 0,034750
CPU 11 DPC count: 3069
_________________________________________________________________________________________________________
https://ibb.co/LDwxmWv questo è lo screen
Blue_screen_of_death
10-10-2019, 22:35
Si confermo, è il driver che gestisce lo storage che causa i freeze.
Il disco ha 228 settori riallocati, dovresti sostituirlo
Si confermo, è il driver che gestisce lo storage che causa i freeze.
Il disco ha 228 settori riallocati, dovresti sostituirlo
perfetto grazie mille
Blue_screen_of_death
10-10-2019, 22:39
Se non c'è niente di essenziale sopra potresti tenerlo scollegato per vedere se i freeze spariscono.
In ogni caso, essendo inaffidabile, se hai dati importanti su E: fai un backup per evitare di perderli.
Se non c'è niente di essenziale sopra potresti tenerlo scollegato per vedere se i freeze spariscono.
In ogni caso, essendo inaffidabile, se hai dati importanti su E: fai un backup per evitare di perderli.
si ce l'ho infatti stavo pensando di farlo.. è che 500gb ora come ora non ce l'ho liberi :doh:
Se non c'è niente di essenziale sopra potresti tenerlo scollegato per vedere se i freeze spariscono.
In ogni caso, essendo inaffidabile, se hai dati importanti su E: fai un backup per evitare di perderli.
allora ho smontato l'hard disk che aveva quei settori danneggiati ma i freeze se apro crystal continuano..
Blue_screen_of_death
11-10-2019, 21:48
Mandami lo screen di CrystalDiskInfo degli altri installati
Allarga la finestra in modo da includere tutte le voci nello screen
Mandami lo screen di CrystalDiskInfo degli altri installati
Allarga la finestra in modo da includere tutte le voci nello screen
sono i tre hard disk l'ultimo è quello di sistema cambiato nuovo nuovo
https://ibb.co/bBtGxLq
https://ibb.co/yQmkhrQ
https://ibb.co/7jZmgyv
Blue_screen_of_death
11-10-2019, 22:16
Comunque siamo vicini alla scoperta della causa, direi i driver SATA o problemi ai dischi / controller SATA / cavetti di collegamento SATA
Devi fare solo un po' di prove per capire meglio :)
In particolare, ci sono molti errori CRC UltraDMA su due dischi, D: e H:
Potrebbero essere causati dai cavetti SATA di collegamento danneggiati.
Scollega i dischi D:, E: e H: o disabilitali temporaneamente da BIOS, se non ti va di rismontare il PC. Lascia solo C:
E vedi se i freeze all'avvio di CrystalDiskInfo spariscono.
Comunque siamo vicini alla scoperta della causa, direi i driver SATA o problemi ai dischi / controller SATA / cavetti di collegamento SATA
Devi fare solo un po' di prove per capire meglio :)
In particolare, ci sono molti errori CRC UltraDMA su due dischi, D: e H:
Potrebbero essere causati dai cavetti SATA di collegamento danneggiati.
Scollega i dischi D:, E: e H: o disabilitali temporaneamente da BIOS, se non ti va di rismontare il PC. Lascia solo C:
E vedi se i freeze all'avvio di CrystalDiskInfo spariscono.
perfetto domani spero di farti sapere qualcosa! potrebbe essere la scheda madre? o solo i cavetti? perchè quando assemblai i pc un disco non veniva visto, poi smanettai tra le porte sata e parti.
Blue_screen_of_death
11-10-2019, 22:26
perfetto domani spero di farti sapere qualcosa! potrebbe essere la scheda madre? o solo i cavetti? perchè quando assemblai i pc un disco non veniva visto, poi smanettai tra le porte sata e parti.
si, o la scheda madre o i cavetti.
Lascia solo il disco di sistema collegato e vedi che succede, immagino che in questo caso i freeze spariscono (a meno che anche il disco di sistema ha errori di CRC, cosa che non posso sapere perché manca lo screen)
Poi colleghi un disco e provi il PC per vedere come si comporta.
Se hai freeze, provi a sostituire il cavetto, per vedere se il problema va via.
E così via
:)
si, o la scheda madre o i cavetti.
Lascia solo il disco di sistema collegato e vedi che succede, immagino che in questo caso i freeze spariscono (a meno che anche il disco di sistema ha errori di CRC, cosa che non posso sapere perché manca lo screen)
Poi colleghi un disco e provi il PC per vedere come si comporta.
Se hai freeze, provi a sostituire il cavetto, per vedere se il problema va via.
E così via
:)
allora tolti tutti gli hard disk tranne quello di sistema ti mando anche lo screen ma penso tu veda poco, tolti ho aperto crystal e solito freeze impercettibile però con la musica accesa ho potuto sentirlo
https://ibb.co/pvN3SPk
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:04:15 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 251,90
Average measured interrupt to process latency (µs): 5,231388
Highest measured interrupt to DPC latency (µs): 243,90
Average measured interrupt to DPC latency (µs): 1,738188
_________________________________________________________________________________________________________
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): 131,670
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,007565
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,009946
ISR count (execution time <250 µs): 82741
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): 340,580
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0,031377
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,084435
DPC count (execution time <250 µs): 774098
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 13
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: spotify.exe
Total number of hard pagefaults 35029
Hard pagefault count of hardest hit process: 7702
Number of processes hit: 81
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 7,717654
CPU 0 ISR highest execution time (µs): 131,670
CPU 0 ISR total execution time (s): 0,300041
CPU 0 ISR count: 80163
CPU 0 DPC highest execution time (µs): 340,580
CPU 0 DPC total execution time (s): 2,210742
CPU 0 DPC count: 704978
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3,625882
CPU 1 ISR highest execution time (µs): 20,230
CPU 1 ISR total execution time (s): 0,002258
CPU 1 ISR count: 693
CPU 1 DPC highest execution time (µs): 172,870
CPU 1 DPC total execution time (s): 0,019866
CPU 1 DPC count: 4721
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,554767
CPU 2 ISR highest execution time (µs): 4,630
CPU 2 ISR total execution time (s): 0,000029
CPU 2 ISR count: 9
CPU 2 DPC highest execution time (µs): 315,10
CPU 2 DPC total execution time (s): 0,080893
CPU 2 DPC count: 15694
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,712196
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): 239,280
CPU 3 DPC total execution time (s): 0,021720
CPU 3 DPC count: 4267
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 3,171119
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): 225,350
CPU 4 DPC total execution time (s): 0,050678
CPU 4 DPC count: 10143
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 3,542682
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): 130,80
CPU 5 DPC total execution time (s): 0,008941
CPU 5 DPC count: 1842
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 3,152382
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): 271,280
CPU 6 DPC total execution time (s): 0,042230
CPU 6 DPC count: 7865
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 3,395596
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): 127,760
CPU 7 DPC total execution time (s): 0,009043
CPU 7 DPC count: 1681
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,345245
CPU 8 ISR highest execution time (µs): 6,290
CPU 8 ISR total execution time (s): 0,001231
CPU 8 ISR count: 1193
CPU 8 DPC highest execution time (µs): 270,690
CPU 8 DPC total execution time (s): 0,075124
CPU 8 DPC count: 15113
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,447034
CPU 9 ISR highest execution time (µs): 2,10
CPU 9 ISR total execution time (s): 0,000058
CPU 9 ISR count: 49
CPU 9 DPC highest execution time (µs): 126,170
CPU 9 DPC total execution time (s): 0,009673
CPU 9 DPC count: 1247
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,680618
CPU 10 ISR highest execution time (µs): 16,020
CPU 10 ISR total execution time (s): 0,000225
CPU 10 ISR count: 172
CPU 10 DPC highest execution time (µs): 145,570
CPU 10 DPC total execution time (s): 0,034517
CPU 10 DPC count: 4263
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,025883
CPU 11 ISR highest execution time (µs): 6,210
CPU 11 ISR total execution time (s): 0,000555
CPU 11 ISR count: 462
CPU 11 DPC highest execution time (µs): 239,970
CPU 11 DPC total execution time (s): 0,020746
CPU 11 DPC count: 2297
_________________________________________________________________________________________________________
edit: allora ho fatto ripartire di nuovo latency ha fatto un bel freeze lungo e poi è ripartito tutto. io non so il disco ssd è nuovo... non so da cosa possa dipendere forse processore scheda video (non credo) scheda madre?
Blue_screen_of_death
12-10-2019, 12:54
Durante il freeze LatencyMon era in esecuzione?
Il report è perfetto nella parte di DPC e ISR, sono spariti i quei valori sballati legati al driver di storage
Adesso resta il problema in questa parte del report,
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: spotify.exe
Total number of hard pagefaults 35029
Hard pagefault count of hardest hit process: 7702
Number of processes hit: 81
Dobbiamo lavorare su questo.
35029 mi sembrano troppi, considerando anche il fatto che hai 24 GB di RAM. Mi aspetterei valori più bassi.
Questo potrebbe dipendere da una configurazione non corretta del sistema.
Com'è impostato il file di paging?
WIN+PAUSA, ti compare il pannello di sistema. RAM utilizzabile e totale coincidono? O sta usando meno RAM di quella installata nel sistema?
P.S. Nel report fa riferimento a spotify.exe, come processo che si sta "comportando male"
Hai problemi solo con spotify o anche altri software?
Durante il freeze LatencyMon era in esecuzione?
Il report è perfetto nella parte di DPC e ISR, sono spariti i quei valori sballati legati al driver di storage
Adesso resta il problema in questa parte del report,
Dobbiamo lavorare su questo.
35029 mi sembrano troppi, considerando anche il fatto che hai 24 GB di RAM. Mi aspetterei valori più bassi.
Questo potrebbe dipendere da una configurazione non corretta del sistema.
Com'è impostato il file di paging?
WIN+PAUSA, ti compare il pannello di sistema. RAM utilizzabile e totale coincidono? O sta usando meno RAM di quella installata nel sistema?
P.S. Nel report fa riferimento a spotify.exe, come processo che si sta "comportando male"
Hai problemi solo con spotify o anche altri software?
il totale ram mi da 23,9 installato ti linko cosa vedo.
si li è stato spotify perchè solo con audio attivo sento il freeze oppure quando guardo un film, tipo prime video.
poi latency era avviato ma stoppato appena ho cliccato su start ha fatto quel freeze
https://ibb.co/ZBG0ymY
stavo pensando una cosa ho rimesso tutto anche gli hard disk tranne quello mezzo morto, ma se fosse un problema di video tipo shceda video anche?perchè ora ho connesso solo un monitor, di solito collego quello della scrivania e poi alla tv grande, e sto provando un pò il pc e ora sta andando anche con latency provando a riaprire crystal ma niente freeze
Blue_screen_of_death
12-10-2019, 20:42
poi latency era avviato ma stoppato appena ho cliccato su start ha fatto quel freeze
Ah ecco perché nell'ultimo report non compariva il driver dello storage.
Siccome ha freezato mentre stava avviando il monitoraggio, non è stato catturato il freeze.
Fammi un ultimo test, per toglierci ogni dubbio: avvia il monitoraggio con LatencyMon, poi avvia testa la velocità dell'SSD con CrystalDiskMark.
Al termine del test mandami il report di LatencyMon.
Se continua a mostrare problemi relativi al driver di storage, cerchiamo una soluzione.
Mi aspetto esito disastroso :D
Blue_screen_of_death
12-10-2019, 20:44
stavo pensando una cosa ho rimesso tutto anche gli hard disk tranne quello mezzo morto, ma se fosse un problema di video tipo shceda video anche?perchè ora ho connesso solo un monitor, di solito collego quello della scrivania e poi alla tv grande, e sto provando un pò il pc e ora sta andando anche con latency provando a riaprire crystal ma niente freeze
OK, lascia quel disco scollegato e prova con CrystalDiskMark come ho scritto nel post precedente.
Magari puoi tenere anche aperto l'audio durante il test, per capire se si manifesta il problema.
OK, lascia quel disco scollegato e prova con CrystalDiskMark come ho scritto nel post precedente.
Magari puoi tenere anche aperto l'audio durante il test, per capire se si manifesta il problema.
intanto ti copio latency subito dopo aver avviato pc e fatto partire crystal ,il freeze non l'ho sentito non avendo l'audio acceso però ho visto la barra diventare rossa su latency quindi presumo sia di nuovo problema del disco di quelli collegati, ora provo comunque col test come mi hai detto
_________________________________________________________________________________________________________
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:00:29 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 197,80
Average measured interrupt to process latency (µs): 5,288301
Highest measured interrupt to DPC latency (µs): 194,0
Average measured interrupt to DPC latency (µs): 1,662894
_________________________________________________________________________________________________________
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): 19,920
Driver with highest ISR routine execution time: Wdf01000.sys - Runtime framework driver modalità kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000783
Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Total time spent in ISRs (%) 0,001587
ISR count (execution time <250 µs): 2055
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): 100844,840
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0,028970
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 0,093593
DPC count (execution time <250 µs): 71968
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 2
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: backgroundtaskhost.exe
Total number of hard pagefaults 1497
Hard pagefault count of hardest hit process: 1135
Number of processes hit: 23
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0,698791
CPU 0 ISR highest execution time (µs): 19,920
CPU 0 ISR total execution time (s): 0,005472
CPU 0 ISR count: 2000
CPU 0 DPC highest execution time (µs): 243,550
CPU 0 DPC total execution time (s): 0,187304
CPU 0 DPC count: 65554
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,339433
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 118,50
CPU 1 DPC total execution time (s): 0,002145
CPU 1 DPC count: 643
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1,201225
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 100844,840
CPU 2 DPC total execution time (s): 0,119075
CPU 2 DPC count: 2097
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,577328
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): 250,550
CPU 3 DPC total execution time (s): 0,004667
CPU 3 DPC count: 925
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,321680
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,550
CPU 4 DPC total execution time (s): 0,004146
CPU 4 DPC count: 1062
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,442157
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): 147,260
CPU 5 DPC total execution time (s): 0,000860
CPU 5 DPC count: 169
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0,245441
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): 19,330
CPU 6 DPC total execution time (s): 0,001008
CPU 6 DPC count: 283
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0,228037
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): 23,450
CPU 7 DPC total execution time (s): 0,000466
CPU 7 DPC count: 134
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,244372
CPU 8 ISR highest execution time (µs): 1,620
CPU 8 ISR total execution time (s): 0,000033
CPU 8 ISR count: 34
CPU 8 DPC highest execution time (µs): 26,070
CPU 8 DPC total execution time (s): 0,001804
CPU 8 DPC count: 468
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,220540
CPU 9 ISR highest execution time (µs): 1,050
CPU 9 ISR total execution time (s): 0,000002
CPU 9 ISR count: 2
CPU 9 DPC highest execution time (µs): 28,90
CPU 9 DPC total execution time (s): 0,000505
CPU 9 DPC count: 103
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0,250299
CPU 10 ISR highest execution time (µs): 1,80
CPU 10 ISR total execution time (s): 0,000014
CPU 10 ISR count: 13
CPU 10 DPC highest execution time (µs): 28,050
CPU 10 DPC total execution time (s): 0,001849
CPU 10 DPC count: 301
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0,255444
CPU 11 ISR highest execution time (µs): 1,40
CPU 11 ISR total execution time (s): 0,000007
CPU 11 ISR count: 6
CPU 11 DPC highest execution time (µs): 27,870
CPU 11 DPC total execution time (s): 0,002054
CPU 11 DPC count: 232
_________________________________________________________________________________________________________
OK, lascia quel disco scollegato e prova con CrystalDiskMark come ho scritto nel post precedente.
Magari puoi tenere anche aperto l'audio durante il test, per capire se si manifesta il problema.
fatto il test
_________________________________________________________________________________________________________
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:05:55 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 215,70
Average measured interrupt to process latency (µs): 6,195179
Highest measured interrupt to DPC latency (µs): 210,90
Average measured interrupt to DPC latency (µs): 2,373999
_________________________________________________________________________________________________________
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): 252,380
Driver with highest ISR routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Highest reported total ISR routine time (%): 0,003975
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,006179
ISR count (execution time <250 µs): 80086
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 1
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): 934312,730
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 2,219115
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,961350
DPC count (execution time <250 µs): 28171302
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 52
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: diskmark64.exe
Total number of hard pagefaults 4319
Hard pagefault count of hardest hit process: 1045
Number of processes hit: 51
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 46,695912
CPU 0 ISR highest execution time (µs): 145,990
CPU 0 ISR total execution time (s): 0,154352
CPU 0 ISR count: 51769
CPU 0 DPC highest execution time (µs): 292,570
CPU 0 DPC total execution time (s): 33,036715
CPU 0 DPC count: 6717389
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 45,559918
CPU 1 ISR highest execution time (µs): 252,380
CPU 1 ISR total execution time (s): 0,094475
CPU 1 ISR count: 23842
CPU 1 DPC highest execution time (µs): 398,920
CPU 1 DPC total execution time (s): 20,839760
CPU 1 DPC count: 7939999
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 21,956164
CPU 2 ISR highest execution time (µs): 12,10
CPU 2 ISR total execution time (s): 0,010833
CPU 2 ISR count: 2752
CPU 2 DPC highest execution time (µs): 239670,554688
CPU 2 DPC total execution time (s): 11,467669
CPU 2 DPC count: 2346686
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 21,541644
CPU 3 ISR highest execution time (µs): 11,240
CPU 3 ISR total execution time (s): 0,002280
CPU 3 ISR count: 764
CPU 3 DPC highest execution time (µs): 555215,794687
CPU 3 DPC total execution time (s): 12,390101
CPU 3 DPC count: 2360124
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 19,875713
CPU 4 ISR highest execution time (µs): 7,360
CPU 4 ISR total execution time (s): 0,000537
CPU 4 ISR count: 259
CPU 4 DPC highest execution time (µs): 381023,219687
CPU 4 DPC total execution time (s): 11,612215
CPU 4 DPC count: 2343580
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 20,067132
CPU 5 ISR highest execution time (µs): 5,520
CPU 5 ISR total execution time (s): 0,000006
CPU 5 ISR count: 1
CPU 5 DPC highest execution time (µs): 426309,234687
CPU 5 DPC total execution time (s): 11,799944
CPU 5 DPC count: 2364755
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 21,094488
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): 314,630
CPU 6 DPC total execution time (s): 12,010117
CPU 6 DPC count: 2025270
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 20,795546
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): 934312,730
CPU 7 DPC total execution time (s): 12,863128
CPU 7 DPC count: 2048519
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 4,848620
CPU 8 ISR highest execution time (µs): 2,30
CPU 8 ISR total execution time (s): 0,000440
CPU 8 ISR count: 442
CPU 8 DPC highest execution time (µs): 230,860
CPU 8 DPC total execution time (s): 0,049927
CPU 8 DPC count: 12137
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,685382
CPU 9 ISR highest execution time (µs): 2,040
CPU 9 ISR total execution time (s): 0,000038
CPU 9 ISR count: 33
CPU 9 DPC highest execution time (µs): 246,850
CPU 9 DPC total execution time (s): 0,012514
CPU 9 DPC count: 2549
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 3,953314
CPU 10 ISR highest execution time (µs): 4,410
CPU 10 ISR total execution time (s): 0,000096
CPU 10 ISR count: 72
CPU 10 DPC highest execution time (µs): 132,10
CPU 10 DPC total execution time (s): 0,041356
CPU 10 DPC count: 6600
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,871520
CPU 11 ISR highest execution time (µs): 3,060
CPU 11 ISR total execution time (s): 0,000177
CPU 11 ISR count: 153
CPU 11 DPC highest execution time (µs): 234,030
CPU 11 DPC total execution time (s): 0,035735
CPU 11 DPC count: 3759
_________________________________________________________________________________________________________
Blue_screen_of_death
12-10-2019, 21:14
Ed ecco gli esiti disastrosi che mi aspettavo.
Con CrystalDiskMark le cose vanno ancora peggio, perché stressa maggiormente il disco e il driver di storage.
Ti sta rallentando 5 processori logici.
Proviamo a reinstallare il driver SATA.
Vai in Gestione dispositivi
Individua il Controller SATA
Disinstallalo
Riavvia il PC
Vedi se il problema di CrystalDiskInfo è sparito. Prova ad aprirlo mentre tieni attivo il monitoraggio e (se vuoi) anche un audio.
Poi condividi il report, come sempre.
Ed ecco gli esiti disastrosi che mi aspettavo.
Con CrystalDiskMark le cose vanno ancora peggio, perché stressa maggiormente il disco e il driver di storage.
Ti sta rallentando 5 processori logici.
Proviamo a reinstallare il driver SATA.
Vai in Gestione dispositivi
Individua il Controller SATA
Disinstallalo
Riavvia il PC
Vedi se il problema di CrystalDiskInfo è sparito. Prova ad aprirlo mentre tieni attivo il monitoraggio e (se vuoi) anche un audio.
Poi condividi il report, come sempre.
ti mando cosa vedo, tutti e 4 quei driver o solo quelli sotto controller ide etc.. fatto al riavvio devo ricollegare tutti gli altri hard disk o tengo solo l'ssd? e rifaccio il test con c.mark o metto solo latency e c.info?
https://ibb.co/58hmfTx
Blue_screen_of_death
12-10-2019, 21:26
ti mando cosa vedo, tutti e 4 quei driver o solo quelli sotto controller ide etc.. fatto al riavvio devo ricollegare tutti gli altri hard disk o tengo solo l'ssd? e rifaccio il test con c.mark o metto solo latency e c.info?
https://ibb.co/58hmfTx
Disinstalla questi:
- Controller standard NVM Express
- AMD SATA Controller
- Controller AHCI SATA standard
Blue_screen_of_death
12-10-2019, 21:27
ti mando cosa vedo, tutti e 4 quei driver o solo quelli sotto controller ide etc.. fatto al riavvio devo ricollegare tutti gli altri hard disk o tengo solo l'ssd? e rifaccio il test con c.mark o metto solo latency e c.info?
https://ibb.co/58hmfTx
Lascia solo SSD per ora.
Avvia LatencyMon, un audio (per capire se c'è il freeze) e apri CrystalDiskInfo.
Edit. Ho dimenticato di chiederti una cosa: hai anche altre periferiche SATA? Masterizzatori, ...
Lascia solo SSD per ora.
Avvia LatencyMon, un audio (per capire se c'è il freeze) e apri CrystalDiskInfo.
Edit. Ho dimenticato di chiederti una cosa: hai anche altre periferiche SATA? Masterizzatori, ...
allora fatto tutto niente freeze ti copio anche il report, si ho un masterizzatore connesso devo toglierlo?
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:00:50 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 171,60
Average measured interrupt to process latency (µs): 5,727222
Highest measured interrupt to DPC latency (µs): 164,60
Average measured interrupt to DPC latency (µs): 1,876447
_________________________________________________________________________________________________________
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): 18,850
Driver with highest ISR routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Highest reported total ISR routine time (%): 0,008155
Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Total time spent in ISRs (%) 0,010925
ISR count (execution time <250 µs): 26134
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): 275,420
Driver with highest DPC routine execution time: tcpip.sys - Driver TCP/IP, Microsoft Corporation
Highest reported total DPC routine time (%): 0,059155
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,143773
DPC count (execution time <250 µs): 188308
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: steamwebhelper.exe
Total number of hard pagefaults 12379
Hard pagefault count of hardest hit process: 2615
Number of processes hit: 61
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1,813655
CPU 0 ISR highest execution time (µs): 18,850
CPU 0 ISR total execution time (s): 0,062546
CPU 0 ISR count: 24944
CPU 0 DPC highest execution time (µs): 245,440
CPU 0 DPC total execution time (s): 0,632201
CPU 0 DPC count: 150180
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1,123925
CPU 1 ISR highest execution time (µs): 10,930
CPU 1 ISR total execution time (s): 0,002591
CPU 1 ISR count: 740
CPU 1 DPC highest execution time (µs): 247,380
CPU 1 DPC total execution time (s): 0,024214
CPU 1 DPC count: 3792
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,659032
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 249,780
CPU 2 DPC total execution time (s): 0,070810
CPU 2 DPC count: 8493
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,559686
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): 124,350
CPU 3 DPC total execution time (s): 0,011499
CPU 3 DPC count: 3242
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,461488
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): 102,560
CPU 4 DPC total execution time (s): 0,014281
CPU 4 DPC count: 3399
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,449674
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): 57,870
CPU 5 DPC total execution time (s): 0,004613
CPU 5 DPC count: 1085
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 0,525170
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): 84,920
CPU 6 DPC total execution time (s): 0,012955
CPU 6 DPC count: 2991
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0,548917
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): 111,610
CPU 7 DPC total execution time (s): 0,005839
CPU 7 DPC count: 1306
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 1,288446
CPU 8 ISR highest execution time (µs): 4,190
CPU 8 ISR total execution time (s): 0,000312
CPU 8 ISR count: 317
CPU 8 DPC highest execution time (µs): 275,420
CPU 8 DPC total execution time (s): 0,051339
CPU 8 DPC count: 9340
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,637012
CPU 9 ISR highest execution time (µs): 2,180
CPU 9 ISR total execution time (s): 0,000030
CPU 9 ISR count: 23
CPU 9 DPC highest execution time (µs): 247,170
CPU 9 DPC total execution time (s): 0,006612
CPU 9 DPC count: 890
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0,560667
CPU 10 ISR highest execution time (µs): 2,020
CPU 10 ISR total execution time (s): 0,000045
CPU 10 ISR count: 39
CPU 10 DPC highest execution time (µs): 222,970
CPU 10 DPC total execution time (s): 0,019532
CPU 10 DPC count: 2595
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0,563214
CPU 11 ISR highest execution time (µs): 4,150
CPU 11 ISR total execution time (s): 0,000088
CPU 11 ISR count: 71
CPU 11 DPC highest execution time (µs): 85,830
CPU 11 DPC total execution time (s): 0,009553
CPU 11 DPC count: 996
_________________________________________________________________________________________________________
Blue_screen_of_death
12-10-2019, 21:36
Questo report è perfetto.
No, per ora non scollegare il masterizzatore, altrimenti non ci capiamo più nulla.
Dobbiamo capire se la reinstallazione dei driver ha risolto il problema. E l'unico modo per capirlo è stressare il driver di storage :D
Magari rifai anche un test con CrystalDiskMark, tenendo aperto come al solito LatencyMon e anche un file audio (per capire se c'è freeze o meno)
Questo report è perfetto.
No, per ora non scollegare il masterizzatore, altrimenti non ci capiamo più nulla.
Dobbiamo capire se la reinstallazione dei driver ha risolto il problema. E l'unico modo per capirlo è stressare il driver di storage :D
Magari rifai anche un test con CrystalDiskMark, tenendo aperto come al solito LatencyMon e anche un file audio (per capire se c'è freeze o meno)
ok perfetto, ho notato che il driver amd che ho disinstallato prima non c'è più ma è venuto fuori un secondo ahci sata standard
Blue_screen_of_death
12-10-2019, 21:40
ok perfetto, ho notato che il driver amd che ho disinstallato prima non c'è più ma è venuto fuori un secondo ahci sata standard
Ti ha installato i driver generici di Microsoft, mentre prima avevi i driver di AMD.
Lascia quelli per adesso. A volte i driver forniti da Microsoft sono più stabili.
Ti ha installato i driver generici di Microsoft, mentre prima avevi i driver di AMD.
Lascia quelli per adesso. A volte i driver forniti da Microsoft sono più stabili.
ok ecco il report senza freeze
_________________________________________________________________________________________________________
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:05:46 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 191,10
Average measured interrupt to process latency (µs): 6,184263
Highest measured interrupt to DPC latency (µs): 186,60
Average measured interrupt to DPC latency (µs): 2,341860
_________________________________________________________________________________________________________
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): 219,780
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,003954
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,004301
ISR count (execution time <250 µs): 40608
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): 915551,490
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 2,161283
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,934418
DPC count (execution time <250 µs): 28260069
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 34
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: msmpeng.exe
Total number of hard pagefaults 1768
Hard pagefault count of hardest hit process: 1085
Number of processes hit: 17
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 49,031929
CPU 0 ISR highest execution time (µs): 203,60
CPU 0 ISR total execution time (s): 0,093401
CPU 0 ISR count: 21486
CPU 0 DPC highest execution time (µs): 258628,858750
CPU 0 DPC total execution time (s): 32,365126
CPU 0 DPC count: 6662719
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 41,612292
CPU 1 ISR highest execution time (µs): 219,780
CPU 1 ISR total execution time (s): 0,077010
CPU 1 ISR count: 17282
CPU 1 DPC highest execution time (µs): 915551,490
CPU 1 DPC total execution time (s): 21,481045
CPU 1 DPC count: 8030047
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 21,769524
CPU 2 ISR highest execution time (µs): 12,680
CPU 2 ISR total execution time (s): 0,007258
CPU 2 ISR count: 1414
CPU 2 DPC highest execution time (µs): 679265,374688
CPU 2 DPC total execution time (s): 12,009237
CPU 2 DPC count: 2424979
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 24,813635
CPU 3 ISR highest execution time (µs): 10,120
CPU 3 ISR total execution time (s): 0,000809
CPU 3 ISR count: 306
CPU 3 DPC highest execution time (µs): 290689,644688
CPU 3 DPC total execution time (s): 10,573754
CPU 3 DPC count: 2397174
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 19,496766
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): 882242,3850
CPU 4 DPC total execution time (s): 11,821747
CPU 4 DPC count: 2346945
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 19,71760
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): 145,970
CPU 5 DPC total execution time (s): 10,13050
CPU 5 DPC count: 2351368
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 21,020021
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): 610743,680
CPU 6 DPC total execution time (s): 12,330940
CPU 6 DPC count: 1994360
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 20,480937
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): 130,310
CPU 7 DPC total execution time (s): 11,049736
CPU 7 DPC count: 2035888
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,669704
CPU 8 ISR highest execution time (µs): 1,570
CPU 8 ISR total execution time (s): 0,000097
CPU 8 ISR count: 100
CPU 8 DPC highest execution time (µs): 112,110
CPU 8 DPC total execution time (s): 0,035634
CPU 8 DPC count: 9972
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,266937
CPU 9 ISR highest execution time (µs): 1,360
CPU 9 ISR total execution time (s): 0,000001
CPU 9 ISR count: 1
CPU 9 DPC highest execution time (µs): 174,310
CPU 9 DPC total execution time (s): 0,004082
CPU 9 DPC count: 1000
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 3,914168
CPU 10 ISR highest execution time (µs): 1,710
CPU 10 ISR total execution time (s): 0,000011
CPU 10 ISR count: 10
CPU 10 DPC highest execution time (µs): 122,990
CPU 10 DPC total execution time (s): 0,024611
CPU 10 DPC count: 3835
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,852824
CPU 11 ISR highest execution time (µs): 1,430
CPU 11 ISR total execution time (s): 0,000009
CPU 11 ISR count: 9
CPU 11 DPC highest execution time (µs): 110,190
CPU 11 DPC total execution time (s): 0,015907
CPU 11 DPC count: 1829
_________________________________________________________________________________________________________
Blue_screen_of_death
12-10-2019, 21:51
Qui c'è ancora troppa latenza sullo storage.
Allora non resta che provare a scollegare anche il masterizzatore, dato che è l'ultima cosa che è rimasta :)
E poi riprovare con i soliti test.
Qui c'è ancora troppa latenza sullo storage.
Allora non resta che provare a scollegare anche il masterizzatore, dato che è l'ultima cosa che è rimasta :)
E poi riprovare con i soliti test.
fatto tutto niente freeze con crystalinfo e poi ho fatto il test ma uguale niente freeze ecco il report:
_________________________________________________________________________________________________________
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:06:24 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 210,20
Average measured interrupt to process latency (µs): 6,106209
Highest measured interrupt to DPC latency (µs): 206,10
Average measured interrupt to DPC latency (µs): 2,221741
_________________________________________________________________________________________________________
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): 242,230
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,003346
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,004087
ISR count (execution time <250 µs): 47005
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): 943889,460313
Driver with highest DPC routine execution time: netbt.sys - MBT Transport driver, Microsoft Corporation
Highest reported total DPC routine time (%): 2,014342
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,721155
DPC count (execution time <250 µs): 28342284
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 33
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: spotify.exe
Total number of hard pagefaults 12763
Hard pagefault count of hardest hit process: 4675
Number of processes hit: 39
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 49,127050
CPU 0 ISR highest execution time (µs): 242,230
CPU 0 ISR total execution time (s): 0,095612
CPU 0 ISR count: 26475
CPU 0 DPC highest execution time (µs): 879916,174063
CPU 0 DPC total execution time (s): 33,258995
CPU 0 DPC count: 6578593
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 46,581889
CPU 1 ISR highest execution time (µs): 181,740
CPU 1 ISR total execution time (s): 0,085865
CPU 1 ISR count: 18557
CPU 1 DPC highest execution time (µs): 651406,954688
CPU 1 DPC total execution time (s): 22,493483
CPU 1 DPC count: 8041612
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 23,890986
CPU 2 ISR highest execution time (µs): 11,660
CPU 2 ISR total execution time (s): 0,005778
CPU 2 ISR count: 1151
CPU 2 DPC highest execution time (µs): 943889,460313
CPU 2 DPC total execution time (s): 11,881266
CPU 2 DPC count: 2443125
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 22,546326
CPU 3 ISR highest execution time (µs): 8,420
CPU 3 ISR total execution time (s): 0,000339
CPU 3 ISR count: 123
CPU 3 DPC highest execution time (µs): 233,550
CPU 3 DPC total execution time (s): 10,962766
CPU 3 DPC count: 2459743
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 20,274866
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): 113,470
CPU 4 DPC total execution time (s): 10,678553
CPU 4 DPC count: 2380001
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 20,484387
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): 218839,979688
CPU 5 DPC total execution time (s): 11,085561
CPU 5 DPC count: 2369152
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 21,572990
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): 358349,1150
CPU 6 DPC total execution time (s): 12,753170
CPU 6 DPC count: 2006922
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 20,938428
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): 558389,244688
CPU 7 DPC total execution time (s): 12,168843
CPU 7 DPC count: 2040141
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,802596
CPU 8 ISR highest execution time (µs): 6,070
CPU 8 ISR total execution time (s): 0,000585
CPU 8 ISR count: 572
CPU 8 DPC highest execution time (µs): 138,750
CPU 8 DPC total execution time (s): 0,052295
CPU 8 DPC count: 14349
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,434905
CPU 9 ISR highest execution time (µs): 1,540
CPU 9 ISR total execution time (s): 0,000012
CPU 9 ISR count: 10
CPU 9 DPC highest execution time (µs): 77,940
CPU 9 DPC total execution time (s): 0,008194
CPU 9 DPC count: 1645
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 4,054431
CPU 10 ISR highest execution time (µs): 2,010
CPU 10 ISR total execution time (s): 0,000049
CPU 10 ISR count: 41
CPU 10 DPC highest execution time (µs): 90,210
CPU 10 DPC total execution time (s): 0,032595
CPU 10 DPC count: 4928
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 4,074454
CPU 11 ISR highest execution time (µs): 4,640
CPU 11 ISR total execution time (s): 0,000095
CPU 11 ISR count: 76
CPU 11 DPC highest execution time (µs): 115,090
CPU 11 DPC total execution time (s): 0,020312
CPU 11 DPC count: 2120
_________________________________________________________________________________________________________
Blue_screen_of_death
12-10-2019, 22:18
ok bene
se non hai già chiuso LatencyMon riesci a mandarmi uno screen della sezione Drivers?
Voglio dare un'occhiata rapida anche agli altri driver.
ok bene
se non hai già chiuso LatencyMon riesci a mandarmi uno screen della sezione Drivers?
Voglio dare un'occhiata rapida anche agli altri driver.
subito dimmi se ti bastano perchè ho visto e gli altri sono tutti a zero
https://ibb.co/hHNK8qb
https://ibb.co/cYGWGLB
https://ibb.co/3FxMzKt
https://ibb.co/QNMQfsN
https://ibb.co/pz8btTS
Blue_screen_of_death
12-10-2019, 22:39
ok, basta così.. quel che dovevo vedere si vede benissimo.
Tutto nella norma, eccetto i tempi di stornvme.sys che sono troppo alti.
Quindi storport.sys dei report precedenti + stornvme.sys di questo report = è colpa dell'SSD o del controller NVME
Quindi c'entra lo storage sì, oramai si è capito, ma probabilmente il SATA non c'entra niente. E' l'NVME il problema o l'SSD.
Vediamo se esistono driver aggiornati per il controller o firmware dell'SSD che risolvono il problema.
Sai quale controller NVME è installato?
Se non sai, vai in gestione dispositivi, apri le proprietà del controller nvme, scheda Dettagli, ID hardware e copiami quei codici
ok, basta così.. quel che dovevo vedere si vede benissimo.
Tutto nella norma, eccetto i tempi di stornvme.sys che sono troppo alti.
Quindi storport.sys dei report precedenti + stornvme.sys di questo report = è colpa dell'SSD o del controller NVME
Quindi c'entra lo storage sì, oramai si è capito, ma probabilmente il SATA non c'entra niente. E' l'NVME il problema o l'SSD.
Vediamo se esistono driver aggiornati per il controller o firmware dell'SSD che risolvono il problema.
Sai quale controller NVME è installato?
Se non sai, vai in gestione dispositivi, apri le proprietà del controller nvme, scheda Dettagli, ID hardware e copiami quei codici
sono questi qui i codici
PCI\VEN_1987&DEV_5012&SUBSYS_50121987&REV_01
PCI\VEN_1987&DEV_5012&SUBSYS_50121987
PCI\VEN_1987&DEV_5012&CC_010802
PCI\VEN_1987&DEV_5012&CC_0108
il mio ssd è questo: https://www.amazon.it/gp/product/B07LGF54XR/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
Blue_screen_of_death
12-10-2019, 23:08
Una curiosità.. le performance mostrate da CrystalDiskMark sono nella norma? O sono troppo basse?
Una curiosità.. le performance mostrate da CrystalDiskMark sono nella norma? O sono troppo basse?
ti mando lo screen a me sembrano nella norma
https://ibb.co/2M9Frc1
Blue_screen_of_death
13-10-2019, 08:47
Si, nella norma.
Comunque i lag sono causati da
- Controller NVME
- SSD NVME
- Controller SATA
- Periferiche SATA
Guardando gli ultimi report direi una delle prime due.
Disabilita il controller SATA nel BIOS.
Poi fai i soliti test, attiva il monitoraggio LatencyMon, apri un audio
Fai partire CrystalDiskInfo e vedi che succede
Poi fai partire CrystalDiskMark e vedi che succede.
Oltre ai report di latencyMon mandami anche lo screenshot della sezione Drivers
Se col controller SATA disabilitato non ci sono problemi allora è il problema è il controller SATA o una periferica SATA
Se col controller SATA disabilitato ci sono ancora problemi allora è il controller NVME o l'SSD.
Si, nella norma.
Comunque i lag sono causati da
- Controller NVME
- SSD NVME
- Controller SATA
- Periferiche SATA
Guardando gli ultimi report direi una delle prime due.
Disabilita il controller SATA nel BIOS.
Poi fai i soliti test, attiva il monitoraggio LatencyMon, apri un audio
Fai partire CrystalDiskInfo e vedi che succede
Poi fai partire CrystalDiskMark e vedi che succede.
Oltre ai report di latencyMon mandami anche lo screenshot della sezione Drivers
Se col controller SATA disabilitato non ci sono problemi allora è il problema è il controller SATA o una periferica SATA
Se col controller SATA disabilitato ci sono ancora problemi allora è il controller NVME o l'SSD.
nel bios della gigabyte non lo vedo il controller SATA, ho sata mode su AHCI, poi NVMe Raid mode disabled e chipset SATA port enabled
Blue_screen_of_death
13-10-2019, 12:11
Metti Chipset SATA Port su Disabled
Riavvia e accertati che è stato disabilitato, ovvero che in Gestione dispositivi non vedi più Controller SATA.
Se è così, prova con i soliti test e scopriamo se il lag sono del controller SATA o NVMe.
Metti Chipset SATA Port su Disabled
Riavvia e accertati che è stato disabilitato, ovvero che in Gestione dispositivi non vedi più Controller SATA.
Se è così, prova con i soliti test e scopriamo se il lag sono del controller SATA o NVMe.
fatto ma vedo sempre sotto controller ide ata/atapi: due voci controller ahci sata standard
Blue_screen_of_death
13-10-2019, 12:24
OK, non so perché viene ancora rilevato
Comunque le periferiche SATA sono tutte scollegate / disattivate?
Cioè nel sistema non vedi nessuna di quelle periferiche?
Se è così, allora fai comunque la prova.
CrystalDiskInfo e CrystalDiskMark con audio attivo e con LatencyMon avviato.
Vediamo se il problema persiste.
OK, non so perché viene ancora rilevato
Comunque le periferiche SATA sono tutte scollegate / disattivate?
Cioè nel sistema non vedi nessuna di quelle periferiche?
Se è così, allora fai comunque la prova.
CrystalDiskInfo e CrystalDiskMark con audio attivo e con LatencyMon avviato.
Vediamo se il problema persiste.
si tutto scollegato, non mi ha freezato ora ti copio il report e lo screen dei driver.
https://ibb.co/26CNw1t
_________________________________________________________________________________________________________
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:07:37 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 250,70
Average measured interrupt to process latency (µs): 6,208129
Highest measured interrupt to DPC latency (µs): 246,40
Average measured interrupt to DPC latency (µs): 2,311951
_________________________________________________________________________________________________________
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): 236,060
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,286876
Driver with highest ISR total time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,00660
ISR count (execution time <250 µs): 141427
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): 872250,640
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 1,637474
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,295440
DPC count (execution time <250 µs): 28456983
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 36
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: chrome.exe
Total number of hard pagefaults 5445
Hard pagefault count of hardest hit process: 2168
Number of processes hit: 42
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 52,739872
CPU 0 ISR highest execution time (µs): 236,060
CPU 0 ISR total execution time (s): 0,192739
CPU 0 ISR count: 82207
CPU 0 DPC highest execution time (µs): 586973,409062
CPU 0 DPC total execution time (s): 33,907368
CPU 0 DPC count: 6762489
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 48,489041
CPU 1 ISR highest execution time (µs): 129,990
CPU 1 ISR total execution time (s): 0,147229
CPU 1 ISR count: 50336
CPU 1 DPC highest execution time (µs): 527317,160
CPU 1 DPC total execution time (s): 20,697122
CPU 1 DPC count: 8062533
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 22,591411
CPU 2 ISR highest execution time (µs): 11,210
CPU 2 ISR total execution time (s): 0,014762
CPU 2 ISR count: 4966
CPU 2 DPC highest execution time (µs): 681789,055312
CPU 2 DPC total execution time (s): 12,06970
CPU 2 DPC count: 2447267
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 23,267294
CPU 3 ISR highest execution time (µs): 10,820
CPU 3 ISR total execution time (s): 0,003688
CPU 3 ISR count: 1577
CPU 3 DPC highest execution time (µs): 504079,604687
CPU 3 DPC total execution time (s): 11,619189
CPU 3 DPC count: 2466219
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 24,272208
CPU 4 ISR highest execution time (µs): 7,910
CPU 4 ISR total execution time (s): 0,002370
CPU 4 ISR count: 1294
CPU 4 DPC highest execution time (µs): 568061,615313
CPU 4 DPC total execution time (s): 12,03770
CPU 4 DPC count: 2333696
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 21,516076
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): 872250,640
CPU 5 DPC total execution time (s): 12,763483
CPU 5 DPC count: 2346565
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 22,271182
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): 415381,984687
CPU 6 DPC total execution time (s): 11,570663
CPU 6 DPC count: 1982577
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 21,699507
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): 126,140
CPU 7 DPC total execution time (s): 11,096116
CPU 7 DPC count: 2031950
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 4,561154
CPU 8 ISR highest execution time (µs): 6,650
CPU 8 ISR total execution time (s): 0,000903
CPU 8 ISR count: 823
CPU 8 DPC highest execution time (µs): 118,390
CPU 8 DPC total execution time (s): 0,049972
CPU 8 DPC count: 13366
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 4,147792
CPU 9 ISR highest execution time (µs): 2,440
CPU 9 ISR total execution time (s): 0,000034
CPU 9 ISR count: 25
CPU 9 DPC highest execution time (µs): 110,240
CPU 9 DPC total execution time (s): 0,008917
CPU 9 DPC count: 1911
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 4,725747
CPU 10 ISR highest execution time (µs): 1,940
CPU 10 ISR total execution time (s): 0,000116
CPU 10 ISR count: 98
CPU 10 DPC highest execution time (µs): 204,180
CPU 10 DPC total execution time (s): 0,036440
CPU 10 DPC count: 5546
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 4,873562
CPU 11 ISR highest execution time (µs): 3,130
CPU 11 ISR total execution time (s): 0,000131
CPU 11 ISR count: 101
CPU 11 DPC highest execution time (µs): 109,770
CPU 11 DPC total execution time (s): 0,029645
CPU 11 DPC count: 2919
_________________________________________________________________________________________________________
Blue_screen_of_death
13-10-2019, 13:05
Non mi tornano i risultati tra lo screen Drivers e il report.
Dicono cose diverse.
Hai chiuso e riaperto LatencyMon prima di fare lo screen dei driver? O fermato e riavviato il monitoraggio?
Non mi tornano i risultati tra lo screen Drivers e il report.
Dicono cose diverse.
Hai chiuso e riaperto LatencyMon prima di fare lo screen dei driver? O fermato e riavviato il monitoraggio?
fermato latency
ti rifaccio tutto?
Blue_screen_of_death
13-10-2019, 13:13
Si
Si
_________________________________________________________________________________________________________
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:05:01 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 303,30
Average measured interrupt to process latency (µs): 6,152540
Highest measured interrupt to DPC latency (µs): 299,60
Average measured interrupt to DPC latency (µs): 2,301044
_________________________________________________________________________________________________________
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): 18,0
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000635
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,000822
ISR count (execution time <250 µs): 6235
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): 661667,2550
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 2,391723
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 3,264158
DPC count (execution time <250 µs): 28725683
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 23
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: svchost.exe
Total number of hard pagefaults 119
Hard pagefault count of hardest hit process: 39
Number of processes hit: 5
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 46,826298
CPU 0 ISR highest execution time (µs): 14,050
CPU 0 ISR total execution time (s): 0,012130
CPU 0 ISR count: 2536
CPU 0 DPC highest execution time (µs): 261139,268750
CPU 0 DPC total execution time (s): 32,420293
CPU 0 DPC count: 6605691
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 39,131115
CPU 1 ISR highest execution time (µs): 18,0
CPU 1 ISR total execution time (s): 0,017142
CPU 1 ISR count: 3481
CPU 1 DPC highest execution time (µs): 570710,090
CPU 1 DPC total execution time (s): 20,864848
CPU 1 DPC count: 8528686
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 27,611816
CPU 2 ISR highest execution time (µs): 7,790
CPU 2 ISR total execution time (s): 0,000317
CPU 2 ISR count: 110
CPU 2 DPC highest execution time (µs): 546844,345313
CPU 2 DPC total execution time (s): 10,274718
CPU 2 DPC count: 2364445
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 21,598712
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): 654112,6150
CPU 3 DPC total execution time (s): 11,523310
CPU 3 DPC count: 2426628
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 19,217510
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): 392138,575313
CPU 4 DPC total execution time (s): 9,851909
CPU 4 DPC count: 2353420
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 19,552929
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): 439457,5150
CPU 5 DPC total execution time (s): 9,975174
CPU 5 DPC count: 2352874
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 20,603307
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): 342885,4250
CPU 6 DPC total execution time (s): 11,498148
CPU 6 DPC count: 2026387
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 20,209706
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): 661667,2550
CPU 7 DPC total execution time (s): 11,430112
CPU 7 DPC count: 2052619
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,799994
CPU 8 ISR highest execution time (µs): 1,420
CPU 8 ISR total execution time (s): 0,000091
CPU 8 ISR count: 97
CPU 8 DPC highest execution time (µs): 115,780
CPU 8 DPC total execution time (s): 0,029730
CPU 8 DPC count: 8705
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,548454
CPU 9 ISR highest execution time (µs): 0,930
CPU 9 ISR total execution time (s): 0,000001
CPU 9 ISR count: 1
CPU 9 DPC highest execution time (µs): 66,190
CPU 9 DPC total execution time (s): 0,005405
CPU 9 DPC count: 1124
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,932871
CPU 10 ISR highest execution time (µs): 1,310
CPU 10 ISR total execution time (s): 0,000005
CPU 10 ISR count: 5
CPU 10 DPC highest execution time (µs): 83,670
CPU 10 DPC total execution time (s): 0,021106
CPU 10 DPC count: 3661
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,986176
CPU 11 ISR highest execution time (µs): 1,150
CPU 11 ISR total execution time (s): 0,000005
CPU 11 ISR count: 5
CPU 11 DPC highest execution time (µs): 93,410
CPU 11 DPC total execution time (s): 0,012523
CPU 11 DPC count: 1484
_________________________________________________________________________________________________________
https://ibb.co/7JytQxx
Blue_screen_of_death
13-10-2019, 14:01
La latenza dello storage driver continua a essere altissima.
Invece il report precedente ha evidenziato latenza alta su dxgkrnl.sys, che è il driver di DirectX.
Sembra strano che due driver diano lo stesso problema.
Comincio a sospettare che c'è qualcosa che non va in tutto il sistema o nella sua configurazione.
Controlla nel BIOS se l'High Precision Event Timer è abilitato, e fammi sapere.
Ma da quanto hai questo problema? Sempre avuto dal momento dell'assemblaggio o è comparso di recente? Ricordi se hai apportato modifiche al sistema? (aggiunto hardware, ...)
La latenza dello storage driver continua a essere altissima.
Invece il report precedente ha evidenziato latenza alta su dxgkrnl.sys, che è il driver di DirectX.
Sembra strano che due driver diano lo stesso problema.
Comincio a sospettare che c'è qualcosa che non va in tutto il sistema o nella sua configurazione.
Controlla nel BIOS se l'High Precision Event Timer è abilitato.
Ma da quanto hai questo problema? Sempre avuto dal momento dell'assemblaggio o è comparso di recente? Ricordi se hai apportato modifiche al sistema? (aggiunto hardware, ...)
mm no di recente lo sta facendo questo freeze le schermate blu che per ora non ho più avuto ci sono state quasi subito.
non lo trovo nel bios gigabyte.. trovato solo IBS ma non penso sia uguale
edit: trovato
Blue_screen_of_death
13-10-2019, 14:21
mm no di recente lo sta facendo questo freeze le schermate blu che per ora non ho più avuto ci sono state quasi subito.
non lo trovo nel bios gigabyte.. trovato solo IBS ma non penso sia uguale
edit: trovato
OK è abilitato o disabilitato?
OK è abilitato o disabilitato?
abilitato
Blue_screen_of_death
13-10-2019, 14:26
OK, è corretto, lascia abilitato.
Che versione del BIOS hai? Ho visto che hanno rilasciato un aggiornamento che migliora la compatibilità degli SSD.
OK, è corretto, lascia abilitato.
Che versione del BIOS hai? Ho visto che hanno rilasciato un aggiornamento che migliora la compatibilità degli SSD.
installata la f42a qualche giorno fa
Blue_screen_of_death
13-10-2019, 14:44
ok, BIOS aggiornato all'ultima versione.
Prova a impostare la scheda video NVIDIA su Prestazioni elevate e non su qualità. Dovresti trovare l'impostazione nel pannello di controllo NVIDIA.
ok, BIOS aggiornato all'ultima versione.
Prova a impostare la scheda video NVIDIA su Prestazioni elevate e non su qualità. Dovresti trovare l'impostazione nel pannello di controllo NVIDIA.
ho una amd rx580 la trovo comunque questa opzione?
Blue_screen_of_death
13-10-2019, 14:54
ho una amd rx580 la trovo comunque questa opzione?
si, dovresti trovarla nelle impostazioni della scheda AMD
si, dovresti trovarla nelle impostazioni della scheda AMD
ho controllato un pò ovunque ma non la trovo come come la nvidia, li al massimo ti fa mettere un'applicazione modificare i parametri tipo per un gioco
Blue_screen_of_death
13-10-2019, 15:26
Ultima cosa che ti chiederei di provare è impostare i settings della RAM nel BIOS. Latenze e voltaggi.
Anziché lasciare le impostazioni su AUTO, prova a impostarle manualmente.
I valori da inserire dipendono dal modello della RAM, e sono scritte nelle specifiche.
Questo perché il tuo problema è causato da DPC di driver diversi eccessivamente lente.
Le DPC possono fare uso inteso della memoria RAM. Quindi se la RAM funziona male, la loro latenza può aumentare.
Il fatto che sono coinvolti diversi driver mi fa pensare alla configurazione errata della RAM.
Ultima cosa che ti chiederei di provare è impostare i settings della RAM nel BIOS. Latenze e voltaggi.
Anziché lasciare le impostazioni su AUTO, prova a impostarle manualmente.
I valori da inserire dipendono dal modello della RAM, e sono scritte nelle specifiche.
Questo perché il tuo problema è causato da DPC di driver diversi eccessivamente lente.
Le DPC possono fare uso inteso della memoria RAM. Quindi se la RAM funziona male, la loro latenza può aumentare.
Il fatto che sono coinvolti diversi driver mi fa pensare alla configurazione errata della RAM.
provo subito!
le mie ram sono queste ti mando una foto va bene perchè ho 3 ram diverse e penso anche di frequenza perchè due le presi 8x2 da 2133 mhx mi pare le altre in un altro negozio e non vorrei che influisse.
https://ibb.co/4j40803
Blue_screen_of_death
13-10-2019, 15:47
Si, RAM di velocità e caratteristiche diverse possono lavorare male insieme.
Per toglierti ogni dubbio, installa solo uno di quei 3 moduli, configura le latenze e il voltaggio manualmente nel BIOS
Riprova i soliti test.
Se i driver continuano ad avere latenza elevata scartiamo anche l'ipotesi RAM :D
Si, RAM di velocità e caratteristiche diverse possono lavorare male insieme.
Per toglierti ogni dubbio, installa solo uno di quei 3 moduli, configura le latenze e il voltaggio manualmente nel BIOS
Riprova i soliti test.
Se i driver continuano ad avere latenza elevata scartiamo anche l'ipotesi RAM :D
fatto https://ibb.co/CHwHPKf
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:05:44 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 8140 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 197,20
Average measured interrupt to process latency (µs): 5,980295
Highest measured interrupt to DPC latency (µs): 193,60
Average measured interrupt to DPC latency (µs): 2,162796
_________________________________________________________________________________________________________
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): 136,30
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000635
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,000770
ISR count (execution time <250 µs): 6408
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): 562650,860
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 2,122875
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,795094
DPC count (execution time <250 µs): 26763040
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 9
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: radeonsettings.exe
Total number of hard pagefaults 2593
Hard pagefault count of hardest hit process: 842
Number of processes hit: 23
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 44,913010
CPU 0 ISR highest execution time (µs): 18,420
CPU 0 ISR total execution time (s): 0,014354
CPU 0 ISR count: 3265
CPU 0 DPC highest execution time (µs): 266,260
CPU 0 DPC total execution time (s): 31,098189
CPU 0 DPC count: 6326050
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 34,912861
CPU 1 ISR highest execution time (µs): 136,30
CPU 1 ISR total execution time (s): 0,016875
CPU 1 ISR count: 2808
CPU 1 DPC highest execution time (µs): 409459,404688
CPU 1 DPC total execution time (s): 20,073310
CPU 1 DPC count: 7765825
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 19,485746
CPU 2 ISR highest execution time (µs): 8,170
CPU 2 ISR total execution time (s): 0,000288
CPU 2 ISR count: 81
CPU 2 DPC highest execution time (µs): 265780,450
CPU 2 DPC total execution time (s): 10,141227
CPU 2 DPC count: 2204996
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 26,464962
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): 276088,289687
CPU 3 DPC total execution time (s): 10,106640
CPU 3 DPC count: 2179496
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 17,081489
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): 384146,580
CPU 4 DPC total execution time (s): 10,297623
CPU 4 DPC count: 2203871
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 17,750272
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): 397347,319688
CPU 5 DPC total execution time (s): 10,645596
CPU 5 DPC count: 2201668
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 18,257986
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): 562650,860
CPU 6 DPC total execution time (s): 11,626503
CPU 6 DPC count: 1918826
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 17,851247
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): 345350,499688
CPU 7 DPC total execution time (s): 11,304829
CPU 7 DPC count: 1944164
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,240710
CPU 8 ISR highest execution time (µs): 2,220
CPU 8 ISR total execution time (s): 0,000188
CPU 8 ISR count: 195
CPU 8 DPC highest execution time (µs): 191,310
CPU 8 DPC total execution time (s): 0,039283
CPU 8 DPC count: 11060
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,820596
CPU 9 ISR highest execution time (µs): 1,390
CPU 9 ISR total execution time (s): 0,000005
CPU 9 ISR count: 5
CPU 9 DPC highest execution time (µs): 72,780
CPU 9 DPC total execution time (s): 0,003843
CPU 9 DPC count: 1044
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 3,298029
CPU 10 ISR highest execution time (µs): 1,730
CPU 10 ISR total execution time (s): 0,000017
CPU 10 ISR count: 15
CPU 10 DPC highest execution time (µs): 91,850
CPU 10 DPC total execution time (s): 0,026219
CPU 10 DPC count: 4136
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,190658
CPU 11 ISR highest execution time (µs): 4,60
CPU 11 ISR total execution time (s): 0,000040
CPU 11 ISR count: 39
CPU 11 DPC highest execution time (µs): 179,670
CPU 11 DPC total execution time (s): 0,018207
CPU 11 DPC count: 1921
_________________________________________________________________________________________________________
Blue_screen_of_death
13-10-2019, 17:06
Latenze ancora alte, la RAM non c'entra.
Vedi se ti trova driver aggiornati per i controller NVMe e SATA (quei 4 controller in gestione dispositivi).
Aggiorna stesso da Gestione dispositivi. click destro sulla periferica -> Aggiorna.
Purtroppo se non ricordo male sul sito della tua scheda madre non sono presenti driver per questi controller, cosa che potrebbe risolvere il problema.
Latenze ancora alte, la RAM non c'entra.
Vedi se ti trova driver aggiornati per i controller NVMe e SATA (quei 4 controller in gestione dispositivi).
Aggiorna stesso da Gestione dispositivi. click destro sulla periferica -> Aggiorna.
Purtroppo se non ricordo male sul sito della tua scheda madre non sono presenti driver per questi controller, cosa che potrebbe risolvere il problema.
mi dice che sono già aggiornati...
Blue_screen_of_death
13-10-2019, 17:46
Le impostazioni di risparmio energia come sono impostate? Prestazioni elevate?
Le impostazioni di risparmio energia come sono impostate? Prestazioni elevate?
su bilanciato
Blue_screen_of_death
13-10-2019, 18:07
su bilanciato
Metti su Prestazioni elevate, disabilita lo spegnimento dei dischi rigidi nelle opzioni risparmio energia.
Controlla che il livello massimo del processore è 100%
Poi rifai i test.
Metti su Prestazioni elevate, disabilita lo spegnimento dei dischi rigidi nelle opzioni risparmio energia.
Controlla che il livello massimo del processore è 100%
Poi rifai i test.
fatto tutto ti mando tutto:
https://ibb.co/dJyLQrS
_________________________________________________________________________________________________________
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:06:41 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 235,70
Average measured interrupt to process latency (µs): 5,972693
Highest measured interrupt to DPC latency (µs): 231,40
Average measured interrupt to DPC latency (µs): 2,383822
_________________________________________________________________________________________________________
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): 232,540
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,003819
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,006144
ISR count (execution time <250 µs): 90434
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): 544891,020
Driver with highest DPC routine execution time: tcpip.sys - Driver TCP/IP, Microsoft Corporation
Highest reported total DPC routine time (%): 2,126716
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,757447
DPC count (execution time <250 µs): 27755854
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 64
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: chrome.exe
Total number of hard pagefaults 9863
Hard pagefault count of hardest hit process: 2370
Number of processes hit: 65
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 51,135069
CPU 0 ISR highest execution time (µs): 232,540
CPU 0 ISR total execution time (s): 0,164352
CPU 0 ISR count: 55574
CPU 0 DPC highest execution time (µs): 54159,329063
CPU 0 DPC total execution time (s): 36,153787
CPU 0 DPC count: 6813196
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 48,660199
CPU 1 ISR highest execution time (µs): 153,330
CPU 1 ISR total execution time (s): 0,116706
CPU 1 ISR count: 30349
CPU 1 DPC highest execution time (µs): 544891,020
CPU 1 DPC total execution time (s): 22,177538
CPU 1 DPC count: 7799597
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 22,987181
CPU 2 ISR highest execution time (µs): 33,390
CPU 2 ISR total execution time (s): 0,011254
CPU 2 ISR count: 2929
CPU 2 DPC highest execution time (µs): 536544,6350
CPU 2 DPC total execution time (s): 12,419460
CPU 2 DPC count: 2302078
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 23,995020
CPU 3 ISR highest execution time (µs): 11,030
CPU 3 ISR total execution time (s): 0,002643
CPU 3 ISR count: 971
CPU 3 DPC highest execution time (µs): 350029,109687
CPU 3 DPC total execution time (s): 12,409019
CPU 3 DPC count: 2291176
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 21,053739
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): 210,240
CPU 4 DPC total execution time (s): 11,611456
CPU 4 DPC count: 2270857
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 21,343822
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): 99866,0450
CPU 5 DPC total execution time (s): 11,783464
CPU 5 DPC count: 2298113
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 22,389859
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): 97,250
CPU 6 DPC total execution time (s): 12,678696
CPU 6 DPC count: 1952255
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 21,831714
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): 364613,290
CPU 7 DPC total execution time (s): 13,276720
CPU 7 DPC count: 1997751
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 4,057324
CPU 8 ISR highest execution time (µs): 6,170
CPU 8 ISR total execution time (s): 0,000463
CPU 8 ISR count: 418
CPU 8 DPC highest execution time (µs): 136,610
CPU 8 DPC total execution time (s): 0,064070
CPU 8 DPC count: 14844
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,542045
CPU 9 ISR highest execution time (µs): 1,820
CPU 9 ISR total execution time (s): 0,000023
CPU 9 ISR count: 19
CPU 9 DPC highest execution time (µs): 233,160
CPU 9 DPC total execution time (s): 0,019496
CPU 9 DPC count: 3682
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 4,064960
CPU 10 ISR highest execution time (µs): 2,060
CPU 10 ISR total execution time (s): 0,000084
CPU 10 ISR count: 69
CPU 10 DPC highest execution time (µs): 159,820
CPU 10 DPC total execution time (s): 0,052126
CPU 10 DPC count: 7450
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,968342
CPU 11 ISR highest execution time (µs): 4,20
CPU 11 ISR total execution time (s): 0,000139
CPU 11 ISR count: 105
CPU 11 DPC highest execution time (µs): 184,50
CPU 11 DPC total execution time (s): 0,047798
CPU 11 DPC count: 4931
_________________________________________________________________________________________________________
Blue_screen_of_death
13-10-2019, 18:44
Sempre alta, il risparmio energia non c'entra niente.
Però stavo pensando che forse non ti ho chiesto di provare ad aggiornare i driver del chipset prendendoli direttamente dal sito di AMD, dato che sul sito della scheda madre c'è poco.
E' una delle prime cose che avrei dovuto consigliarti, ma mi è sfuggito. :D
Comunque,
questa dovrebbe essere la pagina del tuo chipset, AM4: https://www.amd.com/en/support/chipsets/amd-socket-am4/x370
Aggiorna chipset, NVMe e SATA.
Riavvia il sistema.
Rifai i test e :sperem:
Sempre alta, il risparmio energia non c'entra niente.
Però stavo pensando che forse non ti ho chiesto di provare ad aggiornare i driver del chipset prendendoli direttamente dal sito di AMD, dato che sul sito della scheda madre c'è poco.
E' una delle prime cose che avrei dovuto consigliarti, ma mi è sfuggito. :D
Comunque,
questa dovrebbe essere la pagina del tuo chipset, AM4: https://www.amd.com/en/support/chipsets/amd-socket-am4/x370
Aggiorna chipset, NVMe e SATA.
Riavvia il sistema.
Rifai i test e :sperem:
questo è il report aprendo crystal info con driver https://ibb.co/8NzLtZD poi quando ho aperto l'altro crystal e latency e attivato latency ha fatto di nuovo il freeze ora poi faccio il test
_________________________________________________________________________________________________________
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:00:49 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 153,20
Average measured interrupt to process latency (µs): 5,711712
Highest measured interrupt to DPC latency (µs): 149,40
Average measured interrupt to DPC latency (µs): 1,919276
_________________________________________________________________________________________________________
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): 17,850
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,005187
Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation
Total time spent in ISRs (%) 0,008325
ISR count (execution time <250 µs): 18654
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): 100852,870
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0,072234
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,172699
DPC count (execution time <250 µs): 189458
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: steamwebhelper.exe
Total number of hard pagefaults 17525
Hard pagefault count of hardest hit process: 2968
Number of processes hit: 58
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 1,707792
CPU 0 ISR highest execution time (µs): 17,850
CPU 0 ISR total execution time (s): 0,046015
CPU 0 ISR count: 17428
CPU 0 DPC highest execution time (µs): 241,180
CPU 0 DPC total execution time (s): 0,689952
CPU 0 DPC count: 147968
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,457147
CPU 1 ISR highest execution time (µs): 10,680
CPU 1 ISR total execution time (s): 0,002519
CPU 1 ISR count: 821
CPU 1 DPC highest execution time (µs): 102,530
CPU 1 DPC total execution time (s): 0,018862
CPU 1 DPC count: 3476
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,555383
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 263,210
CPU 2 DPC total execution time (s): 0,056755
CPU 2 DPC count: 10747
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,445336
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): 55,540
CPU 3 DPC total execution time (s): 0,011980
CPU 3 DPC count: 3068
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 0,481408
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): 165,70
CPU 4 DPC total execution time (s): 0,025172
CPU 4 DPC count: 5100
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 0,385116
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): 42,20
CPU 5 DPC total execution time (s): 0,004671
CPU 5 DPC count: 1011
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,640048
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): 100852,870
CPU 6 DPC total execution time (s): 0,136812
CPU 6 DPC count: 6162
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 0,649491
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): 100,320
CPU 7 DPC total execution time (s): 0,004919
CPU 7 DPC count: 1149
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,573814
CPU 8 ISR highest execution time (µs): 6,280
CPU 8 ISR total execution time (s): 0,000310
CPU 8 ISR count: 298
CPU 8 DPC highest execution time (µs): 69,280
CPU 8 DPC total execution time (s): 0,025406
CPU 8 DPC count: 5747
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,589293
CPU 9 ISR highest execution time (µs): 2,450
CPU 9 ISR total execution time (s): 0,000019
CPU 9 ISR count: 15
CPU 9 DPC highest execution time (µs): 112,410
CPU 9 DPC total execution time (s): 0,006472
CPU 9 DPC count: 863
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0,499526
CPU 10 ISR highest execution time (µs): 1,90
CPU 10 ISR total execution time (s): 0,000041
CPU 10 ISR count: 36
CPU 10 DPC highest execution time (µs): 113,130
CPU 10 DPC total execution time (s): 0,016901
CPU 10 DPC count: 2164
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0,495890
CPU 11 ISR highest execution time (µs): 3,10
CPU 11 ISR total execution time (s): 0,000066
CPU 11 ISR count: 56
CPU 11 DPC highest execution time (µs): 103,70
CPU 11 DPC total execution time (s): 0,01790
CPU 11 DPC count: 2005
_________________________________________________________________________________________________________
questo invece è il test
https://ibb.co/mzCdhbp
_________________________________________________________________________________________________________
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:04:52 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 147,0
Average measured interrupt to process latency (µs): 6,259449
Highest measured interrupt to DPC latency (µs): 138,80
Average measured interrupt to DPC latency (µs): 2,560880
_________________________________________________________________________________________________________
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): 142,460
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 1,381843
Driver with highest ISR total time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,005924
ISR count (execution time <250 µs): 63306
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): 859660,9850
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 2,075474
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,931610
DPC count (execution time <250 µs): 22812076
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 30
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: fontdrvhost.exe
Total number of hard pagefaults 2218
Hard pagefault count of hardest hit process: 722
Number of processes hit: 14
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 47,183528
CPU 0 ISR highest execution time (µs): 104,10
CPU 0 ISR total execution time (s): 0,110566
CPU 0 ISR count: 39573
CPU 0 DPC highest execution time (µs): 549009,534062
CPU 0 DPC total execution time (s): 31,723623
CPU 0 DPC count: 5962523
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 44,598692
CPU 1 ISR highest execution time (µs): 142,460
CPU 1 ISR total execution time (s): 0,090307
CPU 1 ISR count: 21706
CPU 1 DPC highest execution time (µs): 740173,3950
CPU 1 DPC total execution time (s): 18,168859
CPU 1 DPC count: 7297610
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 20,116359
CPU 2 ISR highest execution time (µs): 10,120
CPU 2 ISR total execution time (s): 0,006073
CPU 2 ISR count: 1791
CPU 2 DPC highest execution time (µs): 606114,9850
CPU 2 DPC total execution time (s): 8,131883
CPU 2 DPC count: 1702011
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 20,305385
CPU 3 ISR highest execution time (µs): 8,470
CPU 3 ISR total execution time (s): 0,000570
CPU 3 ISR count: 164
CPU 3 DPC highest execution time (µs): 236,880
CPU 3 DPC total execution time (s): 7,326655
CPU 3 DPC count: 1674752
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 18,983222
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): 859660,9850
CPU 4 DPC total execution time (s): 11,101214
CPU 4 DPC count: 1664661
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 19,093494
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): 125977,790
CPU 5 DPC total execution time (s): 7,521560
CPU 5 DPC count: 1641183
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 20,398246
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): 823616,220
CPU 6 DPC total execution time (s): 10,303547
CPU 6 DPC count: 1418460
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 19,929382
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): 461990,919687
CPU 7 DPC total execution time (s): 8,382490
CPU 7 DPC count: 1437477
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,808504
CPU 8 ISR highest execution time (µs): 1,750
CPU 8 ISR total execution time (s): 0,000051
CPU 8 ISR count: 57
CPU 8 DPC highest execution time (µs): 192,720
CPU 8 DPC total execution time (s): 0,030607
CPU 8 DPC count: 7737
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,499409
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 90,540
CPU 9 DPC total execution time (s): 0,004396
CPU 9 DPC count: 909
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,966941
CPU 10 ISR highest execution time (µs): 0,980
CPU 10 ISR total execution time (s): 0,000003
CPU 10 ISR count: 4
CPU 10 DPC highest execution time (µs): 93,650
CPU 10 DPC total execution time (s): 0,022146
CPU 10 DPC count: 3379
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,939921
CPU 11 ISR highest execution time (µs): 1,350
CPU 11 ISR total execution time (s): 0,000011
CPU 11 ISR count: 11
CPU 11 DPC highest execution time (µs): 230,650
CPU 11 DPC total execution time (s): 0,012251
CPU 11 DPC count: 1422
_________________________________________________________________________________________________________
Blue_screen_of_death
13-10-2019, 20:23
Sempre latenza altissima.
Pensa a cosa hai cambiato di recente, che potrebbe aver causato il problema. Hai aggiornato a una nuova build di Windows? Installato nuovo hardware?
Sempre latenza altissima.
Pensa a cosa hai cambiato di recente, che potrebbe aver causato il problema. Hai aggiornato a una nuova build di Windows? Installato nuovo hardware?
si ho aggiornato la build ma già lo faceva con la precedente già aggiornata.. nuovo hardware no..
Blue_screen_of_death
13-10-2019, 20:49
Disinstalla qualunque software di sicurezza (antivirus, antimalware, MalwareBytes, ...)
Configura il PC per un avvio pulito, disabilitando i servizi di terze parti e le applicazioni all'avvio.
Ovvero, in Gestione attività, scheda Avvio disabilita tutto
Apri msconfig, scheda Servizi disattiva tutti i servizi non Microsoft.
Se sei in overclock, disabilitalo e ripristina frequenze e voltaggi di default.
Aggiorna tutti i driver del sistema. Ti posto i link.
Scheda audio
https://download.gigabyte.com/FileList/Driver/mb_driver_572_setup.exe_6.0.8688.1.zip
Scheda di rete
https://support.killernetworking.com/download/killer-drivers-installation-64bit/
Chipset
https://www.amd.com/en/support/chipsets/amd-socket-am4/x370
Periferiche Intel (non so se ne hai, ma ti linko il tool che le rileva e aggiorna automaticamente)
https://www.intel.it/content/www/it/it/support/detect.html
Scheda video AMD
https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-580
Riavvia e ripeti i test.
Con questo abbiamo fatto tutti i test possibili :D, se continua a dare problemi, le opzioni sono due:
- l'installazione di Windows è compromessa
- c'è un componente danneggiato
Quindi direi di provare a reinstallare Windows in-place, senza formattare.
E se il problema persiste provare con un'installazione pulita. E' una perdita di tempo, ma così almeno sei sicuro che non è colpa di Windows o dei driver.
:sperem:
Disinstalla qualunque software di sicurezza (antivirus, antimalware, MalwareBytes, ...)
Configura il PC per un avvio pulito, disabilitando i servizi di terze parti e le applicazioni all'avvio.
Ovvero, in Gestione attività, scheda Avvio disabilita tutto
Apri msconfig, scheda Servizi disattiva tutti i servizi non Microsoft.
Se sei in overclock, disabilitalo e ripristina frequenze e voltaggi di default.
Aggiorna tutti i driver del sistema. Ti posto i link.
Scheda audio
https://download.gigabyte.com/FileList/Driver/mb_driver_572_setup.exe_6.0.8688.1.zip
Scheda di rete
https://support.killernetworking.com/download/killer-drivers-installation-64bit/
Chipset
https://www.amd.com/en/support/chipsets/amd-socket-am4/x370
Periferiche Intel (non so se ne hai, ma ti linko il tool che le rileva e aggiorna automaticamente)
https://www.intel.it/content/www/it/it/support/detect.html
Scheda video AMD
https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-580
Riavvia e ripeti i test.
Con questo abbiamo fatto tutti i test possibili :D, se continua a dare problemi, le opzioni sono due:
- l'installazione di Windows è compromessa
- c'è un componente danneggiato
Quindi direi di provare a reinstallare Windows in-place, senza formattare.
E se il problema persiste provare con un'installazione pulita. E' una perdita di tempo, ma così almeno sei sicuro che non è colpa di Windows o dei driver.
:sperem:
allora aggiornato tutto e ho fatto il test ma è sempre alta la latenza quindi niente provaimo con windows ma come devo procedere?
Blue_screen_of_death
13-10-2019, 22:27
Hai provato anche con la configurazione di avvio pulito, disabilitando servizi non Microsoft e applicazioni?
Per la reinstallazione, puoi seguire questa procedura: https://answers.microsoft.com/it-it/windows/forum/all/reinstallazione-in-place-di-windows-10/51a24191-3531-405e-b737-de96f9b70dd7
Hai provato anche con la configurazione di avvio pulito, disabilitando servizi non Microsoft e applicazioni?
Per la reinstallazione, puoi seguire questa procedura: https://answers.microsoft.com/it-it/windows/forum/all/reinstallazione-in-place-di-windows-10/51a24191-3531-405e-b737-de96f9b70dd7
si ho provato disabilitando tutto ma niente
Blue_screen_of_death
13-10-2019, 22:40
Se sei in overclock, disabilitalo e ripristina le frequenze di default.
Se hai antivirus o antimalware, disinstallali.
Poi segui questa procedura.
Gestione attività -> Scheda Avvio -> Seleziona i programmi uno per uno e clicca su Disabilita.
Poi Start -> digita "msconfig".
Nel pannello di configurazione che si apre vai alla scheda Servizi
Spunta "Nascondi tutti i servizi Microsoft
Clicca su Disabilita tutto.
Riavvia e rifai i test di latenza.
Blue_screen_of_death
13-10-2019, 22:41
si ho provato disabilitando tutto ma niente
OK, allora fai la reinstallazione di Windows, mantenendo file e impostazioni
https://answers.microsoft.com/it-it/windows/forum/all/reinstallazione-in-place-di-windows-10/51a24191-3531-405e-b737-de96f9b70dd7
OK, allora fai la reinstallazione di Windows, mantenendo file e impostazioni
https://answers.microsoft.com/it-it/windows/forum/all/reinstallazione-in-place-di-windows-10/51a24191-3531-405e-b737-de96f9b70dd7
niente sempre latenza alta
i software attivi sono msi afterburner quello dell'amd per la scheda video
Blue_screen_of_death
14-10-2019, 11:13
L'ipotesi guasto hardware sta diventando la più probabile. :(
I componenti sono ancora in garanzia?
Secondo me nell'ordine devi provare queste cose:
- Provare singolarmente ciascun modulo di RAM e vedere come si comportano.
- Fare un reset del BIOS, scollegare tutte le periferiche non essenziali per l'avvio del sistema e disabilitare tutto quello che puoi nel BIOS. In particolare scollega scheda video e usa la scheda integrata, scollega tutte le periferiche SATA, disattiva la scheda di rete e la scheda wireless nel BIOS, scollega tutte le periferiche USB. Lascia solo ciò che serve per far partire il PC e vedi se hai ancora latenze alte. Se il problema scompare allora una delle periferiche che hai disconnesso o spento è difettosa.
- Installazione pulita di Windows sempre sull'SSD, la procedura è descritta sempre nella pagina che ti ho linkato. Devi scegliere solo di NON mantenere file e impostazioni.
- Scollegare l'SSD e fare un'installazione pulita di Windows su un hard disk SATA. Se il problema scompare allora probabilmente è l'SSD danneggiato o il controller NVMe.
Blue_screen_of_death
14-10-2019, 11:15
niente sempre latenza alta
i software attivi sono msi afterburner quello dell'amd per la scheda video
Prova a spegnere le ottimizzazioni di MSI afterburner, se attive. Ma se hai eseguito bene la procedura di avvio pulito dovresti aver già disabilitato tutto.
L'ipotesi guasto hardware sta diventando la più probabile. :(
I componenti sono ancora in garanzia?
Secondo me nell'ordine devi provare queste cose:
- Fare un reset del BIOS, scollegare tutte le periferiche non essenziali per l'avvio del sistema e disabilitare tutto quello che puoi nel BIOS. In particolare scollega scheda video e usa la scheda integrata, scollega tutte le periferiche SATA, disattiva la scheda di rete e la scheda wireless nel BIOS, scollega tutte le periferiche USB. Lascia solo ciò che serve per far partire il PC e vedi se hai ancora latenze alte. Se il problema scompare allora una delle periferiche che hai disconnesso o spento è difettosa.
- Installazione pulita di Windows sempre sull'SSD, la procedura è descritta sempre nella pagina che ti ho linkato. Devi scegliere solo di NON mantenere file e impostazioni.
- Scollegare l'SSD e fare un'installazione pulita di Windows su un hard disk SATA. Se il problema scompare allora probabilmente è l'SSD danneggiato o il controller NVMe.
si tutto sia processore che scheda madre, l'ssd mi pare strano perchè avevo un ssd prima sata e ora poi ho voluto prendere quello nvme però ho clonato il tutto per non perdere niente... ora provo a fare un'istallazione pulita su un hard disk sata, devo installarci soliti programmi e ovviamente prima di tutto aggiornare driver ecc?
msi afterburner lo tenevo perchè non mi partono le ventole della scheda video sennò:confused:
ti rimando il report e screen dei driver pechè ora disabilitando msi e riaprendo latency e crystal per fare test mi è venuto fuori un ntoskrnl.exe come latenza.
https://ibb.co/wMVrCbX
_________________________________________________________________________________________________________
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:06:05 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-5GGJV4O
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 24524 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 207,10
Average measured interrupt to process latency (µs): 5,802246
Highest measured interrupt to DPC latency (µs): 200,80
Average measured interrupt to DPC latency (µs): 2,250971
_________________________________________________________________________________________________________
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): 229,640
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,003826
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,004778
ISR count (execution time <250 µs): 56334
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): 828786,770
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 1,349989
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 1,824621
DPC count (execution time <250 µs): 19796628
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 58
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: svchost.exe
Total number of hard pagefaults 204
Hard pagefault count of hardest hit process: 33
Number of processes hit: 19
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 44,215772
CPU 0 ISR highest execution time (µs): 229,640
CPU 0 ISR total execution time (s): 0,120923
CPU 0 ISR count: 36033
CPU 0 DPC highest execution time (µs): 324,910
CPU 0 DPC total execution time (s): 29,079010
CPU 0 DPC count: 5749620
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 39,937024
CPU 1 ISR highest execution time (µs): 211,0
CPU 1 ISR total execution time (s): 0,077090
CPU 1 ISR count: 17735
CPU 1 DPC highest execution time (µs): 326,290
CPU 1 DPC total execution time (s): 14,390549
CPU 1 DPC count: 6534127
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 16,762696
CPU 2 ISR highest execution time (µs): 16,30
CPU 2 ISR total execution time (s): 0,009202
CPU 2 ISR count: 1842
CPU 2 DPC highest execution time (µs): 489220,2050
CPU 2 DPC total execution time (s): 6,028551
CPU 2 DPC count: 1274101
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 16,988709
CPU 3 ISR highest execution time (µs): 11,160
CPU 3 ISR total execution time (s): 0,001621
CPU 3 ISR count: 317
CPU 3 DPC highest execution time (µs): 234363,319688
CPU 3 DPC total execution time (s): 5,637017
CPU 3 DPC count: 1272070
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 15,816348
CPU 4 ISR highest execution time (µs): 8,070
CPU 4 ISR total execution time (s): 0,000062
CPU 4 ISR count: 17
CPU 4 DPC highest execution time (µs): 260,080
CPU 4 DPC total execution time (s): 5,400503
CPU 4 DPC count: 1258820
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 17,682297
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): 394,540
CPU 5 DPC total execution time (s): 5,544021
CPU 5 DPC count: 1275891
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 16,876431
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): 828786,770
CPU 6 DPC total execution time (s): 7,380924
CPU 6 DPC count: 1203017
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 16,389256
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): 95,360
CPU 7 DPC total execution time (s): 6,403857
CPU 7 DPC count: 1219265
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,437345
CPU 8 ISR highest execution time (µs): 2,620
CPU 8 ISR total execution time (s): 0,000281
CPU 8 ISR count: 289
CPU 8 DPC highest execution time (µs): 97,380
CPU 8 DPC total execution time (s): 0,017598
CPU 8 DPC count: 4435
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,167853
CPU 9 ISR highest execution time (µs): 1,940
CPU 9 ISR total execution time (s): 0,000006
CPU 9 ISR count: 5
CPU 9 DPC highest execution time (µs): 139,510
CPU 9 DPC total execution time (s): 0,003554
CPU 9 DPC count: 879
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 3,602472
CPU 10 ISR highest execution time (µs): 2,70
CPU 10 ISR total execution time (s): 0,000026
CPU 10 ISR count: 22
CPU 10 DPC highest execution time (µs): 121,070
CPU 10 DPC total execution time (s): 0,018950
CPU 10 DPC count: 2686
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 3,575220
CPU 11 ISR highest execution time (µs): 4,770
CPU 11 ISR total execution time (s): 0,000086
CPU 11 ISR count: 74
CPU 11 DPC highest execution time (µs): 97,40
CPU 11 DPC total execution time (s): 0,017151
CPU 11 DPC count: 1779
_________________________________________________________________________________________________________
Blue_screen_of_death
14-10-2019, 11:25
si tutto sia processore che scheda madre, l'ssd mi pare strano perchè avevo un ssd prima sata e ora poi ho voluto prendere quello nvme però ho clonato il tutto per non perdere niente... ora provo a fare un'istallazione pulita su un hard disk sata, devo installarci soliti programmi e ovviamente prima di tutto aggiornare driver ecc?
msi afterburner lo tenevo perchè non mi partono le ventole della scheda video sennò:confused:
Prova a spegnere le ottimizzazioni di MSI afterburner, se attive. Ma se hai eseguito bene la procedura di avvio pulito dovresti aver già disabilitato tutto.
Comunque come avevo già scritto in un post precedente, mi sembra strano che sia un software a causare problemi. In realtà escluderei anche l'SSD.
Questo perché oltre al driver di storage a volte anche il driver di rete ha evidenziato problemi di latenza.
Quindi penso sia un problema generale di tutti i driver. Ma dato che noi stiamo stressando il driver di storage, la maggior parte dei log mostra il problema sul driver di storage.
Io propenderei per RAM difettose, scheda madre difettosa o processore difettoso.
Per darti un'idea, sul mio notebook dual-core con 16 GB di RAM, quindi molto meno performante del tuo, ho lasciato girare il monitor per 5 ore e la latenza più alta misurata era di 4 millisecondi.
A te in alcuni casi arriva quasi al secondo.
Fai l'installazione pulita sul SATA e ripeti i i test prima appena finisce di installare il sistema operativo, prima ancora di installare aggiornamenti, driver e applicazioni. Così i test sono più affidabili.
Blue_screen_of_death
14-10-2019, 11:26
edit, ho corretto il post precedente.
Fai direttamente l'installazione pulita sul disco SATA. Così risparmiamo tempo ;)
Blue_screen_of_death
14-10-2019, 11:33
Altra prova che puoi fare è mettere una build di Windows che in passato non ti dava problemi.
Altra prova che puoi fare è mettere una build di Windows che in passato non ti dava problemi.
ok intanto provo con la build nuova che sto scaricando e installo su un altro hard disk e vediamo, però mi roderebbe perdere tutti i programmi che ho.. c'è un modo per non perdere niente?
Blue_screen_of_death
14-10-2019, 11:39
Non puoi spostare i dati dall'hard disk SATA a un altro hard disk? Non hai spazio?
Non puoi spostare i dati dall'hard disk SATA a un altro hard disk? Non hai spazio?
io ho 3 hard disk due da 500 e uno da un tera che li considero esterni e ci salvo tutta la roba e installo i vari giochi, però sul principale ho vari programmi che mi dispiacerebbe perdere.. non mi ricordo dove li trovai ahaha
Non puoi spostare i dati dall'hard disk SATA a un altro hard disk? Non hai spazio?
allora installato windows 10 ultima build su hard disk sata, primo avvio:
installato latency e crystaldisk info e mark.
fatto test su hard disk su cui ho installato il sistema e latenza nella norma sempre verde essendo un hard disk vecchiotto va anche lento.
per scrupolo ho fatto il test con l'hard disk nvme e la latenza è ritornata sballata.
Blue_screen_of_death
14-10-2019, 13:12
per scrupolo ho fatto il test con l'hard disk nvme e la latenza è ritornata sballata.
Non ho capito...
test dell'SSD sulla vecchia installazione?
oppure test dell'SSD sulla nuova installazione?
Non ho capito...
test dell'SSD sulla vecchia installazione?
oppure test dell'SSD sulla nuova installazione?
tutto su nuovo
Blue_screen_of_death
14-10-2019, 13:16
ah ok
Quindi il problema è l'SSD o il controller NVMe. Per capirlo dovresti provare un'altra periferica NVMe nel PC.
Hai un'altra periferica o comunque riesci a procurartene una?
Sul sito del produttore dell'SSD non mi sembra ci siano firmware aggiornati. Magari dai un'occhiata anche tu.
ah ok
Quindi il problema è l'SSD o il controller NVMe. Per capirlo dovresti provare un'altra periferica NVMe nel PC.
Hai un'altra periferica o comunque riesci a procurartene una?
Sul sito del produttore dell'SSD non mi sembra ci siano firmware aggiornati. Magari dai un'occhiata anche tu.
mmm no procurarmene nessuno ce l'ha dei miei amici..
però i freeze me li faceva anche quando avevo montato un ssd normale
Blue_screen_of_death
14-10-2019, 13:21
Prova anche a scollegare l'SSD e pulire bene i contatti, delicatamente, con una gomma da cancellare bianca di tipo morbido.
Blue_screen_of_death
14-10-2019, 13:31
mmm no procurarmene nessuno ce l'ha dei miei amici..
però i freeze me li faceva anche quando avevo montato un ssd normale
L'SSD NVMe era collegato o scollegato?
Adesso che latenze hai? Sempre sopra i 500000 microsecondi?
L'SSD NVMe era collegato o scollegato?
Adesso che latenze hai? Sempre sopra i 500000 microsecondi?
Allora io l’ssd Non ce l’ho più collegato intendo quello vecchio che era 128 gb e li comunque dava lo stesso i freeze. Lo avevo sempre poi quando hai iniziato ad aiutarmi e sembrava tutto apposto ho clonato quello e ci ho messo nvme per non perdere niente. Poi i freeze sono riniziati, ed ora io di sistema ho quei nvme e gli atri sono sata normali. Quello che dava problemi l’ho levato.
Quell’ssd vecchio l’ho messo su un altro pc dato a mia madre perché il suo hard disk non ne poteva più ahaha
E ora su un altro hard disk ho installato Windows nuovo pulito e sto provando i test senza installarci programmi, sui sata normale vedo che la latenza rimane normale sul verde essendo più lenti arrivano a malapena sui 80mb/s. Se provo con l’ssd la latenza aumenta a rosso si sempre sui quei valori.
Ho scritto di velocità perdonami, spero che tu riesca a capire.
Si è attaccato al nuovo sistema appena installato
Blue_screen_of_death
14-10-2019, 14:43
Allora probabilmente il problema c'era e c'è ancora, ma si manifesta solo in casi particolari, ad esempio quando usi intensamente il controller NVMe.
Potrebbe essere colpa di un modulo RAM oppure della scheda madre.
Lascia un solo modulo di RAM collegato e vedi come si comporta il PC.
Se non va, prova scollega quel banco e monta un altro banco e vedi che succede.
Prova con tutti i banchi di RAM che hai e in tutti gli slot della scheda madre.
Allora probabilmente il problema c'era e c'è ancora, ma si manifesta solo in casi particolari, ad esempio quando usi intensamente il controller NVMe.
Potrebbe essere colpa di un modulo RAM oppure della scheda madre.
Lascia un solo modulo di RAM collegato e vedi come si comporta il PC.
Se non va, prova scollega quel banco e monta un altro banco e vedi che succede.
Prova con tutti i banchi di RAM che hai e in tutti gli slot della scheda madre.
Ok stasera riprovo appena torno da lavoro nel caso sennò devo cambiare scheda madre e ram giusto?
Allora probabilmente il problema c'era e c'è ancora, ma si manifesta solo in casi particolari, ad esempio quando usi intensamente il controller NVMe.
Potrebbe essere colpa di un modulo RAM oppure della scheda madre.
Lascia un solo modulo di RAM collegato e vedi come si comporta il PC.
Se non va, prova scollega quel banco e monta un altro banco e vedi che succede.
Prova con tutti i banchi di RAM che hai e in tutti gli slot della scheda madre.
niente sempre latenza alta stessi valori..
Blue_screen_of_death
14-10-2019, 20:37
Quindi probabilmente è un problema di scheda madre. Ma è ancora in garanzia?
Quindi probabilmente è un problema di scheda madre. Ma è ancora in garanzia?
si è in garanzia
per fare cambio di hardware per non compromettere il sistema devo fare qualche passaggio?
Blue_screen_of_death
14-10-2019, 20:46
si è in garanzia
per fare cambio di hardware per non compromettere il sistema devo fare qualche passaggio?
Intendi per cambiare scheda madre senza dover reinstallare Windows?
Intendi per cambiare scheda madre senza dover reinstallare Windows?
si esatto
Blue_screen_of_death
14-10-2019, 21:00
si esatto
Se sostituisci la scheda madre con una identica nessun problema.
Se sostituisci la scheda madre con una simile dovrebbe andare senza problemi.
Se sostituisci la scheda madre con una molto diversa è molto probabile che la vecchia installazione di Windows non funzionerà.
L'unico problema che potresti avere è la licenza di Windows.
Se è OEM, ovvero legata all'hardware, potresti non riuscire a riattivarla.
Se è RETAIL nessun problema.
Se sostituisci la scheda madre con una identica nessun problema.
Se sostituisci la scheda madre con una simile dovrebbe andare senza problemi.
Se sostituisci la scheda madre con una molto diversa è molto probabile che la vecchia installazione di Windows non funzionerà.
L'unico problema che potresti avere è la licenza di Windows.
Se è OEM, ovvero legata all'hardware, potresti non riuscire a riattivarla.
Se è RETAIL nessun problema.
si a questo punto ne prendo un'altra, quindi mi tocca formattare tutto?
volevo prendere questa
https://www.amazon.it/gp/product/B07C64R1TW/ref=ox_sc_act_title_1?smid=A11IL2PNWYJU7H&psc=1
e a questo punto anche il processore se possibile cambiare con uno sempre amd ma ryzen 7 darebbe sempre problemi?
Blue_screen_of_death
14-10-2019, 21:11
si a questo punto ne prendo un'altra, quindi mi tocca formattare tutto?
Non si può dire con certezza se Windows partirà sulla nuova scheda madre e se funzionerà senza problemi.
Dipende dai componenti della nuova scheda madre. Se l'installazione di Windows ha i driver base che servono a far funzionare la nuova scheda madre allora riuscirai a far partire Windows anche senza formattare.
Se invece servono driver che nell'installazione di Windows non sono presenti o sono disattivati allora Windows non partirà.
In generale conviene formattare per avere comunque un'installazione pulita, e per essere sicuro di non avere i vecchi driver, che potrebbero interferire con i nuovi e creare problemi.
Ti costa molto formattare?
Non si può dire con certezza se Windows partirà sulla nuova scheda madre e se funzionerà senza problemi.
Dipende dai componenti della nuova scheda madre. Se l'installazione di Windows ha i driver base che servono a far funzionare la nuova scheda madre allora riuscirai a far partire Windows anche senza formattare.
Se invece servono driver che nell'installazione di Windows non sono presenti o sono disattivati allora Windows non partirà.
In generale conviene formattare per avere comunque un'installazione pulita, e per essere sicuro di non avere i vecchi driver, che potrebbero interferire con i nuovi e creare problemi.
Ti costa molto formattare?
diciamo anche ho dei programmi che non trovo più era per salvarli.. se si potesse salvare quei programmi per il resto non ci sono problemi.
Blue_screen_of_death
14-10-2019, 21:33
diciamo anche ho dei programmi che non trovo più era per salvarli.. se si potesse salvare quei programmi per il resto non ci sono problemi.
OK, su questo non posso risponderti. Dipende dai programmi. Alcuni programmi girano anche senza essere installati, dipende da come sono stati scritti.
Certezze non posso dartene, ma è molto probabile che Windows si avvierà anche sulla nuova scheda madre e CPU
La vera domanda è se riuscirà a girare bene. :)
Blue_screen_of_death
14-10-2019, 21:36
Anche perché la nuova scheda madre ha un chipset diverso, quindi driver completamente diversi.
La cosa migliore da fare è recuperare l'installer dei software che vuoi rimettere dopo la sostituzione e quindi fare un'installazione pulita.
Anche perché la nuova scheda madre ha un chipset diverso, quindi driver completamente diversi.
La cosa migliore da fare è recuperare l'installer dei software che vuoi rimettere dopo la sostituzione e quindi fare un'installazione pulita.
ho capito ti ringrazio sei stato anche fin troppo disponibile e genitle, per il problema invece delle usb 2.0 dici che possa dipendere smepre dalla scheda madre o dal case?
Blue_screen_of_death
14-10-2019, 21:49
In quali porte lo fa? Solo frontali o anche le posteriori?
In quali porte lo fa? Solo frontali o anche le posteriori?
le 2.0 le ho solo davanti le altre sono 3.0 in su quindi li mi fa sempre la rimozione sicura
Blue_screen_of_death
14-10-2019, 22:03
Visto il problema delle latenze anche per il problema delle USB darei la colpa alla scheda madre.
In particolare sto ripensando al problema delle disconnessioni.
Quante porte USB 3 hai sul pannello frontale del case? Quante USB 2.
Se le porte USB 2 frontali danno problemi di disconnessione, mentre quelle USB 3 funzionano allora probabilmente la causa è il controller USB 2 della scheda madre danneggiato.
Secondo me i problemi che hai sono tutti collegati e dovuti tutti alla scheda madre.
I freeze e i problemi di disconnessione delle USB sono comparsi contemporaneamente?
Visto il problema delle latenze anche per il problema delle USB darei la colpa alla scheda madre.
In particolare sto ripensando al problema delle disconnessioni.
Quante porte USB 3 hai sul pannello frontale del case? Quante USB 2.
Se le porte USB 2 frontali danno problemi di disconnessione, mentre quelle USB 3 funzionano allora probabilmente la causa è il controller USB 2 della scheda madre danneggiato.
Secondo me i problemi che hai sono tutti collegati e dovuti tutti alla scheda madre.
I freeze e i problemi di disconnessione delle USB sono comparsi contemporaneamente?
ho due 2.0 e una 3.0, no i problemi delle usb 2.0 che ogni tanto si disconnettono ce l'ho dall'inizio soprattutto il fatto che devo per forza andare in risorse del pc per espellerle, però cercavo di non farci caso. e notai che ultimamente pure la 3.0 frontale ogni tanto dava problemi di disconnessioni motlo rare ma ci sono state. I freeze invece diciamo negli ultimi mesi ma in questi due molto spesso.
Blue_screen_of_death
18-10-2019, 00:18
Novità?
Novità?
Ciao! allora ho finito ora ora di montare il pc e installarci windows ho cambiato ram processore scheda madre e alimentatore.
fatta la prova con latency però mi sembra sempre uguale... fai conto che è tutto vuoto mi conviene provare ad aggiornare i driver? intanto ti copio tutto:
https://ibb.co/rkY242S
_________________________________________________________________________________________________________
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:01:34 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-M604PTK
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16304 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 390 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): 194,50
Average measured interrupt to process latency (µs): 5,352982
Highest measured interrupt to DPC latency (µs): 192,10
Average measured interrupt to DPC latency (µs): 1,843066
_________________________________________________________________________________________________________
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): 27,530
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,005411
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,005462
ISR count (execution time <250 µs): 14556
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): 884012,734615
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 1,580347
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2,285688
DPC count (execution time <250 µs): 12219595
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 2
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: svchost.exe
Total number of hard pagefaults 18
Hard pagefault count of hardest hit process: 9
Number of processes hit: 4
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 11,070373
CPU 0 ISR highest execution time (µs): 27,530
CPU 0 ISR total execution time (s): 0,074717
CPU 0 ISR count: 13246
CPU 0 DPC highest execution time (µs): 160,410
CPU 0 DPC total execution time (s): 6,893595
CPU 0 DPC count: 1946355
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 12,059591
CPU 1 ISR highest execution time (µs): 23,440
CPU 1 ISR total execution time (s): 0,007395
CPU 1 ISR count: 1244
CPU 1 DPC highest execution time (µs): 349074,389744
CPU 1 DPC total execution time (s): 6,026263
CPU 1 DPC count: 3120176
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6,860971
CPU 2 ISR highest execution time (µs): 2,0
CPU 2 ISR total execution time (s): 0,000012
CPU 2 ISR count: 9
CPU 2 DPC highest execution time (µs): 1457,740
CPU 2 DPC total execution time (s): 3,096386
CPU 2 DPC count: 1204293
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 6,953359
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): 874136,130
CPU 3 DPC total execution time (s): 3,917353
CPU 3 DPC count: 1193791
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 6,945534
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): 884012,734615
CPU 4 DPC total execution time (s): 4,006206
CPU 4 DPC count: 1183891
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 7,060133
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): 599602,424872
CPU 5 DPC total execution time (s): 4,285578
CPU 5 DPC count: 1189413
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 6,801031
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): 52,860
CPU 6 DPC total execution time (s): 3,100181
CPU 6 DPC count: 1190753
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 6,869045
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,950
CPU 7 DPC total execution time (s): 3,045923
CPU 7 DPC count: 1189249
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,787722
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): 23,720
CPU 8 DPC total execution time (s): 0,000824
CPU 8 DPC count: 240
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,831231
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 75,950
CPU 9 DPC total execution time (s): 0,002452
CPU 9 DPC count: 336
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 0,774064
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 64,270
CPU 10 DPC total execution time (s): 0,002510
CPU 10 DPC count: 352
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 0,741042
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): 9,450
CPU 11 DPC total execution time (s): 0,000048
CPU 11 DPC count: 11
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 0,722017
CPU 12 ISR highest execution time (µs): 1,330
CPU 12 ISR total execution time (s): 0,000037
CPU 12 ISR count: 48
CPU 12 DPC highest execution time (µs): 54,220
CPU 12 DPC total execution time (s): 0,002682
CPU 12 DPC count: 377
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 0,629045
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 40,110
CPU 13 DPC total execution time (s): 0,000087
CPU 13 DPC count: 10
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 0,795681
CPU 14 ISR highest execution time (µs): 1,910
CPU 14 ISR total execution time (s): 0,000009
CPU 14 ISR count: 9
CPU 14 DPC highest execution time (µs): 52,230
CPU 14 DPC total execution time (s): 0,001912
CPU 14 DPC count: 286
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 0,748531
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 58,820
CPU 15 DPC total execution time (s): 0,000604
CPU 15 DPC count: 69
_________________________________________________________________________________________________________
Blue_screen_of_death
22-10-2019, 15:31
Si prova ad aggiornare i driver ma non credo sia colpa loro.
Quali componenti sono rimaste invariati?
Hai ancora il problema delle porte USB anteriori che causano disconnessioni?
Se sì, mi viene il sospetto che il problema è causato proprio da loro. Quindi ti chiedo di scollegare le porte anteriori dalla scheda madre e vedere come si comporta LatencyMon.
O forse ti ho già chiesto di fare la prova tempo fa e non me lo ricordo :D
Si prova ad aggiornare i driver ma non credo sia colpa loro.
Quali componenti sono rimaste invariati?
Hai ancora il problema delle porte USB anteriori che causano disconnessioni?
Se sì, mi viene il sospetto che il problema è causato proprio da loro. Quindi ti chiedo di scollegare le porte anteriori dalla scheda madre e vedere come si comporta LatencyMon.
O forse ti ho già chiesto di fare la prova tempo fa e non me lo ricordo :D
aggiornato tutto e questo è il risultato:
https://ibb.co/D7V1Hy4
_________________________________________________________________________________________________________
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:05:09 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-M604PTK
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16300 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3693 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): 2623,70
Average measured interrupt to process latency (µs): 4,849104
Highest measured interrupt to DPC latency (µs): 2620,50
Average measured interrupt to DPC latency (µs): 1,693616
_________________________________________________________________________________________________________
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): 25,748714
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,003244
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,003246
ISR count (execution time <250 µs): 30523
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): 951825,166260
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 1,449752
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 1,922291
DPC count (execution time <250 µs): 32663216
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µs): 4
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: chrome.exe
Total number of hard pagefaults 712
Hard pagefault count of hardest hit process: 261
Number of processes hit: 15
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 42,415829
CPU 0 ISR highest execution time (µs): 25,748714
CPU 0 ISR total execution time (s): 0,118526
CPU 0 ISR count: 23322
CPU 0 DPC highest execution time (µs): 2817,590577
CPU 0 DPC total execution time (s): 29,340094
CPU 0 DPC count: 8112276
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 35,138228
CPU 1 ISR highest execution time (µs): 23,253994
CPU 1 ISR total execution time (s): 0,041829
CPU 1 ISR count: 7159
CPU 1 DPC highest execution time (µs): 1918,619821
CPU 1 DPC total execution time (s): 17,309417
CPU 1 DPC count: 10041599
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 16,870758
CPU 2 ISR highest execution time (µs): 8,145410
CPU 2 ISR total execution time (s): 0,000143
CPU 2 ISR count: 37
CPU 2 DPC highest execution time (µs): 629571,436501
CPU 2 DPC total execution time (s): 8,583768
CPU 2 DPC count: 2420302
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 17,179568
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): 2268,912537
CPU 3 DPC total execution time (s): 7,541340
CPU 3 DPC count: 2423248
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 17,286135
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): 43,402112
CPU 4 DPC total execution time (s): 7,592218
CPU 4 DPC count: 2392045
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 16,985047
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): 832465,955050
CPU 5 DPC total execution time (s): 8,471428
CPU 5 DPC count: 2416677
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 16,688821
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): 951825,166260
CPU 6 DPC total execution time (s): 8,594823
CPU 6 DPC count: 2433010
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 16,947869
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): 46,77850
CPU 7 DPC total execution time (s): 7,552623
CPU 7 DPC count: 2412248
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,900173
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): 50,826158
CPU 8 DPC total execution time (s): 0,014097
CPU 8 DPC count: 3845
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,773706
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 59,963444
CPU 9 DPC total execution time (s): 0,006337
CPU 9 DPC count: 1824
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,556195
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 44,323856
CPU 10 DPC total execution time (s): 0,013091
CPU 10 DPC count: 2245
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,542046
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): 32,511508
CPU 11 DPC total execution time (s): 0,000874
CPU 11 DPC count: 165
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 2,770418
CPU 12 ISR highest execution time (µs): 1,021933
CPU 12 ISR total execution time (s): 0,000003
CPU 12 ISR count: 4
CPU 12 DPC highest execution time (µs): 44,634444
CPU 12 DPC total execution time (s): 0,011312
CPU 12 DPC count: 1745
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 2,517161
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 40,817222
CPU 13 DPC total execution time (s): 0,000499
CPU 13 DPC count: 102
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 3,603003
CPU 14 ISR highest execution time (µs): 0,551043
CPU 14 ISR total execution time (s): 0,000001
CPU 14 ISR count: 1
CPU 14 DPC highest execution time (µs): 52,629569
CPU 14 DPC total execution time (s): 0,008358
CPU 14 DPC count: 1525
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 3,333408
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 58,861359
CPU 15 DPC total execution time (s): 0,002426
CPU 15 DPC count: 369
_________________________________________________________________________________________________________
Blue_screen_of_death
22-10-2019, 16:40
C'è qualcosa che non torna.. l'immagine è ok, mentre il report no :D
Hai arrestato e riavviato il monitoraggio prima di fare lo screenshot?
C'è qualcosa che non torna.. l'immagine è ok, mentre il report no :D
Hai arrestato e riavviato il monitoraggio prima di fare lo screenshot?
no ho solo copiato il report e poi ho fatto lo screen c'è stato quel secondo ecco :D
Blue_screen_of_death
22-10-2019, 16:47
Stacca le USB anteriori dalla scheda madre, se danno ancora problemi.
:sperem:
Stacca le USB anteriori dalla scheda madre, se danno ancora problemi.
:sperem:
no le usb anteriori non danno più problemi ma per il resto va bene ora sono "normali" quei valori?
edit: ho riprovato a fare il test ma qui mi sembra uguale se non peggio
Blue_screen_of_death
22-10-2019, 17:09
no le usb anteriori non danno più problemi ma per il resto va bene ora sono "normali" quei valori?
No.
Highest DPC routine execution time (µs): 951825,166260
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
E' un blocco di quasi un secondo causato dal driver di storage.
Non so dirti se continuerai a vedere freeze o altri tipi di errori perché la natura del problema è random.
In pratica ogni tanto un driver (random) blocca alcuni processori (random) per un tempo (random) che va da mezzo secondo a un secondo.
Se il processore incaricato di processare i tuoi dati multimediali (audio, video o giochi) è uno dei processori che subiscono il blocco allora l'audio o il video freezerà. Se il blocco è prolungato, allora Windows si spegne con una bella schermata blu di errore.
Avendo molti processori logici (16), raramente vedi i freeze.
Se avessi una CPU con meno core o senza HyperThreading probabilmente i freeze sarebbero così frequenti da rendere la macchina inutilizzabile.
O avresti BSOD frequenti.
Quindi, riassumendo il problema non è risolto.
Se vuoi continuare ad indagare, elenca i componenti che sono rimasti invariati. Io ho perso il filo :D
E cerchiamo di andare ad esclusione con quelli. Anche le periferiche esterne possono essere causa di problemi. Anche i cavi, sia interni che esterni (motivo per cui ti consigliavo di scollegare le USB anteriori).
Cosa non hai provato a togliere? Scheda video, UPS? Qualunque cosa. Prova anche a collegare il PC a un'altra fonte di alimentazione.
Altrimenti, lascia il PC com'è e che succede nei prossimi giorni, ma secondo me avrai la stessa situazione che avevi con la vecchia scheda madre.
No.
Highest DPC routine execution time (µs): 951825,166260
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
E' un blocco di quasi un secondo causato dal driver di storage.
Non so dirti se continuerai a vedere freeze o altri tipi di errori perché la natura del problema è random.
In pratica ogni tanto un driver (random) blocca alcuni processori (random) per un tempo (random) che va da mezzo secondo a un secondo.
Se il processore incaricato di processare i tuoi dati multimediali (audio, video o giochi) è uno dei processori che subiscono il blocco allora l'audio o il video freezerà. Se il blocco è prolungato, allora Windows si spegne con una bella schermata blu di errore.
Avendo molti processori logici (16), raramente vedi i freeze.
Se avessi una CPU con meno core o senza HyperThreading probabilmente i freeze sarebbero così frequenti da rendere la macchina inutilizzabile.
O avresti BSOD frequenti.
Quindi, riassumendo il problema non è risolto.
Se vuoi continuare ad indagare, elenca i componenti che sono rimasti invariati. Io ho perso il filo :D
E cerchiamo di andare ad esclusione con quelli. Anche le periferiche esterne possono essere causa di problemi. Anche i cavi, sia interni che esterni (motivo per cui ti consigliavo di scollegare le USB anteriori).
Cosa non hai provato a togliere? Scheda video, ...
Altrimenti, lascia il PC com'è e che succede nei prossimi giorni, ma secondo me avrai la stessa situazione che avevi con la vecchia scheda madre.
Allora di vecchi componenti mi è rimasta ma RX580 GB che è la scheda video e il sabrent da 1tb nvme per il resto ho cambiato tutto si può dire i nuovi componenti sono questi:
Asus prime x470 pro
AMD Ryzen 2700x
Corsair Vegance da 16 gb 3200MHz
SilentStorm 750w
Ho cambiato anche i cavi sata collegati agli hard disk sono nuovi di pacca.
Ora provo a scollegare usb frontali.
SI la scheda video mi manca perchè provai ma non mi si avviava il pc.
EDIT: ti metto tutto con usb staccati https://ibb.co/bvdhzf7
_________________________________________________________________________________________________________
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:05:27 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-M604PTK
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16300 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3693 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): 87,10
Average measured interrupt to process latency (µs): 4,662324
Highest measured interrupt to DPC latency (µs): 84,20
Average measured interrupt to DPC latency (µs): 1,629250
_________________________________________________________________________________________________________
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): 15,880043
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000465
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,000465
ISR count (execution time <250 µs): 3485
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): 970669,886813
Driver with highest DPC routine execution time: CLASSPNP.SYS - SCSI Class System Dll, Microsoft Corporation
Highest reported total DPC routine time (%): 1,359450
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 1,814348
DPC count (execution time <250 µs): 33050819
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
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: radeonsettings.exe
Total number of hard pagefaults 3362
Hard pagefault count of hardest hit process: 734
Number of processes hit: 38
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 41,982598
CPU 0 ISR highest execution time (µs): 15,880043
CPU 0 ISR total execution time (s): 0,022974
CPU 0 ISR count: 3303
CPU 0 DPC highest execution time (µs): 601139,494991
CPU 0 DPC total execution time (s): 29,647992
CPU 0 DPC count: 8206946
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 35,665864
CPU 1 ISR highest execution time (µs): 14,607636
CPU 1 ISR total execution time (s): 0,001339
CPU 1 ISR count: 182
CPU 1 DPC highest execution time (µs): 970669,886813
CPU 1 DPC total execution time (s): 18,398535
CPU 1 DPC count: 10141752
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 17,310697
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 134,183861
CPU 2 DPC total execution time (s): 7,530116
CPU 2 DPC count: 2441819
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 17,509693
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): 47,179258
CPU 3 DPC total execution time (s): 7,537943
CPU 3 DPC count: 2460326
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 17,228142
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): 403506,280260
CPU 4 DPC total execution time (s): 8,015586
CPU 4 DPC count: 2447306
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 17,316313
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): 377224,747901
CPU 5 DPC total execution time (s): 7,911540
CPU 5 DPC count: 2437821
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 17,257399
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): 619017,929867
CPU 6 DPC total execution time (s): 8,210108
CPU 6 DPC count: 2456227
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 17,326859
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): 173431,35310
CPU 7 DPC total execution time (s): 7,645807
CPU 7 DPC count: 2446877
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 3,778365
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): 52,609532
CPU 8 DPC total execution time (s): 0,020912
CPU 8 DPC count: 6236
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3,878063
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 33,423233
CPU 9 DPC total execution time (s): 0,002345
CPU 9 DPC count: 500
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,272729
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 36,178446
CPU 10 DPC total execution time (s): 0,010192
CPU 10 DPC count: 1905
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,310301
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): 32,772001
CPU 11 DPC total execution time (s): 0,000387
CPU 11 DPC count: 64
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 2,889238
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 36,849716
CPU 12 DPC total execution time (s): 0,007432
CPU 12 DPC count: 1274
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 2,763602
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 35,386948
CPU 13 DPC total execution time (s): 0,001460
CPU 13 DPC count: 258
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 3,075945
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 43,983211
CPU 14 DPC total execution time (s): 0,006281
CPU 14 DPC count: 1133
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 3,026261
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 50,926347
CPU 15 DPC total execution time (s): 0,002683
CPU 15 DPC count: 382
_________________________________________________________________________________________________________
Blue_screen_of_death
22-10-2019, 19:23
La cosa strana è che ancora nell'immagine le latenze sono basse, mentre nel report sono alte :D
Adesso addirittura CLASSPNP.SYS
Hai periferiche SCSI?
La cosa strana è che ancora nell'immagine le latenze sono basse, mentre nel report sono alte :D
Adesso addirittura CLASSPNP.SYS
Hai periferiche SCSI?
che cosa sarebbe? perdona la mia ignoranza :D
comunque ora ti copio un altro test con immagine magari ti ho copiato un'immagine sbagliata. e ti linko anche un video di un rumore che proviene dal dissipatore di amd non riesco a capire cosa sia più che altro ora ha smesso cosa può essere?
https://drive.google.com/file/d/1bgFtWRmZvDyojG6jaC7ww-I6vHsMUJE4/view?usp=sharing
https://ibb.co/5hvnyPG
_________________________________________________________________________________________________________
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 0:04:49 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-M604PTK
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16300 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3693 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): 1889,30
Average measured interrupt to process latency (µs): 4,281793
Highest measured interrupt to DPC latency (µs): 1886,10
Average measured interrupt to DPC latency (µs): 1,680574
_________________________________________________________________________________________________________
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): 19,877606
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000481
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,000481
ISR count (execution time <250 µs): 3107
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): 1893,552396
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 1,040055
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 1,381337
DPC count (execution time <250 µs): 25274272
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 3
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: msmpeng.exe
Total number of hard pagefaults 88
Hard pagefault count of hardest hit process: 68
Number of processes hit: 4
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 38,925620
CPU 0 ISR highest execution time (µs): 19,877606
CPU 0 ISR total execution time (s): 0,010825
CPU 0 ISR count: 1558
CPU 0 DPC highest execution time (µs): 1893,552396
CPU 0 DPC total execution time (s): 26,563624
CPU 0 DPC count: 7256207
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 30,436321
CPU 1 ISR highest execution time (µs): 15,839968
CPU 1 ISR total execution time (s): 0,011432
CPU 1 ISR count: 1549
CPU 1 DPC highest execution time (µs): 170,552667
CPU 1 DPC total execution time (s): 13,162771
CPU 1 DPC count: 8956125
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 13,102202
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 149,793393
CPU 2 DPC total execution time (s): 3,973042
CPU 2 DPC count: 1499600
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 13,536101
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): 54,172488
CPU 3 DPC total execution time (s): 4,006868
CPU 3 DPC count: 1519966
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 12,961436
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): 43,091525
CPU 4 DPC total execution time (s): 4,035090
CPU 4 DPC count: 1485881
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 13,270214
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): 34,655565
CPU 5 DPC total execution time (s): 4,123144
CPU 5 DPC count: 1519391
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 12,788994
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): 45,646358
CPU 6 DPC total execution time (s): 3,966338
CPU 6 DPC count: 1498656
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 12,920326
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): 41,568643
CPU 7 DPC total execution time (s): 4,029491
CPU 7 DPC count: 1535733
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,103683
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): 38,362578
CPU 8 DPC total execution time (s): 0,004918
CPU 8 DPC count: 1171
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 1,857980
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 9,047116
CPU 9 DPC total execution time (s): 0,000009
CPU 9 DPC count: 1
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,740750
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 32,090712
CPU 10 DPC total execution time (s): 0,001910
CPU 10 DPC count: 347
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1,785368
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): 19,276469
CPU 11 DPC total execution time (s): 0,000124
CPU 11 DPC count: 28
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 2,311753
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 1667,414568
CPU 12 DPC total execution time (s): 0,006227
CPU 12 DPC count: 802
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 2,076336
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 1,202275
CPU 13 DPC total execution time (s): 0,000002
CPU 13 DPC count: 2
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 2,357375
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 46,628216
CPU 14 DPC total execution time (s): 0,002489
CPU 14 DPC count: 324
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2,335341
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 40,877335
CPU 15 DPC total execution time (s): 0,000310
CPU 15 DPC count: 41
_________________________________________________________________________________________________________
La cosa strana è che ancora nell'immagine le latenze sono basse, mentre nel report sono alte :D
Adesso addirittura CLASSPNP.SYS
Hai periferiche SCSI?
l'unica cosa sarebbe provare con una build precedente di windows ma come faccio a trovarla o per tornare indietro perchè io ho usato l'ultima build che mi fa scaricare microsoft
Nicodemo Timoteo Taddeo
24-10-2019, 15:03
https://tb.rg-adguard.net/public.php
https://tb.rg-adguard.net/public.php
grazie mille provo subito!
edit: non è cambiato niente, provo ad aggiornare i driver ma penso che serva a poco
non ho seguito se non giusto distrattamente il thread (anzi, mi prometto di farlo a momenti) ma mi hanno colpito due cose:
1) (più che altro una semplice curiosità): ma hai cambiato PC da quando hai aperto il thread?
Il 1° post infatti riporta un ryzen 5 1600 e una Gygabyte ax370 k3 gaming, LatencyMon (quantomeno l'ultimo report da te postato) fa riferimento ad un Ryzen 7 2700X e una ASUS PRIME X470-PRO...
2) su 1903 sono stati segnalati (e forse mai risolti del tutto) problemi quali quelli da te descritti (e che si verificano evidentemente in circostanze molto particolari complicando sicuramente la comprensione del fenomeno da parte di MS),
https://www.reddit.com/r/Windows10/comments/bu34xv/update_1903_high_dpc_latency_issues/
https://www.tenforums.com/performance-maintenance/133708-v1903-causing-dpc-latency-hits.html
non ho seguito se non giusto distrattamente il thread (anzi, mi prometto di farlo a momenti) ma mi hanno colpito due cose:
1) (più che altro una semplice curiosità): ma hai cambiato PC da quando hai aperto il thread?
Il 1° post infatti riporta un ryzen 5 1600 e una Gygabyte ax370 k3 gaming, LatencyMon (quantomeno l'ultimo report da te postato) fa riferimento ad un Ryzen 7 2700X e una ASUS PRIME X470-PRO...
2) su 1903 sono stati segnalati (e forse mai risolti del tutto) problemi quali quelli da te descritti (e che si verificano evidentemente in circostanze molto particolari complicando sicuramente la comprensione del fenomeno da parte di MS),
https://www.reddit.com/r/Windows10/comments/bu34xv/update_1903_high_dpc_latency_issues/
https://www.tenforums.com/performance-maintenance/133708-v1903-causing-dpc-latency-hits.html
si ho cambiato pc perchè si pensava fosse un problema relativo all'hardware visto che erano in garanzia.
più che altro ho provato oggi con un portatile con la nuova build e lui va tranquillo non capisco il perchè.. e ora sono sono sulla build 1803
quindi, solito fenomeno su 2 macchine diverse che, in comune, hanno giusto un Ryzen (di generazioni peraltro differenti).
Ma c'è qualche componente che hai portato sulla nuova configurazione? (RAM, VGA,..., magari è proprio quel componente comune la causa del fastidio).
Credo te lo abbia già indicato l'utente BSoD, ben più preparato di me, ma ti dovresti mettere nella condizione di eliminare il superfluo (lasciare cioè giusto quello che ti è necessario per il funzionamento di base della macchina), immagino tu l'abbia fatto no?
Puoi dare la lista completa di tutte le periferiche presenti sul PC di qualsiasi natura esse siano?
(trovata almeno in parte, scusa)
Asus prime x470 pro
AMD Ryzen 2700x
Corsair Vegance da 16 gb 3200MHz
SilentStorm 750w
EDIT* e sulla build 1803 ti fa lo stesso gioco??
quindi, solito fenomeno su 2 macchine diverse che, in comune, hanno giusto un Ryzen (di generazioni peraltro differenti).
Ma c'è qualche componente che hai portato sulla nuova configurazione? (RAM, VGA,..., magari è proprio quel componente comune la causa del fastidio).
Credo te lo abbia già indicato l'utente BSoD, ben più preparato di me, ma ti dovresti mettere nella condizione di eliminare il superfluo (lasciare cioè giusto quello che ti è necessario per il funzionamento di base della macchina), immagino tu l'abbia fatto no?
Puoi dare la lista completa di tutte le periferiche presenti sul PC di qualsiasi natura esse siano?
(trovata almeno in parte, scusa)
EDIT* e sulla build 1803 ti fa lo stesso gioco??
si ho cambiato di tutto anche il case, alimentatore e ram. Di "vecchio" ho portato la scheda video RX580 8GB Aorus e l'ssd Sabrent Nvme ma anche quello preso 2 settimane fa il problema me lo dava già da qualche mese.
Si anche provando l'altra build sperando fosse quello ma niente..
il problema dell'ssd lo abbiamo scartato perchè ne avevo uno ssd sata e facevo lo stesso quindi davvero non ho idea di cosa possa essere.
Blue_screen_of_death
24-10-2019, 17:17
Mouse e tastiera o i loro cavi :D
Alimentazione i stabile? Prova ad utilizzare un'altra ciabatta o presa.
Sono le uniche cose che non hai testato, credo
Mouse e tastiera o i loro cavi :D
Alimentazione i stabile? Prova ad utilizzare un'altra ciabatta o presa.
Sono le uniche cose che non hai testato, credo
posso provare ma sono attaccato al gruppo di continuità che è pure a onda sin.pura
Blue_screen_of_death
24-10-2019, 17:22
Si, connettiti direttamente all'alimentazione e prova a cambiare presa.
:sperem:
poveretto, fosse davvero la ciabatta/presa credo si impicchi al primo travicello dato che ha cambiato praticamente PC per riscontare il solito guaio.
Peraltro si apprende che 1803/1903 manifestano il solito discorso (che il 3 gli porti male??).
Seriamente, ti sono solidale ma non so in che modo aiutarti (e di sicuro mi trovassi nella stessa situazione avrei già provveduto a tirar tutto fuor di finestra).
PS: si parla sempre di installazioni pulite (fatte cioè da 0 e non alterate in alcun modo con antivirus esterni etc) o versioni "manipolate" da software?? (discostandoti quindi dalla situazione ideale che in questi casi vuole l'OS vergine :oink: )
poveretto, fosse davvero la ciabatta/presa credo si impicchi al primo travicello dato che ha cambiato praticamente PC per riscontare il solito guaio.
Peraltro si apprende che 1803/1903 manifestano il solito discorso (che il 3 gli porti male??).
Seriamente, ti sono solidale ma non so in che modo aiutarti (e di sicuro mi trovassi nella stessa situazione avrei già provveduto a tirar tutto fuor di finestra).
PS: si parla sempre di installazioni pulite (fatte cioè da 0 e non alterate in alcun modo con antivirus esterni etc) o versioni "manipolate" da software?? (discostandoti quindi dalla situazione ideale che in questi casi vuole l'OS vergine :oink: )
Provato ora, diretto alla presa staccanti internet mouse tastiera e tutto solo lhdmi Collegato al monitor. Ma il problema persiste.
Sisi installazioni pulite provando anche senza installare driver provando subito la latenza ma è uguale.
Blue_screen_of_death
24-10-2019, 17:41
La cosa ha dell'incredibile ahah
Cosa rimane? Non ricordo più.
Per la scheda video poi hai provato a scollegarla e usare l'integrata?
L'avevo scritto qualche pagina fa ma non mi ricordo se l'hai fatto :)
La cosa ha dell'incredibile ahah
Cosa rimane? Non ricordo più.
Per la scheda video poi hai provato a scollegarla e usare l'integrata?
L'avevo scritto qualche pagina fa ma non mi ricordo se l'hai fatto :)
No davvero non so più che fare ahaha no non mi parte il pc e non riesco a disabilitarla dal bios
Nicodemo Timoteo Taddeo
24-10-2019, 17:51
La cosa ha dell'incredibile ahah
Cosa rimane? Non ricordo più.
https://i.ibb.co/WGWwPjL/7s200rym33-chi-vuole-un-goccio-acqua-di-lourdes-vaccata-a-2.jpg
no non mi parte il pc e non riesco a disabilitarla dal biosquello è normale, Ryzen non ha una VGA integrata.
Cmq:
provata la versione del BIOS 5220 datata 24.9?
Hai installato gli AMD Chipset Drivers 1.9.27.1033 del 27.9?
E gli ultimi driver certificati per la tua MB per le periferiche rimanenti? (Realtek per il comparto audio/Intel Gigabit Ethernet Driver per la LAN)..
Cmq che sfiga (si, permettimi: questa è proprio nera)
quello è normale, Ryzen non ha una VGA integrata.
Cmq:
provata la versione del BIOS 5220 datata 24.9?
Hai installato gli AMD Chipset Drivers 1.9.27.1033 del 27.9?
E gli ultimi driver certificati per la tua MB per le periferiche rimanenti? (Realtek per il comparto audio/Intel Gigabit Ethernet Driver per la LAN)..
Cmq che sfiga (si, permettimi: questa è proprio nera)
Sisi installato tutto dal sito dellasus ma rimane io posso provare anche una build più vecchia ma penso che il problema persista
Sisi installato tutto dal sito dell’asus ma rimane io posso provare anche una build più vecchia ma penso che il problema persista
semmai a questo punto & se hai altro tempo da cestinare ti potrei suggerire l'ultima insider del ramo 20H1 e vedere un pò:
https://www.tenforums.com/windows-10-news/143039-new-windows-10-insider-preview-fast-skip-build-19008-20h1-oct-22-a.html (ti dice anche come entrare in quel ramo etc)
Credo siano questi i problemi (rari, per fortuna) che spingono i malaugurati utenti a rimpiangere una consolle etc :O
semmai a questo punto & se hai altro tempo da cestinare ti potrei suggerire l'ultima insider del ramo 20H1 e vedere un pò:
https://www.tenforums.com/windows-10-news/143039-new-windows-10-insider-preview-fast-skip-build-19008-20h1-oct-22-a.html (ti dice anche come entrare in quel ramo etc)
Credo siano questi i problemi (rari, per fortuna) che spingono i malaugurati utenti a rimpiangere una consolle etc :O
Adesso provo grazie mille
semmai a questo punto & se hai altro tempo da cestinare ti potrei suggerire l'ultima insider del ramo 20H1 e vedere un pò:
https://www.tenforums.com/windows-10-news/143039-new-windows-10-insider-preview-fast-skip-build-19008-20h1-oct-22-a.html (ti dice anche come entrare in quel ramo etc)
Credo siano questi i problemi (rari, per fortuna) che spingono i malaugurati utenti a rimpiangere una consolle etc :O
niente ho provato ma il problema persiste. :muro:
poi devo staccare per cui nel caso leggerò domani:
dovresti aprire *urgentemente* una segnalazione perchè tentino quantomeno di identificare il problema partendo dalle tracce che gli dovrai inviare (sempre che tu abbia tempo e interesse a confonderti ulteriormente).
Come?
"For category, please choose -- 'power and battery' -> 'fast drain screen-on'
Under Add more details, choose 'Recreate my problem', choose include data about 'performance', repro the performance issue, and submit feedback" (https://www.reddit.com/r/Windows10/comments/c8wndl/news_on_the_dpc_latency_bug_in_1903/eth4ham/?context=3 (srepaka del team MS))
Altrimenti puoi contattare direttamente pete_brown (https://twitter.com/pete_brown/status/1155340823824883713) via twitter.
In bocca al lupo, ti sono vicino.
E fai sapere eh
Blue_screen_of_death
24-10-2019, 21:59
Mah, la cosa diventa sempre più interessante. :D
Prova a mandarmi una traccia costruita con Windows Performance Toolkit. Così vediamo più in dettaglio cosa fa il sistema negli istanti in cui hai stuttering.
Scarica https://support.microsoft.com/it-it/help/4027209/oems-adk-download-for-windows-10
E' un kit di strumenti per developers. Avvia l'installer. Nella schermata in cui ti chiede quali componenti installare spunta soltanto Windows Performance Toolkit.
Al termine dell'installazione apri il prompt dei comandi.
Esegui questo comando:
xperf -on DiagEasy
Fai qualcosa che di solito causa stuttering (es. eseguire CrystalDiskMark o CrystalDiskInfo).
Poi esegui questo comando per generare la traccia
xperf -d %userprofile%\Desktop\trace.etl
Attendi il termine dell'operazione e mandami il file trace.etl che trovi sul desktop.
Mah, la cosa diventa sempre più interessante. :D
Prova a mandarmi una traccia costruita con Windows Performance Toolkit. Così vediamo più in dettaglio cosa fa il sistema negli istanti in cui hai stuttering.
Scarica https://support.microsoft.com/it-it/help/4027209/oems-adk-download-for-windows-10
E' un kit di strumenti per developers. Avvia l'installer. Nella schermata in cui ti chiede quali componenti installare spunta soltanto Windows Performance Toolkit.
Al termine dell'installazione apri il prompt dei comandi.
Esegui questo comando:
xperf -on DiagEasy
Fai qualcosa che di solito causa stuttering (es. eseguire CrystalDiskMark o CrystalDiskInfo).
Poi esegui questo comando per generare la traccia
xperf -d %userprofile%\Desktop\trace.etl
Attendi il termine dell'operazione e mandami il file trace.etl che trovi sul desktop.
ecco fatto
https://www.dropbox.com/s/lnbw2hkbllaor51/trace.etl?dl=0
Blue_screen_of_death
24-10-2019, 23:38
qui i valori sono nella norma
sei certo di aver catturato almeno un freeze?
P.S. Assicurati anche di avere installato gli aggiornamenti nel link postato da nTi0
qui i valori sono nella norma
sei certo di aver catturato almeno un freeze?
P.S. Assicurati anche di avere installato gli aggiornamenti nel link postato da nTi0
si ho lanciato cmark e latency e ho visto poi arrivare al rosso latency come sempre ma freeze ora come ora non ne vedo più come prima almeno...
Blue_screen_of_death
25-10-2019, 00:06
ok, il problema era sempre su storport.sys immagino
Potresti rifarmi il trace.etl allo stesso modo?
Scusa, non è riuscito a catturare il nome del modulo
Prova così.
Avvia il trace, avvia CrystalDiskInfo / CrystalDiskMark
Aspetta 5 minuti
Termina il trace
Manda il file trace.etl
ok, il problema era sempre su storport.sys immagino
Potresti rifarmi il trace.etl allo stesso modo?
Scusa, non è riuscito a catturare il nome del modulo
Prova così.
Avvia il trace, avvia CrystalDiskInfo / CrystalDiskMark
Aspetta 5 minuti
Termina il trace
Manda il file trace.etl
si te lo faccio subito, una cosa ho attivato driver verifer e mi ha crashato il sistema più volte però il .dmp pesa quasi un 1,5gb riprovo con quello più piccolo kernel?
Blue_screen_of_death
25-10-2019, 00:09
si te lo faccio subito, una cosa ho attivato driver verifer e mi ha crashato il sistema più volte però il .dmp pesa quasi un 1,5gb riprovo con quello più piccolo kernel?
Si vai, proviamo prima con quello piccolo. Per alcune tipologie di errore è sufficiente.
Per errori più complicati serve guardare il contenuto delle pagine di memoria e quindi serve il dump completo.
Si vai, proviamo prima con quello piccolo. Per alcune tipologie di errore è sufficiente.
Per errori più complicati serve guardare il contenuto delle pagine di memoria e quindi serve il dump completo.
https://www.dropbox.com/s/kp8r22x5bs9u2pb/102519-17421-01.dmp?dl=0
https://www.dropbox.com/s/1bxf32cf0zyjj1d/102519-17703-01.dmp?dl=0
ne ho due guarda se vanno bene poi il trace mi da 5 gb è normale?
Blue_screen_of_death
25-10-2019, 00:22
https://www.dropbox.com/s/kp8r22x5bs9u2pb/102519-17421-01.dmp?dl=0
https://www.dropbox.com/s/1bxf32cf0zyjj1d/102519-17703-01.dmp?dl=0
ne ho due guarda se vanno bene poi il trace mi da 5 gb è normale?
ahah beh si dentro c'è tutto quello che il sistema ha fatto per 5 minuti (driver, processi e kernel). E il sistema operativo di lavoro ne fa tanto.
Se non riesci a inviarlo, fallo girare per meno tempo. 1 o 2 minuti, dovrebbe venire abbastanza piccolo.
ahah beh si dentro c'è tutto quello che il sistema ha fatto per 5 minuti (driver, processi e kernel). E il sistema operativo di lavoro ne fa tanto.
Se non riesci a inviarlo, fallo girare per meno tempo. 1 o 2 minuti, dovrebbe venire abbastanza piccolo.
più che altro poi mi viene scritto "xperf: warning: Session "NT Kernel Logger" lost 215065 events."
sto caricando quello da 2gb e li quell'errore non mi è venuto.
ahah beh si dentro c'è tutto quello che il sistema ha fatto per 5 minuti (driver, processi e kernel). E il sistema operativo di lavoro ne fa tanto.
Se non riesci a inviarlo, fallo girare per meno tempo. 1 o 2 minuti, dovrebbe venire abbastanza piccolo.
ecco a te scusami ma ora stacco leggo domani mattina grazie di nuovo speriamo di riuscire nell'intento. nel caso poi provo a fare una partizione e installarci un windows 7 magari per vedere se il problema c'è anche li (non penso) che dici?
https://www.dropbox.com/s/boiwjdke9s4mv6d/trace.etl?dl=0
Blue_screen_of_death
25-10-2019, 00:49
nel caso poi provo a fare una partizione e installarci un windows 7 magari per vedere se il problema c'è anche li (non penso) che dici?
Si, mi sembra un'ottima idea.
La penso come te, ovvero che il problema è limitato a W10.
Intanto guardo le BSOD e ti faccio sapere. Ma ti sono comparse a PC appena avviato oppure mentre eseguivi CrystalDiskInfo / CrystalDiskMark?
Si, mi sembra un'ottima idea.
La penso come te, ovvero che il problema è limitato a W10.
Intanto guardo le BSOD e ti faccio sapere. Ma ti sono comparse a PC appena avviato oppure mentre eseguivi CrystalDiskInfo / CrystalDiskMark?
Diciamo che ogni tanto noto dei freeze ma leggeri e non di audio ma sono impercettibili non so nemmeno se si possono chiamare così ed è difficile anche notarli e se uno deve fare un report deve stare mezzora acceso e ti viene troppo grosso il file poi ahaha
Blue_screen_of_death
25-10-2019, 07:40
Ok, ma le schermate blu ti sono comparse durante l'avvio del PC oppure mentre eseguivo CrystalDiskMark?
Ok, ma le schermate blu ti sono comparse durante l'avvio del PC oppure mentre eseguivo CrystalDiskMark?
La prima volta con cristaldisk mark e latency avviato è la seconda subito dopo lavvio
Blue_screen_of_death
25-10-2019, 13:02
Ok grazie per i log. Li guardo a fine giornata.
Hai fatto l'installazione pulito dopo aver cambiato scheda madre? Questo per escludere problemi legati a vecchi driver ancora presenti nel sistema.
Ok grazie per i log. Li guardo a fine giornata.
Hai fatto l'installazione pulito dopo aver cambiato scheda madre? Questo per escludere problemi legati a vecchi driver ancora presenti nel sistema.
Grazie a te dellaiuto, il trace dimmi poi se ti andava bene, comunque sisi installazione pulita
Blue_screen_of_death
28-10-2019, 09:52
Si, sia i dump che i trace contengono le informazioni che cercavo.
Le schermate blu indicano un problema con un driver di Microsoft, clipsp.sys, che durante una procedura di uninitialize fa delle operazioni (probabilmente rilascio di handle) usando un livello di priorità troppo alto).
Driver verifier non ha catturato il livello di priorità nel driver, ma se è superiore a una certa soglia le DPC vengono rallentate e le latenze di tutti i driver crescono (che è proprio il tuo problema).
Non sono sicuro che è questa la causa delle latenze alte, perché se non ricordo male in precedenza questo problema non c'era. Forse è stato introdotto nella nuova build di Windows? (oppure hai rimesso la build che avevi in precedenza?)
Essendo un bug del driver Microsoft ed essendo Windows closed source non possiamo risolvere il problema, ma possiamo cercare di limitare le chiamate al driver e vedere se il problema delle latenze sparisce o se almeno viene attenuato.
Il bug del driver è stato attivato probabilmente dal servizio Protezione software, quindi come prima cosa prova a disattivare quel servizio in Servizi.
Poi riavvia il sistema con driver verifier disattivato e testa le latenze.
Se sono ancora alte, riattiva driver verifier e vedi se hai altre schermate blu.
Si, sia i dump che i trace contengono le informazioni che cercavo.
Le schermate blu indicano un problema con un driver di Microsoft, clipsp.sys, che durante una procedura di uninitialize fa delle operazioni (probabilmente rilascio di handle) usando un livello di priorità troppo alto).
Driver verifier non ha catturato il livello di priorità nel driver, ma se è superiore a una certa soglia le DPC vengono rallentate e le latenze di tutti i driver crescono (che è proprio il tuo problema).
Non sono sicuro che è questa la causa delle latenze alte, perché se non ricordo male in precedenza questo problema non c'era. Forse è stato introdotto nella nuova build di Windows? (oppure hai rimesso la build che avevi in precedenza?)
Essendo un bug del driver Microsoft ed essendo Windows closed source non possiamo risolvere il problema, ma possiamo cercare di limitare le chiamate al driver e vedere se il problema delle latenze sparisce o se almeno viene attenuato.
Il bug del driver è stato attivato probabilmente dal servizio Protezione software, quindi come prima cosa prova a disattivare quel servizio in Servizi.
Poi riavvia il sistema con driver verifier disattivato e testa le latenze.
Se sono ancora alte, riattiva driver verifier e vedi se hai altre schermate blu.
questo è il report dopo averlo disattivato
https://ibb.co/hZmMc2C
_________________________________________________________________________________________________________
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:06:13 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-9P086B6
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16300 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3992 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): 99,20
Average measured interrupt to process latency (µs): 4,376785
Highest measured interrupt to DPC latency (µs): 96,0
Average measured interrupt to DPC latency (µs): 1,626656
_________________________________________________________________________________________________________
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): 20,551102
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0,000498
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Total time spent in ISRs (%) 0,000501
ISR count (execution time <250 µs): 4843
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): 943037,004008
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 1,200649
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 1,598543
DPC count (execution time <250 µs): 32455719
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
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: shellexperiencehost.exe
Total number of hard pagefaults 217
Hard pagefault count of hardest hit process: 83
Number of processes hit: 15
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 43,084396
CPU 0 ISR highest execution time (µs): 19,298597
CPU 0 ISR total execution time (s): 0,027610
CPU 0 ISR count: 4525
CPU 0 DPC highest execution time (µs): 943037,004008
CPU 0 DPC total execution time (s): 30,509288
CPU 0 DPC count: 8034833
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 34,889336
CPU 1 ISR highest execution time (µs): 20,551102
CPU 1 ISR total execution time (s): 0,002274
CPU 1 ISR count: 310
CPU 1 DPC highest execution time (µs): 92,885772
CPU 1 DPC total execution time (s): 16,923504
CPU 1 DPC count: 9806251
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 17,423248
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 416439,043086
CPU 2 DPC total execution time (s): 7,931141
CPU 2 DPC count: 2430786
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 17,812851
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): 392526,437625
CPU 3 DPC total execution time (s): 8,524482
CPU 3 DPC count: 2433899
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 17,542963
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): 369989,774549
CPU 4 DPC total execution time (s): 8,060080
CPU 4 DPC count: 2442784
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 17,714540
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): 400991,938878
CPU 5 DPC total execution time (s): 8,284565
CPU 5 DPC count: 2408910
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 17,327045
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): 124,358717
CPU 6 DPC total execution time (s): 7,633610
CPU 6 DPC count: 2452445
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 17,652758
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): 54,388778
CPU 7 DPC total execution time (s): 7,496148
CPU 7 DPC count: 2437450
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,652984
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): 53,396794
CPU 8 DPC total execution time (s): 0,020013
CPU 8 DPC count: 5847
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,615862
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 28,296593
CPU 9 DPC total execution time (s): 0,000163
CPU 9 DPC count: 19
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,460015
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 45,771543
CPU 10 DPC total execution time (s): 0,005062
CPU 10 DPC count: 799
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,545312
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): 62,134269
CPU 11 DPC total execution time (s): 0,000638
CPU 11 DPC count: 65
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 2,305222
CPU 12 ISR highest execution time (µs): 0,811623
CPU 12 ISR total execution time (s): 0,000005
CPU 12 ISR count: 7
CPU 12 DPC highest execution time (µs): 47,935872
CPU 12 DPC total execution time (s): 0,008202
CPU 12 DPC count: 1127
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 2,148792
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 29,058116
CPU 13 DPC total execution time (s): 0,000036
CPU 13 DPC count: 5
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 2,445132
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 51,432866
CPU 14 DPC total execution time (s): 0,002923
CPU 14 DPC count: 385
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2,50650
CPU 15 ISR highest execution time (µs): 0,761523
CPU 15 ISR total execution time (s): 0,000001
CPU 15 ISR count: 1
CPU 15 DPC highest execution time (µs): 58,517034
CPU 15 DPC total execution time (s): 0,001172
CPU 15 DPC count: 122
_________________________________________________________________________________________________________
Blue_screen_of_death
28-10-2019, 13:51
Sempre alte.
Attiva driver verifier e avvia CrystalDiskInfo / CrystalDiskMark. Se hai altre schermate blu, manda il dump.
Sempre alte.
Attiva driver verifier e avvia CrystalDiskInfo / CrystalDiskMark. Se hai altre schermate blu, manda il dump.
provato e niente schermata blu ho fatto due test uno senza latencymon attivo e uno attivo e le latenze sono alte comunque nonostante crystaldiskmark analizzi a velocità bassa l'ssd nvme
Blue_screen_of_death
28-10-2019, 22:12
Bene, quindi è effettivamente causato dal servizio Protezione software, ma come sospettavo non è legato al problema delle latenze alte, che è presente già da diverso tempo :D
Ho guardato il trace che mi hai mandato.
Contiene qualcosa di interessante: la CPU è spesso impegnata in operazioni di gestione del risparmio energetico del sistema (il che può essere un problema, ma non lo è necessariamente, dipende dall'hardware, dai driver, dal sistema, ...).
Questo mi fa pensare a una funzionalità di Windows, il Dynamic Tick, che spegne il timer di sistema per risparmiare energia. Queste operazioni devono essere rapidissime, altrimenti rallentano il sistema e possono causare problemi di latenza.
Siccome tu sei su un desktop e siccome ormai non hai più nulla da perdere (:D), direi che puoi benissimo farne a meno e quindi puoi eseguire questo comando per disabilitarlo.
bcdedit /set disabledynamictick Yes
Riavvia e monitora le latenze.
Ho in mente anche altre idee che mi son venute sempre guardando il trace. Se quel comando non dovesse risolvere, te le propongo.
Bene, quindi è effettivamente causato dal servizio Protezione software, ma come sospettavo non è legato al problema delle latenze alte, che è presente già da diverso tempo :D
Ho guardato il trace che mi hai mandato.
Contiene qualcosa di interessante: la CPU è spesso impegnata in operazioni di gestione del risparmio energetico del sistema (il che può essere un problema, ma non lo è necessariamente, dipende dall'hardware, dai driver, dal sistema, ...).
Questo mi fa pensare a una funzionalità di Windows, il Dynamic Tick, che spegne il timer di sistema per risparmiare energia. Queste operazioni devono essere rapidissime, altrimenti rallentano il sistema e possono causare problemi di latenza.
Siccome tu sei su un desktop e siccome ormai non hai più nulla da perdere (:D), direi che puoi benissimo farne a meno e quindi puoi eseguire questo comando per disabilitarlo.
bcdedit /set disabledynamictick Yes
Riavvia e monitora le latenze.
Ho in mente anche altre idee che mi son venute sempre guardando il trace. Se quel comando non dovesse risolvere, te le propongo.
disabilitato da cmd come amministratore, riavviato e fatto tutto ma niente sempre alte
Blue_screen_of_death
28-10-2019, 23:15
ok,
allora prova con questo comando:
bcdedit /set useplatformclock No
Assicurati che il comando va a buon fine e che non vengono restituiti errori.
Riavvia e vedi che succede.
Se le latenze continuano ad essere alte, entra nel BIOS e disabilita HPET (High Precision Event Timer).
Entrambi i comandi disabilitano il timer hardware, che è un'altro componente che in alcuni sistemi alza i tempi delle DPC.
Il primo comando disabilita via software, il secondo via BIOS.
Dai che questo funziona! :sperem: :D
ok,
allora prova con questo comando:
bcdedit /set useplatformclock No
Assicurati che il comando va a buon fine e che non vengono restituiti errori.
Riavvia e vedi che succede.
Se le latenze continuano ad essere alte, entra nel BIOS e disabilita HPET (High Precision Event Timer).
Entrambi i comandi disabilitano il timer hardware, che è un'altro componente che in alcuni sistemi alza i tempi delle DPC.
Il primo comando disabilita via software, il secondo via BIOS.
Dai che questo funziona! :sperem: :D
Ho provato con i comandi e nulla.. hpet non lo trovò nel bios:muro:
Blue_screen_of_death
29-10-2019, 00:36
Per il BIOS controllo sul manuale e ti faccio sapere.
Comunque la situazione è chiara: Windows 10 da un certa build in poi gestisce male alcune configurazioni hardware/software.
Diversi lamentano questo problema in rete. E credo che il problema è ancora più diffuso di quel che si pensa, ma tanti non se ne accorgono perché non giocano e non fanno uso di applicazioni multimediali.
Sono convinto che installando Windows 7 o Windows 8.1 oppure una build molto vecchia di Windows 10 le latenze sono basse.
Prova a giocare con i settings di Ryzen, togliere overclock, impostare timings manualmente per la RAM.
Ad esempio, guarda questo thread: https://community.amd.com/thread/234496
Qualcuno scrive
i had the same issue . thaiphoon burner and ryzen timings calculator resolved the issue .
Potresti provare e vedere se risolvono il problema.
edit. Anche i settings del BIOS potrebbero aiutare ad abbassare le latenze. Ad esempio, disabilitare tutte le funzionalità di risparmio energetico e funzionalità di overclock / turbo boost.
Ad esempio, vedo che il BIOS ha la funzionalità di EPU Power Saving Mode. Prova a disabilitarla e vedi che succede.
Blue_screen_of_death
29-10-2019, 01:02
Non c'è l'opzione per attivare/disattivare HPET. Purtroppo non è disattivabile su schede ASUS.
Allora come prossimo step, prova a disabilitare EPU Power Saving Mode nel BIOS. Questa voce c'è, ho appena controllato :D
edit. Esegui il comando bcdedit e assicurati che sotto la sezione relativa a Windows 10 compaiono i seguenti settings, che ti ho fatto aggiungere in precedenza.
useplatformclock No
disabledynamictick Yes
edit2. Altra cosa: che utility hai per il setting di RAM e della CPU AMD? Vediamo se c'è la possibilità di spegnere le funzionalità di risparmio energetico e di impostare il profilo High performance.
Non c'è l'opzione per attivare/disattivare HPET. Purtroppo non è disattivabile su schede ASUS.
Allora come prossimo step, prova a disabilitare EPU Power Saving Mode nel BIOS. Questa voce c'è, ho appena controllato :D
edit. Esegui il comando bcdedit e assicurati che sotto la sezione relativa a Windows 10 compaiono i seguenti settings, che ti ho fatto aggiungere in precedenza.
useplatformclock No
disabledynamictick Yes
edit2. Altra cosa: che utility hai per il setting di RAM e della CPU AMD? Vediamo se c'è la possibilità di spegnere le funzionalità di risparmio energetico e di impostare il profilo High performance.
Non trovo nemmeno questo ci sto diventando matto ahahah
Comunque vado su ai tweker nel bios, poi su ai overclok tuner e mi dava lopzione D.O.C.P. E li mi ha impostato i valori della ram a 3200mhz e la cpu a 4.0 ghz. Ho provato anche senza e le latenze ci sono comunque.
Per programmi sono andato nelle case produttrici e li mi fanno scaricare and ryzenmaster mi pare si chiami e ezutily per asus
Blue_screen_of_death
29-10-2019, 10:40
Secondo il manuale EPU Power Saving Mode è nella sezione AI Tweaker del BIOS.
Se non è presente, probabilmente non è supportato dalla CPU.
Possiamo provare a giocare anche con Ryzen Master e EZ Utility, sempre nell'ottica di disabilitare tutto ciò che riguarda il risparmio energetico.
Secondo il manuale EPU Power Saving Mode è nella sezione AI Tweaker del BIOS.
Se non è presente, probabilmente non è supportato dalla CPU.
Possiamo provare a giocare anche con Ryzen Master e EZ Utility, sempre nell'ottica di disabilitare tutto ciò che riguarda il risparmio energetico.
ora ho disabilitato tutto dal bios ho messo tutto auto. comunque qui settaggi che mi hai detto sono come hai scritto te. il primo No e il secondo Yes
si ci ho guardato ma non lo trovo
Blue_screen_of_death
29-10-2019, 10:53
Controlliamo se il timer è ok.
http://www.mediafire.com/file/xzo9n84d8lze9nb/WinTimerTester_1.1.zip/file
Avvialo, clicca su start, fallo girare 5 minuti
Poi clicca su stop.
Mandami lo screenshot o comunque fai copia-incolla dei valori, come ti viene più comodo.
Controlliamo se il timer è ok.
http://www.mediafire.com/file/xzo9n84d8lze9nb/WinTimerTester_1.1.zip/file
Avvialo, clicca su start, fallo girare 5 minuti
Poi clicca su stop.
Mandami lo screenshot o comunque fai copia-incolla dei valori, come ti viene più comodo.
il programma di asus si chiama al suit 3 e li vedo epu ma non riesco a capire se è attivo o no. comunque questo è quello che mi viene:
https://ibb.co/THp5WgC
Blue_screen_of_death
29-10-2019, 11:22
Ecco, hai 3 profili: Performance, Power Saving e Away Mode.
Attiva il profilo Performance.
Ecco, hai 3 profili: Performance, Power Saving e Away Mode.
Attiva il profilo Performance.
attivato, comunque poi ho provato a fare tuning con quel programma e ha iniziato a stressare il processore ha raggiunto più di 90 gradi e si è riavviato il pc con errore della temperatura sul bios.
e le latenze sono sempre alte
vBulletin® v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.