TechiGamer :
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.