Mon ordinateur redémarre après la veille et le démarrage

[Ocalec]

Bonjour, j'ai acheté mon ordinateur il y a 6 mois bientôt et en ce moment il commence à beaucoup ralentir : démarrage plus long (écran noir environ 10 secs) et pareil pour la sortie de veille. Mais là n'est pas le problème puisque maintenant il se met à redémarrer à chaque sorties de veille ou à chaque démarrages ... Il y a quelques jours j'ai eu un écran bleu avec "WDF_VIOLATION" qui maintenant n’apparaît plus.

PS :Mon antivirus c'est Norton mais j'avais Avast avant qui est maintenant désinstallé.

Voilà en espérant que vous pourriez m'aider et d'ailleurs je suis pas très bon en informatique donc je connais pas toutes les abréviations et tout ^^'

[EinsteinZero]

Bonjour et bienvenue
pour commencer, on va interroger un peu ton écran bleu avec un logciciel, sans installation, d'analyse
ensuite on verra....

télécharge whocrashed >>ici sur External mirror 1<<

lance le logiciel et fait un copier-coller de son rapport sur ton prochain message
On saura alors, peut-être, s'il y a un souci matériel
Si c'est cela, ce sera direction service après vente car le PC n'a pas 1 an

[Ocalec]

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

computer name: THOMAS-PC
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: HP ENVY 17 Notebook PC, Hewlett-Packard, 1968
CPU: GenuineIntel Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8518656000 total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 14/05/2015 09:46:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051415-18484-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE000F01EB9E0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 Thu 14/05/2015 09:46:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: syntp.sys (SynTP+0x1A6BC)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE000F01EB9E0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\syntp.sys
product: Synaptics Pointing Device Driver
company: Synaptics Incorporated
description: Synaptics Touchpad Driver
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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: syntp.sys (Synaptics Touchpad Driver, Synaptics Incorporated).
Google query: Synaptics Incorporated WDF_VIOLATION



On Thu 14/05/2015 08:35:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051415-20078-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE001497000F0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 13/05/2015 19:19:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051315-30484-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE000399D65A0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 13/05/2015 15:36:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051315-26078-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE00109DD6010)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 12/05/2015 18:34:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051215-20359-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE000E0F9E7A0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 12/05/2015 17:22:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051215-23828-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE001C9EE69A0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 Mon 11/05/2015 19:02:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051115-20140-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE000B9227860)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 Mon 11/05/2015 15:59:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051115-28468-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE001005387E0)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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 Sun 10/05/2015 18:53:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051015-28250-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x75CAA)
Bugcheck code: 0x10D (0x5, 0x0, 0x1200, 0xFFFFE000DC21AC20)
Error: WDF_VIOLATION
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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.





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

14 crash dumps have been found and analyzed. Only 10 are included in this report. 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 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.

[webdesigner]

Cela semble venir d'un problème matériel

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

Le chargement des pilotes lors du démarrage cause un problème, si tu n'avais pas se problème avant, identifie le dernier matériel ou périphérique que tu as branché, une fois identifié réalise une mise à jour de celui-ci sinon vérifie que l'ensemble des pilotes sont à jour si tu n'arrivas pas à trouver le composant causant le problème.

Au pire des cas cela peu venir d'un virus.

[routman54]

Bonjour ,
Mon anglais étant limité j'ai vérifié avec Bing translator , ce n'est pas du à un problème matériel
Par contre il y a de fortes chances que ce soit un pilote , donc tu peux te rendre sur Ma config qui après analyse va te donner les pistes et pilotes à télécharger .
Bonne continuation .

[Ocalec]

Merci beaucoup tout le monde, je pensais pas avoir des réponses aussi rapidement ^^

[webdesigner]

Bonjour ,
Mon anglais étant limité j'ai vérifié avec Bing translator , ce n'est pas du à un problème matériel
Par contre il y a de fortes chances que ce soit un pilote , donc tu peux te rendre sur Ma config qui après analyse va te donner les pistes et pilotes à télécharger .
Bonne continuation .

software driver bug

caused by hardware problem

Le problème vient du pilote causé par la matériel cela va veut dire la même chose que se que tu viens de dire

[EinsteinZero]

Merci beaucoup tout le monde, je pensais pas avoir des réponses aussi rapidement ^^

Certes ici il n'y a que des bénévoles... mais, quand le travail pro n'est pas trop "prenant" on est souvent là

donc, comme le signal mes comparses, il s'agit à priori d'un souci de pilote, je pense au niveau du touchpad

donc , la première chose à tenter est une mise à jour du pilote

ensuite, si le souci perdure 2 possibilités probables

1> un élément logiciel en mémoire interfère....possibilité d'un virus

2> le touchpad est peut-être défectueux alors:
----> pour test: branche une souris et désactive le touchpad pour voir si la machine est stable
----> si le PC est alors stable sans souci, comme la machine est sous garantie... je signalerai le souci au SAV