problème windows 10 Watchdog Violation Résolu/Fermé

Question

Bonsoir,

Ayant eu récemment des bugs informatiques amenant jusq'à l'écran bleu avec le problème watch dog je fait donc ce post. Je pense que ce problème peut venir de mon autre disque dur car en allant dessus, j'ai des micro bug. Plusieurs fois en lançant un vidéo cela peut arriver également.

J'ai également eu des problèmes "page in nonpaged area" je pense que cela vient du même problème.

Voici les rapports que j'ai déjà fait :

Addition : https://pjjoint.malekal.com/files.php?id=20200122_d12n10q15l13l6

FRST : https://pjjoint.malekal.com/files.php?id=FRST_20200122_m12m9w11f6w15

Shortcut : https://pjjoint.malekal.com/files.php?id=20200122_u6m11i7k12v14


Pouvez vous m'aider ?

Merci d'avance.

Malekal_morte- · Answer

Salut,

Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed 
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

~~

commence par une mise à jour de pilotes avec DriversCloud :
=> tutoriel comment mettre à jour ses pilotes avec DriversCloud

Aviation_972 · Answer

Bonjour,

Tout d'abord merci de votre réponse aussi complète.

Voici le rapport WhoCrashed

Welcome to WhoCrashed (HOME EDITION) v 6.65

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)

Computer name: NICOLASTOUSSAIN
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: MS-7A74, MSI, B250M PRO-VD (MS-7A74)
CPU: GenuineIntel Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 17142038528 bytes (16,0GB)



Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Tue mardi 21 janvier 2020 21:23:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: aow_drv_x64_ev.sys (aow_drv_x64_ev+0x41A01)
Bugcheck code: 0x50 (0xFFFFBE0A0DB8DE20, 0x11, 0xFFFFBE0A0DB8DE20, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aow_drv_x64_ev.sys .
Google query: aow_drv_x64_ev.sys PAGE_FAULT_IN_NONPAGED_AREA



On Mon lundi 20 janvier 2020 17:01:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012020-41875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8062677B358)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32
toskrnl.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.



The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\012120-46984-01.dmp



Conclusion

3 crash dumps have been found and analyzed. Only 2 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:

aow_drv_x64_ev.sys

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.

Malekal_morte- · Answer

aow_drv_x64_ev.sys = Programme Tencent
C'est lui qui fait planter Windows.

Cherche un programme Tencent Gaming ou autre et désinstalle le.

sinon :

Pour vérifier ton ordinateur, pour d'éventuels infections et avoir un état général du système :

Suis le tutoriel FRST en cliquant sur ce lien bleu. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Télécharge et lance le scan FRST, 
Attendre la fin du scan, un message indique que l'analyse est terminée.

Trois rapports FRST seront générés :

 FRST.txt
 Shortcut.
 Additionnal.txt

Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.

(Les liens bleus mènent à des tutoriels explicatifs pas à pas, clic dessus pour avoir les instructions plus précises à suivre).

Aviation_972 · Answer

D'accord, je fait le nécéssaire,

Voici également les rapports :

_ Addition https://pjjoint.malekal.com/files.php?id=20200122_c5l10d8b15u5
_ FRST https://pjjoint.malekal.com/files.php?id=FRST_20200122_p11v6m11w6o6
_ Shortcut https://pjjoint.malekal.com/files.php?id=20200122_l5w15c8u9d14

Malekal_morte- · Answer

Essaye ça :


Voici la correction à effectuer avec FRST. Tu peux t'aider de cette note explicative avec des captures d'écran.
Relance FRST puis sur ton clavier appuyer sur la touche CTRL + Y.
Le bloc-note va s'ouvrir, copie/colle ceci.

Start:CloseProcesses:CreateRestorePoint:2020-01-21 18:30 - 2020-01-21 21:23 - 000000000 ____D C:\ProgramData\Tencent2020-01-21 18:30 - 2020-01-21 18:30 - 000000000 ____D C:\Users\Nicolas\AppData\Local\Tencent2020-01-21 18:29 - 2020-01-21 18:29 - 009566192 _____ (Tencent) C:\Users\Nicolas\Downloads\com.activision.callofduty.shooter_900205109_NormalPackage_2653.exe2020-01-21 18:23 - 2020-01-22 10:39 - 000000000 ____D C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Tencent Software2020-01-21 18:17 - 2020-01-22 10:39 - 000000000 ____D C:\Users\Nicolas\AppData\Roaming\TencentS4 WsAppService; C:\Program Files (x86)\Wondershare\WAF\2.4.2.222\WsAppService.exe [474768 2017-03-01] (Wondershare software CO., LIMITED -> Wondershare)RemoveProxy:Hosts:Reboot:End:

Enregistre le contenu par le menu fichier puis enregistrer.

Ferme le bloc-note, retourne sur FRST et clique sur le bouton "Corriger / Fix"
Un redémarrage sera peut-être nécessaire et automatique.
Un fichier texte apparaît, copie/colle le contenu ici dans un nouveau message.

Redémarre l'ordinateur.

Aviation_972 · Answer

D'accord voici le rapport après la manipulation :

https://pjjoint.malekal.com/files.php?id=20200122_v13k9r7o8k8

Problème windows 10 Watchdog Violation

6 réponses

Discussions similaires