Ecrans bleus à répétition sur Windows 10 ! [Résolu]

[juju75]

Bonsoir,

Je vous soumets un problème très handicapant (et très énervant), que je rencontre sur Windows 10 depuis près de deux mois : de multiples écrans bleus (jusqu'à une douzaine par jour !), avec une variété de "codes d'arrêt" (cf. captures d'écran en fin de post). Ceux-ci se produisent à tout moment, sans que j'arrive à identifier une action ou un logiciel qui pourrait en être la cause.
Ces écrans bleus apparaissent parfois juste après le démarrage et il arrivent qu'ils s'enchaînent avant même que je fasse quoi que ce soit sur mon PC... Je constate également régulièrement que mon PC a redémarré (a priori suite à un énième écran bleu) alors que je ne m'en servais pas, que ce soit pendant la nuit (si je ne l'ai pas éteint) ou la journée lorsque je m'absente.

Il me semble, sans qu'en sois certain, que ces problèmes sont apparus suite à des mises à jour Windows. Si cela peut aider, en voici la liste complète :

04/11/2021 Mise à jour de fonctionnalité vers Windows 10, version 20H2
04/11/2021 KB4023057
18/11/2021 KB5007884
18/11/2021 KB5002032 / KB5002056 / KB4486670
19/11/2021 KB5007186
08/12/2021 Mise à jour de fonctionnalité vers Windows 10, version 21H2
08/12/2021 KB5001940 / KB4023057
15/12/2021 KB5002098 / KB5002033 / KB4504710 / KB4504745 / KB5008212
18/12/2021 KB5002099
05/01/2022 KB4504713


Il y a aussi eu des mises à jour de pilotes :

04/11/2021 Intel - Net - 12.18.11.1
18/11/2021 Apple, Inc. - USBDevice - 486.0.0.0
19/11/2021 Logitech - Image - 1.4.40.0
02/12/2021 Logitech - HIDClass - 1.10.80.0
06/12/2021 Apple - USBDevice - 1.0.1.0


Je précise que :

• mon PC fonctionnait jusqu'à présent comme une horloge, et ce depuis plusieurs années (cf. configuration ci-dessous)

• il arrive qu'aucun écran bleu n'apparaisse pendant plusieurs jours d'affilée, notamment si je ne l'ai ni redémarré ni mis en veille

• j'ai fait un Memtest86+ (2 passes) qui n'a révélé aucun problème sur mes barrettes de mémoire vive

Configuration :

Processeur : QuadCore Intel Core i7-6700, 3900 MHz (39 x 100)
Carte mère : Asus Z170-Deluxe
Chipset de la carte mère : Intel Sunrise Point Z170, Intel Skylake-S
Mémoire système : 16320 Mo (DDR4 SDRAM) / DIMM2: Crucial BLE8G4D26AFEA.16FAD 8 Go DDR4-2666 / DIMM4: Crucial BLE8G4D26AFEA.16FAD 8 Go DDR4-2666
Type de Bios : AMI (03/14/2018)
Carte graphique : NVIDIA GeForce GTX 750 Ti (2 Go)

Merci par avance pour votre aide !

Juju

Les captures d'écran du jour sont consultables ici : https://drive.google.com/drive/folders/ ... sp=sharing

[juju75]

Re-bonsoir,

J'ai ajouté le rapport de WhoCrashed ici : https://drive.google.com/file/d/1oqvM_o ... sp=sharing

Code : Tout sélectionner

System Information (local)

Windows version: Windows 10, 10.0, version 2009, build: 19044 Windows
dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., Z170-DELUXE
CPU: GenuineIntel Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz 8664, level: 6
8 logical processors, active mask: 255
RAM: 17109790720 bytes (15,9GB)

Crash Dump Analysis

Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
C:\WINDOWS\LiveKernelReports
On Thu 06/01/2022 15:27:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-16062-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80730DDC8AB)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFF80730DDC8AB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL
that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means
that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused
by another driver on your system that cannot be identified at this time.

On Thu 06/01/2022 15:24:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-13687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F70D0)
Bugcheck code: 0x154 (0xFFFF8B837FD24000, 0xFFFFF9019D1A6760, 0x1, 0x0)
Error: UNEXPECTED_STORE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the store component caught an unexpected exception.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at
this time.

On Thu 06/01/2022 14:37:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-13453-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8035B7DC8AB)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFF8035B7DC8AB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL
that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means
that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused
by another driver on your system that cannot be identified at this time.

On Thu 06/01/2022 13:44:55 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-13640-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8061DFDC8AB)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFF8061DFDC8AB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL
that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means
that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused
by another driver on your system that cannot be identified at this time.

On Thu 06/01/2022 11:31:23 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-12968-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF806343DC8AB)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFF806343DC8AB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL
that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means
that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused
by another driver on your system that cannot be identified at this time.

On Thu 06/01/2022 11:29:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-14187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F70D0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8007D00932B, 0x0, 0xFFFF8489C000018C)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not
catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating
(thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at
this time.

On Thu 06/01/2022 11:18:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-12984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F70D0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFD0, 0x2, 0xFFFFF806780082B6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System

company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at
this time.

On Thu 06/01/2022 11:15:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-14031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F70D0)
Bugcheck code: 0xA (0xFFFFCA86C00001C4, 0x2, 0x1, 0xFFFFF8011E485697)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at
DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means
that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at
this time.

On Thu 06/01/2022 11:13:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-19031-01.dmp
This was probably caused by the following module: eamonm.sys (0xFFFFF80226174AFF)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80226174AFF, 0xFFFFF682226F6260, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\eamonm.sys
product: ESET Security
company: ESET
description: ESET real-time file system monitor

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-
privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update
for the following driver: eamonm.sys (ESET real-time file system monitor, ESET).
Google query: eamonm.sys ESET SYSTEM_SERVICE_EXCEPTION

On Thu 06/01/2022 10:10:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010622-14234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F70D0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8064CA09C7C, 0xFFFF8D8EB9BFC580, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

Bug check description: This indicates that an exception happened while executing a routine that transitions from non-
privileged code to privileged code.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at
this time.

Conclusion

On your computer a total of 44 crash dumps have been found. Only 10 have been analyzed. A third party driver has been
identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these
drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
eamonm.sys (ESET real-time file system monitor, ESET)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with
the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the
query. This often yields interesting results from discussions on the web by users who have been experiencing similar
problems.

Merci !

[Malekal_morte]

Salut,

Désinstalle ESET et teste pendant quelques jours.
Vérifie que Windows Defender reprend bien le délai.

[juju75]

Bonjour,

Merci du conseil, je vais tester sans ESET.
Pour info, j'utilise cet antivirus depuis toujours et n'ai jamais rencontré de problème jusqu'à présent. Serait-ce la dernière version qui serait en cause ? Cet antivirus est-il connu pour poser des problèmes particuliers ? J'avais cru comprendre qu'il présentait un des meilleurs rapports efficacité/consommation ressources.

Bonne journée,

Juju

[Malekal_morte]

Tes rapports montrent que c'est le pilote de NOD32 qui plante.
Donc déjà tester sans, si plus aucun plantage, tu le réinstalles, comme ça tu auras la dernière version... des fois qu'un bug soit corrigé.

Sinon vu tous les plantages et STOP CODE différent, il est possible qu'un problème matériel soit aussi derrière tout cela.

[juju75]

Bonsoir,

Je reviens faire un petit update de ma situation. Je touche du bois, mais la situation semble être rentrée dans l'ordre et les écrans bleus en série ont cessé. Finalement, et contre toute attente, l'antivirus Eset ne semblait pas en cause. Ce qui a semble-t-il réglé le problème (je reste prudent) est la mise à jour des drivers des cartes réseaux de ma carte mère. Ce qui est surprenant, c'est que j'avais déjà envisagé cette mise à jour après avoir lu ici ou là que ça pouvait être la cause de ces écrans bleus. Sauf que Windows me disait que j'avais les derniers drivers et qu'aucune mise à jour n'était disponible... C'est finalement via le logiciel CCleaner et sa fonction "Driver Updater" que j'ai pu faire cette mise à jour.

Si cela est possible, je souhaite laisser ce post ouvert encore quelques temps, au cas où les écrans bleus seraient de retour.

Encore merci pour votre disponibilité et vos conseils,

Juju

[Malekal_morte]

ok tant mieux si tu as trouvé la solution.
Tiens nous au courant !

[juju75]

Bonjour,

J'ai finalement bien fait de ne pas fermer le post : après près de deux semaines sans problème, les écrans bleus à répétition sont de retour...
Deux origines principales : ntoskrnl.exe et netio.sys
Je vais donc tenter ta suggestion initiale, consistant à désinstaller mon antivirus ESET.
Je reviendrai ici pour donner des nouvelles.

Bonne journée,

Juju

[Malekal_morte]

yep, tiens nous au courant =)

[juju75]

Bonjour,
Je m'aperçois que je n'ai jamais clôturé ce post...
Après 1 an sans écran bleu, je pense qu'on peut le considérer comme résolu ;-)
J'ai en revanche un autre problème depuis peu : mon PC refuse de s'arrêter et redémarre instantanément, trois ou quatre secondes après l'arrêt...
Je fais un nouveau post sur le forum.