Ecran bleu MEMPORY_MANAGEMENT windows 7
Fermé
nanouj39
Messages postés
4
Date d'inscription
vendredi 10 août 2012
Statut
Membre
Dernière intervention
12 août 2012
-
10 août 2012 à 22:17
nanouj39 Messages postés 4 Date d'inscription vendredi 10 août 2012 Statut Membre Dernière intervention 12 août 2012 - 12 août 2012 à 19:50
nanouj39 Messages postés 4 Date d'inscription vendredi 10 août 2012 Statut Membre Dernière intervention 12 août 2012 - 12 août 2012 à 19:50
A voir également:
- Ecran bleu MEMPORY_MANAGEMENT windows 7
- Double ecran - Guide
- Retourner ecran windows - Guide
- Écran bleu - Guide
- Passer de windows 7 à windows 10 - Guide
- Capture d'écran windows - Guide
4 réponses
nanouj39
Messages postés
4
Date d'inscription
vendredi 10 août 2012
Statut
Membre
Dernière intervention
12 août 2012
10 août 2012 à 22:30
10 août 2012 à 22:30
Bonjour,
L'écran bleu apparait n'importe quand... y'a pas de règle.
L'écran bleu apparait n'importe quand... y'a pas de règle.
nanouj39
Messages postés
4
Date d'inscription
vendredi 10 août 2012
Statut
Membre
Dernière intervention
12 août 2012
11 août 2012 à 23:18
11 août 2012 à 23:18
Nouveau écran bleu avec nouvelle erreur : cette fois j'ai un compte rendu de whocrashed qui est le suivant :Crash
Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 11/08/2012 19:08:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081112-14773-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00D9F7890, 0xFFFFF8A00D9F7810, 0xFFFFF8A00D9F7890)
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 Sat 11/08/2012 19:08:02 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x955D)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00D9F7890, 0xFFFFF8A00D9F7810, 0xFFFFF8A00D9F7890)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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 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 Sat 11/08/2012 14:54:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081112-23181-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFF900C0083F10)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.
qu'est ce que ça veut dire?
Merci par avance
Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 11/08/2012 19:08:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081112-14773-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00D9F7890, 0xFFFFF8A00D9F7810, 0xFFFFF8A00D9F7890)
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 Sat 11/08/2012 19:08:02 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x955D)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A00D9F7890, 0xFFFFF8A00D9F7810, 0xFFFFF8A00D9F7890)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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 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 Sat 11/08/2012 14:54:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081112-23181-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFF900C0083F10)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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
3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.
qu'est ce que ça veut dire?
Merci par avance
12 août 2012 à 19:50