===============
http://www.tomshardware.com/answers/id-2223087/kernel-data-inpage-error.html
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.
------------------------------
**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.
==========
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/kerneldatainpageerror-every-few-days/650474dd-46e2-42c1-b74b-21413fbaad55
The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.
Method 1: I would suggest you to try the steps provided below and check if it helps.
a) Click on Start, type Command Prompt, right click on it and select to run as administrator.
b) In command prompt, type chkdsk volume: /f /r and hit enter to check and repair any volume disk errors or bad sectors present on the drive which would be causing this problem.
==========
try ssd life : http://ssd-life.com/
download UBCD, and run memtest86+ for ram (couple of passes)
For an SSD - check the manufacturers site for a diagnostic tool, or post the model here
eg, for an intel SSD:
eg, for an intel SSD:
Intel® Solid-State Drive Firmware Update Tool
http://windows.microsoft.com/en-US/windows7/Check-a-drive-for-errors
LibreOffice
Firefox
OpenSUSE
No comments:
Post a Comment