code d'arrêt CLOCK WATCHDOG TIMEOUT

Question

Bonjour,

J'ai acheté une nouvelle carte graphique ( GIGABYTE GeForce RTX 3060 Eagle 12G (rev. 2.0) NVIDIA 12 Go GDDR6 Noir) que je viens d'installer. J'ai ensuite installé les pilotes nécessaires et depuis mon pc crash assez souvent en m'indiquant le code d'arrêt suivant :

code d'arrêt : CLOCK WATCHDOG TIMEOUT.

Voici un screen des installations réalisés :

Mon pc est le suivant :

Des solutions?

Voici une copie de mon who crashed:

---

Welcome to WhoCrashed (Home Edition) v 6.70

---

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: DESKTOP-8Q44N6A
Windows version: Windows 10, 10.0, version 2009, build: 19044
Windows dir: C:\WINDOWS
Hardware: MS-7C52, Micro-Star International Co., Ltd., A320M-A PRO MAX (MS-7C52)
CPU: AuthenticAMD AMD Ryzen 5 3400G with Radeon Vega Graphics 8664, level: 23
8 logical processors, active mask: 255
RAM: 17125560320 bytes (15,9GB)

---

Crash Dump Analysis

---

Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Thu 28/07/2022 00:16:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072822-6671-01.dmp
This was probably caused by the following module: 0n87.sys (0n87)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFE581BEB5F180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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: 0n87.sys .
Google query: 0n87.sys CLOCK_WATCHDOG_TIMEOUT

On Thu 28/07/2022 13:05:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072822-7656-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0xf7f2)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFB180BE78D180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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 Thu 28/07/2022 13:05:58 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: netwtw10.sys (netwtw10+0xc9006)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFB180BE78D180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\drivers\netwtw10.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: R Intel Wireless WiFi Link Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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: netwtw10.sys (R Intel Wireless WiFi Link Driver, Intel Corporation).
Google query: netwtw10.sys Intel Corporation CLOCK_WATCHDOG_TIMEOUT

On Wed 27/07/2022 15:16:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072722-7468-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0xf7f2)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFF9E81F3F5F180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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 27/07/2022 15:14:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072722-6765-01.dmp
This was probably caused by the following module: 0n87.sys (0n87)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFDB80ECAD5180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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: 0n87.sys .
Google query: 0n87.sys CLOCK_WATCHDOG_TIMEOUT

On Wed 27/07/2022 06:05:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072722-7406-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0xf7f2)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFB001D68A5180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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 Tue 19/07/2022 23:59:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\NDIS-20220719-2359.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisReleaseNicActive+0xB1D)
Bugcheck code: 0x15E (0x25, 0x23, 0xFFFFA6091E4D6708, 0xD010310)
Error: BUGCODE_NDIS_DRIVER_LIVE_DUMP
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: NDIS has captured a live kernel dump. NDIS does not generate a bug check in this situation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

---

Conclusion

---

7 crash dumps have been found and analyzed. 2 third party drivers have 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:

netwtw10.sys (R Intel Wireless WiFi Link Driver, Intel Corporation)
0n87.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.

Answer 1

Bonjour

Merci pour votre réponse.

Avez - vous déjà essayé de désinstaller le pilote de carte vidéo et votre ordinateur sera - t - il à l'écran bleu sans le pilote de carte vidéo?

Si le pilote de carte vidéo est déchargé et que l'écran bleu disparaît. Vous pouvez essayer d'installer une version plus ancienne du pilote de carte vidéo pour vérifier.

N'hésitez pas à nous contacter si vous rencontrez des difficultés dans le processus.

Je vous présente mes respects.

Derrick Qian | Microsoft community support specialist

Answer 2

Bonjour,
Je vous confirme qu'avant l'installation de cette nouvelle carte graphique mon ordinateur était sain et très stable. Je n'avais absolument aucun problème. Je n'ai pas d'antivirus sur mon pc, je ne pense pas que ce soit utile. J'ai effectivement mis à jour le pilote de ma carte réseau car cette dernière avait été désinstaller temporairement lorsque j'ai ajouté ma carte graphique, je l'ai remise donc j'ai du réinstallé les pilotes choses que je n'avais pas fait. Pour le point 4, j'ai voulu mettre à jour les pilote de la carte mère en allant sur le site de amd mais je n'y suis pas parvenu, ça me mets systématiquement un message d'erreur, je pense que cela vient de fait que je dispose d'une carte graphique intégré et comme j'ai installé une nouvelle carte graphique, il ne veut pas de la carte graphique intégré, cela me semble logique donc c'est possible que mon soucis viennent de ce point là, peut-être que le pilote de la carte mère n'est pas à jour si c'est le cas, pouvez-vous m'indiquer comment le faire.
A noter que les bug surviennent quand je mets de la vidéo.

Sur un autre forum, on me dit que mon alimentation serait responsable de cette instabilité. Je cite la réponse de cette personne:

https://i.imgur.com/uG50Vot.png

Merci.

Answer 3

Hi

Welcome to Microsoft community.

From your description, your problem seems to be caused by replacing a new graphics card. Did you have the same problem before replacing the graphics card? You could try the following steps first.

1. Execute the clean startup and check whether the problem still exists.

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate and safe information. Watch out for ads on the site that may advertise products frequently classified as PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

2. If you have anti-virus software installed, uninstall it first to see if the problem occurs again.
3. Judging from your error log, there are still network problems. You could first try to disable your network card and check whether your crash occurs again without enabling your network card?

Type the device manager in the search box in the lower left corner of the desktop, find the network adapter option, right-click your intel network card, click disable, use your computer for a period of time, and check whether the problem still exists.

4. There is also an AMD motherboard driver error in your error message. Have you installed your amd motherboard driver? If it is not installed, you can go to your motherboard official website to download and install the corresponding motherboard driver. Check whether the problem still exists.
5. You could try to unplug your 3060 graphics card and check whether the problem still occurs when only the integrated graphics card is used?

Keep us posted if you encounter any challenges along the process.

Best regards

Derrick Qian | Microsoft Community Support Specialist