ordinateur portable qui s'éteint et se rallume tout seul

[Malbar15]

Bonjour à tous. 
Depuis quelques jours j'ai un problème assez frustrant avec mon ordinateur. Il s'éteint et se rallume tout seul. Avant qu'il ne s'éteigne il me prévient (pas mal élevé le pc portable quand même LoL). En gros ça dit : votre ordinateur a rencontré un problème et doit redémarrer.
Je suis souvent sur internet et je n'installe pas grand chose comme logiciel. Une utilisation banale quoi. 
Quelqu'un pourrait m'aider à trouver une solution please ? je vous en serais très reconnaissant. 
Merci

[EinsteinZero]

Bonsoir et bienvenue
si le message est accompagné d'un écran Bleu, télécharge whocrashed >>ici sur external mirror 1<<
lance le logiciel qui est sans installation
et poste par un copié collé son rapport
nous aurons alors quelques élément qui donneront peut-être une piste

[Malbar15]

Merci beaucoup pour ton aide.

J'ai fais ce que tu m'as dis.
Je ne savais pas trop quoi te fournir comme informations, alors j'ai tout copier pour ne rien manquer. J'espère que cela ne t'embêtera pas trop.

PS : VRAIMENT MERCI DE BIEN VOULOIR M'APPORTER TON AIDE. C'EST VRAIMENT TRES AIMABLE.



Voilà le résultat :

System Information (local)
--------------------------------------------------------------------------------

computer name:
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: HP Pavilion g7 Notebook PC, Hewlett-Packard, 184B
CPU: AuthenticAMD AMD A4-4300M APU with Radeon(tm) HD Graphics AMD586, level: 21
2 logical processors, active mask: 3
RAM: 3726909440 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 21/03/2015 12:04:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032115-45021-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x13D744)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001C1C744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Sat 21/03/2015 12:04:43 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x1FCD)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001C1C744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\aswtdi.sys
product: avast! Antivirus
company: AVAST Software
description: avast! TDI Filter Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: AVAST Software DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 20/03/2015 13:21:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032015-34913-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x13D744)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001B91744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Fri 20/03/2015 12:42:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032015-43867-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x13D744)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001C08744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Fri 20/03/2015 12:35:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032015-74131-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x13D744)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001B90744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Wed 18/03/2015 15:45:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031815-47892-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x13D744)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001BEF744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Wed 18/03/2015 14:30:27 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031815-40778-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x13D744)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001B84744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Wed 18/03/2015 13:39:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031815-50279-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x13D744)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001B72744)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Tue 17/03/2015 15:39:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031715-118357-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1381E3)
Bugcheck code: 0xD1 (0x158, 0x2, 0x1, 0xFFFFF88001BB21E3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard 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.



On Wed 11/03/2015 14:18:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031215-83476-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153836)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00197813880, 0xFFFFF80257A84900)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

10 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:

aswtdi.sys (avast! TDI Filter Driver, AVAST Software)

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.

[EinsteinZero]

Bonsoir
le fichier système TCIP.sys revient majoritairement dans les plantages, il est peut-être corrompu
ceci dit, le souci peut apparaitre si un disque dur est défectueux ou un conflit avec un virus

commençons par voir les disque dur.... télécharge CristalDiskinfo Portable >>ici<<... si son bilan n'est pas sur correct, le disque dur est peut-être la cause du souci

sinon, sous quelle version de windows est ta machine ?

[Malbar15]

Je suis sous Windows 8.

[Malbar15]

Je ne sais pas pourquoi mais je n'arrive pas à joindre une photo du rapport.
Ca dit : Etat de santé (voyant orange) : PRUDENCE
Température : 48°C

[routman54]

Bonjour ,
Je te mets un lien vers un Huit à télécharger ( lien qui fonctionne encore ) si cela s'avère nécessaire .
Si le résultat de Crystaldiskinfo te dit correct , je pense que mon ami EZ te demandera de télécharger ce fichier et de t'en servir pour réparer .
Ton disque dur est malade il va falloir le changer , tu peux en racheter un et essayer de cloner le tien tant que cela fonctionne .
Lien > ICI < , avec mes excuses je l'avais pas mis .
Bonne continuation .

[Malbar15]

Merci encore pour ton aide.
Bonne continuation à toi aussi.

[EinsteinZero]

Re
Prudence...ça veut dire que le disque dur a potentiellement un souci...cela pourrait être la cause du problème

donc...je crains qu'il ne faille, pour commencer songer à remplacer le disque dur

--> ça veut dire faire une image du système (si ça ne plante pas) pour la cloner sur un nouveau disque ou réinstaller 8 sur un nouveau disque avec l'image de routman