Freeze aléatoire Windows 10

[Pico51]

Bonjour,

Au sein de mon entreprise, nous venons tout juste de migrer certains postes sur de nouvelles machines Dell Optiplex 5060 avec Windows 10 Pro 64 bits (version 1809, OS build 17763.316) avec 16 Go de RAM et nous souffrons depuis de freezes aléatoires. Cela est très variable puisque certains d'entre nous n'avons jamais connu de plantage alors que d'autres en rencontrent plusieurs par semaine (deux ou trois).

Sur une machine posant assez souvent problème, j'ai procédé à une mise à jour des pilotes et du BIOS mais cela n'a strictement rien changé.

Ces plantages n'ont pas l'air d'être dû à une application en particulier mais se présentent toujours de la même manière : quelques secondes avant le blocage total de l'ordinateur, les mouvements du curseur de la souris deviennent saccadés et le curseur, parfois, se met à grossir.

Que puis-je mettre en place pour identifier la source de ce problème ?

Merci.

[Malekal_morte]

Salut,

En général, c'est un pilote ou BIOS.

Faudrait faire une mise à jour des pilotes.
Tester en désactivant des périphériques un à un dans le gestionnaire de périphériques
Un test de Latencymon pendant quelques minutes, voir ce qu'il ressort.
Mettre à jour le BIOS.

[Pico51]

Bonjour,

Le BIOS et les pilotes sont déjà à jour.
Je suis passé en performances maximales mais j'ai encore connu un freeze aujourd'hui.
Je viens de refaire un test avec Latencymon, voici le rapport :

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. 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  2:18:09  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        UC109
OS version:                                           Windows 10 , 10.0, build: 17763 (x64)
Hardware:                                             OptiPlex 5060, Dell Inc., 0J8G6F
CPU:                                                  GenuineIntel Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
Logical processors:                                   6
Processor groups:                                     1
RAM:                                                  16180 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed:                                   30 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):   4620,60
Average measured interrupt to process latency (µs):   3,873098

Highest measured interrupt to DPC latency (µs):       4585,10
Average measured interrupt to DPC latency (µs):       1,179765


_________________________________________________________________________________________________________
 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):              2904,984667
Driver with highest ISR routine execution time:       HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%):          0,012161
Driver with highest ISR total time:                   HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%)                          0,012404

ISR count (execution time <250 µs):                   290897
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-999 µs):                2
ISR count (execution time 1000-1999 µs):              13
ISR count (execution time 2000-3999 µs):              5
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):              1710,7290
Driver with highest DPC routine execution time:       ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

Highest reported total DPC routine time (%):          0,043223
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,088666

DPC count (execution time <250 µs):                   15344946
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                21
DPC count (execution time 1000-1999 µs):              2
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:                 thunderbird.exe

Total number of hard pagefaults                       19961
Hard pagefault count of hardest hit process:          7339
Number of processes hit:                              68


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       339,890349
CPU 0 ISR highest execution time (µs):                2904,984667
CPU 0 ISR total execution time (s):                   6,133249
CPU 0 ISR count:                                      279169
CPU 0 DPC highest execution time (µs):                1710,7290
CPU 0 DPC total execution time (s):                   41,998633
CPU 0 DPC count:                                      15053470
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       205,024885
CPU 1 ISR highest execution time (µs):                58,946333
CPU 1 ISR total execution time (s):                   0,004573
CPU 1 ISR count:                                      1230
CPU 1 DPC highest execution time (µs):                238,2750
CPU 1 DPC total execution time (s):                   0,281349
CPU 1 DPC count:                                      40023
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       155,623372
CPU 2 ISR highest execution time (µs):                48,820667
CPU 2 ISR total execution time (s):                   0,003283
CPU 2 ISR count:                                      1215
CPU 2 DPC highest execution time (µs):                1453,617667
CPU 2 DPC total execution time (s):                   0,210844
CPU 2 DPC count:                                      28096
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       168,510217
CPU 3 ISR highest execution time (µs):                64,267667
CPU 3 ISR total execution time (s):                   0,009622
CPU 3 ISR count:                                      2961
CPU 3 DPC highest execution time (µs):                167,355667
CPU 3 DPC total execution time (s):                   0,398539
CPU 3 DPC count:                                      51104
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       177,030270
CPU 4 ISR highest execution time (µs):                61,8260
CPU 4 ISR total execution time (s):                   0,010341
CPU 4 ISR count:                                      3451
CPU 4 DPC highest execution time (µs):                158,852667
CPU 4 DPC total execution time (s):                   0,542728
CPU 4 DPC count:                                      72776
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       199,512866
CPU 5 ISR highest execution time (µs):                63,019667
CPU 5 ISR total execution time (s):                   0,008429
CPU 5 ISR count:                                      2891
CPU 5 DPC highest execution time (µs):                239,569333
CPU 5 DPC total execution time (s):                   0,668986
CPU 5 DPC count:                                      99500
_________________________________________________________________________________________________________

Du coup, j'ai désactivé le CPU Throttling dans le BIOS, je vais voir si je rencontre d'autres freezes à l'avenir.

Merci.

[Malekal_morte]

Vas dans le gestionnaire de périphériques;
Si tu désactives la carte Wifi et reboot, c'est mieux ?
Si pas le cas, réactive teste avec la carte audio de cette manière.

ou encore mieux si tu démarres en mode diagnostiques => Type de démarrage de Windows.

[Pico51]

Bonjour,

Je n'ai pas de carte Wifi, du coup, ça ne risque pas de venir de là.
Par contre, j'ai désactivé tous les périphériques de la liste "contrôleurs audio, vidéo et jeu" et je viens encore de connaître un freeze.

Par contre, comme je ne freeze qu'environ une fois par semaine et qu'il s'agit de mon poste de travail, je ne me vois pas travailler constamment en mode diagnostic.

Du coup, je ne sais plus trop où chercher.

Merci.

[Malekal_morte]

Le mode diagnostique c'est pour tester en désactivant et en réactivant petit à petit pour trouver le coupable.
Maintenant si ça n'arrive qu'une fois par semaine, ça risque d'être compliqué.