BSoD: KERNEL_DATA_INPAGE_ERROR running some programs after reinstall

Satori · 17 Apr 2014

I've reinstalled Windows 7 on this machine several times, and even on a new hard drive in it, without these problems happening. A few weeks ago, someone grabbed my Latitude e4300 out of my hands and broke part of its case and one of my front teeth against each other. Since the part that broke was where the power adapter plugs in and I didn't want it coming away from the motherboard, I got a new case and transferred the innards over to the new one. In the process, the internal clock battery was disconnected and it not only forgot the time, but also the BIOS settings and couldn't come back from Hibernate (due to the e4300's notable SATA AHCI/IRRT quirk). Before I found out the cause, I ended up just reinstalling Windows 7 again.

My User data, including about 5 gigs of downloads, was in my Windows.old structure and I copied the files in it over. Now, when I try running programs that are particularly hard drive-intensive (a fresh install of uTorrent, an install of the same copy of PowerPoint I'd used before, and ditto with BlueStacks) uTorrent BSoDs while it's rushing to scan my downloads folder, and the other two halt midway through installation. PowerPoint complains the install file has been corrupted.

The uTorrent BSoD throws a KERNEL_DATA_INPAGE_ERROR, so I ran CHKDSK and got this interesting error (Error Code: 2000-0142) during the DST Short Test. The hard drive was working fine for weeks after the attack with the old Windows install, so I have to think something's off in the driver, firmware, lost BIOS settings or controller.

Arc · 18 Apr 2014

Stop 0xF4 alongwith Stop 0x7A.

Code:

BugCheck F4, {3, fffffa80064c29e0, fffffa80064c2cc0, fffff80002d7f260}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------

Code:

BugCheck 7A, {fffff6fc50021f08, ffffffffc000009d, a2e80820, fffff8a0043e1d0e}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3423e )

Followup: MachineOwner
---------

Code:

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50021f08, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 00000000a2e80820, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a0043e1d0e, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Code:

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

So it is some issue with the HDD. Seagate ST9500424AS 500GB SATA 7.2K RPM 16MB 2.5IN DISC.

Test the HDD: SeaTools for DOS and Windows - How to Use

Also reseat the sata and power. Change the SATA cable if possible, and apply it to an unused SATA port on the motherboard.

Let us know the results.

Satori · 18 Apr 2014

Firstly, thank you kindly for the assistance.

Installing SeaTools for Windows halted, requiring dotNet 4 to be installed.
Installing dotNet 4 halted, complaining that it couldn't find one of the files specified.
I went to the AppData's Temp directory to delete the folder dotNet was using and try redownloading the files, but the problem recurred.

Installing SeaTools for DOS per the directions caused the system to boot to a screen which read only, "FREEDOS" in the upper-left corner, accompanied by a cursor which accepted no commands. After several keypresses, the system would beep at each new keypress. The file written to my USB drive was SeaTools.img, renamed from SeaTools.ima, which I'd extracted from the FreeDOS image.

Arc · 18 Apr 2014

You may get dotnet standalone, and install it.
Download .NET Framework Version 4.5.1 - FileHippo.com

If the burn to USB does not work properly, there is another option to burn it in a blank disc. You may take that way too.

Satori · 18 Apr 2014

Thank you. The standalone also threw a fatal error, logged here. I do not have a CD to burn.

As my laptop wasn't doing any of this before the reinstall, even after the attack, a physical problem seems likely anyway but I can't open it at present.

Arc · 18 Apr 2014

A bland disc is not too tough to obtain. Get the seatools image burned on a blank CD and test the HDD.

If the HDD is corrupt beyond a level, it will not be able to write the data on it.

Satori · 18 Apr 2014

It's a little tough, as I'm living on the street with a laptop and have no income. It may be a while before I can continue this case. Will the thread close automatically after a certain period?

Arc · 18 Apr 2014

No, it will remain open forever, even after you mark it as solved.

Satori · 24 Jun 2014

Managed to get the SeaTools log file, attached.

It repaired a few errors, but the problem continues. Every so often Windows will check the drive when I start up, fix a whole host of things, and then continue. Seems like data isn't being written correctly sometimes, particularly when there's a lot of drive activity. This suggests an IRRT problem.

essenbe · 25 Jun 2014

Satori, can you tell me if you are meaning IRST? Intel Rapid Storage Technology? If so, can you tell me why you think that? I believe your Hard Drive is on it's way out. If you have a way to do it, I would suggest you back up your personal files to another location. Your drive was found to have errors during the Long Drive Self Test and repairs were done. Yet, if I understand correctly, Windows keeps finding errors and scanning the drive. What that indicates is your drive had errors during the test and those errors were fixed. More correctly, it is most probable that your hard drive controller was instructed where not to place data. Yet, Windows keeps finding more errors. That means the errors are growing and will keep increasing until the drive no longer is functional and you will lost everything on it. From my experience, that is what I see happening. You are being warned that the drive is going to fail.

I really don't think IRST has anything to do with a failing hard drive. But, if you would, please click the start button, and type device manager in the search box, click on the device manager entry that appears. Click the arrow next to IDE ATA/ATAPI controllers and post a screenshot of the page. Screenshots and Files - Upload and Post in Seven Forums .