Et le fameux écran bleu aux multiples raisons
nibiru01
Messages postés
4
Statut
Membre
-
nibiru01 Messages postés 4 Statut Membre -
nibiru01 Messages postés 4 Statut Membre -
Bonjour à la communauté^^
Je me présente Nibiru01, étudiant pas content!
Je vous expose mon problème. Cet écran bleu qui arrive comme un cheveu sur la soupe et viens égayer mes doux moment de geekerie..
Je n'arrive pas a définir la source du problème.
Je vous donne les détails de whocrashed :
Je signal que j'ai déjà effectué un memtest mais seulement 1h sans aucun problèmes.
Windows 7 pro 64 bits
AMD Athlon II X3 450 Processor AMD586
6 Go de Ram en ddr3 (1333)
Radeon HD6870
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 29/08/2011 22:06:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083011-21871-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x4E (0x99, 0x4D13A, 0x2, 0x4D132)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 Mon 29/08/2011 22:06:33 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: 0x4E (0x99, 0x4D13A, 0x2, 0x4D132)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Wed 17/08/2011 20:45:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-19344-01.dmp
This was probably caused by the following module: unknown_module_00000000'00000023.sys (Unloaded_Unknown_Module_00000000'00000023+0x2D)
Bugcheck code: 0x50 (0xFFFFFA8010127000, 0x0, 0xFFFFF880063B62D0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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_module_00000000'00000023.sys .
Google query: unknown_module_00000000'00000023.sys PAGE_FAULT_IN_NONPAGED_AREA
On Tue 16/08/2011 17:19:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-20389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xEEC8, 0x721F009)
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 16/08/2011 10:53:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081611-17830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1 (0x7745F72A, 0x0, 0xFFFF0000, 0xFFFFF8800C37ACA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 14/08/2011 20:29:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-19125-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x229D0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF880010E49D0, 0xFFFFF8800556CBD0, 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.
On Sun 14/08/2011 19:18:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-17690-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002EF262E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 14/08/2011 18:41:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-23306-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0xD1 (0xFFFFF800026A7BC6, 0x0, 0x8, 0xFFFFF800026A7BC6)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
En vous remerciant de votre aide future.
Cordialement.
Je me présente Nibiru01, étudiant pas content!
Je vous expose mon problème. Cet écran bleu qui arrive comme un cheveu sur la soupe et viens égayer mes doux moment de geekerie..
Je n'arrive pas a définir la source du problème.
Je vous donne les détails de whocrashed :
Je signal que j'ai déjà effectué un memtest mais seulement 1h sans aucun problèmes.
Windows 7 pro 64 bits
AMD Athlon II X3 450 Processor AMD586
6 Go de Ram en ddr3 (1333)
Radeon HD6870
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 29/08/2011 22:06:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083011-21871-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x4E (0x99, 0x4D13A, 0x2, 0x4D132)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 Mon 29/08/2011 22:06:33 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: 0x4E (0x99, 0x4D13A, 0x2, 0x4D132)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 Wed 17/08/2011 20:45:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-19344-01.dmp
This was probably caused by the following module: unknown_module_00000000'00000023.sys (Unloaded_Unknown_Module_00000000'00000023+0x2D)
Bugcheck code: 0x50 (0xFFFFFA8010127000, 0x0, 0xFFFFF880063B62D0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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_module_00000000'00000023.sys .
Google query: unknown_module_00000000'00000023.sys PAGE_FAULT_IN_NONPAGED_AREA
On Tue 16/08/2011 17:19:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-20389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xEEC8, 0x721F009)
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 16/08/2011 10:53:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081611-17830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1 (0x7745F72A, 0x0, 0xFFFF0000, 0xFFFFF8800C37ACA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 14/08/2011 20:29:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-19125-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x229D0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF880010E49D0, 0xFFFFF8800556CBD0, 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.
On Sun 14/08/2011 19:18:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-17690-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002EF262E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 14/08/2011 18:41:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-23306-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0xD1 (0xFFFFF800026A7BC6, 0x0, 0x8, 0xFFFFF800026A7BC6)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
En vous remerciant de votre aide future.
Cordialement.
A voir également:
- Et le fameux écran bleu aux multiples raisons
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
5 réponses
Bonsoir,
d'apres ce que j'ai réussie a comprendre il me semble que tout vient du karnel de windows, alors dans un premier temps a tu un logisciel windows original ?
sinon si tu a un pirater alors il l'es tres mal fait
en 2eme solution essaye de retirez les barettes mémoire et utilise seulement 2gb juste pour tester.
Marc
d'apres ce que j'ai réussie a comprendre il me semble que tout vient du karnel de windows, alors dans un premier temps a tu un logisciel windows original ?
sinon si tu a un pirater alors il l'es tres mal fait
en 2eme solution essaye de retirez les barettes mémoire et utilise seulement 2gb juste pour tester.
Marc
A priori je dirai que vous avez un driver soit corrompu soit inadapté lequel? reprenez les uns a un et vérifiez
Hum en effet ma version windows n'est pas une authentique( pas les moyens)
Mais je n'avais pas eu de problèmes jusque la( depuis 4 mois d'utilisation)
Concernant les drivers, j'ai tout mis a jour via tousmesdrivers mais il est probable que je l'ai mal fait. Comment voir si ils sont corrompus ou inadaptés?
Merci de votre aide
Mais je n'avais pas eu de problèmes jusque la( depuis 4 mois d'utilisation)
Concernant les drivers, j'ai tout mis a jour via tousmesdrivers mais il est probable que je l'ai mal fait. Comment voir si ils sont corrompus ou inadaptés?
Merci de votre aide
Et un nouveau crash ce matin.....
On Fri 02/09/2011 08:12:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x3AD9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880010137B8, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software KMODE_EXCEPTION_NOT_HANDLED
On Fri 02/09/2011 08:12:50 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x3AD9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880010137B8, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswmonflt.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
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.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: aswmonflt.sys AVAST Software KMODE_EXCEPTION_NOT_HANDLED
Essaie de ne laisser qu'une seule barrette dedans et si ça crash, mets une autre, puis la 3e...
De telle façon tu sauras deja si ça vient de la RAM et tu pourras isoler un problème.
Si ça ne crash que avec une barette en particuler c'est qu'elle est foireuse et si ça le fait pour toutes, c'est que cela ne provient pas de la mémoire.
De telle façon tu sauras deja si ça vient de la RAM et tu pourras isoler un problème.
Si ça ne crash que avec une barette en particuler c'est qu'elle est foireuse et si ça le fait pour toutes, c'est que cela ne provient pas de la mémoire.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
