Problème écran bleu (arrêts intempestifs)
Sam le skieur
Messages postés
64
Statut
Membre
-
Sam le skieur Messages postés 64 Statut Membre -
Sam le skieur Messages postés 64 Statut Membre -
Bonjour à tous,
Je me permets d'intervenir car je rencontre depuis un bout de temps déjà des problèmes d'écran bleu sur mon ordinateur.
En général, cela se traduit par des arrêts soudains de l'ordinateur, mais je les vois également quasiment à chaque redémarrage : l'ordinateur a besoin de démarrer peut-être 3 ou 4 fois avant que cette erreur disparaisse et je puisse enfin accéder à mon bureau.
En général le code d'erreur que je vois s'afficher est SYSTEM_SERVICE_EXCEPTION.
Je vous joins un rapport WhoCrashed réalisé aujourd'hui :
System Information (local)
--------------------------------------------------------------------------------
Computer name: LAPTOP-B61BBIT6
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: HP Pavilion Notebook, HP, 84F7
CPU: GenuineIntel Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 8463147008 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 05/04/2020 00:00:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040520-31156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80145315E58, 0xFFFFFE0F511E0640, 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.
On Sun 05/04/2020 09:08:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040520-37984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80783715E58, 0xFFFFC3088DEAD640, 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.
On Fri 03/04/2020 17:07:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040320-58187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFF80412097A4D)
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 Mon 30/03/2020 10:51:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033020-34578-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF8073FBC0FD0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8073FBC0FD0, 0xFFFFD682D1FAE880, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Je précise avoir déjà essayé plusieurs choses, après avoir parcouru divers forums.
J'ai donc désinstallé quelques programmes (notamment Daemon Tools, ou encore avast).
J'ai également mis à jour les différents drivers de périphériques que je peux avoir, et les mises à jour de Windows sont effectuées automatiquement.
Malgré tout cela, je continue à avoir ces erreurs qui sont assez pénibles. Je dois préciser également que ça arrive de manière totalement aléatoire : il peut se passer une semaine sans qu'il n'y ait d'arrêt brutal, et celui-ci peut arriver sans aucune raison (j'ai déjà eu le cas alors que le PC était en veille).
J'espère avoir été assez précis dans mes explications, et que vous pourrez m'aider à trouver des solutions à mon problème.
Je vous remercie !
Je me permets d'intervenir car je rencontre depuis un bout de temps déjà des problèmes d'écran bleu sur mon ordinateur.
En général, cela se traduit par des arrêts soudains de l'ordinateur, mais je les vois également quasiment à chaque redémarrage : l'ordinateur a besoin de démarrer peut-être 3 ou 4 fois avant que cette erreur disparaisse et je puisse enfin accéder à mon bureau.
En général le code d'erreur que je vois s'afficher est SYSTEM_SERVICE_EXCEPTION.
Je vous joins un rapport WhoCrashed réalisé aujourd'hui :
System Information (local)
--------------------------------------------------------------------------------
Computer name: LAPTOP-B61BBIT6
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: HP Pavilion Notebook, HP, 84F7
CPU: GenuineIntel Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 8463147008 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sun 05/04/2020 00:00:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040520-31156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80145315E58, 0xFFFFFE0F511E0640, 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.
On Sun 05/04/2020 09:08:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040520-37984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF80783715E58, 0xFFFFC3088DEAD640, 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.
On Fri 03/04/2020 17:07:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040320-58187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFF80412097A4D)
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 Mon 30/03/2020 10:51:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033020-34578-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF8073FBC0FD0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8073FBC0FD0, 0xFFFFD682D1FAE880, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Je précise avoir déjà essayé plusieurs choses, après avoir parcouru divers forums.
J'ai donc désinstallé quelques programmes (notamment Daemon Tools, ou encore avast).
J'ai également mis à jour les différents drivers de périphériques que je peux avoir, et les mises à jour de Windows sont effectuées automatiquement.
Malgré tout cela, je continue à avoir ces erreurs qui sont assez pénibles. Je dois préciser également que ça arrive de manière totalement aléatoire : il peut se passer une semaine sans qu'il n'y ait d'arrêt brutal, et celui-ci peut arriver sans aucune raison (j'ai déjà eu le cas alors que le PC était en veille).
J'espère avoir été assez précis dans mes explications, et que vous pourrez m'aider à trouver des solutions à mon problème.
Je vous remercie !
A voir également:
- Problème écran bleu (arrêts intempestifs)
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
3 réponses
Bonjour,
Va dans le gestionnaire de périphériques et donne-moi le libellé exact de ta carte réseau WiFi (wireless) ou de la carte réseau Ethernet, en fait donne-moi le libellé de celle dont tu te sers.
Va dans le gestionnaire de périphériques et donne-moi le libellé exact de ta carte réseau WiFi (wireless) ou de la carte réseau Ethernet, en fait donne-moi le libellé de celle dont tu te sers.
Alors je te donne le libellé des 2 car je m'en sers alternativement :
Pour l'Ethernet : Realtek PCIe GbE Family Controller #2
Pour le Wi-Fi : Realtek RTL8822BE 802.11ac PCIe Adapter #2
Pour l'Ethernet : Realtek PCIe GbE Family Controller #2
Pour le Wi-Fi : Realtek RTL8822BE 802.11ac PCIe Adapter #2
Pour la carte WiFi installe CE PILOTE.
Pour la carte Ethernet vérifie si elle est à jour avec DRIVERSCLOUD ne prendre que les pilotes ayant une pertinence de 5.
Pour info ta version de Windows 10 n'est pas à jour tu peux le vérifier avec CET OUTIL DE MICROSOFT
Vérifie si c'est mieux.
Pour la carte Ethernet vérifie si elle est à jour avec DRIVERSCLOUD ne prendre que les pilotes ayant une pertinence de 5.
Pour info ta version de Windows 10 n'est pas à jour tu peux le vérifier avec CET OUTIL DE MICROSOFT
Vérifie si c'est mieux.
Bonjour,
Du coup ayant suivi les mises à jour comme demandé, j'ai été tranquille un petit moment...jusqu'à ce que ça me le refasse ces derniers jours.
Visiblement, il n'y a plus de problèmes lors des redémarrages, par contre ce sont des arrêts intempestifs qui se produisent.
Le rapport concernant les derniers arrêts :
On Sat 25/04/2020 18:08:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042520-16671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFF800098046CD)
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 Wed 22/04/2020 00:35:11 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042220-13421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C90D6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFE081504F5040, 0xFFFFF3074C05F7E0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 20/04/2020 20:02:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042020-14031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C90D6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFAD84A4F78040, 0xFFFFAC8A8762F7E0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
En espérant que cela puisse aider...
Du coup ayant suivi les mises à jour comme demandé, j'ai été tranquille un petit moment...jusqu'à ce que ça me le refasse ces derniers jours.
Visiblement, il n'y a plus de problèmes lors des redémarrages, par contre ce sont des arrêts intempestifs qui se produisent.
Le rapport concernant les derniers arrêts :
On Sat 25/04/2020 18:08:06 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042520-16671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x14, 0x2, 0x0, 0xFFFFF800098046CD)
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 Wed 22/04/2020 00:35:11 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042220-13421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C90D6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFE081504F5040, 0xFFFFF3074C05F7E0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 20/04/2020 20:02:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042020-14031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C90D6)
Bugcheck code: 0x1000009F (0x4, 0x12C, 0xFFFFAD84A4F78040, 0xFFFFAC8A8762F7E0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
En espérant que cela puisse aider...
