Nettoyer un PC Toshiba Satellite C870-145

[Vanessa262003]

Bonjour à tous,

 

Mon pc Toshiba refaisant des siennes côté alerte de surchauffe, j'ai voulu l'ouvrir pour nettoyer le ventilo.

Sauf que je n'ai pas réussi, malgré toute les vis enlevées rien!

Hier j'ai eu un écran bleu :

 

 

 

Signature du problème :

Nom dévénement de problème: BlueScreen

Version du système: 6.1.7601.2.1.0.768.3

Identificateur de paramètres régionaux: 1036

Informations supplémentaires sur le problème :

BCCode: 5

BCP1: FFFFFA8003FB99E0

BCP2: FFFFFA80092B6B30

BCP3: 0000000000000000

BCP4: 0000000000000001

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

Fichiers aidant à décrire le problème :

C:\Windows\Minidump\072214-36348-01.dmp

C:\Users\Utilisateur\AppData\Local\Temp\WER-68422-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne nest pas disponible, lisez la version hors connexion :

C:\windows\system32\fr-FR\erofflps.txt

 

 

J'ai fait un test avec "whocrashed" qui a donné ce résultat :

 

 

computer name: UTILISATEUR-PC

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

windows dir: C:\windows

Hardware: SATELLITE C870-145, TOSHIBA, Type2 - Board Vendor Name1, Type2 - Board Product Name1

CPU: GenuineIntel Intel® Pentium® CPU B950 @ 2.10GHz Intel586, level: 6

2 logical processors, active mask: 3

RAM: 4179419136 total

 

 

 

 

Crash Dump Analysis

 

 

Crash dump directory: C:\windows\Minidump

 

Crash dumps are enabled on your computer.

 

On Tue 22/07/2014 15:40:26 GMT your computer crashed

crash dump file: C:\windows\Minidump\072214-36348-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

Bugcheck code: 0x5 (0xFFFFFA8003FB99E0, 0xFFFFFA80092B6B30, 0x0, 0x1)

Error: INVALID_PROCESS_ATTACH_ATTEMPT

file path: C:\windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).

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 22/07/2014 15:40:26 GMT your computer crashed

crash dump file: C:\windows\memory.dmp

This was probably caused by the following module: syntp.sys (SynTP+0x3B9FB)

Bugcheck code: 0x5 (0xFFFFFA8003FB99E0, 0xFFFFFA80092B6B30, 0x0, 0x1)

Error: INVALID_PROCESS_ATTACH_ATTEMPT

file path: C:\windows\system32\drivers\syntp.sys

product: Synaptics Pointing Device Driver

company: Synaptics Incorporated

description: Synaptics Touchpad 64-bit Driver

Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).

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: syntp.sys (Synaptics Touchpad 64-bit Driver, Synaptics Incorporated).

Google query: Synaptics Incorporated INVALID_PROCESS_ATTACH_ATTEMPT

 

 

 

 

Conclusion

 

 

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

 

syntp.sys (Synaptics Touchpad 64-bit Driver, Synaptics Incorporated)

 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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.

 

 

Suite à l'écran bleu il a redémarré sans souci depuis. Hier j'avais eu un message d'erreur (avant l'écran bleu) mais je n'ai pas pensé à le noter mais c'était ce genre de message "a problem with the cooling system has been detected[/size]

Please turn off the computer immediately, and return it for service"[/size]... et suite à ce message où j'ai cliqué sur ok, le ventilo s'est mis à tourner à pleine vitesse et le bruit allant avec. En l'éteignant le bruit s'est calmé.

J'avais déjà eu ce souci quelques mois à peine après son achat, je l'avais alors renvoyé en SAV où il m'avait changé le DD et dit qu'il était poussiéreux d'où pourquoi je voulais l'ouvrir

 

Je vous ai pris quelques photos du capot peut être arriverez vous à m'aider à trouver comment ouvrir ce pc, à croire qu'ils l'ont collé ptdr

http://i39.servimg.com/u/f39/18/87/42/80/capot_10.jpg

http://i39.servimg.com/u/f39/18/87/42/80/wp_20110.jpg

http://i39.servimg.com/u/f39/18/87/42/80/wp_20111.jpg

 

Merci d'avance

[thorgal]

Bonjour et bienvenue sur le forum,

 

Regarder cette petite vidéo pour t'aider :

 

http://www.youtube.com/watch?feature=player_detailpage&v=gFKF3R-7nZg

Modifié le 23 juillet 2014 par thorgal

[Vanessa262003]

Bonjour,

 

J'ai regardé la vidéo le problème c'est que je n'ai pas de vis sous la batterie et au niveau du clavier non plus lol

Sinon ce matin j'allume mon pc, il démarre jsqu'à l'écran d'accueil et bug. J'ai eu droit à un espèce de sifflement infernal avec la souris bloqué puis paf écran bleu avec un décompte avant de redémarrer

Redémarrage sans problème, j'ai fait une analyse whocrashed voilà le rapport

 

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\windows\Minidump

 

Crash dumps are enabled on your computer.

 

On Fri 25/07/2014 08:54:52 GMT your computer crashed

crash dump file: C:\windows\Minidump\072514-35443-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

Bugcheck code: 0x5 (0xFFFFFA8003FB99E0, 0xFFFFFA8009055B30, 0x0, 0x1)

Error: INVALID_PROCESS_ATTACH_ATTEMPT

file path: C:\windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Fri 25/07/2014 08:54:52 GMT your computer crashed

crash dump file: C:\windows\memory.dmp

This was probably caused by the following module: syntp.sys (SynTP+0x3B9FB)

Bugcheck code: 0x5 (0xFFFFFA8003FB99E0, 0xFFFFFA8009055B30, 0x0, 0x1)

Error: INVALID_PROCESS_ATTACH_ATTEMPT

file path: C:\windows\system32\drivers\syntp.sys

product: Synaptics Pointing Device Driver

company: Synaptics Incorporated

description: Synaptics Touchpad 64-bit Driver

Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).

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: syntp.sys (Synaptics Touchpad 64-bit Driver, Synaptics Incorporated).

Google query: Synaptics Incorporated INVALID_PROCESS_ATTACH_ATTEMPT

 

 

 

On Tue 22/07/2014 15:40:26 GMT your computer crashed

crash dump file: C:\windows\Minidump\072214-36348-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)

Bugcheck code: 0x5 (0xFFFFFA8003FB99E0, 0xFFFFFA80092B6B30, 0x0, 0x1)

Error: INVALID_PROCESS_ATTACH_ATTEMPT

file path: C:\windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

3 crash dumps have been found and analyzed. 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:

 

syntp.sys (Synaptics Touchpad 64-bit Driver, Synaptics Incorporated)

 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

 

[vieu bison boiteu]

salut Vanessa262003

 

cela proviendrait des drivers du Touch Pad = http://support1.toshiba-tro.de/tedd-files2/0/tpdrv-20120510102122.zip

 

page générale = http://www.toshiba-windows-drivers.com/2012/06/toshiba-satellite-c870-windows-7.html

 

avec une souris optique USB , tu désinstalles le Touch Pad

tu redémarres le PC

et tu le réinstalles ( après avoir dézipé le fichier tpdrv-20120510102122.zip )

 

sous Windows 7 : Windows ( Démarrer ) => clic "droit" sur "Ordinateur" => "Gérer" => "Gestion des périphériques"

 

à+

Modifié le 25 juillet 2014 par vieu bison boiteu

[Vanessa262003]

Et quand on a pas de souris optique usb? Lol

je ne me sers que du pavé tactile

merci en tout cas pour la réponse

[thorgal]

Bonjour,

 

Trouver une souris n'est pas très compliqué. Un voisin, un ami, sinon tu en achètes une. Il y en a à moins de 10 €. Ce n'est pas excessif. Surtout si tu parviens à dépanner ton pc.

[Vanessa262003]

C'est vrai!

Sinon je viens de retrouver le compte rendu (vive les archives de conversation) du SAV du 8/5/2013 suite à ces fameux écrans bleus à l'époque...

Voilà ce qu'ils m'avaient fait :

Changement de pièces =>

- disque dur 500gb

- top cover w/touch pad

- Thermal modulé C870

- bottom case/base inf

et ils ont fait une resto complete du systeme, mise a jour windows + différent test

[thorgal]

Ce que tu peux tenter mais je ne peux pas t'assurer le résultat final, c'est de démarrer ton pc en invite de commande (touche F8 au démarrage de ton pc). Cela t'ouvre un menu dans lequel tu dois voir la ligne "invite de commande". Une fois celle-ci accessible, tu tapes chkdsk /r. Cela va faire un contrôle de ton disque dur. Il y a fort à parier qu'il connaît un problème de fonctionnement.

[Vanessa262003]

Ah oui je n'avais pas penser à le faire, je ferai ça au prochain redémarrage merci

[Vanessa262003]

Bonjour,

J'ai effectué la vérification du DD au démarrage, vu le temps que ça a pris je me suis endormie dessus donc difficile de vous dire s'il m'a détecté des erreurs lol

Pour le moment ça fonctionne, à voir sur plusieurs jours....