• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Installing XP: KERNEL_DATA_INPAGE_ERROR

V

vicwang

Member
I keep getting the following BSOD error message during my clean Win XP installation, immediately after it has finished copying files needed for the installation:

A problem has been detected... blah blah...

KERNEL_DATA_INPAGE_ERROR

i8042prt.sys Address blah blah...

From doing a few searches, it appears that perhaps my HDD is bad. Any other ideas?

Maxtor 40 gig HDD
MSI K7N420 (nForce 420D) motherboard
256 MB PC2100 DDR
Sony 52X CD-ROM

By the way, I've tried partitioning/formatting the drive with the Maxblast software and with the WinXP built-in partitioning app, but neither way works.
 
This is going to sound odd, but, I did some searching on that I8042prt.sys file and kept on seeing computer mice being associated with it. Microsofts Knowledge Base had nothing pertaining to the KERNAL_DATA_INPAGE_ERROR at all. So obviously this isn't common. Some things you could try is a different mouse, or I don't know how, but disable the mouse port and use a USB mouse. Unless of course you are already using USB mouse, then go to PS/2 mouse. I hope this helps even a little bit.
 
By the way I found something quite interesting on About.com. It talks about how to crash Win2K with a BSOD just by changing a Registry parameter that looks something like a mouse command and is placed under a folder called I8042prt! This link may not work but here, About.com. If the link doesn't work but you really have to see it you can just search at about.com just on I8042prt without the ".sys".

Here is some more information I found pertaining to the KERNEL part. I copied it from a site called Systems Group Inc.


KERNEL_DATA_INPAGE_ERROR (0x7A)

The requested page of kernel data could not be read in. This error is
caused by a bad block in the paging file or a disk controller error.
See also KERNEL_STACK_INPAGE_ERROR.

Parameters
----------

1 - Lock type that was held (value 1, 2, 3, or PTE address)
2 - Error status (normally I/O status code)
3 - Current process (virtual address for lock type 3, or PTE)
4 - Virtual address that could not be in-paged


It even gives information pertaining to the parameters.
 
Thanks guys! I'm using a Logitech USB optical mouse plugged into the PS/2 port with a PS/2 adapter, if that means anything. I'll try it again without the mouse to see if it makes any difference. If the BSOD happens again I'll jot down the error codes to see if they can tell me anything.

That registry hack was interesting... but I assume it wouldn't do any good while doing a clean install.

I'm still thinking it may be HDD related though. One thing I forgot to mention earlier is that while partitioning the drive with MaxBlast, the first time I tried it showed up as a *560 GIG* drive, with fourteen 40-gig partitions. Needless to say, it errored out when I tried to partition it with the default setup. The next time I ran it, it properly reported the drive as being 40 gig and I was able to partition it into two 20-gig partitions.

One other thing... After running MaxBlast and rebooting, if I boot to the HDD and hit CTRL, it shows a boot menu where I can either boot from A:\ or C:\. It mentions something about Windows setup disks. However, this wouldn't apply when doing a clean XP install, right? I'm just booting from CD. I'd better not have to use XP Install disks....
 
Well what a coincidence. When I removed the mouse, I was able to circumvent the KERNEL_DATA_INPAGE_ERROR message, but upon reboot it would give me a "Unable to read disk" error. So I ran the Maxtor diagnostic app and it failed the SMART Self Test every time. So it looks like the mouse driver was causing issues AND the HDD was bad. Oh well... Thanks for the help anyway!
 
It could just be a faulty IDE cable, try a different cable before giving up on the drive.
 
A couple of other things to try, after trying different cable if the issue persists then try it in the 2nd IDE slot. Also, was the HDD on the cable by itself? what else is on the cable with it? did you leave it set to factory default or config it as master?
 
Hmmm... that's a good idea, I'll try a different cable and the other IDE channel before giving up on it. Right now I have it on the primary IDE channel as the master device and a CD-ROM on the same cable as slave. Not the best setup performance-wise, but it's not going to be used for much more than basic tasks so I'd prefer to keep the case clutter free. I'll see if it makes any difference.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top