Dpc watchdog violation en boucle

Résolu/Fermé
Lucroz94 - 17 juil. 2019 à 16:56
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 - 18 juil. 2019 à 11:31
Bonjour à tous,

Suite à de très nombreux problèmes sur mon ordinateur, j'ai décidé de TOUT formater et désinstaller pour partir sur une base saine.

Suite à une installation chaotique de Windows 10 en 1809 et à de très nombreux problèmes lors du passage en 1903, j'ai décidé de revenir en 1809 et de ne pas faire la MAJ.

J'ai tout mes drivers à jour, MAJ Windows Update aussi, j'ai une clef de licence Windows 10 Pro valide et pourtant lorsque je décide de copier mes données de mon DD externe vers mon PC, j'ai à chaque fois, de manière assez aléatoire, une erreur DPC WATCHDOG VIOLATION.

J'ai donc tester un CHKDSK qui fait planter le PC, tester SFC scan now mais il n'effectue pas la réparation "La Protection des ressources Windows a détecté des fichiers corrompus, mais n'a pas pu réparer certains d'entre eux."

J'ai installé WhoCrashed et voici le rapport :

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Wed 17/07/2019 16:13:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071719-7828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0xA (0xFFFFDC0EE4655658, 0x2, 0x1, 0xFFFFF8072F736EB3)
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 17/07/2019 16:13:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0xDC658)
Bugcheck code: 0xA (0xFFFFDC0EE4655658, 0x2, 0x1, 0xFFFFF8072F736EB3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Wed 17/07/2019 15:55:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071719-7671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80729345380, 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 17/07/2019 14:23:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071719-11406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80041344380, 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 17/07/2019 13:34:40 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071719-8515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8040C551380, 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 17/07/2019 13:09:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071719-8500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8067FBF3380, 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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

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




J'en ai vraiment marre et je ne sais plus quoi faire, j'ai essayer pleins de choses pour réparer Windows, désinstaller et réinstaller tout les drivers à la main plutôt qu'avec Windows Update et pourtant, le système reste instable...

Toute aide serait fortement apprécié car je n'en peux plus d'avoir un PC performant qui ne fonctionne pas à cause du système...

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 627
17 juil. 2019 à 17:00
Salut,

C'est matériel donc voir avec un magasin d'informatique.
Vérifie le disque dur avec CrystalDiskInfo

Vérifie l'état de santé de tes barrettes de mémoire :
- memtest : vérifier barette de mémoire (malekal.com)
- memtest : vérifier barette de mémoire (CCM)



Installe "Real Temp" ou "Coretemp" pour Monitorer la température de l'ordinateur.
Voir à combien monte la température de l'ordinateur lors de son utilisation. Celle-ci ne doit pas dépasser les 60 degrés Celsius. Si possible joindre au message une capture d'écran du logiciel.

0
Bonjour,


Merci beaucoup, le soucis venait effectivement des barrettes mémoires...

En 1 minute, Memtest86+ a détecter 1000 erreurs....
L'outil Windows m'a aussi envoyé un message en disant qu'elles étaient défectueuses...

Pourtant achetées neuves, elles ont moins d'un an. Je suis vraiment dégoûté. Je vais essayer de faire jouer la garantie sinon tant pis, rachat d'une paire !
0
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 627
18 juil. 2019 à 11:31
bon courage à toi =)
0