Piccoli freeze durante uso del pc

[Blue_screen_of_death]

Quindi non riesci ad usare tutte le periferiche USB? O solo una pen drive?

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

Disinstalla i driver del controller USB e riavvia.
Lasciagli installare i driver che vuole lui e vedi se il problema scompare.

[serpinu]

provato ma niente ti faccio vedere cosa vedo io

https://ibb.co/CJbRSdh

[Blue_screen_of_death]

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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?

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

Ok

[serpinu]

Originariamente inviato da Blue_screen_of_death

Ok

allora ora come ora c'è stato veramente un millesimo di secondo il freeze ma ovviamente non avevo abilitato latency

[Blue_screen_of_death]

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?

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

Si confermo, è il driver che gestisce lo storage che causa i freeze.

Il disco ha 228 settori riallocati, dovresti sostituirlo

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

Mandami lo screen di CrystalDiskInfo degli altri installati
Allarga la finestra in modo da includere tutte le voci nello screen

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

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.