Pc portable qui plante sans raison

[Draper]

Bonjour, depuis quelques temps mon Toshiba plante sans raison, je ne voit pas de fenêtre bleue ou quoi que ce soit, mon pc freeze et je ne peut que le redémarrer, ctrl alt suppr ne fonctionne pas rien à faire, j'aurais aimé votre aide, je suis sur windows 7 x64bits
J'ai le rapport d'erreur suivante pour un arrêt non planifié de windows :

Signature du problème
Nom d’événement du problème : BlueScreen
Version du système: 6.1.7600.2.0.0.768.3
Identificateur de paramètres régionaux: 1036

Informations complémentaires sur le problème
BCCode: 101
BCP1: 0000000000000031
BCP2: 0000000000000000
BCP3: FFFFF88003163180
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Merci d'avance

[EinsteinZero]

Bonjour

comme le message mentionne un écran bleu (même si tu ne l'as pas vu) windows a peut-être eu le temps de créer un fichier d'erreur.

télécharge Wohcrashed >>ici (external mirror 1)<<

installe et lance le programme puis poste son rapport (copier -coller) s'il trouve des choses

on en saura alors peut-être un peu plus pour avoir une piste.

[Draper]

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 28/06/2011 07:58:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062811-18938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003163180, 0x2)
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 which cannot be identified at this time.


On Tue 28/06/2011 07:58:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk!?DispatchPassThrough@DEVICEDISPATCH@@CAJPEAU_DEVICE_OBJECT@@PEAU_IRP@@@Z+0xA9)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003163180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE.14.0.0.351.x64
company: McAfee, Inc.
description: Host Intrusion Detection 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 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: mfehidk.sys (Host Intrusion Detection Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. CLOCK_WATCHDOG_TIMEOUT




On Tue 28/06/2011 07:25:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062811-20264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002F63180, 0x2)
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 which cannot be identified at this time.


On Tue 28/06/2011 06:51:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062811-24632-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003163180, 0x2)
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 which cannot be identified at this time.


Voila ce que je trouve !

[EinsteinZero]

Bonsoir

Cause du pb...
Le contrôle de bogue CLOCK_WATCHDOG_TIMEOUT indique que une interruption d'horloge prévu sur un processeur secondaire, dans un système multi-processeur, n'a pas été reçu dans l'intervalle alloué.

c'est toujours la même panne avec une grande régularité de structure

> Soit un problème de pilote est à l'origine du problème (j'y crois pas trop)
> Soit un problème matériel est à l'origine des ennuis (chipset ou processeur)

si tu n'a installé aucun matériel particulier juste avant l'apparition du problème, je crains le gros pb matériel

Dans ce cas, si le PC est sous garantie, sauvegarde tes données et contacte le SAV.