Bonjour,
Voici mon gros soucis, mon xp plante et j'ai pas compris ou est le pb exactement.
Est que c'est un pb matériels ou logiciels/pilotes ?
Pour trouver le responsable, j'ai utiliser WhoCrashed mais j'ai pas compris!!! Apparemment il y a plusieurs pbs mais le quel est le resp.
est ce qu'il y a qlq1 qui peut m'aider.
Voila une partie du résultat de l'analyse:
On Tue 20/01/2009 11:16:00 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF816AC5, 0xEDE0DBBC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 19/01/2009 17:40:30 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000000A (0xEC09, 0x1C, 0x0, 0x804E1637)
Error: Unknown
file path: C:\WINDOWS\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 19/01/2009 11:05:19 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000C5 (0x4, 0x2, 0x1, 0x805515A1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 19/01/2009 11:01:03 your computer crashed
This was likely caused by the following module: klif.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80551AE2, 0xF7D91BA4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\klif.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Klif Mini-Filter fre_wnet_x86
On Sun 18/01/2009 15:12:34 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x805519E9, 0xEDE49120, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 18/01/2009 14:19:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFD9C4, 0x1C, 0x1, 0x804E1630)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 18/01/2009 13:46:55 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x805519E9, 0xEE4615A8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 12/01/2009 20:31:58 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Noyau et système NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
Merci d'avance