|
Piccoli freeze durante uso del pc
Buonasera,
scrivo qui ma non so è la sezione giusta. Ho un problema con il mio pc: AMD ryzen 5 1600 RX 580 8gb Gygabyte ax370 k3 gaming. Praticamente ogni tanto mi vengono dei mini freeze di anche un secondo o meno in cui si blocca l'audio e video e poi riparte (suono tipo gracchiante). anche quando navigo normalmente o guardo video. Cosa può essere? ho 3 hard disk sata collegati e il principale ssd. Ho notato che quando aprivo CrystalDiskInfo me lo faceva quindi ho pensato fosse un problema di qualche disco è possibile? grazie mille |
Una routine DPC o ISR lenta. Dobbiamo capire a quale driver o periferica appartiene.
Scarica LatencyMon Clicca su Start Monitor per avviare il monitoraggio dei driver Attendi che si verifica un freeze (se riesci puoi anche replicare le operazioni che lo causano) Clicca su Stop Edit -> Copy report text to clipboard Incolla il report in un messaggio di risposta |
allora ho provato per un'oretta ma non mi ha fatto niente comunque copio lo stesso.
_________________________________________________________________________________________________________ CONCLUSION _________________________________________________________________________________________________________ Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. LatencyMon has been analyzing your system for 1:20:38 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: DESKTOP-5GGJV4O OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64) Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd. CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor Logical processors: 12 Processor groups: 1 RAM: 24524 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 320 MHz Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. _________________________________________________________________________________________________________ MEASURED INTERRUPT TO USER PROCESS LATENCIES _________________________________________________________________________________________________________ The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event. Highest measured interrupt to process latency (µs): 100776,30 Average measured interrupt to process latency (µs): 7,814270 Highest measured interrupt to DPC latency (µs): 100763,40 Average measured interrupt to DPC latency (µs): 4,299982 _________________________________________________________________________________________________________ REPORTED ISRs _________________________________________________________________________________________________________ Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal. Highest ISR routine execution time (µs): 306,080 Driver with highest ISR routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation Highest reported total ISR routine time (%): 0,008869 Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation Total time spent in ISRs (%) 0,014508 ISR count (execution time <250 µs): 4344987 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-999 µs): 2 ISR count (execution time 1000-1999 µs): 0 ISR count (execution time 2000-3999 µs): 0 ISR count (execution time >=4000 µs): 0 _________________________________________________________________________________________________________ REPORTED DPCs _________________________________________________________________________________________________________ DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution. Highest DPC routine execution time (µs): 1052,250 Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation Highest reported total DPC routine time (%): 0,017558 Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in DPCs (%) 0,054327 DPC count (execution time <250 µs): 10743975 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 1506 DPC count (execution time 1000-1999 µs): 1 DPC count (execution time 2000-3999 µs): 0 DPC count (execution time >=4000 µs): 0 _________________________________________________________________________________________________________ REPORTED HARD PAGEFAULTS _________________________________________________________________________________________________________ Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution. NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit. Process with highest pagefault count: gamebar.exe Total number of hard pagefaults 7015 Hard pagefault count of hardest hit process: 3683 Number of processes hit: 34 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 164,136135 CPU 0 ISR highest execution time (µs): 306,080 CPU 0 ISR total execution time (s): 8,391763 CPU 0 ISR count: 4330295 CPU 0 DPC highest execution time (µs): 1052,250 CPU 0 DPC total execution time (s): 28,923236 CPU 0 DPC count: 10373649 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 65,461988 CPU 1 ISR highest execution time (µs): 16,940 CPU 1 ISR total execution time (s): 0,025582 CPU 1 ISR count: 10092 CPU 1 DPC highest execution time (µs): 303,750 CPU 1 DPC total execution time (s): 0,052265 CPU 1 DPC count: 8062 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 35,833792 CPU 2 ISR highest execution time (µs): 0,0 CPU 2 ISR total execution time (s): 0,0 CPU 2 ISR count: 0 CPU 2 DPC highest execution time (µs): 242,990 CPU 2 DPC total execution time (s): 0,176115 CPU 2 DPC count: 33804 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 33,175892 CPU 3 ISR highest execution time (µs): 0,0 CPU 3 ISR total execution time (s): 0,0 CPU 3 ISR count: 0 CPU 3 DPC highest execution time (µs): 297,030 CPU 3 DPC total execution time (s): 0,031001 CPU 3 DPC count: 7054 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 31,033964 CPU 4 ISR highest execution time (µs): 0,0 CPU 4 ISR total execution time (s): 0,0 CPU 4 ISR count: 0 CPU 4 DPC highest execution time (µs): 218,450 CPU 4 DPC total execution time (s): 0,085970 CPU 4 DPC count: 15950 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 30,910317 CPU 5 ISR highest execution time (µs): 0,0 CPU 5 ISR total execution time (s): 0,0 CPU 5 ISR count: 0 CPU 5 DPC highest execution time (µs): 187,30 CPU 5 DPC total execution time (s): 0,027941 CPU 5 DPC count: 6162 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 35,233412 CPU 6 ISR highest execution time (µs): 0,0 CPU 6 ISR total execution time (s): 0,0 CPU 6 ISR count: 0 CPU 6 DPC highest execution time (µs): 403,840 CPU 6 DPC total execution time (s): 0,839686 CPU 6 DPC count: 119593 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 31,094520 CPU 7 ISR highest execution time (µs): 0,0 CPU 7 ISR total execution time (s): 0,0 CPU 7 ISR count: 0 CPU 7 DPC highest execution time (µs): 225,210 CPU 7 DPC total execution time (s): 0,028786 CPU 7 DPC count: 5108 _________________________________________________________________________________________________________ CPU 8 Interrupt cycle time (s): 37,574432 CPU 8 ISR highest execution time (µs): 0,0 CPU 8 ISR total execution time (s): 0,0 CPU 8 ISR count: 0 CPU 8 DPC highest execution time (µs): 305,090 CPU 8 DPC total execution time (s): 0,730383 CPU 8 DPC count: 104402 _________________________________________________________________________________________________________ CPU 9 Interrupt cycle time (s): 33,839061 CPU 9 ISR highest execution time (µs): 0,0 CPU 9 ISR total execution time (s): 0,0 CPU 9 ISR count: 0 CPU 9 DPC highest execution time (µs): 172,450 CPU 9 DPC total execution time (s): 0,020843 CPU 9 DPC count: 3415 _________________________________________________________________________________________________________ CPU 10 Interrupt cycle time (s): 36,158694 CPU 10 ISR highest execution time (µs): 0,0 CPU 10 ISR total execution time (s): 0,0 CPU 10 ISR count: 0 CPU 10 DPC highest execution time (µs): 260,960 CPU 10 DPC total execution time (s): 0,470784 CPU 10 DPC count: 50361 _________________________________________________________________________________________________________ CPU 11 Interrupt cycle time (s): 36,962506 CPU 11 ISR highest execution time (µs): 7,140 CPU 11 ISR total execution time (s): 0,005175 CPU 11 ISR count: 4602 CPU 11 DPC highest execution time (µs): 396,570 CPU 11 DPC total execution time (s): 0,153389 CPU 11 DPC count: 17922 _________________________________________________________________________________________________________ |
Assicurati che nel BIOS è attivato High Precision Event Timer
Nel report si legge Reported CPU speed: 320 MHz, che potrebbe indicare che qualcosa sta limitando la velocità del processore oppure è un errore di misurazione del software. Nelle impostazioni avanzate risparmio energia di Windows assicurati che il Livello massimo prestazioni del processore è impostato al 100% Inoltre scarica CPU-Z e verifica che il processore sta lavorando alla sua frequenza. Aggiorna driver di rete all'ultima versione disponibile sul sito del produttore. Se i problemi persistono, avvia il monitoraggio con LatencyMon, lascialo girare finché si verificano i freeze e manda il nuovo report. Mi aspetto che negli istanti dei freeze audio / video c'è qualcosa che schizza in alto, e non sono sicuro che nel report che hai postato sia stata catturata. Per questo dovresti cercare di catturare i freeze prima di mandare il report. |
Quote:
https://vimeo.com/user103598545/revi...006/f8e5268503 |
Non riesco ad aprire il link
"Sorry, we couldn’t find that page" |
OK, trovato il video.
Quella schermata dice ben poco. I dettagli dell'errore vengono scritti in file con estensione .dmp, salvati per default nella cartella C:\Windows\Minidump Analizzando il contenuto di quei file possiamo capire la causa del problema. Carica tutti i file che trovi in quella cartella su un sito di hosting o su un sistema di cloud storage (Google Drive, Dropbox, ...) e manda il link. |
Quote:
https://www.dropbox.com/s/mw6y6kmmz9...53-01.dmp?dl=0 |
Si riesco a scaricare
Ne hai solo uno? Se ne hai anche altri manda tutta la cartella. |
no solo uno
|
OK, allora il sistema è configurato per eliminare i vecchi dump.
Prosegui comunque con quello che ti avevo scritto, in particolare questo: Quote:
:) |
Quote:
|
Ho analizzato il dump.
Il problema è stato causato dalla corruzione in una page table. Le page table mappano lo spazio di indirizzamento virtuale nello spazio di indirizzamento fisico. In parole più semplici, contengono informazioni che servono ai processi per leggere o scrivere in RAM. Si dovrebbe vedere a quale processo appartiene la memoria corrotta, e da questo si potrebbe risalire al nome del driver che la corrompe. Ma purtroppo questo non riesco a farlo perché il dump non contiene queste informazioni. Dovremmo configurare Windows per creare dump più grandi che includono anche queste informazioni e attendere il prossimo crash. Ma per evitare di perdere altro tempo, aggiungiamo altre due cose alla lista di cose da fare :) - Nelle impostazioni avanzate risparmio energia di Windows assicurati che il Livello massimo prestazioni del processore è impostato al 100% - Scarica CPU-Z e verifica che il processore sta lavorando alla sua frequenza. - Testa la RAM con MemTest86+ - Testa i driver con driver verifier, come descritto di seguito - Lascia avviato LatencyMon in background e al primo mini-freeze, manda il report Procedura per testare i driver Apri verifier (strumento incluso in Windows), seleziona Crea impostazioni standard Seleziona automaticamente tutti i driver installati in questo computer Fine Ora riavvia. Al riavvio, Windows fa tiene sotto controllo tutti i driver, quindi potrebbe essere più lento del solito. Attendi il prossimo crash, manda una foto e manda il minidump. Questa volta dovrebbe contenere informazioni più dettagliate incluso il nome del driver incriminato. Se non riesci più ad avviare Windows a causa dei crash (perché magari si verificano in fase di avvio), avvia Windows in modalità provvisoria e disattiva Driver Verifier scegliendo Elimina impostazioni esistenti. |
Quote:
poi il processore è al 100% la ram la ritesterò ma già lo feci a uno degli ultimi crash con lo stesso errore e non venne fuori nessun problema. per verificare i driver ed evitare che mi crashi devo fare qualcos'altro? grazie mille per l'aiuto sei gentilissimo :) |
Quote:
Se sì, manda il file che do un'occhiata Se no, allora fai una foto alla schermata blu e manda, e speriamo che c'è l'informazione che ci serve |
Quote:
|
Quote:
|
Quote:
|
OK
Con driver verifier abiliti la verifica soltanto su un sottoinsieme di driver. Ovvero li testi a gruppi, finché non individui il driver che impedisce l'avvio. Ad esempio potresti partire testando i driver non Microosft, poi abiliti il test solo sui driver con lettera iniziale compresa tra A e E, poi F e L, ... Quando individui il gruppo di driver che impedisce l'avvio, selezioni un sottoinsieme di quel gruppo e così via, fino a rimanere con un solo driver. A quel punto provi ad aggiornarlo, e ti accerti che l'aggiornamento ha risolto il problema all'avvio con verifier attivato. So che richiede un po' di tempo. :) In alternativa, potresti provare ad aggiornare tutti i driver - Audio - Video - Scheda di rete wireless - Scheda di rete Ethernet - Chipset - Controller USB Ma così stiamo andando a tentativi e non è detto che riesci a individuare e risolvere il problema. Scegli tu come procedere. |
Quote:
|
Forse è impostato per creare un dump completo della memoria, ovvero il file C:\Windows\MEMORY.DMP
|
c'era ho riavviato il pc e ora non c'è più forse la pulizia?
poi in un altro HD ho 3 file DUMP26c1, DUMP2625, DUMP2626 e tutti pesano sui 25 gb con estensione .tmp |
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. |
Quote:
|
allora il dmp lo ha fatto ti linko tutto è di 800 mega il file.
https://www.dropbox.com/s/4uo8p353o7...EMORY.DMP?dl=0 |
Beccato :)
Il driver che impedisce l'avvio (e che probabilmente è anche causa dei freeze) è ScpVBus, ovvero Virtual USB Bus. E' un driver usato da joystick, controller PS4, Xbox, o cose simili. (Hai uno di questi dispositivi?) La versione del driver installata risale al 2013, due anni prima del rilascio di Windows 10. Quindi potrebbe essere incompatibile con Windows 10. Dovresti aggiornare quel driver. |
si uso i joystick per giocare ogni tanto come faccio ad aggiornare?
usavo il programma ds4 perchè ogni tanto alcuni giochi il joystick non lo leggeva, e questo emula il driver del controller di xbox 360 potrebbe essere? |
Marca / modello dei joystick?
|
_________________________________________________________________________________________________________
CONCLUSION _________________________________________________________________________________________________________ Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. LatencyMon has been analyzing your system for 0:00:19 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: DESKTOP-5GGJV4O OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64) Hardware: AX370-Gaming K3, Gigabyte Technology Co., Ltd. CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor Logical processors: 12 Processor groups: 1 RAM: 24524 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 320 MHz Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results. WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature. _________________________________________________________________________________________________________ MEASURED INTERRUPT TO USER PROCESS LATENCIES _________________________________________________________________________________________________________ The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event. Highest measured interrupt to process latency (µs): 3436,20 Average measured interrupt to process latency (µs): 8,553457 Highest measured interrupt to DPC latency (µs): 3431,20 Average measured interrupt to DPC latency (µs): 4,965094 _________________________________________________________________________________________________________ REPORTED ISRs _________________________________________________________________________________________________________ Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal. Highest ISR routine execution time (µs): 46,380 Driver with highest ISR routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation Highest reported total ISR routine time (%): 0,095639 Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation Total time spent in ISRs (%) 0,104814 ISR count (execution time <250 µs): 151398 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-999 µs): 0 ISR count (execution time 1000-1999 µs): 0 ISR count (execution time 2000-3999 µs): 0 ISR count (execution time >=4000 µs): 0 _________________________________________________________________________________________________________ REPORTED DPCs _________________________________________________________________________________________________________ DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution. Highest DPC routine execution time (µs): 100868,490 Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation Highest reported total DPC routine time (%): 0,062182 Driver with highest DPC total execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation Total time spent in DPCs (%) 0,240834 DPC count (execution time <250 µs): 136264 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 58 DPC count (execution time 1000-1999 µs): 0 DPC count (execution time 2000-3999 µs): 0 DPC count (execution time >=4000 µs): 0 _________________________________________________________________________________________________________ REPORTED HARD PAGEFAULTS _________________________________________________________________________________________________________ Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution. NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit. Process with highest pagefault count: tiworker.exe Total number of hard pagefaults 566 Hard pagefault count of hardest hit process: 297 Number of processes hit: 15 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 0,982381 CPU 0 ISR highest execution time (µs): 46,380 CPU 0 ISR total execution time (s): 0,237280 CPU 0 ISR count: 149793 CPU 0 DPC highest execution time (µs): 654,210 CPU 0 DPC total execution time (s): 0,380497 CPU 0 DPC count: 120062 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 0,259422 CPU 1 ISR highest execution time (µs): 9,540 CPU 1 ISR total execution time (s): 0,000758 CPU 1 ISR count: 321 CPU 1 DPC highest execution time (µs): 87,910 CPU 1 DPC total execution time (s): 0,013835 CPU 1 DPC count: 882 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 0,251673 CPU 2 ISR highest execution time (µs): 0,0 CPU 2 ISR total execution time (s): 0,0 CPU 2 ISR count: 0 CPU 2 DPC highest execution time (µs): 625,090 CPU 2 DPC total execution time (s): 0,024260 CPU 2 DPC count: 10413 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 0,130216 CPU 3 ISR highest execution time (µs): 0,0 CPU 3 ISR total execution time (s): 0,0 CPU 3 ISR count: 0 CPU 3 DPC highest execution time (µs): 20,110 CPU 3 DPC total execution time (s): 0,000158 CPU 3 DPC count: 52 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 0,154943 CPU 4 ISR highest execution time (µs): 0,0 CPU 4 ISR total execution time (s): 0,0 CPU 4 ISR count: 0 CPU 4 DPC highest execution time (µs): 24,040 CPU 4 DPC total execution time (s): 0,001178 CPU 4 DPC count: 225 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 0,120851 CPU 5 ISR highest execution time (µs): 0,0 CPU 5 ISR total execution time (s): 0,0 CPU 5 ISR count: 0 CPU 5 DPC highest execution time (µs): 165,690 CPU 5 DPC total execution time (s): 0,001274 CPU 5 DPC count: 238 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 0,195983 CPU 6 ISR highest execution time (µs): 0,0 CPU 6 ISR total execution time (s): 0,0 CPU 6 ISR count: 0 CPU 6 DPC highest execution time (µs): 83,540 CPU 6 DPC total execution time (s): 0,004517 CPU 6 DPC count: 646 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 0,158261 CPU 7 ISR highest execution time (µs): 0,0 CPU 7 ISR total execution time (s): 0,0 CPU 7 ISR count: 0 CPU 7 DPC highest execution time (µs): 19,160 CPU 7 DPC total execution time (s): 0,000198 CPU 7 DPC count: 55 _________________________________________________________________________________________________________ CPU 8 Interrupt cycle time (s): 0,550784 CPU 8 ISR highest execution time (µs): 6,360 CPU 8 ISR total execution time (s): 0,000896 CPU 8 ISR count: 1074 CPU 8 DPC highest execution time (µs): 100868,490 CPU 8 DPC total execution time (s): 0,116971 CPU 8 DPC count: 2763 _________________________________________________________________________________________________________ CPU 9 Interrupt cycle time (s): 0,180135 CPU 9 ISR highest execution time (µs): 1,30 CPU 9 ISR total execution time (s): 0,000013 CPU 9 ISR count: 13 CPU 9 DPC highest execution time (µs): 113,450 CPU 9 DPC total execution time (s): 0,000404 CPU 9 DPC count: 53 _________________________________________________________________________________________________________ CPU 10 Interrupt cycle time (s): 0,196084 CPU 10 ISR highest execution time (µs): 1,770 CPU 10 ISR total execution time (s): 0,000058 CPU 10 ISR count: 57 CPU 10 DPC highest execution time (µs): 86,690 CPU 10 DPC total execution time (s): 0,005298 CPU 10 DPC count: 794 _________________________________________________________________________________________________________ CPU 11 Interrupt cycle time (s): 0,171310 CPU 11 ISR highest execution time (µs): 5,780 CPU 11 ISR total execution time (s): 0,000159 CPU 11 ISR count: 140 CPU 11 DPC highest execution time (µs): 76,720 CPU 11 DPC total execution time (s): 0,000944 CPU 11 DPC count: 140 _________________________________________________________________________________________________________ ti mando anche il tab con un piccolo freeze |
Quote:
|
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. |
Quote:
|
Quote:
|
Quote:
|
ok, manda
|
Hai installato qualcosa per far funzionare il joystick? Ad esempio un software di gestione.
Qui sto lavorando di immaginazione. Non avendone mai visto uno, non so quali step hai fatto per installarlo e cosa si porta dietro l'installazione del joystick :D Quindi vorrei capire cosa ha installato quel driver ScpVBus, che di default in Windows non è presente. Questo spiega le mie domande. |
Quote:
|
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/ |
Quote:
https://www.dropbox.com/s/t925dkejwe...EMORY.DMP?dl=0 |
Sto scaricando il dump.
C'è una periferica Scp Virtual Bus Driver in gestione dispositivi? |
| Tutti gli orari sono GMT +1. Ora sono le: 03:01. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Hardware Upgrade S.r.l.