[coronoahcoro]

Hi all, one of the PCs in the company froze once in a while (like 2-3 times in a week). Sometimes it gave the blue screen sometimes it just froze and the user had to restart it. I'm having a problem to regenerate the error but here is the dump file from BlueScreenView:

==================================================
Dump File : Mini051310-01.dmp
Crash Time : 5/13/2010 3:21:06 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc0411600
Parameter 2 : 0xc000000e
Parameter 3 : 0x10b53860
Parameter 4 : 0x822c06cc
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+89a7c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5938 (xpsp_sp3_gdr.100216-1514)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini051310-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 6001
==================================================

Any help is appreciated.

The PC is running Windows Vista 32-bit

[Advertisements]

KERNEL_DATA_INPAGE_ERROR aka Stop Error code 0x7a:

The Stop 0×7A message message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

Or in plain English: It's usually a hardware problem, typically defective memory, a failing hard drive or (on ocassion) a problem with the motherboard.
You may be able to get a utility from the website of the manufacturer of the hard drive to do diagnostics on it.
For memory, you can use this: http://www.memtest.org/

[Neil Jones]

KERNEL_DATA_INPAGE_ERROR aka Stop Error code 0x7a:

The Stop 0×7A message message indicates that the requested page of kernel data from the paging file could not be read into memory. This Stop message is usually caused by a bad block (sector) in a paging file, a virus, a disk controller error, or failing RAM. In rare cases, it is caused when nonpaged pool resources run out. It is also caused by defective hardware.

Or in plain English: It's usually a hardware problem, typically defective memory, a failing hard drive or (on ocassion) a problem with the motherboard.
You may be able to get a utility from the website of the manufacturer of the hard drive to do diagnostics on it.
For memory, you can use this: http://www.memtest.org/