HELP NEEDED: Kernel_Data_Inpage_Error

Toggle sidebar Toggle sidebar
P

Pain_1

Prominent
Jun 30, 2017
3
0
510
Please help I am using a Windows 8 Laptop and everytime when I try to run League of Legends it ends up restarting due to Kernel_Data_Inpage_Error. I already used chkdsk C: /f /r, used Memory Diagnostic test, Norton Power Eraser, and I am about to wipe my operating system. Before I do that is their any other solutions on getting rid of this error. I am just a freshmen in highschool and I can't lose my League of Legends please help.
Here is the WhoCrashed Logs
Computer name: MICHAEL
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: HP 2000 Notebook PC, Hewlett-Packard, 1854
CPU: GenuineIntel Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4178862080 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 6/30/2017 3:57:24 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-27484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000248F99E0, 0xA1C8E45918)
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 6/30/2017 3:57:24 PM 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, 0xFFFFE000248F99E0, 0xA1C8E45918)
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 Fri 6/30/2017 1:25:09 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-31062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0006BFB5740, 0x58A964)
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 6/30/2017 12:41:01 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-36406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000DF2B2DE0, 0x7FF9596E8568)
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 6/30/2017 12:30:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-43265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000B9A38D30, 0x7E87DBE3F)
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
--------------------------------------------------------------------------------

30 crash dumps have been found and analyzed. Only 5 are included in this report. 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.
 
Solution
J
the system called a bugcheck because it could not load something into memory. It looks like a software lock problem and a user mode application talking to a kernel mode driver.

Here is what you should do: update the BIOS and all of the motherboard drivers from the motherboard vendors website. (this is just general advice in case you have not done it yet)

update your third party utilities (firmware of solid state drives, firmware of certain mouse hardware and any utilities like voice software)

at this point you would if you still have the problem you would need to do the following:
change the memory dump type from minidump to a kernel memory dump. Then boot your windows and run cmd.exe as an admin then type the following...
Sort by date Sort by votes
P

Pain_1

Prominent
Jun 30, 2017
3
0
510


Computer name: MICHAEL
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: HP 2000 Notebook PC, Hewlett-Packard, 1854
CPU: GenuineIntel Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4178862080 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 6/30/2017 3:57:24 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-27484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000248F99E0, 0xA1C8E45918)
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 6/30/2017 3:57:24 PM 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, 0xFFFFE000248F99E0, 0xA1C8E45918)
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 Fri 6/30/2017 1:25:09 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-31062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0006BFB5740, 0x58A964)
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 6/30/2017 12:41:01 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-36406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000DF2B2DE0, 0x7FF9596E8568)
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 6/30/2017 12:30:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-43265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DDA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000B9A38D30, 0x7E87DBE3F)
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
--------------------------------------------------------------------------------

30 crash dumps have been found and analyzed. Only 5 are included in this report. 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.

 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the system called a bugcheck because it could not load something into memory. It looks like a software lock problem and a user mode application talking to a kernel mode driver.

Here is what you should do: update the BIOS and all of the motherboard drivers from the motherboard vendors website. (this is just general advice in case you have not done it yet)

update your third party utilities (firmware of solid state drives, firmware of certain mouse hardware and any utilities like voice software)

at this point you would if you still have the problem you would need to do the following:
change the memory dump type from minidump to a kernel memory dump. Then boot your windows and run cmd.exe as an admin then type the following command:
verifier.exe /standard /all
and reboot your system and wait for the next bugcheck:

note: be sure you know how to get into safe mode in case your system bugchecks on the next boot. if it does you will have to run the command
verifier.exe /reset
this will turn of verifier functions ( you have to do this after testing or your machine will run slowly until you do)

after you have got at bugcheck with verifier enabled you need to provide the memory dump file. it will be located at
c:\windows\memory.dmp and will have the proper debug info to determine the cause of the problem.

c:\windows\mindump directory will have your minidumps. you could also put one of these on a server and I could take a quick look. often I can just see which driver is the likely cause of the problem.

anyway, the files are large and you will have to put them on a public server like Microsoft one drive and share the files for public access then post a link here.

when the debugging is enabled, there is a good chance that whocrashed.exe or bluescreenviewer.exe will name the correct bad driver. (just in case I am not here to look at the memory dump)
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom