zakilescorpion
Messages postés3Date d'inscriptionmardi 28 février 2012StatutMembreDernière intervention 8 septembre 2012
-
12 avril 2012 à 19:39
Bonjour,
J'ai un problème:
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7600.2.0.0.256.1
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: 1a
BCP1: 00003452
BCP2: 060A4000
BCP3: C080CA98
BCP4: 11594C66
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\041212-21387-01.dmp
C:\Users\Don Zaki\AppData\Local\Temp\WER-61152-0.sysdata.xml
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c
Si la déclaration de confidentialité en ligne n'est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
WhoCrashed
System Information (local)
--------------------------------------------------------------------------------
computer name: AUDI-A4-PC-9963
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 1072160768 total
VM: 2147352576, free: 1929269248
On Thu 12/04/2012 17:07:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041212-21387-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA06EE)
Bugcheck code: 0x1A (0x3452, 0x60A4000, 0xFFFFFFFFC080CA98, 0x11594C66)
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 Thu 12/04/2012 17:07:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt+0xA06EE)
Bugcheck code: 0x1A (0x3452, 0x60A4000, 0xFFFFFFFFC080CA98, 0x11594C66)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe MEMORY_MANAGEMENT
On Thu 12/04/2012 15:22:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041212-18610-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE64)
Bugcheck code: 0x4E (0x2, 0x2B8FC, 0x3FEDF, 0xFFFF)
Error: PFN_LIST_CORRUPT
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 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 Fri 06/04/2012 18:49:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040612-19796-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xBBAC)
Bugcheck code: 0x4E (0x99, 0x21C8, 0x2, 0x24C9)
Error: PFN_LIST_CORRUPT
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 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.
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 PFN_LIST_CORRUPT
On Tue 03/04/2012 23:37:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040412-20404-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE34)
Bugcheck code: 0x4E (0x99, 0x2B3DA, 0x2, 0x37499)
Error: PFN_LIST_CORRUPT
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 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 Tue 20/03/2012 14:40:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032012-19047-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA06EE)
Bugcheck code: 0x1A (0x3452, 0x45C000, 0xFFFFFFFFC08051D4, 0x22FF7C66)
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 13/03/2012 14:29:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031312-27003-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB9C59)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC080208A, 0xFFFF, 0x0)
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 13/03/2012 14:07:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031312-29172-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x80679)
Bugcheck code: 0x34 (0x55F, 0xFFFFFFFFC0000420, 0x0, 0x0)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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 Thu 08/03/2012 13:46:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030812-19702-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB9C59)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC0802778, 0xFFFF, 0x0)
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 06/03/2012 19:20:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030612-19312-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x18C51)
Bugcheck code: 0x50 (0xFFFFFFFF9DA3C000, 0x0, 0xFFFFFFFF82A36A3A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
On Tue 06/03/2012 19:13:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030612-21340-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xA06EE)
Bugcheck code: 0x1A (0x41790, 0xFFFFFFFFC080278C, 0xFFFF, 0x0)
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 06/03/2012 14:58:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030612-24679-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x10489)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF828C80D4, 0xFFFFFFFF8A5FD2DC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization 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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Fri 02/03/2012 18:22:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-19874-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x91756)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF941B1756, 0xFFFFFFFF9A05DACC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 Fri 02/03/2012 13:31:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030212-25194-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD9E4B)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFFFE939E70, 0xFFFFFFFFFE939E70, 0xFFFFFFFFFE939E71)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
14 crash dumps have been found and analyzed. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.