Piccoli freeze durante uso del pc

[Blue_screen_of_death]

Forse è impostato per creare un dump completo della memoria, ovvero il file C:\Windows\MEMORY.DMP

[serpinu]

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]

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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

[serpinu]

allora il dmp lo ha fatto ti linko tutto è di 800 mega il file.

https://www.dropbox.com/s/4uo8p353o7...EMORY.DMP?dl=0

[Blue_screen_of_death]

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.

[serpinu]

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]

Marca / modello dei joystick?

[serpinu]

_________________________________________________________________________________________________________
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

[serpinu]

Originariamente inviato da Blue_screen_of_death

Marca / modello dei joystick?

dualshock 4 quello normale della ps4

[Blue_screen_of_death]

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.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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]

Originariamente inviato da serpinu

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

[serpinu]

Originariamente inviato da Blue_screen_of_death

Si esatto

ok provato e niente mi da sempre quell'errore, quindi rimane qualcosa dentro? ti rimando il dmp?

[Blue_screen_of_death]

ok, manda

[Blue_screen_of_death]

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
Quindi vorrei capire cosa ha installato quel driver ScpVBus, che di default in Windows non è presente.

Questo spiega le mie domande.

[serpinu]

Originariamente inviato da Blue_screen_of_death

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

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]

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/

[serpinu]

Originariamente inviato da Blue_screen_of_death

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/t925dkejwe...EMORY.DMP?dl=0

[Blue_screen_of_death]

Sto scaricando il dump.

C'è una periferica Scp Virtual Bus Driver in gestione dispositivi?