freddy7551

Bonjour,
J'ai une imprimante Canon Pixma MP 250 , je l'allume elle me met un code E - O - 5 en clignotant, j'ai éteint l'imprimante et zen la ré-allumant elle clignote toujour
voila que doit faire car dans le manuelle il ne parle pas des codes d'erreur
freddy

Bonjour,
J'ai une imprimante Canon Pixma MP 250 , je l'allume elle me met un code E - O - 5 en clignotant, j'ai éteint l'imprimante et zen la ré-allumant elle clignote toujour mais avec un code P - O - 2.
voila que doit faire car dans le manuelle il ne parle pas des codes d'erreur
freddy

bonjour a vous tous,
j'ai un souci avec l'ordi, au démarrage l'ordi demande le disc boot que je n'ai pas, en essayant de de remettre windows il ne reconnait pas le disc dur, ordi a plus ou moins 2 ans

bonjour,
j'ai une imprimante Canon Pixma MP 250, j'ai remplacer les cartouches et depuis ! abracadabra, elle me marque a l'écran un signal d'erreur ( 0-5 et E)
quelqu'un peut -il me dire a quoi sa rhyme et pourquoi elle me marque cela .
que faut t-il faire?
freddy

bonsoir a tous,
j'ai un petit souci, j'ai deux fichiers un iso (cue) executable auto DBU.exe et l'autre qui est un fichier bin
Le problème quand j'ouvre le fichier iso il me dit Error executing file, je supose que c'est du au deuxième fichier.
J'ai essayer de monter le deuxième avec deamon tool il le fait donc il me de un executable, mais quand je clic il me remet le même message, alors que doit-je faire?
Merci pour le coup de main.
Freddy

Bonjour ou bonsoir,
Quelque qui si connais peut t-il me dire se qu'es un fichier Unknown que windows ne peut ouvrir.
J'ai des fichiers sur une image Iso ??????
merci
freddy

bonjour,
j'ai installer le logiciel Sodipodi (logiciel victoriel pour dessin) et quand je veut l'ouvrir il me dit que c'est pas possible car le fichier ZLIB-1.dll est manquant.
es que ça vient du programme ou bien c'est de l'ordi?
par contre il a été fait pour windows +/- XP et comme j'ai le seven 7.
voila si vous pouvez m'expliquer je suis preneur.
freddy

bonjour,
je voulais savoir si a part des vis voyante, il y aurai exemple des vis caché pour pouvoir enlever le cach du dessous de l'ordi portable.
il faut remplacer le cable de l'alim.
j'ai enlever les vis que je voyais mais ca tient toujours vers le centre, il ne faut quand même pas démonter toute les touche du clavier?
merci pour votre aide
freddy

salut a tous j'ai beaucoup de blèmes regarder qui peut me dire?

Code: Tout sélectionner

whocrashed: résumé

Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.


To obtain technical support visit http://www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: FREDDY7551-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488866304 total
VM: 2147352576, free: 1987510272



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 21/10/2011 21:14:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102211-18156-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD863)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFE8, 0x2, 0x1, 0xFFFFFFFF828DEAE6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 21/10/2011 21:14:57 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngLockSurface+0x1EFE)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFE8, 0x2, 0x1, 0xFFFFFFFF828DEAE6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 21/10/2011 19:34:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102111-16125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0x6CBAB650, 0x2, 0x1, 0xFFFFFFFF8289CE36)
Error: 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 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 Fri 21/10/2011 12:17:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102111-18453-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9BCF3)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF82891A6B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 20/10/2011 17:44:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-16859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0x6CBF0950, 0x2, 0x1, 0xFFFFFFFF8289FE36)
Error: 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 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 Thu 20/10/2011 15:22:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-23671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF828DEE36)
Error: 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 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 19/10/2011 18:32:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101911-26390-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xA3D2)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFE8, 0x2, 0x1, 0xFFFFFFFF828E19B2)
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: aswsp.sys .
Google query: aswsp.sys IRQL_NOT_LESS_OR_EQUAL




On Tue 18/10/2011 20:47:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-25078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF828DED16)
Error: 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 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 Tue 18/10/2011 19:53:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-14703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF82894D16)
Error: 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 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 Tue 18/10/2011 16:25:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-14234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF828E0D16)
Error: 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 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 Tue 18/10/2011 15:16:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-21812-01.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x9EA6)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFE8, 0x2, 0x1, 0xFFFFFFFF828E59B2)
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: aswsp.sys .
Google query: aswsp.sys IRQL_NOT_LESS_OR_EQUAL




On Tue 18/10/2011 15:13:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-22265-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x113D32)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF94D29D32, 0xFFFFFFFF90FC66C4, 0xFFFFFFFF90FC62A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 280.26
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 280.26
Bug check description: This indicates that a system thread 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 280.26 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Tue 18/10/2011 15:09:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101811-25187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF828E0D16)
Error: 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 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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

13 crash dumps have been found and analyzed. 2 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 280.26 , NVIDIA Corporation)

aswsp.sys

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.

merci pour votre aide
freddy

bonjours je vient de faire rouler par la sociètè bmx pour mon ordi, en garantie j'ai retourner mon ordi pour un écran bleu qui perdure depuis que je l'ai donc un an, il revient de réparation dont il parrait que c'était du a un driver de l'imprimante et au grand étonnement quand il est revenu toujours blue screem.
ne serait il pas mieux de revenir au windows XP qui parament ne créé moins de problème.
voici le résultat de
whocrashet
computer name: FREDDY7551-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488866304 total
VM: 2147352576, free: 2005041152



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 16/10/2011 09:29:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101611-13125-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x171AE)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFE8, 0x2, 0x1, 0xFFFFFFFF828A39B2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software IRQL_NOT_LESS_OR_EQUAL




On Sun 16/10/2011 09:29:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x171AE)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFE8, 0x2, 0x1, 0xFFFFFFFF828A39B2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software IRQL_NOT_LESS_OR_EQUAL




On Sat 15/10/2011 21:31:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-13390-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0xA3D2)
Bugcheck code: 0xA (0xFFFFFFFF83BFFFE8, 0x2, 0x1, 0xFFFFFFFF828BF9B2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: aswsp.sys AVAST Software IRQL_NOT_LESS_OR_EQUAL




On Sat 15/10/2011 21:22:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-11656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF828A0D16)
Error: 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 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 Sat 15/10/2011 19:19:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-28265-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9BC24)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF8289194B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 15/10/2011 18:18:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-13390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF82898D16)
Error: 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 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 Sat 15/10/2011 18:15:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101511-15984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xA (0xFFFFFFFF9BBFFFF0, 0x2, 0x1, 0xFFFFFFFF8288FD16)
Error: 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 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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. 2 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:

aswsp.sys (avast! self protection module, AVAST Software)

aswsnx.sys (avast! Virtualization Driver, AVAST Software)

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.