Sign in with
Sign up | Sign in
Your question

Kernel data inpage error???? What is this???

Last response: in Windows 8
Share
July 17, 2014 8:36:34 AM

Hi

Recently I have been receiving this blue screen of death with the error being "Kernel data inpage error". I'm just about tired of always being booted from what I was doing every so often because of this error. During my research, I noticed that it was considered a registry issue. Therefore, I completely formatted my ssd and hdd and did a complete clean install. However, that Still has not solved the puzzle. I am still getting this error!?!?!?!? What can I do?? Is it my motherboard??? Please help

Thanks

System specs.

i5 4670k

8gb ddr3 ram

z87-D3HP motherboard

750 watt Antec 80 gold plus PSU

7970 OC + r9 280x CF

128 gb ssd

1Tb Hdd
July 17, 2014 9:46:07 PM

TechiGamer said:
Hi

Recently I have been receiving this blue screen of death with the error being "Kernel data inpage error". I'm just about tired of always being booted from what I was doing every so often because of this error. During my research, I noticed that it was considered a registry issue. Therefore, I completely formatted my ssd and hdd and did a complete clean install. However, that Still has not solved the puzzle. I am still getting this error!?!?!?!? What can I do?? Is it my motherboard??? Please help

Thanks

System specs.

i5 4670k

8gb ddr3 ram

z87-D3HP motherboard

750 watt Antec 80 gold plus PSU

7970 OC + r9 280x CF

128 gb ssd

1Tb Hdd


Hi,

the KERNEL_DATA_INPAGE_ERROR occurs when memory in the kernel's paged pool is swapped to the hard disk and cannot be read when needed at a later time.

Windows broadly divides memory into three pools:

The kernel non-paged pool

The kernel paged pool

The user paged pool

The kernel non-paged pool contains memory that must be in memory at all times. This includes all of the memory used to handle interrupts, track thread and process states, and handle deferred procedure calls. Memory allocated to the kernel or drivers from this pool will always remain resident in memory at all times, it will never be swapped out to the hard disk drive and referencing memory in the non-paged pool will never generate a page fault (in fact, PAGE_FAULT_IN_NONPAGED_AREA is another famous BSoD).

The kernel paged-pool contains kernel memory that can be swapped to a page file or swap file located on a secondary storage medium such as a hard disk drive. If memory is infrequently used, it may be swapped out. If the kernel references memory located in the kernel paged-pool it will generate a page-fault interrupt which will bring it back into the physical memory (note that as I mentioned above, the page-fault interrupt handler operates only on non-paged memory).

The user paged-pool contains memory that can be allocated to user processes.

To best address your question, imagine a scenario when an application causes a page fault by referencing memory that has been swapped out to a page file that is located on a secondary storage device that has been removed or is inaccessible. That memory can no longer be found, so the application must be terminated as it can no longer proceed.

The same is true when the kernel causes a page fault by referencing memory that has been swapped out to a page file that is located on a secondary storage device that has been removed or is inaccessible. The kernel cannot proceed to a consistent state, so it must terminate and halt the machine.

If you have any removable storage devices, make sure that they are configured as such. If they contain page files (pagefile.sys, swapfile.sys, hiberfile.sys) they may unwittingly be used to store memory and that memory will go with them when they are removed. Your machine will run uninhibited until something references the memory that has now disappeared at which point the referencing task will fail.

Your hard disk drive and SSD may also be failing. CHKDSK /R will scan for bad sectors but it won't catch non-deterministic read errors and long-latency events. Check the health of the drive using a vendor supplied S.M.A.R.T monitoring tool.
m
0
l
Related resources
July 18, 2014 7:56:45 AM

Pinhedd said:
TechiGamer said:
Hi

Recently I have been receiving this blue screen of death with the error being "Kernel data inpage error". I'm just about tired of always being booted from what I was doing every so often because of this error. During my research, I noticed that it was considered a registry issue. Therefore, I completely formatted my ssd and hdd and did a complete clean install. However, that Still has not solved the puzzle. I am still getting this error!?!?!?!? What can I do?? Is it my motherboard??? Please help

Thanks

System specs.

i5 4670k

8gb ddr3 ram

z87-D3HP motherboard

750 watt Antec 80 gold plus PSU

7970 OC + r9 280x CF

128 gb ssd

1Tb Hdd


Hi,

the KERNEL_DATA_INPAGE_ERROR occurs when memory in the kernel's paged pool is swapped to the hard disk and cannot be read when needed at a later time.

Windows broadly divides memory into three pools:

The kernel non-paged pool

The kernel paged pool

The user paged pool

The kernel non-paged pool contains memory that must be in memory at all times. This includes all of the memory used to handle interrupts, track thread and process states, and handle deferred procedure calls. Memory allocated to the kernel or drivers from this pool will always remain resident in memory at all times, it will never be swapped out to the hard disk drive and referencing memory in the non-paged pool will never generate a page fault (in fact, PAGE_FAULT_IN_NONPAGED_AREA is another famous BSoD).

The kernel paged-pool contains kernel memory that can be swapped to a page file or swap file located on a secondary storage medium such as a hard disk drive. If memory is infrequently used, it may be swapped out. If the kernel references memory located in the kernel paged-pool it will generate a page-fault interrupt which will bring it back into the physical memory (note that as I mentioned above, the page-fault interrupt handler operates only on non-paged memory).

The user paged-pool contains memory that can be allocated to user processes.

To best address your question, imagine a scenario when an application causes a page fault by referencing memory that has been swapped out to a page file that is located on a secondary storage device that has been removed or is inaccessible. That memory can no longer be found, so the application must be terminated as it can no longer proceed.

The same is true when the kernel causes a page fault by referencing memory that has been swapped out to a page file that is located on a secondary storage device that has been removed or is inaccessible. The kernel cannot proceed to a consistent state, so it must terminate and halt the machine.

If you have any removable storage devices, make sure that they are configured as such. If they contain page files (pagefile.sys, swapfile.sys, hiberfile.sys) they may unwittingly be used to store memory and that memory will go with them when they are removed. Your machine will run uninhibited until something references the memory that has now disappeared at which point the referencing task will fail.

Your hard disk drive and SSD may also be failing. CHKDSK /R will scan for bad sectors but it won't catch non-deterministic read errors and long-latency events. Check the health of the drive using a vendor supplied S.M.A.R.T monitoring tool.


Wow. Amazing reply. I really appreciate the effort and time you set aside to assist me with this issue. Thanks ! :) 

I downloaded the "Western Digital Data LifeGuard Diagnostics" app since I have a WD hard drive. Fortunately, it was also able to scan my ssd. On the "Smart Status", a green check mark is displayed followed by "Pass". So it seems to be good. Is there any possibility that it is my motherboard. For example, just before I booted up to reply to your message, I went into the bios. But when I just clicked on the cd drive in the boot order section, both my hdd and ssd disappeared from the list. Seems fishy. Especially after my endeavors and 2 RMA's with this particular motherboard.
Lat time I had to RMA because the motherboard was not detecting the hdd and ssd At all. Only the cd drive was detected.

Anyways, which components could be the cause? Mainly, the RAM, hdd and ssd, and the motherboard, right? Those could be the only culprits, right? But, if the storage devices pass the test than it is 100% the motherboard, right?

I will be running in CHDSK /R in a moment and I will respond back with those results.

Thanks
Stephen
m
0
l
July 18, 2014 9:33:08 AM

TechiGamer said:
Pinhedd said:
TechiGamer said:
Hi

Recently I have been receiving this blue screen of death with the error being "Kernel data inpage error". I'm just about tired of always being booted from what I was doing every so often because of this error. During my research, I noticed that it was considered a registry issue. Therefore, I completely formatted my ssd and hdd and did a complete clean install. However, that Still has not solved the puzzle. I am still getting this error!?!?!?!? What can I do?? Is it my motherboard??? Please help

Thanks

System specs.

i5 4670k

8gb ddr3 ram

z87-D3HP motherboard

750 watt Antec 80 gold plus PSU

7970 OC + r9 280x CF

128 gb ssd

1Tb Hdd


Hi,

the KERNEL_DATA_INPAGE_ERROR occurs when memory in the kernel's paged pool is swapped to the hard disk and cannot be read when needed at a later time.

Windows broadly divides memory into three pools:

The kernel non-paged pool

The kernel paged pool

The user paged pool

The kernel non-paged pool contains memory that must be in memory at all times. This includes all of the memory used to handle interrupts, track thread and process states, and handle deferred procedure calls. Memory allocated to the kernel or drivers from this pool will always remain resident in memory at all times, it will never be swapped out to the hard disk drive and referencing memory in the non-paged pool will never generate a page fault (in fact, PAGE_FAULT_IN_NONPAGED_AREA is another famous BSoD).

The kernel paged-pool contains kernel memory that can be swapped to a page file or swap file located on a secondary storage medium such as a hard disk drive. If memory is infrequently used, it may be swapped out. If the kernel references memory located in the kernel paged-pool it will generate a page-fault interrupt which will bring it back into the physical memory (note that as I mentioned above, the page-fault interrupt handler operates only on non-paged memory).

The user paged-pool contains memory that can be allocated to user processes.

To best address your question, imagine a scenario when an application causes a page fault by referencing memory that has been swapped out to a page file that is located on a secondary storage device that has been removed or is inaccessible. That memory can no longer be found, so the application must be terminated as it can no longer proceed.

The same is true when the kernel causes a page fault by referencing memory that has been swapped out to a page file that is located on a secondary storage device that has been removed or is inaccessible. The kernel cannot proceed to a consistent state, so it must terminate and halt the machine.

If you have any removable storage devices, make sure that they are configured as such. If they contain page files (pagefile.sys, swapfile.sys, hiberfile.sys) they may unwittingly be used to store memory and that memory will go with them when they are removed. Your machine will run uninhibited until something references the memory that has now disappeared at which point the referencing task will fail.

Your hard disk drive and SSD may also be failing. CHKDSK /R will scan for bad sectors but it won't catch non-deterministic read errors and long-latency events. Check the health of the drive using a vendor supplied S.M.A.R.T monitoring tool.


Wow. Amazing reply. I really appreciate the effort and time you set aside to assist me with this issue. Thanks ! :) 

I downloaded the "Western Digital Data LifeGuard Diagnostics" app since I have a WD hard drive. Fortunately, it was also able to scan my ssd. On the "Smart Status", a green check mark is displayed followed by "Pass". So it seems to be good. Is there any possibility that it is my motherboard. For example, just before I booted up to reply to your message, I went into the bios. But when I just clicked on the cd drive in the boot order section, both my hdd and ssd disappeared from the list. Seems fishy. Especially after my endeavors and 2 RMA's with this particular motherboard.
Lat time I had to RMA because the motherboard was not detecting the hdd and ssd At all. Only the cd drive was detected.

Anyways, which components could be the cause? Mainly, the RAM, hdd and ssd, and the motherboard, right? Those could be the only culprits, right? But, if the storage devices pass the test than it is 100% the motherboard, right?

I will be running in CHDSK /R in a moment and I will respond back with those results.

Thanks
Stephen


I doubt that the primary memory (RAM) has any role in this. This BSOD is being generated because the kernel's memory manager is unable to find kernel memory that has been ejected from primary memory and written to a backing store located in secondary memory. You should still run Memtest86 to be certain though.

You should also make sure that your motherboard has the latest UEFI firmware revision installed. The latest revision available for your motherboard is F7c which can be downloaded from Gigabyte's website.
m
0
l
July 19, 2014 12:13:52 AM

*** if you get a inpage error and do not get a memory dump: Look for a drive disconnection issue*********

a common cause of a kernel inpage error would be a disconnection of a drive.
This can be caused by some simple issues, Thermal expansion/contraction of the sata cable can make and break a connection several times a second. You might consider checking the cable connections for your drive with on the sata port.

There can be bugs in the chipset drivers for the sata port ( update chipset drivers, or change the cable to connect to another Sata chipset if you have 2.

-there can be bugs in the BIOS setup for the electronics on your board (update the BIOS)

- special issues involving solid state drives. where the SSD gets behind on it cleanup routines and takes too long to respond
causing windows to reset the port. and the drive does not reconnect.

sometimes you can enable hotswap in BIOS on the sata port of the drive and it will reconnect (hides the disconnect issue but you don't bugcheck)

- sometimes you have to update the firmware of the SSD because of bugs that cause the drive not to respond correctly
(often caused by using image software to install the OS)
- sometimes you can boot your machine into BIOS and leave the SSD drive powered, after 5 mins the cleanup routines in the drive will start and it can fix the errors. (just leave it powered and not in use for a few hours)
(most of the time you will see a event viewer error from the disk subsystem that indicates that the sata port was reset)

you can also get inpage error with some physical problems with the memory sticks (basically, thermal breaks on certain pads where the memory chips connects to the circuit board. The defect is hard to detect because and most people will think it is related to when they first turn on the machine but it occurs due to the heat cycle of the memory stick. (when the board is cool, the circuit contracts and opens a address line (line disconnected therfore wired to 0 logic) drivers are loaded into the memory then the memory chip heats up in 5 to 7 seconds circuit and the connection is made and the address line gets set correctly. This can cause a whole block of memory to move after a device driver was loaded into it. Results is memory corruption that only occurs when the memory is cool. And the memtest86 would not find this type of failure.



m
1
l
!