BSOD causés par différent processus
Résolu
djjoman
Messages postés
235
Statut
Membre
-
djjoman Messages postés 235 Statut Membre -
djjoman Messages postés 235 Statut Membre -
Bonjour, j'ai eu plusieurs BSOD depuis que j'ai installé ma config mais ce n'est jamais le même problème.
Voici la liste des crash:
On Fri 22/07/2011 14:47:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-13150-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x4163)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFFFFF8F0D98D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 21/07/2011 15:48:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-15303-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E40B)
Bugcheck code: 0x50 (0xFFFFFFFF8B18F9E8, 0x0, 0xFFFFFFFF8366A12A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Thu 30/06/2011 11:56:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063011-13759-01.dmp
This was probably caused by the following module: bckd.sys (bckd+0x9C11)
Bugcheck code: 0xD1 (0x38, 0x2, 0x1, 0xFFFFFFFF8BFF0C11)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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: bckd.sys .
Google query: bckd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 22/06/2011 16:42:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062211-16255-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8F5425B8, 0xFFFFFFFF8F542190, 0xFFFFFFFF8355CF1F)
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 30/05/2011 15:58:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053011-28750-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x9470)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8353C87B, 0xFFFFFFFFAB4678AC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Sat 28/05/2011 16:39:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052811-12573-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8DF49898, 0xFFFFFFFF8DF49470, 0xFFFFFFFF836CCC7A)
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 Sat 28/05/2011 08:56:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052811-12916-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x26FD3)
Bugcheck code: 0xC5 (0x5, 0x2, 0x1, 0xFFFFFFFF835584C1)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that the system attempted to access invalid 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. 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software DRIVER_CORRUPTED_EXPOOL
On Sun 15/05/2011 13:02:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051511-14305-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xE11C6)
Bugcheck code: 0x1A (0x41287, 0x25, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 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 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 07/05/2011 07:51:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050711-16177-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3430)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP
On Thu 05/05/2011 05:24:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050511-14024-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x14EB, 0x14ED956)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 03/05/2011 17:47:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050311-11419-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0xF7 (0xFFFFFFFFA80AED10, 0x2E69A58C, 0xFFFFFFFFD1965A73, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 28/04/2011 17:17:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042811-16863-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x51 (0x1, 0xFFFFFFFF8FA5D008, 0x27C6000, 0x374)
Error: REGISTRY_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Je voudrai savoir comment éviter d'autre BSOD et réparer les erreurs.
Merci d'avance!
Voici la liste des crash:
On Fri 22/07/2011 14:47:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072211-13150-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x4163)
Bugcheck code: 0xD1 (0xC, 0x2, 0x0, 0xFFFFFFFF8F0D98D6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 21/07/2011 15:48:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072111-15303-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E40B)
Bugcheck code: 0x50 (0xFFFFFFFF8B18F9E8, 0x0, 0xFFFFFFFF8366A12A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Thu 30/06/2011 11:56:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063011-13759-01.dmp
This was probably caused by the following module: bckd.sys (bckd+0x9C11)
Bugcheck code: 0xD1 (0x38, 0x2, 0x1, 0xFFFFFFFF8BFF0C11)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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: bckd.sys .
Google query: bckd.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Wed 22/06/2011 16:42:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062211-16255-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8F5425B8, 0xFFFFFFFF8F542190, 0xFFFFFFFF8355CF1F)
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 30/05/2011 15:58:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053011-28750-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0x9470)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8353C87B, 0xFFFFFFFFAB4678AC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Sat 28/05/2011 16:39:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052811-12573-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9AF)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8DF49898, 0xFFFFFFFF8DF49470, 0xFFFFFFFF836CCC7A)
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 Sat 28/05/2011 08:56:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052811-12916-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x26FD3)
Bugcheck code: 0xC5 (0x5, 0x2, 0x1, 0xFFFFFFFF835584C1)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that the system attempted to access invalid 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. 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software DRIVER_CORRUPTED_EXPOOL
On Sun 15/05/2011 13:02:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051511-14305-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xE11C6)
Bugcheck code: 0x1A (0x41287, 0x25, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 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 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 07/05/2011 07:51:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050711-16177-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3430)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: hal.sys .
Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP
On Thu 05/05/2011 05:24:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050511-14024-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x1A (0x5003, 0xFFFFFFFFC0802000, 0x14EB, 0x14ED956)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.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 03/05/2011 17:47:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050311-11419-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0xF7 (0xFFFFFFFFA80AED10, 0x2E69A58C, 0xFFFFFFFFD1965A73, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 28/04/2011 17:17:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042811-16863-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x51 (0x1, 0xFFFFFFFF8FA5D008, 0x27C6000, 0x374)
Error: REGISTRY_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Je voudrai savoir comment éviter d'autre BSOD et réparer les erreurs.
Merci d'avance!
A voir également:
- BSOD causés par différent processus
- Bsod - Guide
- Ordinateur ralenti causes - Guide
- Nb.si.ens différent de ✓ - Forum Excel
- Différent de 0 excel - Forum Excel
- Processus inactif du systeme - Forum Matériel & Système
2 réponses
par expérience, les stop 0x50 que j'ai eu que se soit sur serveur ou sur pc, ont toujours été du à des imprimantes. en particuliers la marque Br...
Mais en général on a pas autant de type de stop à la fois.
A ta place je testerais les mémoires avec testmen pour m'assurer qu'elles sont bonnes ensuite soit débugger avec windbg, soit réinstall.
Mais en général on a pas autant de type de stop à la fois.
A ta place je testerais les mémoires avec testmen pour m'assurer qu'elles sont bonnes ensuite soit débugger avec windbg, soit réinstall.
Windbg, ça devient un truc balaise.
Analyser un crash dump, c'est pas une mince affaire.
Il faut d'abord, activer l'écriture complète de la mémoire plutôt que d'avoir une image noyau.
en gros quand ça plante, cela transfert tout le contenu de la ram dans un fichier memory.dmp. il fait donc la taille de la ram.
ensuite une fois ce fichier crée lors du plantage on l'ouvre avec windbg, à condition que tous les symboles sont installés, on peut arriver plus ou moins à trouver l'application fautive qui a appeler l'instruction ou le pilote fautif en lançant les commandes qui vont bien.
Dans ton cas, vu la quantité de stop que tu ramasses, je vérifierais la ram et j'essaierais de mettre à jour des pilotes, principalement d'imprimantes car dans la dizaine de machine que j'ai eu là dessus ça a toujours été à cause de cela.
Analyser un crash dump, c'est pas une mince affaire.
Il faut d'abord, activer l'écriture complète de la mémoire plutôt que d'avoir une image noyau.
en gros quand ça plante, cela transfert tout le contenu de la ram dans un fichier memory.dmp. il fait donc la taille de la ram.
ensuite une fois ce fichier crée lors du plantage on l'ouvre avec windbg, à condition que tous les symboles sont installés, on peut arriver plus ou moins à trouver l'application fautive qui a appeler l'instruction ou le pilote fautif en lançant les commandes qui vont bien.
Dans ton cas, vu la quantité de stop que tu ramasses, je vérifierais la ram et j'essaierais de mettre à jour des pilotes, principalement d'imprimantes car dans la dizaine de machine que j'ai eu là dessus ça a toujours été à cause de cela.
