Forum Clubic

Porbleme ecran bleu pc

Bonjour,
voila j’ai un pc qui fonctionnait jusqu’a present trés bien et j’ai du rajouté une carte graphique (MSI N210) à mon UC pour pouvoir visionner des films 3D sur ma tv 3D !
ma CM est une GIGABYTE GA-890GPA (avec chipset graphique integré).
J’ai installer ma nvelle carte graphique, installer les pilotes, et quand je duplique l’affichage tout fonctionne je vois mon film.$*LE GROS PROB : au bout de 3-4 minutes environs mon PC plante (ecran bleu) avec compte à rebours de 100 à 0 …
J’ai formaté le pc (je suis sous WIN7 integral) et TOUJOURS le meme soucis …
je ne sais pas quoi faire alors si quelqu’un a une idée ?
Merci beaucoup !!

ps : quand je dis fonctionnait tres bien c’est faux car depuis que je l’ai monté, il fait 4 bip bip bip bip au demarrage et je dois l’eteindre et le rallumer pour qu’il boot ! (lol)
mais il marche tres bien apres avoir fait reset dessuite apres les 4 “bip”
Edité le 17/02/2012 à 23:58

[Photo supprimée]

En tapant le code d’erreur j’ai trouvé ca :
microsoft

Deja merci a toi PG !
Je suis sous windows 7 integral X64 e dois installer QUEL correctif ? Il y en a une flopée !!

En haut de page tu a le lien “Accéder aux téléchargements de correctif et soumettre votre demande” Tu clique dessus et il te repère automatiquement la bonne version après il faut remplir les infos demander.

impossible de recuperer le fichier le pc plante avant …

EDIT : j’ai retiré la CG du pc et la c’est le drame : l’ecran reste noir, je n’ai plus d’affichage (alors que j’ai un chipset graphique sur ma CM) !!

Help I need somebody helllllp !

Salut,
Fait un clearcmos de ta cm ,ou retire la pile pendant quelques seconde et replace-la.
Rentre dans le bios ,ajuste la date et l’heure et, si possible ,choisit l’option démarrage par défaut .
Normalement tu devrais avoir l’affichage sur ton écran , (branche-le sur le port de ta cm !)
Essaie cela ,et on verra ensuite !
A+

j’ai suivu à la lettre tes indications et le pc parait stable ( pas de reboot apres 1h de marche) !
Par contre la CG n’est pas dans le PC hors le but est de passé un film de l’ordi sur la TV …
^^

Salut,
Maintenant réinstalle les pilotes de ta cg .
Si tout se passe bien ,il demandera de redémarrer et tu pourras utiliser ta cg.
A+

Avant de tenter quoi que ce soit et de perdre du temps à faire des choses inutiles, il serait intéressant de savoir qu’est ce qui a causé ce dumping crash.

Lorsque tu as un dumping crash, plus connu sous le nom de BSOD (Bleu Screen Of Death), Windows génère un fichier .dmp, c’est le rapport d’erreur qui te dit mot pour mot ce qui a causé le plantage. Tu trouveras ces fichiers ici : C:\Windows\Minidump

Pour lire ces rapports d’erreur il te faut le soft WhoCrashed disponible ici : www.01net.com…

Une fois installé, lance-le et clique sur le bouton en haut à gauche, Analyze. Le soft ouvrira automatiquement le fichier .dmp le plus récent.

Dis nous ce que le rapport d’erreur explique, on t’aidera à régler le problème très facilement, sans que tu n’aies à bidouiller aveuglément dans ton PC, car dans presque tous les cas, les dumping crash ne sont pas la cause d’un problème matériel, mais d’un problème software.
Edité le 22/02/2012 à 12:29

Voici le rapport d’erreur :

System Information (local)

computer name: PADRÉ
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon™ II X4 640 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 3757236224 total
VM: 2147352576, free: 1971355648


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 21/02/2012 19:00:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x7FEF9D75C95)
Bugcheck code: 0x19 (0x22, 0xFFFFFA8003F94000, 0x0, 0x0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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: Unknown .
Google query: Unknown BAD_POOL_HEADER

On Tue 21/02/2012 18:01:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022112-14227-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 20/02/2012 19:29:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-13884-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 20/02/2012 19:22:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-16052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 20/02/2012 18:42:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-16801-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Mon 20/02/2012 18:30:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-17503-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x23571)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 which cannot be identified at this time.

On Mon 20/02/2012 18:22:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-18267-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880056859C8, 0xFFFFF88005685220, 0xFFFFF80002FB790D)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.

On Mon 20/02/2012 18:18:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-17643-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x19 (0x22, 0xFFFFF8A00889D000, 0x1, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 19/02/2012 20:19:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022012-13915-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41284, 0xFFFFF98002EBA001, 0xB7F, 0xFFFFF780C0000000)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 19/02/2012 15:47:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021912-15600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC0105, 0xFFFFF8800295DCD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.

On Sun 19/02/2012 10:13:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021912-15553-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 19/02/2012 10:02:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021912-15163-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ECFD97, 0xFFFFF880054BE050, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.

On Sun 19/02/2012 09:50:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021912-15771-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F8678C, 0xFFFFF88009B9CFA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.

On Sun 19/02/2012 09:42:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021912-15490-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xF2A36)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F44A36, 0xFFFFF880031168A8, 0xFFFFF88003116100)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 19/02/2012 09:33:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021912-19422-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EDA478, 0xFFFFF88006E51F50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


Conclusion

44 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

unknown

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 actually 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.


ps : losrque je vais ds gestionnaire des peripheriques j'ai un "?" jaune a coté du periph usb et quand je fais click droit - mettre à jour le pilote window n'y parvient pas.

44 dumping crash… Il a subit ces trois derniers jours le pauvre ! Bon, ça ne semble pas être un problème matériel d’après ce qui est dit, c’est déjà ça. Tu vois que c’était inutile d’aller bidouiller les composants.

Alors, ce que tu vas faire :

1. Dans un premier temps, tu vas supprimer tout le contenu du dossier Minidump, on va éviter à chaque fois d’avoir 500 rapports d’erreur. On a une copie des précédents ici, ça nous suffit.

2. Tu vas désinstaller proprement les pilotes de ta carte graphique et tu vas vider le temp de Windows (dans le champs de recherche du menu démarrer tu tapes %temp% et tu valides). Tu vides tout le contenu du dossier, et tu ignores ce qui doit être ignoré au moment de la confirmation. Ce n’est pas ça qui va résoudre notre problème mais au moins ça sera un peu plus propre.

3. Tu lances Windows Update et tu télécharges et installe toutes les mises à jour qu’il te propose, sans exception. Si tu as des échecs, tu recommences.

4. Tu reboots ton PC. Si tu as un nouveau dumping crash, tu mets le rapport d’erreur à la suite de ce message, parce que là il y a en a trop, et beaucoup sont probablement erronés vu que tu as bidouillé pas mal de choses entre temps.

Pour ce qui est du ? n’y prête pas attention, ce n’est pas là la cause de ton soucis. Je l’ai aussi moi et tout fonctionne, tu sais Windows, hein… bon.

Je continue de regarder, à tout de suite.

PS. Il me semble que ton Seven soit en version 64bits, tu peux me confirmer s’il te plait ? (dans le champs de recherche du menu démarrer, tu tapes dxdiag, dans le premier onglet “Système” à la ligne “Système d’exploitation”) Je crois peut-être savoir d’où vient le problème.
Edité le 23/02/2012 à 10:02

windows 7 integrale 64 bits (6.1) version 7600

D’accord, et as tu fais ce que je t’ai recommandé ?

Le probleme c’est que DES que je met la CG dans l’ordi il reboot au bout de 1 a 2minutes … Et je ne peux rien faire !!

Voici le nouveau rapport d’erreur apres avoir suivi a la LETTRE ce que tu m’a dis :

rash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 22/02/2012 22:49:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022212-27580-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031F30BF, 0xFFFFF880069A0F40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.

On Wed 22/02/2012 22:49:02 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031F30BF, 0xFFFFF880069A0F40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.


Conclusion

2 crash dumps have been found and analyzed.
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 actually 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.
Edité le 23/02/2012 à 00:00

Salut.

A présent installe ces pilotes là : www.nvidia.fr… (tu ne reboot pas après l’installation) Maintenant t’es à jour à ce niveau là, mais notre soucis ne se trouve pas ici.

Il semble que le problème vient de ntoskrnl.exe (Windows Boot-Up Kernel) qui à l’air d’être corrompu. Manque de bol c’est un processus qui sert au démarrage de Windows, et il déconne lorsque tu utilises ta carte graphique (et ses pilotes). On va donc en créer un tout neuf et gicler celui là.

Il va falloir que tu procèdes à une réparation du système en créant un disque comme indiqué ici : www.forum-seven.com…

Ou alors si tu disposes sur CD d’installation de Windows 7, insère-le dans ton lecteur, redémarre le PC et boot dessus. Lorsque tu arriveras sur l’interface d’installation, tu auras un lien en bas à gauche de la fenêtre, Réparer l’ordinateur. Clique dessus et laisse-le faire.

Reboot et redonne moi le nouveau rapport d’erreur s’il y a un encore un dumping crash (les anciens tu peux les supprimer on a la copie ici)

Je ne te garantie pas à 100% que ça fonctionne, parce que l’informatique des fois il ne faut pas chercher à comprendre, mais en tout cas c’est en bonne voie.

Bonne chance !

PS. Fait toutes ses manipulations sans ta carte graphique de connecté, si ça reboot tout seul lorsqu’elle est dedans. Mais une fois tout terminé, remet la.
Edité le 23/02/2012 à 10:03

ces peut etre possible que la carte graphine ne soit pas complement compatible avec son pc

[Photo supprimée]

voila le message que j’ai quand je veux restaurer !

EDIT : si je veux installer le pilote, je dois OBLiGATOIrEMeNT mettre la CG en place mais des que je la met le pc plante …
Edité le 23/02/2012 à 23:25

Apres restauration c’est le nouveau rapport :

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 23/02/2012 22:09:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022312-24289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031A4F8C, 0xFFFFF88005F397F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.

On Thu 23/02/2012 22:09:23 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetStreamHandleContext+0x638)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031A4F8C, 0xFFFFF88005F397F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.

Conclusion

2 crash dumps have been found and analyzed.
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 actually 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.