Bonjour,
Depuis quelques jours mon ordinateur crash et me montre un écran bleu de ce genre : https://jochenscomputer.files.wordpress.com/2013/12/bluescreen.jpg
J'ai parcouru google afin de trouver des solutions à mon problème mais en vain.
Je me tourne donc vers vous en espérant que quelqu'un ait une solution.
Ce que j'ai déjà fais :
- Les commandes windows du genre sfc /scannow ou les test de disque dur OS
- Test de mémoire windows avec le diagnostic windows qui est négatif, pas de problème
- J'ai utilisé HDtune pour analyser mon HDD et il a trouvé que 0.01% de mon disque dur était endommagé..
J'ai téléchargé un logiciel qui rassemble des infos sur le crashdump...
Voilà ce qu'il en est, je fais un copié-collé.
System Information (local)
--------------------------------------------------------------------------------
Computer name: PORTABLE-POYO
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: X550VC, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6322536448 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 17-03-16 15:06:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031716-32593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002E2A3972, 0xFFFFD0002350C3B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.
On Thu 17-03-16 15:06:39 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x444B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8002E2A3972, 0xFFFFD0002350C3B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\aswmonflt.sys
product: Avast Antivirus
company: AVAST Software
description: avast! File System Minifilter for Windows 2003/Vista
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software).
Google query: AVAST Software SYSTEM_SERVICE_EXCEPTION
On Wed 16-03-16 22:41:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031616-30703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001D68623C0, 0xB79018)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
On Wed 16-03-16 17:40:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031616-34640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000B98E1010, 0xAD78D39360)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
On Tue 15-03-16 21:41:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031516-25687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00076A909D0, 0x11C2D0B4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
On Tue 15-03-16 17:28:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031516-28421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0019F42BC20, 0x3631481388)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
On Tue 15-03-16 16:40:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031516-31125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00159E55580, 0xFFFFF901406D265C)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
On Mon 14-03-16 19:24:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031416-30312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001E8E59630, 0x7FFBBBA054D8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
On Mon 14-03-16 18:01:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031416-28531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001D58CA680, 0xFFFFC00041D0ED08)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
On Sun 13-03-16 16:16:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031316-42125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0011EBAB010, 0x7FFD23229510)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.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 that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
19 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
Si vous avez besoin de plus d'informations, indiquez moi comment les obtenir et merci de vous intéresser à mon problème ! 
