Bonjour, a tous
Je viens sur ce forum car j'ai un problème avec mon ordinateur ( de bureau ).
Voici mon problème (c'est une image que j'ai trouve sur internet) :
Je crois que ça s'appelle un crash dump ? Mon ordinateur rame beaucoup alors que je viens juste de l'allume puis il redémarre avec cette écran (je n'ai le temps de rien faire, tout plante ) . En plus il fait beaucoup de bruit enfin moins maintenant mais il y a eu un temps ou on aurais presque dit qu'une voiture
Tu l'installes et tu le lances par Analyze. Tu postes un copier-coller de ce qui apparait .
Le rapport LOCALT~11.html sera dans le dossier du programme WhoCrashed.
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
On Sun 15/07/2012 16:13:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-19234-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x162C8)
Bugcheck code: 0x7A (0xFFFFFFFFC0501830, 0xFFFFFFFFC0000185, 0x340D88C0, 0xFFFFFFFFA0306000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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_DATA_INPAGE_ERROR
On Sun 15/07/2012 14:09:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-16021-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x5164)
Bugcheck code: 0xA (0x34, 0x2, 0x1, 0xFFFFFFFF83084A8F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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 14/07/2012 21:07:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071412-15319-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCF7B7)
Bugcheck code: 0x7A (0xFFFFFFFFC07FA028, 0xFFFFFFFFC0000185, 0xFFFFFFFF8A7088C0, 0xFFFFFFFFFF405EB4)
Error: KERNEL_DATA_INPAGE_ERROR
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 bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 14/07/2012 19:53:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071412-15428-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x8D24)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF8318B818, 0x0, 0xFFFFFFFF8318B818)
Error: BAD_POOL_HEADER
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 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.
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 BAD_POOL_HEADER
On Sat 14/07/2012 10:45:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071412-17815-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x5164)
Bugcheck code: 0xA (0x47800034, 0x2, 0x1, 0xFFFFFFFF830B4A8F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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 14/07/2012 08:56:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071412-15740-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x5164)
Bugcheck code: 0xA (0x47800034, 0x2, 0x1, 0xFFFFFFFF830BCA8F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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 13/07/2012 09:10:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071312-21637-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C)
Bugcheck code: 0x7A (0xFFFFFFFFC0572F90, 0xFFFFFFFFC0000185, 0x6F2E98C0, 0xFFFFFFFFAE5F201C)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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/07/2012 22:35:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071312-18205-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C)
Bugcheck code: 0x7A (0xFFFFFFFFC04521C0, 0xFFFFFFFFC0000185, 0xAF148C0, 0xFFFFFFFF8A4387B4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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/07/2012 12:29:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-17752-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C)
Bugcheck code: 0x7A (0xFFFFFFFFC04D07D8, 0xFFFFFFFFC0000185, 0x5A9ED8C0, 0xFFFFFFFF9A0FBE80)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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/07/2012 10:02:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-18298-01.dmp
This was probably caused by the following module: ataport.sys (ataport+0x1485E)
Bugcheck code: 0x7A (0xFFFFFFFFC04A2988, 0xFFFFFFFFC0000185, 0x55C508C0, 0xFFFFFFFF94531568)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 12/07/2012 08:59:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071212-18626-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17511)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF875BB970, 0xFFFFFFFF875BBADC, 0xFFFFFFFF83262DF0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 CRITICAL_OBJECT_TERMINATION
On Wed 11/07/2012 14:08:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071112-23025-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE9C)
Bugcheck code: 0x7A (0xFFFFFFFFC0466858, 0xFFFFFFFFC0000185, 0x48F0EBE0, 0xFFFFFFFF8CD0B000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 10/07/2012 19:10:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071012-26223-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x162C8)
Bugcheck code: 0x7A (0xFFFFFFFFC0416060, 0xFFFFFFFFC0000185, 0xFFFFFFFF83F448C0, 0xFFFFFFFF82C0C000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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_DATA_INPAGE_ERROR
13 crash dumps have been found and analyzed. A third party driver has 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.
Bonjour,
Quand il y a plusieurs causes comme dans ton cas, c'est souvent un problème de mémoire. Avec Vista et Sept.
Dans le panneau de configuration, Outils d'administration, Diagnostic de mémoire Windows, choisis parmi les deux options proposées.
Cette opération se fera au redémarrage.
Un rapport sera affiché sur le bureau en cas de problème.
Avec Memtest, tous systèmes Voir sur ce site
Il faut graver un CD ou l'installer sur une clé USB bootable et démarrer sur ce médium pour lancer l'analyse.
Un cycle dure environ 15 à 25 minutes avec une machine assez récente. Il ne faut pas d'erreur dans le cadre en bas à droite.
Une analyse complète peut durer 4 heures.
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
Bonjour
Pour Avast cela peut venir aussi de la RAM, nous verrons après s'il y a lieu de la changer ou de le réinstaller.
Pour le test je préfère celui de Memtest mais tu peux faire les deux en commençant par celui de MS.
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
(je n'ai le temps de rien faire, tout plante ) . En plus il fait beaucoup de bruit enfin moins maintenant mais il y a eu un temps ou on aurais presque dit qu'une voiture 
Tu postes un copier-coller de ce qui apparait .
Il ne faut pas d'erreur dans le cadre en bas à droite.
