Dpc watchdog violation [Fermé]

Signaler
Messages postés
1
Date d'inscription
mardi 25 février 2020
Statut
Membre
Dernière intervention
25 février 2020
-
Messages postés
27903
Date d'inscription
dimanche 18 janvier 2009
Statut
Contributeur
Dernière intervention
10 mai 2021
-
Bonjour
Donc j ai ce fameux écran bleu ( dpc watchdog violation)
Le problématique c est que cette erreur se produit seulement qd je joue à Gta V et non à Fortnite
J ai beau faire tous les tutos possibles rien ne marche
Est ce que quelqu’un pourrait m aider?

2 réponses

Messages postés
27903
Date d'inscription
dimanche 18 janvier 2009
Statut
Contributeur
Dernière intervention
10 mai 2021
3 698
Salut,

Tu peux essayer WhoCrashed pour examiner les MiniDumps
1
Merci

Quelques mots de remerciements seront grandement appréciés. Ajouter un commentaire

CCM 65492 internautes nous ont dit merci ce mois-ci

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 26/02/2020 16:07:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022620-28234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8002EB73358, 0x0)
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 Wed 26/02/2020 16:07:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: mmcss.sys (mmcss+0x1e6d)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8002EB73358, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\drivers\mmcss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MMCSS Driver
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 a Microsoft module. The description of the module may give a hint about a non responding device in the system.



On Wed 26/02/2020 13:25:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022620-27156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80174773358)
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
--------------------------------------------------------------------------------

3 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.


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.
Messages postés
27903
Date d'inscription
dimanche 18 janvier 2009
Statut
Contributeur
Dernière intervention
10 mai 2021
3 698
Vérifies si les températures de ton CPU sont normales, tu peux utiliser Core Temp

Si c'est pour te donner un indice., mmcss.sys est en rapport avec Multimedia Class Scheduler - Windows 10 Service

A tu bien la version 1909 de Win10 ?

Tu peux vérifier avec Exécuter: winver

Aucun driver tiers n'est relié directement, mais...

A tu mis à jour tous tes drivers ?

Tu peux voir avec Touslesdrivers.com et ou DriversCloud.com