Mon pc freeze puis un écran bleu s'affiche
Fermé
kider34
Messages postés
3
Date d'inscription
jeudi 17 août 2017
Statut
Membre
Dernière intervention
20 août 2017
-
20 août 2017 à 19:56
Kider34 - 21 août 2017 à 11:28
Kider34 - 21 août 2017 à 11:28
A voir également:
- Genuineintel.sys
- Pc freeze - Guide
- Double ecran pc - Guide
- Test performance pc - Guide
- Réinitialiser un pc - Guide
- Ecran noir pc - Guide
2 réponses
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 656
20 août 2017 à 20:00
20 août 2017 à 20:00
Salut,
Utilise Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
Utilise Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
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 656
Modifié le 21 août 2017 à 12:15
Modifié le 21 août 2017 à 12:15
Apparemment c'est lié à NVIDIA.
Réinstalle les pilotes de la carte graphique
Quel antivirus est installé ?
Veuillez appuyer sur une touche pour continuer la désinfection...
Réinstalle les pilotes de la carte graphique
Quel antivirus est installé ?
Veuillez appuyer sur une touche pour continuer la désinfection...
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 656
>
Kider34
21 août 2017 à 08:57
21 août 2017 à 08:57
Mcafee tu devrais le désinstaller.
20 août 2017 à 22:27
--------------------------------------------------------------------------------
Computer name: DESKTOP-G1KGMP4
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: G20CB, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8512131072 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 20/08/2017 21:29:12 your computer crashed
crash dump file: C:\WINDOWS\Minidump\082017-26546-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFB70105F168E0, 0xFFFFDA0D2178B740)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard 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 Sun 20/08/2017 21:29:12 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: watchdog.sys (watchdog!WdLogEvent5_WdCriticalError+0xCE)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFB70105F168E0, 0xFFFFDA0D2178B740)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard 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 Sun 20/08/2017 21:27:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\082017-25968-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Sun 20/08/2017 20:10:40 your computer crashed
crash dump file: C:\WINDOWS\Minidump\082017-99671-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF80003A2728E0, 0xFFFF90862AEF0120)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard 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 Sun 20/08/2017 20:03:45 your computer crashed
crash dump file: C:\WINDOWS\Minidump\082017-27171-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x355E)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFF9D0054FFB8E0, 0xFFFFE58A44F63DA0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard 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
--------------------------------------------------------------------------------
9 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.28 , NVIDIA 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.