plantage pc
Posté : 24 avr. 2010, 18:08
Bonjour, j'ai des plantages systematiques. aussi j'ai installé "whocrashed home edition" ci dessous le resultat de l'analyse.
Pouvez vous me donner le mode opératoire pour traiter les problems merci.
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. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 24/04/2010 07:25:26 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x867A4020, 0x867A416C, 0x81C60710)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini042410-01.dmp
file path: C:\Windows\system32\csrss.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Processus d'exécuttion client-serveur
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 18/04/2010 07:37:30 your computer crashed
This was likely caused by the following module: classpnp.sys
Bugcheck code: 0x7A (0xC04409D8, 0xC000000E, 0x29AB48C0, 0x8813B010)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\Windows\Minidump\Mini041810-01.dmp
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 07/04/2010 20:07:52 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x86471780, 0x864718CC, 0x81C32650)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini040710-01.dmp
file path: C:\Windows\system32\csrss.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Processus d'exécuttion client-serveur
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 20:39:44 your computer crashed
This was likely caused by the following module: wininit.exe
Bugcheck code: 0xF4 (0x3, 0x864175F8, 0x86417744, 0x81C6E650)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini040310-02.dmp
file path: C:\Windows\system32\wininit.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Application de démarrage de Windows
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 09:48:45 your computer crashed
This was likely caused by the following module: msrpc.sys
Bugcheck code: 0x7A (0xC043AC10, 0xC000000E, 0x79E5E860, 0x87582234)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\Windows\Minidump\Mini040310-01.dmp
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Tue 30/03/2010 16:50:43 your computer crashed
This was likely caused by the following module: wininit.exe
Bugcheck code: 0xF4 (0x3, 0x85A204A8, 0x85A205F4, 0x81C3E650)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini033010-01.dmp
file path: C:\Windows\system32\wininit.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Application de démarrage de Windows
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
Pouvez vous me donner le mode opératoire pour traiter les problems merci.
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. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 24/04/2010 07:25:26 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x867A4020, 0x867A416C, 0x81C60710)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini042410-01.dmp
file path: C:\Windows\system32\csrss.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Processus d'exécuttion client-serveur
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sun 18/04/2010 07:37:30 your computer crashed
This was likely caused by the following module: classpnp.sys
Bugcheck code: 0x7A (0xC04409D8, 0xC000000E, 0x29AB48C0, 0x8813B010)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\Windows\Minidump\Mini041810-01.dmp
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Wed 07/04/2010 20:07:52 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x86471780, 0x864718CC, 0x81C32650)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini040710-01.dmp
file path: C:\Windows\system32\csrss.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Processus d'exécuttion client-serveur
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 20:39:44 your computer crashed
This was likely caused by the following module: wininit.exe
Bugcheck code: 0xF4 (0x3, 0x864175F8, 0x86417744, 0x81C6E650)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini040310-02.dmp
file path: C:\Windows\system32\wininit.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Application de démarrage de Windows
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Sat 03/04/2010 09:48:45 your computer crashed
This was likely caused by the following module: msrpc.sys
Bugcheck code: 0x7A (0xC043AC10, 0xC000000E, 0x79E5E860, 0x87582234)
Error: KERNEL_DATA_INPAGE_ERROR
Dump file: C:\Windows\Minidump\Mini040310-01.dmp
file path: C:\Windows\system32\drivers\msrpc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Remote Procedure Call Provider
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
On Tue 30/03/2010 16:50:43 your computer crashed
This was likely caused by the following module: wininit.exe
Bugcheck code: 0xF4 (0x3, 0x85A204A8, 0x85A205F4, 0x81C3E650)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\Mini033010-01.dmp
file path: C:\Windows\system32\wininit.exe
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Application de démarrage de Windows
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.