Kernel_Data_Inpage_Error

[provenlogic]

Ok guys, here's one even i haven't been able to get a handle on. It's reguarding my laptop, Dell Inspiron 4150, WinXP Pro, P4m 1.4Ghz, 512Mb RAM.

I've had it for quite some time, it's old obviously. I usually keep it laying around in case i want to check my mail or go online without having to turn on my workstation PC. So usually when i'm done i just close the lid and let it go into standby. I've been doing that forever with no problems.

In the last 2 weeks or so, it's started giving me a BSoD whenever i flip open the laptop and it tries to resume from standby. BSoD reads KERNEL_DATA_INPAGE_ERROR, beginning dump of physical memory, etc... etc... (i'll come back with the specific error address when it happens again).

That's not the worst part however. When i turn on the computer again after the BSoD, i get a "WARNING: Primary Hard Drive 0 Failure! No Boot Options available, press F1 to try again or F2 for setup". I'll have to power it down and turn it on again, sometimes 4 or 5 times until it boots normally. This last time it happened i had to remove the laptop battery and leave it unplugged for a few minutes before it would reboot without a HDD0 failure error.

I've looked up the KERNEL_DATA_INPAGE_ERROR online, but haven't found any reall information as to what to do to prevent it from happening again. I know what exactly the error is, i can read about that until i'm blue in the face, i just can't seem to find any viable solutions anywhere. So any ideas?

[techboywi]

Sounds like the hard drive itself may be dying.

[T-Rexx]

^ Yep! Time for a new drive. Or maybe even a new computer, PL!

[winterknight]

As the others have said, KERNEL_DATA_INPAGE_ERROR is usually a signal of imminant catastrophic hard drive failure. We've had three PC's at work go that way in the last year.

There's nothing to be done for it except swap the HDD out and put a new one in. Sorry.

[Corny]

does this *ONLY* happen when you close the LCD, or maybe use some other power safing/suspend to disk options?

[noelie]

From: http://www.osronline.com/article.cfm?id=336

What Happened?

When one or more pages of physical memory that have been marked as pageable are not actively being used by anyone in the system, the Memory Manager may free up that physical memory by temporarily storing the contents of those pages in the paging file. The next time the paged out memory is accessed, a page fault will occur (see So, Exactly What Is A Page Fault).

As part of processing that page fault, the Windows Memory Manager will need to use the storage stack to read the data it stored in the paging file. If the storage stack fails to retrieve the data from the paging file for just about any reason, the system bugchecks with KERNEL_DATA_INPAGE_ERROR. The reasons for such a failure are generally limited to the lack of system resources on a highly stressed system or hardware failure.

Who Did It?

This bugcheck is caused exclusively by a malfunctioning driver in the storage stack. The second parameter to the bugcheck is the NTSTATUS error value that was returned by a member of the storage stack and that ultimately led to the bugcheck. The DDK documentation lists common error values and the components in the storage stack that return them, so consult the documentation in order to gain clues as to which component is malfunctioning.

How Should I Fix It?

The steps that you would need to take in order to resolve this problem depend on the error code returned in the second bugcheck parameter.


We need the rest of the error code provenlogic.


But it does seem to indicate either bad RAM or a dying HDD.

[provenlogic]

does this *ONLY* happen when you close the LCD, or maybe use some other power safing/suspend to disk options?

it ONLY happens when i open the lid and the computer tries to resume from suspend. And it doesn't happen every time, it happens randomly, but only when i open the lid to resume from suspend.

I'll come back with the error code next time the error pops up.

[Corny]

ok then it seems like a flawed acpi function/driver to me. it's something where almost no bios is without bugs - look if you find new drivers for your chipset or a bios upgrade from your manufacturer

[provenlogic]

ok then it seems like a flawed acpi function/driver to me. it's something where almost no bios is without bugs - look if you find new drivers for your chipset or a bios upgrade from your manufacturer

I just wonder why it popped up so suddenly...

[noelie]

To quote corny "it's something where almost no bios is without bugs" and that's why it popped up so suddenly.

I never enable resume, standby or hibernate on a PC or laptop because of it being so buggy.

I know it means you lose certain convenient functions but the downside is too much (as you've just discovered).

[provenlogic]

Here is the actual BSoD, i snapped a pic of it with my cell phone (easier than typing it out).




And the subsequent startup message when the computer reboots.

[provenlogic]

And since a different file is ID'd as the culprit each time, here's another BSoD.

[noelie]

Hi provenlogic,

Did I not PM you a link to an app that might help? Did you use it?

If you can get a copy of ERD Commander 2005 (Winternals) it has a utility to disable certain devices and drivers or if you can get BartPE and do a chkdsk from that it may help.

The worse case scenario is that your HDD is a goner but it could be as simple as data corruption.