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.