Tout d'abord bonne année ! (et oui on est encore le 31 donc ça passe ^^)
Voila si je viens vous voir c'est parce qu'à la suite de l'installation d'un pilote pour mes port USB 3.0 j'ai eu un premier soucis qui était que dès la mise en veille de mon PC, lorsque je le relançais, celui-ci plantait et rebootait. J'ai trouvé l'origine du soucis avec WhoCrashed en voyant l'erreur :
Error: WDF_VIOLATION
J'ai désinstallé ce pilote et la mise en veille re-fonctionne nickel je n'ai pu de cash avec cette erreur.
Par contre à la suite de cela, tous les 2/3 jours j'ai un plantage écran bleu pendant l'utilisation de mon pc (bureautique lors du problème) et j'ai l'erreur suivante:
Error: KMODE_EXCEPTION_NOT_HANDLED
J'ai lu des sujet à propos de soucis de RAM mais j'ai fais un diagnostic via une commande DOS+ redémarrage du pc et aucun soucis dedans... Je galère donc un petit peu. Je vous met ci dessous ma config (obtenu via speccy) et apres le rapport complet de Whocrashed.
ps: mon pc (enfin plutot CPU/CG/RAM et disque dur ne dépasse jamais les 30 degré même en plein jeu (BF3, far cry 3 etc...) je ne pense donc pas que c'est un problème de température. J'ai acheté ce PC en juin 2012 en sachant que la tour est une 932 HAF un modèle optimisé pour avoir de faible température. (j'ai également un ventirad coolermaster assez performant.)
Système d'exploitation
Microsoft Windows 8 Professionnel 64-bit
Processeur
Intel Core i7 3820 @ 3.60GHz 24 °C
Technologie Sandy Bridge-E 32nm
RAM
8,00 Go Canal-Double DDR3 @ 666 MHz (9-9-11-24)
Carte mère
Gigabyte Technology Co., Ltd. X79-UD3 (SOCKET 0) 23 °C
Graphiques
PL2273HDS (1920x1080@60Hz)
PL2280H (1920x1080@60Hz)
NVIDIA GeForce GTX 680
Disques durs
119 Go SAMSUNG SSD 830 Series (SSD)
932 Go Seagate ST1000DM003-9YN162 (SATA) 26 °C
Disques optiques
DTSOFT Virtual CdRom Device
HL-DT-ST DVDRAM GH22NS90
Audio
Realtek High Definition Audio
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 4.01
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit http://www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: TIMOTHÉ-PC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8540037120 total
VM: 2147352576, free: 1917652992
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 31/01/2013 18:27:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013113-10406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA80120E9869, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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.
On Thu 31/01/2013 18:27:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA80120E9869, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
On Sat 26/01/2013 00:15:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012613-6500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA8011A8593F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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.
On Sat 19/01/2013 16:57:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011913-7000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA800D40382E, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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.
On Fri 18/01/2013 22:29:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-6500-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1113)
Bugcheck code: 0x10D (0x5, 0x0, 0x1024, 0xFFFFFA80087C4590)
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 Fri 18/01/2013 22:22:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-6343-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1113)
Bugcheck code: 0x10D (0x5, 0x0, 0x1024, 0xFFFFFA80087A3010)
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 Fri 18/01/2013 22:00:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-6859-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1113)
Bugcheck code: 0x10D (0x5, 0x0, 0x1024, 0xFFFFFA800879FA60)
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 Fri 18/01/2013 20:51:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-6625-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1113)
Bugcheck code: 0x10D (0x5, 0x0, 0x1024, 0xFFFFFA80087A3E40)
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 15/01/2013 10:20:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011513-6421-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x1113)
Bugcheck code: 0x10D (0x5, 0x0, 0x1024, 0xFFFFFA8008791300)
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 13/01/2013 01:40:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011313-9718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B340)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA80124DE835, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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.
On Thu 10/01/2013 18:39:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011013-14640-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x49BA4)
Bugcheck code: 0x10D (0x8, 0x57FEF11AFD8, 0x3, 0xFFFFFA80087C5600)
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 01/11/2012 17:29:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-11546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7B040)
Bugcheck code: 0x50 (0xFFFFFFF5FFF6FFEE, 0x1, 0xFFFFF800F5F2A55A, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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 actually 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.
Si quelqu'un pouvait m'aider cela ce serait vraiment sympa
merci d'avance.
