kernel_data_inpage_error (BSOD)

justme101 · 31-10-2011, 04:51 PM

I am laughing as i write this post

because till now i didn't have any BSOD issues with windows 7 but i am getting quite a few of them after reading somebody else's BSOD problems in the digit forum itself. could it be a "trouble reading virus"

Ok now the problem:

The pc runs smoothly while playing games and browsing net but as soon as i insert a CD/DVD in the dvd-drive the PC hangs up and after a few seconds gives me this BSOD - "kernel_data_inpage_error".

I setup windows to create a dump file and below is the link to the file.

https://skydrive.live.com/redir.aspx...1a53MD*QaNQ%24

So can anyone tell what suddenly went wrong???

Zangetsu · 31-10-2011, 05:30 PM

I guess the problem is with every CD/DVD u put in DVD drive..

check the cable connections of DVD drive.
how old is the DVD drive?

d6bmg · 31-10-2011, 10:07 PM

This generally happens when kernel data from the paging file could not be read into memory.

Update the ata driver (i.e. somethinglike this: ataport.sys )

**asingh** · 01-11-2011, 12:04 AM

Just looked at the minidump:

Quote:

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: fffff6fc40008278, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000003d457860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800104f93c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff880031cb5e0 -- (.trap 0xfffff880031cb5e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88001047500 rbx=0000000000000000 rcx=fffffa80047ae050
rdx=fffffa8005d7a010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800104f93c rsp=fffff880031cb778 rbp=fffffa8003b4c370
r8=0000000000000007 r9=fffffa80047ae1a0 r10=0000000000000000
r11=fffffa8005d7a1b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
ataport!ChannelQueryDeviceRelations:
fffff880`0104f93c 4053 push rbx
Resetting default scope

LOCK_ADDRESS: fffff80002ecf400 -- (!locks fffff80002ecf400)

Resource @ nt!PiEngineLock (0xfffff80002ecf400) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff80002ecf400
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff80002d40168 to fffff80002ccb740

STACK_TEXT:
fffff880`031cb2c8 fffff800`02d40168 : 00000000`0000007a fffff6fc`40008278 ffffffff`c000000e 00000000`3d457860 : nt!KeBugCheckEx
fffff880`031cb2d0 fffff800`02cbd52b : fffffa80`0608b4e0 fffff880`031cb440 fffff800`02e58440 00000000`00000028 : nt! ?? ::FNODOBFM::`string'+0x34c0e
fffff880`031cb3b0 fffff800`02ce65c4 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`031cb5e8 : nt!MiIssueHardFault+0x28b
fffff880`031cb480 fffff800`02cc982e : 00000000`00000008 fffffa80`05d7a010 fffffa80`00000000 fffff880`031cb670 : nt!MmAccessFault+0x11c4
fffff880`031cb5e0 fffff880`0104f93c : fffff880`0104d4ce 00000000`00000000 fffff880`031cb840 fffff800`02dcad30 : nt!KiPageFault+0x16e
fffff880`031cb778 fffff880`0104d4ce : 00000000`00000000 fffff880`031cb840 fffff800`02dcad30 fffffa80`0441ab40 : ataport!ChannelQueryDeviceRelations
fffff880`031cb780 fffff800`0308a06e : 00000000`00000000 00000000`00000000 fffffa80`03b4c370 fffff880`009e8180 : ataport!IdePortDispatchPnp+0x22
fffff880`031cb7b0 fffff800`0308a3da : 00000000`00000000 fffffa80`03b4c370 fffff800`02dcad30 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031cb7f0 fffff800`0308c6c7 : fffff800`02ecf1c0 fffffa80`0441bd90 00000000`00000002 00000000`000004a0 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031cb8b0 fffff800`030b82cc : fffffa80`0441bd90 fffffa80`04410020 fffffa80`0441bd90 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031cb910 fffff800`030b88d8 : fffff800`02eccd80 00000000`00000000 00000000`00000001 fffff800`02f38840 : nt!PipProcessDevNodeTree+0x21c
fffff880`031cbb80 fffff800`02dcd3a7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031cbbd0 fffff800`02cd8961 : fffff800`02dcd080 fffff800`02fc7c01 fffffa80`039deb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031cbc70 fffff800`02f6fc06 : 00978d50`0051af60 fffffa80`039deb60 00000000`00000080 fffffa80`039cc040 : nt!ExpWorkerThread+0x111
fffff880`031cbd00 fffff800`02ca9c26 : fffff880`02f63180 fffffa80`039deb60 fffff880`02f6dfc0 0051d390`00982330 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd40 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cb020 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
ataport!IdePortDispatchPnp+22
fffff880`0104d4ce eb04 jmp ataport!IdePortDispatchPnp+0x28 (fffff880`0104d4d4)

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: ataport!IdePortDispatchPnp+22

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ataport

IMAGE_NAME: ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc118

FAILURE_BUCKET_ID: X64_0x7a_c000000e_ataport!IdePortDispatchPnp+22

BUCKET_ID: X64_0x7a_c000000e_ataport!IdePortDispatchPnp+22

You can try these links to fix ataport errors:

A rootkit problem. Which can be caught by TDSSKiller.

Defrag your HDDs.

Though one minidump is not enough to diagnose.

justme101 · 01-11-2011, 02:15 PM

Quote:

Originally Posted by Zangetsu

I guess the problem is with every CD/DVD u put in DVD drive..

you mean more than 50 DVD's i possess have the same problem??

@asingh @d6bmg

well i did a check disk of all the drives from the command prompt , no errors on disk found and after i restarted the PC the trouble with the CD/DVD's was gone.

If i get any more BSODs i'll post here and then we'll see what the problem is. In the meanwhile i'll check out the ata driver thing.