Salut, j'ai un problème avec mon ordinateur, il plante tout seul d'un seul coup, il me l'a fait là il y a environs 10 minutes.
Le truc bizarre, c'est que ce problème je l'avais eu même il y a de ça plusieurs mois, j'ai depuis changé de disque dur et le problème recommence... Là ça me l'a fait tout à l'heure mais il n'avait plus planté anormalement depuis environs 2 semaines et il recommence aujourd'hui...
J'ai regardé dans "Observateur d'événements" et il y a ce message d'erreur :
Et aussi ça :
Y'a aussi quelques autres erreurs...
Voici un rapport (copié/collé) du logiciel "WhoCrashed"
Si quelqu'un peut m'aider
Welcome to WhoCrashed (HOME EDITION) v 5.03
--------------------------------------------------------------------------------
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 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 allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ALI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A77TD PRO
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4292988928 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 01/01/2015 13:56:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010115-13774-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1DFE)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880010EBDFE, 0x0, 0xFFFFFA80073EE400)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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/01/2015 13:56:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltAcquirePushLockShared+0x69E)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880010EBDFE, 0x0, 0xFFFFFA80073EE400)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
J'ai testé ma ram avec memtest et apparemment ça ne vient pas de ma barrette de ram puisque je suis allé jusqu'au pass 7 et aucune erreur (6h environs)
vire avira et met t'es drivers a jour
Fltmgr.sys est un pilote Windows. Un pilote est un petit logiciel qui permet à votre ordinateur de communiquer avec du matériel ou des périphériques branchés. Cela signifie qu'un pilote a un accès direct à la partie interne du SE, du matériel, etc.
Notre forum vous permet de trouver des informations sur fltmgr.sys afin de savoir si c'est un virus, troyen, spyware, espiongiciel afin de le supprimer, ou si c'est un fichier système de Windows ou une application de confiance.
sinon test ceci
1.Démarrez l'Éditeur du Registre.
2.Développez la sous-clé de Registre suivante :
HKEY_LOCAL_MACHINE\SOFTWARE\Softricity\SoftGrid Client\CurrentVersion\AppFS
3.Double-cliquez sur l'entrée de Registre de nom de fichier ..
4.Dans la boîte de dialogue Modification de la chaîne , notez le chemin d'accès dans la zone données de la valeur ..
5.Dans la boîte de dialogue Modification de la chaîne , cliquez sur Annuleret quittez l'Éditeur du Registre.
6.Démarrez l'Explorateur Windows et recherchez le chemin d'accès que vous avez noté à l'étape 4.
7.Vérifiez que le chemin d'accès existe. Si le chemin d'accès n'existe pas, créez le chemin d'accès ou modifier la valeur de l'entrée de Registre de nom de fichier pour faire correspondre le chemin d'accès réel.
8.Quittez l'Explorateur Windows et puis démarrez le service SoftGrid Client.
liens http://www.forum-seven.com/forum/topic13510.html
Avira je l'utilise depuis longtemps je connais pas d'antivirus gratuit mieux qu'Avira
bas fait comme tu veut, mais c'et lui fou la merde