Bsod kernel_data_inpage_error

[special jester]

Hello All.

I could use some help. I've been having BSOD problems for a few months now. I went to stone computers (local computer store) and they did a reformat and a virus check with AVG and told me they fixed the issue. Of course they didn't and I am still having problems.

I tried upping the fan speed on my graphics card and that didn't work. I downloaded bluescreen view and did a scan and if you need I can upload any images you would need to help me out.

I think I uploaded what you guys need for BSOD posts. It should be in the attachments

 

[americancritic2]

Hello and welcome to the seven forum.

Hang on as a BSOD expert will look at your problem and then they will know how to help you...

 

[Gator]

Hello Jester, welcome to Sevenforums!

Sorry to hear about your problems with local shops, its all too common. Luckily now you have us.

Here is a summary of the BSOD's you're receiving

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 7A[/COLOR], {fffff6fc40027d40, ffffffff[COLOR=Red]c000000e[/COLOR], 13c82abe0, fffff88004fa8000}

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36c1a )

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

0: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 7A[/COLOR], {fffff6fc40019878, ffffffff[COLOR=Red]c000009d[/COLOR], a367ebe0, fffff8800330f000}

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

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

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
3: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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.

Debugging Details:
------------------


[COLOR=Red]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.[/COLOR]

DISK_HARDWARE_ERROR: There was error with disk hardware
[COLOR=Red]
BUGCHECK_STR:  0x7a_c000000e[/COLOR]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

All of your BSODs are pointing to some sort of problem with your hard drive or controller.

Make sure your cables are all secure. Switch to a different Sata connection and see if that helps.

If problems still persist (actually either way do this) run Hard drive tests
SeaTools for Windows | Seagate

 

[special jester]

Okay. I will give that a try. I'll let you know if it works.

 

[americancritic2]

Hi Gator, great post and thank you for helping special jester...

 

[special jester]

Still having BSOD

I tried replacing an ATA cable with a SATA cable and changed the port on the motherboard. I ran a seagate Long Generic test and the program said that my computer passed.

Still scratching my head on this one. Any ideas?

 

[Gator]

Did you receive a new BSOD?

If so, can you upload the new dump files?

 

[special jester]

Oh right. Here it is.

 

[Gator]

Hi Jester, you're still getting the same BSOD's

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 7A[/COLOR], {fffff6fc400098f8, ffffffff[COLOR=Red]c000000e[/COLOR], 1d84c0860, fffff8800131fdc4}

GetPointerFromAddress: unable to read from fffff8000330f278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
Probably caused by : memory_corruption

Followup: memory_corruption
---------

0: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]KERNEL_DATA_INPAGE_ERROR (7a)[/COLOR]
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: fffff6fc400098f8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000001d84c0860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800131fdc4, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


[COLOR=Red]ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.[/COLOR]

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

This is looking more and more like a hardware issue. Either your Hard drive or the Disk controller itself

Try running chkdsk /f /r (See option two for command line)
http://www.sevenforums.com/tutorials/433-disk-check.html

 

[special jester]

I tried removing the serial ATA cable connecting the hard drive and disk drive to the motherboard. I replaced the one connecting the hard drive with a SATA cable and I couldn't find my other SATA cable so I just left the disk drive unhooked. I was trying to run the disk check that you asked me to but before I could spend more than one or two minutes on the computer all my icons would disappear on my desk top and be replaced with this.

 

[Gator]

Which program were you trying to run when receiving that error?

 

[special jester]

I was just running waterfox and trying to use the internet and also so my data check.

I just went out and bought a new sata cable for my disk drive to connect it to my mother board and now everything seems to be running alright but I will have to wait and see. I still have yet to do the data check.

 

[special jester]

I was actually trying to run the data check in the command prompt.

 

[Gator]

I was actually trying to run the data check in the command prompt.

Ok, after buying a new cord you haven't had a BSOD?

Have you gotten further than before (without BSOD)?

 

[special jester]

I haven't gotten one yet. I just had that one error again. The one with the picture that I sent. And it was after replacing the cords.

 

[special jester]

It seems the only way to get the computer back to normal is to restart it with a cold boot.

 

[special jester]

Here are some pictures of the most recent error.

 

[Gator]

Ok I still think this is going to go down to your Disk Controller but let me get another set of eyes here just to be sure.

However, it is encouraging that no BSODs have happened, its still a little concerning that you're getting that type of error.

Cannot find drive specified is not a great sign.

 

[special jester]

Not sure what happened but the error keeps happening and it's really weird. The computer is essentially unusable right now. I'm not sure why it's getting worse and I don't know what it could be.

 

[Gator]

If you can get onto the system, please try to see if you can follow this guide so we can eliminate some potential causes
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Lets try to check the Disk with Seatools, start with Option 2
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

If you can't run chkdsk while you're in OS, try in a command prompt before booting up
http://www.sevenforums.com/tutorials/682-command-prompt-startup.html

Run this command:
chkdsk c: /f /r