Dpc watchdog violation

GoldenDestiny Messages postés 2 Date d'inscription   Statut Membre Dernière intervention   -  
GoldenDestiny Messages postés 2 Date d'inscription   Statut Membre Dernière intervention   -
Salut a tous je jous en ce moment a un jeu qui me provoque des crash du pc :dpc watchdog violation avec un ecran bleu.

J'ai télécharger un logiciel qui a fait cette analyse :

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 24/01/2016 19:54:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-24500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 24/01/2016 19:54:05 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1A1999)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 332.35
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 332.35
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.35 , NVIDIA Corporation).
Google query: NVIDIA Corporation DPC_WATCHDOG_VIOLATION



On Sun 24/01/2016 19:26:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-27468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 24/01/2016 12:26:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-24296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 24/01/2016 11:31:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-98828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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
--------------------------------------------------------------------------------

5 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 332.35 , 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.


Merci a ceux qui pourront m'aider car c'est assez chiant comme bug :/

1 réponse

pistouri Messages postés 18900 Date d'inscription   Statut Contributeur Dernière intervention   Ambassadeur 8 507
 
bonsoir ,

regarder içi :

https://www.thewindowsclub.com/dpc_watchdog_violation-blue-screen-in-windows-10

Écran DPC_WATCHDOG_VIOLATION bleu dans Windows 10

Certains de Windows 10 utilisateurs ont signalé qu'ils reçoivent parfois un DPC_WATCHDOG_VIOLATION Blue Screen, avec une vérification de bogue code de 0x00000133, lorsque vous travaillez sur leur ordinateur.

Apparemment, ce problème se produit parce que le iastor le chauffeur, est pas compatible avec Windows 10. Microsoft est conscient de ce problème et étudie actuellement des façons de résoudre ce problème, en empêchant le pilote à partir en cours de migration lors de la mise à Windows 10.
DPC_WATCHDOG_VIOLATION Stop Error

Pour contourner ce problème, Microsoft a proposé de remplacer le pilote problématique avec le Microsoft iastor le chauffeur.
Pour ce faire, suivez cette procédure:
Faites un clic droit sur ??le bouton Démarrer pour ouvrir le menu WinX et sélectionnez Gestionnaire de périphériques. Développez contrôleurs IDE ATA / ATAPI.
Sélectionnez le contrôleur avec SATA AHCI en son nom.

Pour vérifier que vous avez sélectionné le bon de commande, cliquez-droit sur ??le contrôleur, sélectionnez Propriétés, cliquez sur l'onglet Pilote, puis sur Détails du pilote. Vérifiez que iastor .sys est un pilote répertorié, puis cliquez sur OK.

Maintenant, à partir de l'onglet Pilote, sélectionnez Mise à jour du pilote. Ensuite, sélectionnez Parcourir mon ordinateur pour logiciel pilote.
Sélectionnez Me laisser choisir parmi une liste de pilotes de périphériques sur mon ordinateur, puis sélectionnez enfin la norme SATA AHCI Controller.

Cliquez sur Suivant, puis suivez la procédure pour installer le pilote.

Redémarrez votre ordinateur Windows 10.
0
GoldenDestiny Messages postés 2 Date d'inscription   Statut Membre Dernière intervention  
 
Merci j'essaierais ça demain mais moi j'ai windows 8, ça fait quoi du coup ?
0