plantage pc
plantage pc
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.
concernat les pilotes si tu parle des pilotes par defaut que vista utilise (carte mere, carte graphique) change les par ceux des sites constructeurs.claudio a écrit :Bonjour,
j'ai laissé mettre a jour vista tous les pilotes.
le pc plante prinicpalement quand je regarde un film en streaming sur internet ou alors quand les engants deroulent des jeux en reseaux sur internet.
merci de ton aide.
si tu a une cg nvidia va sur le site nvidia pour instalé tes pilotes.
idem pour la carte mere.
autre solution tu peux essayer une restauration du systeme a une date anterieur a ta mise a jour.(tous les programmes--accessoire--outil systeme)
c'est ce que j'ai fait en allant sur chanque site construteurs a partir duquel j'ai fait les mises a jours pour la carte graphique. je n'ai pas fait de montee de version du bios de la carte mere.
je viens en plus d'avoir un plantage avec le message :
c:/ windows / systeme 32/browseuil. dll/ n'est pas concu pour fonctionner sous windows. et le pc a reboote tout seul.
a te lire.
je viens en plus d'avoir un plantage avec le message :
c:/ windows / systeme 32/browseuil. dll/ n'est pas concu pour fonctionner sous windows. et le pc a reboote tout seul.
a te lire.
Re: plantage pc
j'ai fini par trouver.
c'est l'alimentation qui n'etait pas assé puissante.
je l'ai remplacée par une alimentation crosair TX 650 w et depuis je n'ai plus aucun problemes.
merci a tous pour votre aide.
c'est l'alimentation qui n'etait pas assé puissante.
je l'ai remplacée par une alimentation crosair TX 650 w et depuis je n'ai plus aucun problemes.


merci a tous pour votre aide.
- k-e-n-2
- Overclockeur
- Messages : 1632
- Enregistré le : 26 nov. 2008, 00:00
- Localisation : Bruxelles, Belgique
Re: plantage pc

quelle était ton alimentation??
Celle de maintenant te permettra de futurs upgrades

- sabreoclair
- Assembleur de configs
- Messages : 7711
- Enregistré le : 28 mars 2008, 00:00
Re: plantage pc
c'était la marque préférée desk-e-n-2 a écrit : quelle était ton alimentation??

une ADVANCE 450 W
- k-e-n-2
- Overclockeur
- Messages : 1632
- Enregistré le : 26 nov. 2008, 00:00
- Localisation : Bruxelles, Belgique
Re: plantage pc
Voilà pourquoi il ne faut pas faire le radin avec l'alimsabreoclair a écrit :c'était la marque préférée desk-e-n-2 a écrit : quelle était ton alimentation??
![]()
une ADVANCE 450 W

Re: plantage pc
désolé mais c'est ce que mettait NEC quand j'ai acheté mon pc avec un athlon 1900+
maintenant j'ai une config a jour
a+
cl
maintenant j'ai une config a jour
a+
cl
Re: plantage pc
bonjour,
moi aussi j'ai le même problème depuis quelques jours, mon écran s'éteint tout seul, ou c'est la souris qui se bloque avec un bruit bizarre et j'ai eue aussi un écran bleu ce matin avec des messages en anglais.
cela se produit quand je joue au jeu farmville sur facebook.
moi aussi j'ai le même problème depuis quelques jours, mon écran s'éteint tout seul, ou c'est la souris qui se bloque avec un bruit bizarre et j'ai eue aussi un écran bleu ce matin avec des messages en anglais.
cela se produit quand je joue au jeu farmville sur facebook.