Ecran bleu BAD_POOL_HEADER
Fermé
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
-
13 oct. 2012 à 08:48
jane1261 Messages postés 276 Date d'inscription dimanche 10 février 2008 Statut Membre Dernière intervention 3 août 2024 - 15 oct. 2012 à 19:13
jane1261 Messages postés 276 Date d'inscription dimanche 10 février 2008 Statut Membre Dernière intervention 3 août 2024 - 15 oct. 2012 à 19:13
15 réponses
antipolis a
Messages postés
15609
Date d'inscription
mercredi 5 novembre 2008
Statut
Membre
Dernière intervention
12 novembre 2014
2 859
13 oct. 2012 à 10:16
13 oct. 2012 à 10:16
Bonjour.
Voyez cette fiche pratique CCM :
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
Voyez cette fiche pratique CCM :
https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
13 oct. 2012 à 10:18
13 oct. 2012 à 10:18
Bonjour, et merci. Je vais essayer, mais j'aurais vraiment besoin que l'on me guide car je n'y comprends rien.
antipolis a
Messages postés
15609
Date d'inscription
mercredi 5 novembre 2008
Statut
Membre
Dernière intervention
12 novembre 2014
2 859
13 oct. 2012 à 10:28
13 oct. 2012 à 10:28
Lors d'un écran bleu, il y a des informations intéressantes à l'écran permettant de localiser le dysfonctionnement.
============================================
Informations techniques
*** STOP 0x0000001D (0x000E00E0, 0XF83207D0, 0XF83204D0, OXF46E9F4F)
============================================
Quels codes avez-vous ?
============================================
Informations techniques
*** STOP 0x0000001D (0x000E00E0, 0XF83207D0, 0XF83204D0, OXF46E9F4F)
============================================
Quels codes avez-vous ?
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
Modifié par jane1261 le 13/10/2012 à 11:03
Modifié par jane1261 le 13/10/2012 à 11:03
STOP : 0X00000019(0X0000000000000003, 0XFFFFFA800547B080, plusieurs fois cette même référence)
J'ai fait il y a quelques jours un whocashed que voici :
System Information (local)
--------------------------------------------------------------------------------
computer name: CUPERS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441549824 total
VM: 2147352576, free: 1914187776
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/10/2012 15:36:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-25365-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
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 Tue 9/10/2012 15:36:56 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: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 7/10/2012 18:49:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF70, 0xFFFF, 0x0)
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 Sat 29/09/2012 09:20:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-16988-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8A01EE6A0C0, 0x0, 0xFFFFF80003496A10, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 28/09/2012 04:25:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092812-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
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 Thu 27/09/2012 13:40:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA80183688C0, 0x2, 0x0, 0xFFFFF800035132F4)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 23/09/2012 06:31:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000384EB23, 0xFFFFF880094E8150, 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 Fri 21/09/2012 03:25:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092112-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFE8A00FB5CD20, 0x0, 0xFFFFF800035AD9BC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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
--------------------------------------------------------------------------------
8 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.
J'ai fait il y a quelques jours un whocashed que voici :
System Information (local)
--------------------------------------------------------------------------------
computer name: CUPERS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 6441549824 total
VM: 2147352576, free: 1914187776
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/10/2012 15:36:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-25365-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
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 Tue 9/10/2012 15:36:56 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: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 7/10/2012 18:49:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-17955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF70, 0xFFFF, 0x0)
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 Sat 29/09/2012 09:20:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-16988-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8A01EE6A0C0, 0x0, 0xFFFFF80003496A10, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 28/09/2012 04:25:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092812-18954-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B6FF40, 0xFFFF, 0x0)
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 Thu 27/09/2012 13:40:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA80183688C0, 0x2, 0x0, 0xFFFFF800035132F4)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 23/09/2012 06:31:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000384EB23, 0xFFFFF880094E8150, 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 Fri 21/09/2012 03:25:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092112-15990-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFE8A00FB5CD20, 0x0, 0xFFFFF800035AD9BC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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
--------------------------------------------------------------------------------
8 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.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
rafit jad kuldinger
Messages postés
7689
Date d'inscription
dimanche 4 avril 2010
Statut
Membre
Dernière intervention
2 février 2024
1 151
13 oct. 2012 à 11:17
13 oct. 2012 à 11:17
la ram rend l ame !..
rafit jad kuldinger
Messages postés
7689
Date d'inscription
dimanche 4 avril 2010
Statut
Membre
Dernière intervention
2 février 2024
1 151
13 oct. 2012 à 14:05
13 oct. 2012 à 14:05
merc i pour le - 1 sans justification ...
allez je veux des détails !!
parce que moi je sais de par expérience que si un fichier du noyaux de windows plante, que cela vien de la ram ...
surtout que les méssage d erreur sont eux aussi assez explicite..
allez je veux des détails !!
parce que moi je sais de par expérience que si un fichier du noyaux de windows plante, que cela vien de la ram ...
surtout que les méssage d erreur sont eux aussi assez explicite..
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
13 oct. 2012 à 11:42
13 oct. 2012 à 11:42
et ??? Que faut-il faire ?
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
13 oct. 2012 à 13:11
13 oct. 2012 à 13:11
antipolis a
Votre avis svp ?
Votre avis svp ?
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
Modifié par jane1261 le 13/10/2012 à 14:07
Modifié par jane1261 le 13/10/2012 à 14:07
De quoi parles-tu ? C'est quoi le -1 ??
Et si j'ai un problème de ram que faut-il faire ? Je l'ai dit au départ, je suis nulle.
Et si j'ai un problème de ram que faut-il faire ? Je l'ai dit au départ, je suis nulle.
rafit jad kuldinger
Messages postés
7689
Date d'inscription
dimanche 4 avril 2010
Statut
Membre
Dernière intervention
2 février 2024
1 151
13 oct. 2012 à 14:13
13 oct. 2012 à 14:13
bien, ta ram est défaillant, elle perd des info ce qui fait plante les fichiers qui sont chargé dessus.
2 solution :
1- change la ram pour une de meilleur qualité.
2- si cela n est point trop tard, rentrée dans le bios (supr) dés le démarrage du pc.
cherché et réglé au plus bas la tension d alimentation de la ram.
2 solution :
1- change la ram pour une de meilleur qualité.
2- si cela n est point trop tard, rentrée dans le bios (supr) dés le démarrage du pc.
cherché et réglé au plus bas la tension d alimentation de la ram.
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
Modifié par jane1261 le 13/10/2012 à 15:12
Modifié par jane1261 le 13/10/2012 à 15:12
Pour la solution 2, comment faut-il faire pour au moins essayer quelque chose avant de changer la ram ?
Est-ce un truc qui coute cher ?
Tu ne m'as pas répondu pour le -1... Je vois que l'un de tes messages reste en dessous avec un -1 à gauche, s'agit-il de cela ? Si oui, ai-je un pouvoir pour y changer quelque chose ?
Est-ce un truc qui coute cher ?
Tu ne m'as pas répondu pour le -1... Je vois que l'un de tes messages reste en dessous avec un -1 à gauche, s'agit-il de cela ? Si oui, ai-je un pouvoir pour y changer quelque chose ?
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
Modifié par jane1261 le 13/10/2012 à 16:52
Modifié par jane1261 le 13/10/2012 à 16:52
Je viens de voir pour le -1, mais ce n'est pas moi. D'ailleurs je viens de le mettre à zéro. Je n'ai jamais touché aux touches + - je ne savais même pas à quoi elles servent. Ca a une influence sur qoui ?
rafit jad kuldinger
Messages postés
7689
Date d'inscription
dimanche 4 avril 2010
Statut
Membre
Dernière intervention
2 février 2024
1 151
13 oct. 2012 à 16:54
13 oct. 2012 à 16:54
en rien, mais des petits malin s amuse avec ...
ca change le classement de la réponse .
ca change le classement de la réponse .
antipolis a
Messages postés
15609
Date d'inscription
mercredi 5 novembre 2008
Statut
Membre
Dernière intervention
12 novembre 2014
2 859
14 oct. 2012 à 06:55
14 oct. 2012 à 06:55
Bonjour "rafit jad kuldinger".
C'est vraiment une belle co**erie cet indice de pertinence.
Tout juste bon à mettre la zizanie dans un sujet.
En plus, les réponses, par défaut, sont triés sur celui-ci.
Inutile et ridicule.
A chaque reprise du sujet il faut remettre le tri sur la date.
Bon dimanche à vous.
C'est vraiment une belle co**erie cet indice de pertinence.
Tout juste bon à mettre la zizanie dans un sujet.
En plus, les réponses, par défaut, sont triés sur celui-ci.
Inutile et ridicule.
A chaque reprise du sujet il faut remettre le tri sur la date.
Bon dimanche à vous.
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
13 oct. 2012 à 19:31
13 oct. 2012 à 19:31
Et pour mon problème, y a t'il une solution possible ?
rafit jad kuldinger
Messages postés
7689
Date d'inscription
dimanche 4 avril 2010
Statut
Membre
Dernière intervention
2 février 2024
1 151
14 oct. 2012 à 03:54
14 oct. 2012 à 03:54
relit ma première réponse...
antipolis a
Messages postés
15609
Date d'inscription
mercredi 5 novembre 2008
Statut
Membre
Dernière intervention
12 novembre 2014
2 859
14 oct. 2012 à 06:55
14 oct. 2012 à 06:55
Le rapport est clair : RAM défaillante.
jane1261
Messages postés
276
Date d'inscription
dimanche 10 février 2008
Statut
Membre
Dernière intervention
3 août 2024
14
15 oct. 2012 à 19:13
15 oct. 2012 à 19:13
merci à tous les deux