Re: Plantage après l'installation d'un pilote
le 05 Fév 2015 21:32
Voila je viens de faire un scan aucun virus sur mon ordi et j'ai utilisé WhoCrashed
Résultat :
computer name: EMILIEN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: HP Pavilion g7 Notebook PC, Hewlett-Packard, 1844
CPU: GenuineIntel Intel(R) Pentium(R) CPU B980 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4179918848 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 02/02/2015 19:36:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-14788-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF8000317A42C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 02/02/2015 19:36:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64!hybDriverEntry+0x5968B)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF8000317A42C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel Graphics Accelerator Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL
On Mon 02/02/2015 19:34:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020215-13696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800031B042C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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
--------------------------------------------------------------------------------
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:
igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
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.
Je me demande donc si ça ne vient pas pas d'un de mes composants