Dpc watchdog violation
Fermé
Sandro6
Messages postés
1
Date d'inscription
mardi 25 février 2020
Statut
Membre
Dernière intervention
25 février 2020
-
25 févr. 2020 à 00:56
fabul Messages postés 38898 Date d'inscription dimanche 18 janvier 2009 Statut Modérateur Dernière intervention 15 octobre 2024 - 26 févr. 2020 à 16:44
fabul Messages postés 38898 Date d'inscription dimanche 18 janvier 2009 Statut Modérateur Dernière intervention 15 octobre 2024 - 26 févr. 2020 à 16:44
A voir également:
- The dpc watchdog detected a prolonged run time at an irql of dispatch_level or above
- Vulkan run time ✓ - Forum Logiciels
- Boot failure detected - Forum BIOS
- The legend of zelda: a link to the past - Accueil - Guide jeu vidéo
- Time machine - Guide
- Input signal out of range ✓ - Forum Matériel & Système
2 réponses
fabul
Messages postés
38898
Date d'inscription
dimanche 18 janvier 2009
Statut
Modérateur
Dernière intervention
15 octobre 2024
5 367
25 févr. 2020 à 01:18
25 févr. 2020 à 01:18
Salut,
Tu peux essayer WhoCrashed pour examiner les MiniDumps
Tu peux essayer WhoCrashed pour examiner les MiniDumps
26 févr. 2020 à 16:31
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.