Bonjour à tous,
Depuis quelques jours, mon pc me plante et systématiquement l'écran bleu affiche "KERNEL_DATA_INPAGE_ERROR" avant de redémarrer.
J'ai fait une analyse avec WhoCrashed, mais je comprends la 1/2 du résultat. Quelqu'un pourrait il expliquer l'autre moitié svp ?
Merci d'avance
System Information (local)
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: Compaq 15 Notebook PC, Hewlett-Packard, 21F7
CPU: AuthenticAMD AMD E1-2100 APU with Radeon(TM) HD Graphics AMD586, level: 22
2 logical processors, active mask: 3
RAM: 8003792896 total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 11/07/2016 23:33:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071216-36671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFE000A76EE7C8, 0x0)
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 11/07/2016 23:33: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 (0x20, 0xFFFFFFFFC000009D, 0xFFFFE000A76EE7C8, 0x0)
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 07/07/2016 07:24:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070716-27890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0xFFFFF6E800707F60, 0xFFFFFFFFC00000C0, 0x20EA3DBE0, 0xFFFFD000E0FEC000)
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/06/2016 01:01:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062916-32546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E3A0)
Bugcheck code: 0x7A (0xFFFFC00146FD6848, 0xFFFFFFFFC00000C0, 0x1E194E880, 0xFFFFF801042B9000)
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
4 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 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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
