Salut,

Je fait un test OCCT (Power supplément) pour tester mon OC GPU et j’ai eu 2 fois un BSOD Clock_wtachdog_timeout.

De ce que je comprend, ce n’est pas lié à l’OC du GPU mais un problème CPU.

J’ai fait un SFC /scannow qui m’a retourner des erreurs, corrigées avec un DISM.

Mais après un nouveau test’ de nouveau ce BSOD après 45min de OCCT.

Une idée ?

voila ce que me donne WhoCrashed

On Tue 12/11/2019 21:38:03 your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\Minidump\111219-6921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFE600ED5CB180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 12/11/2019 21:38:03 your computer crashed or a problem was reported

crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: cpuz148_x64.sys (cpuz148_x64+0x1ecc)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFE600ED5CB180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\temp\cpuz148\cpuz148_x64.sys
product: CPUID service
company: CPUID
description: CPUID 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: cpuz148_x64.sys (CPUID Driver, CPUID).
Google query: cpuz148_x64.sys CPUID CLOCK_WATCHDOG_TIMEOUT

Yo, c'est un manque de Vcore, ton processeur demande plus d'énergie qu'il n'en reçois, essaie de ne pas allez au dela de 1.3 de Vcore, 1.4 si tu à un très bon refroidissement