Piccoli freeze durante uso del pc

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

Originariamente inviato da serpinu

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

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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?

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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

[Blue_screen_of_death]

Originariamente inviato da serpinu

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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
_________________________________________________________________________________________________________

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

Originariamente inviato da serpinu

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]

Originariamente inviato da serpinu

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, ...

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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

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)

[serpinu]

Originariamente inviato da Blue_screen_of_death

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

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]

Originariamente inviato da serpinu

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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
_________________________________________________________________________________________________________