Se connecter / S'enregistrer

Résolu Un écran bleu avec un message d'erreur s'affiche sous Windows 7. Que faire?

Solutions (3)
Tags :
  • Windows 7
  • Écran bleu
  • Windows
  • Système d'exploitation
|
bonsoir a tous je me preente franck 30 ans de lille je viens vers vous car un tres gros probleme et je deviens dingue



System Information (local)
--------------------------------------------------------------------------------

computer name: FRANCK-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X6 1055T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 4293054464 total
VM: 2147352576, free: 1950060544



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 05/08/2012 19:02:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-21559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x22, 0x800000000000000, 0x0, 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 05/08/2012 19:02:36 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: 0x19 (0x22, 0x800000000000000, 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.
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 05/08/2012 18:33:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-27034-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x50 (0xFFFFF8A029802008, 0x0, 0xFFFFF80002EA4BFB, 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 Sun 05/08/2012 18:30:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-22994-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031842D8, 0xFFFFF88006176020, 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 05/08/2012 18:10:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-28766-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031E9258, 0xFFFFF880086F20A0, 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 05/08/2012 17:56:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-24070-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A40F3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030050F3, 0xFFFFF880031848B8, 0xFFFFF88003184120)
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 05/08/2012 17:26:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-26863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x19 (0x22, 0x800000000000000, 0x0, 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 05/08/2012 16:34:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-35615-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031A1139, 0xFFFFF88009507AA0, 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 05/08/2012 16:29:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080512-35443-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003192AED, 0xFFFFF88009DE7770, 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
--------------------------------------------------------------------------------

9 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.
  • Meuniers a édité ce message
Contenus similaires
Meilleure solution
partage
|
Problème je pense résolu mes barrettes de mémoire entrer en conflits j ai test plein de position différente car normalement mes 2x 2 GO devais être sur les 2 sots rouge ou noir et jamais ça fonctionner la meilleur solution à était slot rouge tout à gauche et slot noir tout à droite et depuis que du bohneur j espère que ça continuera comme ça
Merci.
  • chrisnvdia a sélectionné cette solution comme la meilleure réponse
  • Commenter cette solution |
Score
1
òh
òi
, Expert en configs PC |
Salut

Essaye de faire ceci ;

Etein ton pc et débranche le

Ensuite enlève la pile de la carte mère

Et redémarre le pc sans la pile jusqu'à écran bleu ( si il y a )

Ensuite éteint le pc puis débranché

Remet la pile et redémarre le pc normalement

Ceci est un Clear CMOS sa remet la mémoire à zéro sans rien perdre

Documents , photos etc

Et redit moi si c'est bon ou pas
  • Commenter cette réponse |
Score
0
òh
òi
, Expert en configs PC |
@ umax59

Ok et tien moi au courant ;) 
  • Commenter cette réponse |

Ce n'est pas ce que vous cherchiez ?

Tom's guide dans le monde
  • Allemagne
  • Italie
  • Irlande
  • Royaume Uni
  • Etats Unis
Suivre Tom's Guide
Inscrivez-vous à la Newsletter
  • ajouter à twitter
  • ajouter à facebook
  • ajouter un flux RSS