Ecran bleu

Fermé
niko07 Messages postés 84 Date d'inscription samedi 2 décembre 2006 Statut Membre Dernière intervention 29 janvier 2014 - Modifié par niko07 le 29/08/2012 à 16:49
niko07 Messages postés 84 Date d'inscription samedi 2 décembre 2006 Statut Membre Dernière intervention 29 janvier 2014 - 3 sept. 2012 à 11:11
Bonjour, j'ai des écrans bleus environ une fois par semaine.
Voici un rapport de Whocrashed

On Wed 29/08/2012 14:23:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082912-21481-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4165B)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF7, 0x0, 0x0, 0xFFFFFFFF8326D5DF)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 29/08/2012 14:23:31 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29D3)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF7, 0x0, 0x0, 0xFFFFFFFF8326D5DF)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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 IRQL_NOT_LESS_OR_EQUAL

2 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:

ntkrpamp.exe

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.

J'ai déjà fais un Memtest de la ram sans erreur. Pouvez-vous m'aider? Merci d'avance.
A voir également:

2 réponses

bonjour
si vous avez le cd de windows tentez une reparation......
0
niko07 Messages postés 84 Date d'inscription samedi 2 décembre 2006 Statut Membre Dernière intervention 29 janvier 2014 8
3 sept. 2012 à 11:11
J'ai maintenant eu ceci
On Sun 2/09/2012 18:45:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090212-25287-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x17789)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9CF8BB00, 0xFFFFFFFFAFCC9B58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus
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
0