Ecran bleu, arrêt de l'ordinateur
Fermé
basketpresse75011
Messages postés
51
Date d'inscription
mardi 14 avril 2015
Statut
Membre
Dernière intervention
22 mars 2020
-
21 mars 2020 à 16:01
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 23 mars 2020 à 10:26
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 23 mars 2020 à 10:26
A voir également:
- Teedriverw8x64
- Ordinateur lent - Guide
- Double ecran - Guide
- Ordinateur ecran noir - Guide
- Écran bleu - Guide
- Capture d'écran samsung - Guide
5 réponses
Maxtor_37
Messages postés
73
Date d'inscription
samedi 16 novembre 2019
Statut
Membre
Dernière intervention
11 mai 2022
2
21 mars 2020 à 23:56
21 mars 2020 à 23:56
Le problème vient surement de tes pilotes ou des fichiers systèmes Windows.
Pour les pilotes : Essaie de les mettre à jour via le logiciel DriversCloud.
Pour Windows fait cela :
Télécharge une image disque Windows 10 avec Media Tool de Microsoft (https://www.microsoft.com/fr-fr/software-download/windows10ISO)
et boote l’image sur une clé USB.
Quand tu auras terminé, va sur la clé usb booter Windows 10 et lance le setup.
Et tu choisis l’option mettre à niveau le PC et conserver mes données et logiciels.
Pour les pilotes : Essaie de les mettre à jour via le logiciel DriversCloud.
Pour Windows fait cela :
Télécharge une image disque Windows 10 avec Media Tool de Microsoft (https://www.microsoft.com/fr-fr/software-download/windows10ISO)
et boote l’image sur une clé USB.
Quand tu auras terminé, va sur la clé usb booter Windows 10 et lance le setup.
Et tu choisis l’option mettre à niveau le PC et conserver mes données et logiciels.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
22 mars 2020 à 01:15
22 mars 2020 à 01:15
Salut,
Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc
Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.
plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc
Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.
plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
basketpresse75011
Messages postés
51
Date d'inscription
mardi 14 avril 2015
Statut
Membre
Dernière intervention
22 mars 2020
22 mars 2020 à 17:50
22 mars 2020 à 17:50
Bonjour
Tout d'abord, merci pour votre réponse
Voici le rapport whocrashed de mon ordinateur :
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-TOA0R1U
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: Aspire A715-72G, Acer, CFL, Charmeleon_CFS
CPU: GenuineIntel Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Intel8664, level: 6
12 logical processors, active mask: 4095
RAM: 17014513664 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sun 22/03/2020 00:24:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032220-12625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80257D73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 22/03/2020 00:24:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: teedriverw8x64.sys (teedriverw8x64+0x1a304)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80257D73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\teedriverw8x64.sys
product: Intel(R) Management Engine Interface
company: Intel Corporation
description: Intel(R) Management Engine Interface
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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: teedriverw8x64.sys (Intel(R) Management Engine Interface, Intel Corporation).
Google query: teedriverw8x64.sys Intel Corporation DPC_WATCHDOG_VIOLATION
On Sat 21/03/2020 21:15:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032120-10812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80479373358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 21/03/2020 15:40:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032120-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80219F73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 16/03/2020 17:35:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031620-12312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80528573358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 13/03/2020 14:50:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031320-12593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8021C373358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and 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:
teedriverw8x64.sys (Intel(R) Management Engine Interface, Intel Corporation)
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Tout d'abord, merci pour votre réponse
Voici le rapport whocrashed de mon ordinateur :
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Please note that this version of WhoCrashed is not licensed for use by professional support engineers.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-TOA0R1U
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: Aspire A715-72G, Acer, CFL, Charmeleon_CFS
CPU: GenuineIntel Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz Intel8664, level: 6
12 logical processors, active mask: 4095
RAM: 17014513664 bytes (15,8GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Sun 22/03/2020 00:24:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032220-12625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80257D73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 22/03/2020 00:24:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: teedriverw8x64.sys (teedriverw8x64+0x1a304)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80257D73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\teedriverw8x64.sys
product: Intel(R) Management Engine Interface
company: Intel Corporation
description: Intel(R) Management Engine Interface
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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: teedriverw8x64.sys (Intel(R) Management Engine Interface, Intel Corporation).
Google query: teedriverw8x64.sys Intel Corporation DPC_WATCHDOG_VIOLATION
On Sat 21/03/2020 21:15:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032120-10812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80479373358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 21/03/2020 15:40:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032120-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80219F73358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 16/03/2020 17:35:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031620-12312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80528573358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
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 13/03/2020 14:50:54 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031320-12593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2380)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8021C373358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and 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:
teedriverw8x64.sys (Intel(R) Management Engine Interface, Intel Corporation)
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.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
22 mars 2020 à 18:14
22 mars 2020 à 18:14
Fais une mise à jour avec Snappy Driver Installer : https://www.malekal.com/tutoriel-snappy-driver-installer-mettre-a-jour-pilotes/
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
basketpresse75011
Messages postés
51
Date d'inscription
mardi 14 avril 2015
Statut
Membre
Dernière intervention
22 mars 2020
22 mars 2020 à 22:32
22 mars 2020 à 22:32
Bonsoir
c'est fait
MAIS
je n"ai plus d'acccès à mon clavier ! :-(
il y a un souci avec le périphérique ELAN EZTouchFilter
"ce périphérique ne peut pas démarrer. (Code10)
A required I2C connection and/or interrupt ressource was missing
c'est fait
MAIS
je n"ai plus d'acccès à mon clavier ! :-(
il y a un souci avec le périphérique ELAN EZTouchFilter
"ce périphérique ne peut pas démarrer. (Code10)
A required I2C connection and/or interrupt ressource was missing
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
23 mars 2020 à 10:26
23 mars 2020 à 10:26
Désinstalle ELAN EzTouchFilter pour voir.
