BSOD Whochashed
Résolu
Super_carotte
Messages postés
185
Date d'inscription
Statut
Membre
Dernière intervention
-
Super_carotte Messages postés 185 Date d'inscription Statut Membre Dernière intervention -
Super_carotte Messages postés 185 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
J'ai depuis quelques temps des BSOD. (de plus en plus frequent me semble t'il).
J'ai installé "Whocrashed" pour savoir d'ou ça viendrait.
Voici le rapport:
On Mon 18/11/2013 10:41:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-16473-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880032F7180, 0x6)
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 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 Mon 18/11/2013 10:41:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x5DEA8)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880032F7180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.65
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 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 331.65 , NVIDIA Corporation).
Google query: NVIDIA Corporation CLOCK_WATCHDOG_TIMEOUT
Auriez vous une idée pour corriger ça?
Merci.
J'ai depuis quelques temps des BSOD. (de plus en plus frequent me semble t'il).
J'ai installé "Whocrashed" pour savoir d'ou ça viendrait.
Voici le rapport:
On Mon 18/11/2013 10:41:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111813-16473-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880032F7180, 0x6)
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 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 Mon 18/11/2013 10:41:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x5DEA8)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880032F7180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.65
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.65
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 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 331.65 , NVIDIA Corporation).
Google query: NVIDIA Corporation CLOCK_WATCHDOG_TIMEOUT
Auriez vous une idée pour corriger ça?
Merci.
4 réponses
-
Apres avoir regarder pas mal de paramètres (températeures, fréquences etc...)
J'ai vu grâce a un soft d'intel: (utilitaire d'identification de processeur INTEL) que mon processeur était overclocké (alors que je n'ai jamais essayer de faire ça).
J'ai donc baissé le % de processeur utilisé via l'utilitaire windows
Panneau de configuration
Matériel et audio
Options d'alimentation
modifier parametre du mode (usage normal par exemple)
Modifier parametre d'alimentation avancé
Gestion de l'alimentation du preocesseur
et j'ai mis 95% a etat maximal du processeur.
Relancez l'outils d'INTEL jusqu'a être repassé très légèrement en dessous du "seuil maximal" qu'il vous indique.
voila, on va voir si il persiste des erreurs
Merci a moi pour ma réponse :) -
Merci pour ta proposition Super_carotte mais le problème continue :/
-
D'accord....
Autre tentative, j'ai rollbacké la version du pilote de NVIDIA de la 331.65 à la 311.64.
On va voir si ça résout le soucis :)
(la schizophrénie a du bon, ça comble les conversations :p ) -
Après plusieurs jours sans BSOD, je déclare le patient (mon PC) guéri \o/
Le problème venait donc bien du pilote version 331.65 de Nvidia qui fait bugger mon G53.
Solution: garder pilote version 311.64
Merci à Super_carotte pour avoir résolu mon problème ! :)
Bon, après en avoir longuement parlé avec moi-même, on en est arrivé à la conclusion que l'on était pas schizophrène.
