Ecran bleu - Error kernel date inpage error

Bonjour

Alors voilà je posséde mon ordinateur depuis fin octobre 2014, c'est un lenovo y50-70 (acheté sur amazon). La première fois que j'ai eu ce bug c'était en décembre et puis plus rien. Mais maintenant depuis 1 mois cela c'est intensifié

https://i.imgur.com/KpQ8qX6.jpg

Avez vous une idée de quoi faire svp ?

J'ai fais un test avec WhoCrashed (j'ai lu sa quelques part sur le net)

System Information (local)

computer name: THOMAS_LENOVO
windows version: Windows 8.1 , 6.3, build: 9600
windows dir: C:\WINDOWS
Hardware: 20378, LENOVO, Lenovo Y50-70
CPU: GenuineIntel Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8497946624 total



Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 29/07/2015 13:39:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072915-24484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x7A (0xFFFFF6E000B0E010, 0xFFFFFFFFC000003F, 0x1A769D880, 0xFFFFC00161C02000)
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 29/07/2015 13:39:54 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x2688B)
Bugcheck code: 0x7A (0xFFFFF6E000B0E010, 0xFFFFFFFFC000003F, 0x1A769D880, 0xFFFFC00161C02000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\aswsnx.sys
product: Avast Antivirus
company: Avast Software s.r.o.
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 s.r.o.).
Google query: Avast Software s.r.o. KERNEL_DATA_INPAGE_ERROR



On Tue 28/07/2015 19:32:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072815-25468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x7A (0xFFFFF6FB40001BB0, 0xFFFFFFFFC000003F, 0x816A7880, 0xFFFFF68000376000)
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 Thu 23/07/2015 12:30:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072315-28203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x7A (0xFFFFF6E000933078, 0xFFFFFFFFC000003F, 0x57F82880, 0xFFFFC0012660F000)
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 Fri 17/07/2015 16:52:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071715-46859-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Wed 15/07/2015 15:46:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071515-24343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x7A (0xFFFFF6FB400001A8, 0xFFFFFFFFC000003F, 0x2311E9880, 0xFFFFF68000035368)
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 Thu 09/07/2015 10:02:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070915-36765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0)
Bugcheck code: 0x7A (0xFFFFF6FB40000070, 0xFFFFFFFFC000003F, 0x127693880, 0xFFFFF6800000E000)
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

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

aswsnx.sys (avast! Virtualization Driver, Avast Software s.r.o.)

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.

Merci par avance