je viens vers vous pour une question/curiosité.
nouveau possesseur d'un legion y540, j'ai commencé à remarqué depuis peu la présence du processus interruption système dans mon gestionnaire des tache et utilisant le cpu dans des proportions anormalement élevé (au alentour de 30/40% avant de chuter très vite dés l'ouverture du gestionnaire)
J'ai alors commencé à écumer l'internet à la recherche de solution, je les ait toute appliquée patiemment:
vérification et mise à jour des pilotes
réparation dism et sfc
tcheck du ssd
mise à jour du bios
point de restauration windows
et pour finir j'ai décidé de réinitialiser totalement windows... mais ça n'a rien changé, j'observe toujours ce processus de temps à autre, et il apparait souvent lors d'une sollicitation soudaine du cpu (ouverture d'un programme, lecture d'une vidéo, téléchargement etc...)
donc voilà, même si au final ça n'est qu'un problème bénin, mon pc reste tout à fait utilisable, je reste un peu chagriné (et aussi curieux) de ne pas avoir l'origine de ce "problème".
à mon avis cela doit provenir d'un soucis de pilote car c'est bien là que j'ai pu louper des pistes
auriez vous éventuellement une sugestion à me proposer ?
Edit: j'oubliais une question, en épluchant le gestionnaire des taches, j'ai remarqué le processus Intel(r) Rapid Storage Technologie management service. Or, mon système est en AHCI, pas en RST, du coup se pourrait-ce que ce soit ce processus qui est en cause ?
ci dessous mon rapport Latencymon :
Code : Tout sélectionner
_________________________________________________________________________________________________________
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. Also one or more ISR 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:16:32 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-IEAKD6L
OS version: Windows 10, 10.0, version 2009, build: 19042 (x64)
Hardware: 81SX, LENOVO
CPU: GenuineIntel Intel(R) Core(TM) i5-9300HF CPU @ 2.40GHz
Logical processors: 8
Processor groups: 1
RAM: 16304 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 240 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.
_________________________________________________________________________________________________________
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): 1054,10
Average measured interrupt to process latency (µs): 10,088266
Highest measured interrupt to DPC latency (µs): 996,50
Average measured interrupt to DPC latency (µs): 3,855239
_________________________________________________________________________________________________________
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): 2485,619167
Driver with highest ISR routine execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Highest reported total ISR routine time (%): 0,005989
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Total time spent in ISRs (%) 0,006077
ISR count (execution time <250 µs): 37620
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 42
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 1
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): 341499,071667
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0,048859
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 461.72 , NVIDIA Corporation
Total time spent in DPCs (%) 0,181073
DPC count (execution time <250 µs): 729377
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 282
DPC count (execution time 1000-2000 µs): 5
DPC count (execution time 2000-4000 µs): 1
DPC count (execution time >=4000 µs): 8
_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: svchost.exe
Total number of hard pagefaults 4821
Hard pagefault count of hardest hit process: 2190
Number of processes hit: 25
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 35,216031
CPU 0 ISR highest execution time (µs): 2485,619167
CPU 0 ISR total execution time (s): 0,438887
CPU 0 ISR count: 34276
CPU 0 DPC highest execution time (µs): 2641,306667
CPU 0 DPC total execution time (s): 10,472835
CPU 0 DPC count: 597776
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 6,036848
CPU 1 ISR highest execution time (µs): 826,610
CPU 1 ISR total execution time (s): 0,043802
CPU 1 ISR count: 3387
CPU 1 DPC highest execution time (µs): 883,040833
CPU 1 DPC total execution time (s): 0,249703
CPU 1 DPC count: 12957
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6,927318
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): 341499,071667
CPU 2 DPC total execution time (s): 1,080332
CPU 2 DPC count: 47127
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4,957602
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): 341496,980833
CPU 3 DPC total execution time (s): 0,638814
CPU 3 DPC count: 2716
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 6,548057
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): 341494,790
CPU 4 DPC total execution time (s): 0,953384
CPU 4 DPC count: 31423
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 4,919224
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): 666,73750
CPU 5 DPC total execution time (s): 0,056276
CPU 5 DPC count: 6409
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 5,761121
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): 720,220
CPU 6 DPC total execution time (s): 0,227813
CPU 6 DPC count: 22149
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 5,439824
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): 341483,314167
CPU 7 DPC total execution time (s): 0,703735
CPU 7 DPC count: 9116
_________________________________________________________________________________________________________