Bonjour,
Depuis ce matin, j’ai eu trois fois un ecran bleu avec le message ‘‘kernel data inpage error’’. Mon pc redemarre, remarche un temps et reaffiche cela…
J’ai deja vu des sujets la dessus mais les manipulations proposées sont diverses et je ne voudrais pas faire de betises.
J’ai verifié mes peripherique et n’ai aucun triangle jaune signalant une erreur.
J’ai nettoyé avec ccleaner et ai lancé une analyse avec mon antivirus.
Je suis allé voir l’observateur d’evenement qui affiche des rond avec un point d’exclamation rouge aux heures de bug et ce message:
Les chaînes de performance dans la valeur de Registre Performance sont endommagées lors du traitement du fournisseur de compteurs d?extension Performance. La valeur BaseIndex à partir du Registre de performance est le premier DWORD dans la section Données, la valeur LastCounter est le deuxième DWORD dans la section Données, et la valeur LastHelp est le troisième DWORD dans la section Données.
Journal: application Source: LoadPerf Evenement: 3012 Niveau:Erreur
J’ai lancé Whocrashed, qui m’a donné ce rapport:
System Information (local)
computer name: SAY-PC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:Windows
Hardware: HP Pavilion g7 Notebook PC, Hewlett-Packard, 1842
CPU: GenuineIntel Intel® Core™ i3-3120M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4182007808 total
Crash Dump Analysis
Crash dump directory: C:WindowsMinidump
Crash dumps are enabled on your computer.
On Thu 04/06/2015 12:14:53 GMT your computer crashed
crash dump file: C:WindowsMinidump60415-29359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800AF0A620, 0xA55130C004)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:Windowssystem32ntoskrnl.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 04/06/2015 12:14:53 GMT your computer crashed
crash dump file: C:Windowsmemory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800AF0A620, 0xA55130C004)
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 04/06/2015 11:59:56 GMT your computer crashed
crash dump file: C:WindowsMinidump60415-72546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800AC3B6C0, 0xFFFFF8A007DFC4B8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:Windowssystem32ntoskrnl.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 04/06/2015 11:18:39 GMT your computer crashed
crash dump file: C:WindowsMinidump60415-76546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800C2BE310, 0x87B01B298)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:Windowssystem32ntoskrnl.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.
Edité le 04/06/2015 à 15:11
