DPC Latency causée par "Wdf01000.sys - Runtime de l'infrastructure de pilotes en mode noyau"

  • Thread starter Thread starter CasperCayrol
  • Start date Start date
C

CasperCayrol

Guest
Bonjour,


Depuis quelques temps, après la mise à jour du pilote de ma carte son externe (Focusrite Scarlett 2i2 1st gen), quelque chose s'est altéré dans mon ordinateur. De temps en temps, j'ai la sensation que le pilote audio perd contrôle et le son que j'ai est complètement déchiqueté, saccadé jusqu'à ce que je désactive puis réactive le périphérique dans le menu "Périphériques de Lecture". En plus de cela, j'éprouve des micro-coupures parfois intempestives qui peuvent gêner dans mes tâches lié à la MAO. Autre chose qui a peut-être un rapport avec tout ça : mon entrée sur Discord est également saccadé, aussi bien sur sous-moteur Legacy que le normal.


J'ai contacté le support de Focusrite, qui m'ont proposé de diagnostiquer le problème et en trouver l'origine. Avec le logiciel LatencyMon, j'ai pu chercher ce qui posait problème : voici le rapport de LatencyMon.


_________________________________________________________________________________________________________

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:19:27 (h:mm:ss) on all processors.





_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: DESKTOP-E0QCLJR

OS version: Windows 10 , 10.0, version 1607, build: 14393 (x64)

Hardware: Inspiron 7559, Dell Inc., 0H0CC0

CPU: GenuineIntel Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz

Logical processors: 8

Processor groups: 1

RAM: 16250 MB total





_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 2592 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): 5445,539469

Average measured interrupt to process latency (µs): 10,013894



Highest measured interrupt to DPC latency (µs): 5436,453035

Average measured interrupt to DPC latency (µs): 2,723618





_________________________________________________________________________________________________________

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): 133,333333

Driver with highest ISR routine execution time: ACPI.sys - Pilote ACPI pour NT, Microsoft Corporation



Highest reported total ISR routine time (%): 0,003716

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



ISR count (execution time <250 µs): 112133

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): 4488,407407

Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation



Highest reported total DPC routine time (%): 0,135644

Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation



Total time spent in DPCs (%) 0,229057



DPC count (execution time <250 µs): 2997806

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-999 µs): 10718

DPC count (execution time 1000-1999 µs): 1

DPC count (execution time 2000-3999 µs): 5

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: mcshield.exe



Total number of hard pagefaults 2569

Hard pagefault count of hardest hit process: 768

Number of processes hit: 27





_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 74,365573

CPU 0 ISR highest execution time (µs): 133,333333

CPU 0 ISR total execution time (s): 0,409595

CPU 0 ISR count: 98134

CPU 0 DPC highest execution time (µs): 4488,407407

CPU 0 DPC total execution time (s): 19,511431

CPU 0 DPC count: 2853985

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 41,248410

CPU 1 ISR highest execution time (µs): 58,086420

CPU 1 ISR total execution time (s): 0,006597

CPU 1 ISR count: 3353

CPU 1 DPC highest execution time (µs): 438,047840

CPU 1 DPC total execution time (s): 0,084439

CPU 1 DPC count: 6404

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 33,137613

CPU 2 ISR highest execution time (µs): 52,355710

CPU 2 ISR total execution time (s): 0,002987

CPU 2 ISR count: 1523

CPU 2 DPC highest execution time (µs): 452,385802

CPU 2 DPC total execution time (s): 0,419886

CPU 2 DPC count: 32462

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 44,906768

CPU 3 ISR highest execution time (µs): 67,399691

CPU 3 ISR total execution time (s): 0,011595

CPU 3 ISR count: 5822

CPU 3 DPC highest execution time (µs): 380,644290

CPU 3 DPC total execution time (s): 0,136560

CPU 3 DPC count: 14526

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 30,843579

CPU 4 ISR highest execution time (µs): 40,368827

CPU 4 ISR total execution time (s): 0,001766

CPU 4 ISR count: 980

CPU 4 DPC highest execution time (µs): 899,804784

CPU 4 DPC total execution time (s): 0,475965

CPU 4 DPC count: 37667

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 42,982659

CPU 5 ISR highest execution time (µs): 60,824074

CPU 5 ISR total execution time (s): 0,001916

CPU 5 ISR count: 846

CPU 5 DPC highest execution time (µs): 268,922840

CPU 5 DPC total execution time (s): 0,026462

CPU 5 DPC count: 4822

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 33,07470

CPU 6 ISR highest execution time (µs): 43,781636

CPU 6 ISR total execution time (s): 0,001392

CPU 6 ISR count: 806

CPU 6 DPC highest execution time (µs): 540,479938

CPU 6 DPC total execution time (s): 0,674065

CPU 6 DPC count: 52295

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 44,539671

CPU 7 ISR highest execution time (µs): 55,320988

CPU 7 ISR total execution time (s): 0,001313

CPU 7 ISR count: 669

CPU 7 DPC highest execution time (µs): 460,626543

CPU 7 DPC total execution time (s): 0,056293

CPU 7 DPC count: 6371

_________________________________________________________________________________________________________


Je peux voir que ce "Wdf01000.sys - Runtime de l'infrastructure de pilotes en mode noyau" semble poser problème. Je n'ai aucune idée de ce que c'est et de comment je pourrai résoudre ces micro-coupures.


Merci d'avance pour votre réponse !

Continue reading...
 

Similar threads

Y
Replies
0
Views
8
YamanashiMoondragon
Y
Y
Replies
0
Views
23
YamanashiMoondragon
Y
N
Replies
0
Views
10
NicolasHaquin
N
S
Replies
0
Views
11
SoulEater5674
S
Back
Top