Bonjour depuis 6 jours, j'ai un écran bleu qui s'affiche quand je lance certaines applications et il est noté : "kernel data in page error"
Je précise que c'est un pc portable que je dispose depuis maintenant 1 ans et 2-3 mois.
Ma config :
computer name: ASUS
windows version: Windows 8.1
Carte mère: K75VJ, ASUSTeK COMPUTER INC.
Processeur : Intel(R) Core(TM) i7-3630QM CPU @ 2.40 - 3,20 GHz Intel586, level: 6
RAM: 4GO
Carte graphique : GT 635 M 2 GO
J'ai fais un scan avec whocrashed et ça m'affiche ça :
Crash Dump Analysis
--------------------------------------------------
------------------------------

Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 08/05/2014 13:55:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050814-29812-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0010BA2C980, 0x2017A780)
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 08/05/2014 13:55:25 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0010BA2C980, 0x2017A780)
Error: KERNEL_DATA_INPAGE_ERROR
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 08/05/2014 12:11:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050814-21968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001A4EAF970, 0x1AA71E83)
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 07/05/2014 19:43:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050714-21718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001C3D68D70, 0x14705000)
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 07/05/2014 09:28:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050714-21406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0000BAB5200, 0x264B80A0)
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 Sat 03/05/2014 09:32:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050314-31453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7A (0x4, 0x200, 0xFFFFE0013583BC70, 0x141645E0)
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 02/05/2014 11:59:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050214-41578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7A (0x4, 0x200, 0xFFFFE001D668B120, 0x1F732840)
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. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.

j'ai fais un sfc /scannow
et ça me dit ça : La protection des ressources Windows a trouvé des fichiers endommagés, mais n'a pas réussi à tous les réparer. Des détails sont inclus dans le journal CBS.Log windir/Logs/CBS/CBS.log. Par exemple C:/Windows/Logs/CBS/CBS.log. Notez que la journalisation n'est pas actuellement prise en charge dans les scénarios de service hors connexion

Merci d'avance

up