BSOD kernel_data_inpage_error !

[Rofl]

Bonjour,

2 eme fois que mon ordi affiche ce bsod, j'aimerais savoir comment aretter cela.

Merci

[EinsteinZero]

Bonsoir et bienvenue
un BSOD peut avoir de nombreuse cause... aussi il nous faudrait un peu plus d'info....
à cette fin, télécharge le logiciel gratuit sans installation Whocrashed >>ici sur "External mirror 1"<<
--> lance le logiciel et fais un copier/coller de sont rapport dans ton prochain message

On aura alors peut-être quelques éléments intéressant pour trouver la cause du souci

[Rofl]

System Information (local)
--------------------------------------------------------------------------------

computer name:
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: K55VD, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Pentium(R) CPU 2020M @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 8469856256 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 02/07/2015 13:08:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070215-31859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA8006F3F900, 0x5EB3000)
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 02/07/2015 02:42:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\070215-39171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFFA800DF01680, 0x69FBA964)
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 28/02/2015 12:33:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022815-28593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xE4 (0x1, 0xFFFFFA800A3A8AF0, 0x1, 0x0)
Error: WORKER_INVALID
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 memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 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.

[routman54]

Bonjour ,
D'après le rapport il ne s'agit pas d'un problème matériel , mais logiciel .
Pour commencer essaies de mettre à jour tout les pilotes de ton appareil sur le site du constructeur , tu l'aurais mis ainsi que le modèle je t'aurai faciliter la tâche mais comme je ne suis pas devin ou alors tu vas sur ma config.com > ICI < , après analyse de ton appareil ils te diront quels sont les derniers pilotes pour celui-ci .
N'oublies pas non plus les Maj de Windows avec Windows Update .
Bonne continuation .

[Rofl]

Sa à l'aire de s'être arranger merci a toi !