KERNEL_DATA_INPAGE_ERROR

NTFSD
1

hi, i have encountered a KERNEL_DATA_INPAGE_ERROR while testing my filter
driver. the status is STATUS_NO_SUCH_DEVICE. can i conclude that this is a
purely hardware problem?

this is the bugcheck analysis:

****************************************************************************
***
*
*
* 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.
Arguments:
Arg1: c03e6688, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: f99a2bb4, current process (virtual address for lock type 3, or PTE)
Arg4: 0c26e860, virtual address that could not be in-paged

Debugging Details:

BUGCHECK_STR: 0x7a_c000000e

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

DISK_HARDWARE_ERROR: There was error with disk hardware

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f5fa4494 805258ca 00000003 f5fa47c4 c03e6688
nt!RtlpBreakWithStatusInstruction
f5fa44e0 80526160 00000003 f99a2bb4 c03e6688 nt!KiBugCheckDebugBreak+0x19
f5fa48ac 805266db 0000007a c03e6688 c000000e nt!KeBugCheck2+0x46d
f5fa48cc 8051abc0 0000007a c03e6688 c000000e nt!KeBugCheckEx+0x19
f5fa48f4 804f0da4 80d6da50 c03e6688 f99a2bb4
nt!MiWaitForInPageComplete+0x1c3
f5fa4968 804f530c 81543290 f99a2bb4 c03e6688 nt!MiDispatchFault+0x29e
f5fa49b8 804dcc5e 00000000 f99a2bb4 00000000 nt!MmAccessFault+0x5bb
f5fa49b8 f99a2bb4 00000000 f99a2bb4 00000000 nt!KiTrap0E+0xb8
f5fa4a40 804eca36 81782030 81639420 f5fa4abc atapi!IdePortDispatchPnp
f5fa4a50 8056b1ed 00000000 8178edd0 8178edd0 nt!IopfCallDriver+0x31
f5fa4a7c 804d7745 81782030 f5fa4a98 8178eeb0 nt!IopSynchronousCall+0xb8
f5fa4abc 805542be 00000000 8178f630 00000001 nt!IopQueryDeviceRelations+0x39
f5fa4ad0 8055abfe 8178edd0 00000001 8178edd0 nt!PipEnumerateDevice+0x20
f5fa4d18 8055af62 8178edd0 00000001 00000000 nt!PipProcessDevNodeTree+0x1b1
f5fa4d4c 804d7125 00000003 80549fc0 8054eddc nt!PiProcessReenumeration+0x5e
f5fa4d74 804ed629 00000000 00000000 813ea020 nt!PipDeviceActionWorker+0x133
f5fa4dac 8057c73a 00000000 00000000 00000000 nt!ExpWorkerThread+0xfe
f5fa4ddc 805124c1 804ed556 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
atapi!IdePortDispatchPnp+0
f99a2bb4 0000 add [eax],al

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: atapi!IdePortDispatchPnp+0

MODULE_NAME: atapi

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6ddb04

STACK_COMMAND: kb

BUCKET_ID: 0x7a_c000000e_atapi!IdePortDispatchPnp+0

Followup: MachineOwner

Ampsi

2

This doesn’t look like a typical disk read error; instead it looks more like
a device removal error (did you remove the driver from which you had
booted?)

The IDE drive attempts to access memory - the memory is VALID, but not
present, so the memory manager issues a paging I/O to fetch it (you don’t
show us the PTE here, try doing “!pte c03e6688” to see information about the
page for the faulting operation.) But the paging I/O fails to complete
because the device is gone. This could happen if someone disconnected a
physical disk on which a paging file was stored (for example).

That seems more likely given the earlier steps in that stack - PnP is
re-enumerating the device relations (looking for new or missing devices)
because of some change in configuration.

Another possibility is that your filter driver made it appear as if the
system had reconfigured in some way.

But neither of these sound like a typical hardware failure.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Ampsi [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Sunday, May 25, 2003 11:42 PM
To: File Systems Developers
Subject: [ntfsd] KERNEL_DATA_INPAGE_ERROR

hi, i have encountered a KERNEL_DATA_INPAGE_ERROR while testing my filter
driver. the status is STATUS_NO_SUCH_DEVICE. can i conclude that this is a
purely hardware problem?

this is the bugcheck analysis:

****************************************************************************
***
*
*
* 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.
Arguments:
Arg1: c03e6688, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: f99a2bb4, current process (virtual address for lock type 3, or PTE)
Arg4: 0c26e860, virtual address that could not be in-paged

Debugging Details:

BUGCHECK_STR: 0x7a_c000000e

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

DISK_HARDWARE_ERROR: There was error with disk hardware

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f5fa4494 805258ca 00000003 f5fa47c4 c03e6688
nt!RtlpBreakWithStatusInstruction
f5fa44e0 80526160 00000003 f99a2bb4 c03e6688 nt!KiBugCheckDebugBreak+0x19
f5fa48ac 805266db 0000007a c03e6688 c000000e nt!KeBugCheck2+0x46d
f5fa48cc 8051abc0 0000007a c03e6688 c000000e nt!KeBugCheckEx+0x19
f5fa48f4 804f0da4 80d6da50 c03e6688 f99a2bb4
nt!MiWaitForInPageComplete+0x1c3
f5fa4968 804f530c 81543290 f99a2bb4 c03e6688 nt!MiDispatchFault+0x29e
f5fa49b8 804dcc5e 00000000 f99a2bb4 00000000 nt!MmAccessFault+0x5bb
f5fa49b8 f99a2bb4 00000000 f99a2bb4 00000000 nt!KiTrap0E+0xb8
f5fa4a40 804eca36 81782030 81639420 f5fa4abc atapi!IdePortDispatchPnp
f5fa4a50 8056b1ed 00000000 8178edd0 8178edd0 nt!IopfCallDriver+0x31
f5fa4a7c 804d7745 81782030 f5fa4a98 8178eeb0 nt!IopSynchronousCall+0xb8
f5fa4abc 805542be 00000000 8178f630 00000001 nt!IopQueryDeviceRelations+0x39
f5fa4ad0 8055abfe 8178edd0 00000001 8178edd0 nt!PipEnumerateDevice+0x20
f5fa4d18 8055af62 8178edd0 00000001 00000000 nt!PipProcessDevNodeTree+0x1b1
f5fa4d4c 804d7125 00000003 80549fc0 8054eddc nt!PiProcessReenumeration+0x5e
f5fa4d74 804ed629 00000000 00000000 813ea020 nt!PipDeviceActionWorker+0x133
f5fa4dac 8057c73a 00000000 00000000 00000000 nt!ExpWorkerThread+0xfe
f5fa4ddc 805124c1 804ed556 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
atapi!IdePortDispatchPnp+0
f99a2bb4 0000 add [eax],al

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: atapi!IdePortDispatchPnp+0

MODULE_NAME: atapi

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6ddb04

STACK_COMMAND: kb

BUCKET_ID: 0x7a_c000000e_atapi!IdePortDispatchPnp+0

Followup: MachineOwner

Ampsi

You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

thanks, Tony.

unfortunately i did not save the dump.

btw, how did you know that the memory is valid but not present?

Ampsi

----- Original Message -----
From: “Tony Mason”
To: “File Systems Developers”
Sent: Monday, May 26, 2003 19:41
Subject: [ntfsd] RE: KERNEL_DATA_INPAGE_ERROR

This doesn’t look like a typical disk read error; instead it looks more like
a device removal error (did you remove the driver from which you had
booted?)

The IDE drive attempts to access memory - the memory is VALID, but not
present, so the memory manager issues a paging I/O to fetch it (you don’t
show us the PTE here, try doing “!pte c03e6688” to see information about the
page for the faulting operation.) But the paging I/O fails to complete
because the device is gone. This could happen if someone disconnected a
physical disk on which a paging file was stored (for example).

That seems more likely given the earlier steps in that stack - PnP is
re-enumerating the device relations (looking for new or missing devices)
because of some change in configuration.

Another possibility is that your filter driver made it appear as if the
system had reconfigured in some way.

But neither of these sound like a typical hardware failure.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Ampsi [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Sunday, May 25, 2003 11:42 PM
To: File Systems Developers
Subject: [ntfsd] KERNEL_DATA_INPAGE_ERROR

hi, i have encountered a KERNEL_DATA_INPAGE_ERROR while testing my filter
driver. the status is STATUS_NO_SUCH_DEVICE. can i conclude that this is a
purely hardware problem?

this is the bugcheck analysis:

*******************************************************************


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.
Arguments:
Arg1: c03e6688, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: f99a2bb4, current process (virtual address for lock type 3, or PTE)
Arg4: 0c26e860, virtual address that could not be in-paged

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

BUGCHECK_STR: 0x7a_c000000e

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

DISK_HARDWARE_ERROR: There was error with disk hardware

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f5fa4494 805258ca 00000003 f5fa47c4 c03e6688
nt!RtlpBreakWithStatusInstruction
f5fa44e0 80526160 00000003 f99a2bb4 c03e6688 nt!KiBugCheckDebugBreak+0x19
f5fa48ac 805266db 0000007a c03e6688 c000000e nt!KeBugCheck2+0x46d
f5fa48cc 8051abc0 0000007a c03e6688 c000000e nt!KeBugCheckEx+0x19
f5fa48f4 804f0da4 80d6da50 c03e6688 f99a2bb4
nt!MiWaitForInPageComplete+0x1c3
f5fa4968 804f530c 81543290 f99a2bb4 c03e6688 nt!MiDispatchFault+0x29e
f5fa49b8 804dcc5e 00000000 f99a2bb4 00000000 nt!MmAccessFault+0x5bb
f5fa49b8 f99a2bb4 00000000 f99a2bb4 00000000 nt!KiTrap0E+0xb8
f5fa4a40 804eca36 81782030 81639420 f5fa4abc atapi!IdePortDispatchPnp
f5fa4a50 8056b1ed 00000000 8178edd0 8178edd0 nt!IopfCallDriver+0x31
f5fa4a7c 804d7745 81782030 f5fa4a98 8178eeb0 nt!IopSynchronousCall+0xb8
f5fa4abc 805542be 00000000 8178f630 00000001 nt!IopQueryDeviceRelations+0x39
f5fa4ad0 8055abfe 8178edd0 00000001 8178edd0 nt!PipEnumerateDevice+0x20
f5fa4d18 8055af62 8178edd0 00000001 00000000 nt!PipProcessDevNodeTree+0x1b1
f5fa4d4c 804d7125 00000003 80549fc0 8054eddc nt!PiProcessReenumeration+0x5e
f5fa4d74 804ed629 00000000 00000000 813ea020 nt!PipDeviceActionWorker+0x133
f5fa4dac 8057c73a 00000000 00000000 00000000 nt!ExpWorkerThread+0xfe
f5fa4ddc 805124c1 804ed556 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
atapi!IdePortDispatchPnp+0
f99a2bb4 0000 add [eax],al

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: atapi!IdePortDispatchPnp+0

MODULE_NAME: atapi

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6ddb04

STACK_COMMAND: kb

BUCKET_ID: 0x7a_c000000e_atapi!IdePortDispatchPnp+0

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

Ampsi

—
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

Ampsi,

I assume if it is a software problem, you will see it again.

The trace shows you are in MiWaitForInpageComplete. Thus, the Memory
Manager is attempting to retrieve the contents of the page (that is the
“inpage” operation). It would not do this if the virtual address were
invalid, only if it were valid. If the page were present in memory, it would
not need to fetch the data contents from the disk. Hence, the address is
valid, but the data is not currently in memory.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Ampsi [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Monday, May 26, 2003 11:29 PM
To: File Systems Developers
Subject: [ntfsd] RE: KERNEL_DATA_INPAGE_ERROR

thanks, Tony.

unfortunately i did not save the dump.

btw, how did you know that the memory is valid but not present?

Ampsi

----- Original Message -----
From: “Tony Mason”
To: “File Systems Developers”
Sent: Monday, May 26, 2003 19:41
Subject: [ntfsd] RE: KERNEL_DATA_INPAGE_ERROR

This doesn’t look like a typical disk read error; instead it looks more like
a device removal error (did you remove the driver from which you had
booted?)

The IDE drive attempts to access memory - the memory is VALID, but not
present, so the memory manager issues a paging I/O to fetch it (you don’t
show us the PTE here, try doing “!pte c03e6688” to see information about the
page for the faulting operation.) But the paging I/O fails to complete
because the device is gone. This could happen if someone disconnected a
physical disk on which a paging file was stored (for example).

That seems more likely given the earlier steps in that stack - PnP is
re-enumerating the device relations (looking for new or missing devices)
because of some change in configuration.

Another possibility is that your filter driver made it appear as if the
system had reconfigured in some way.

But neither of these sound like a typical hardware failure.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Ampsi [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Sunday, May 25, 2003 11:42 PM
To: File Systems Developers
Subject: [ntfsd] KERNEL_DATA_INPAGE_ERROR

hi, i have encountered a KERNEL_DATA_INPAGE_ERROR while testing my filter
driver. the status is STATUS_NO_SUCH_DEVICE. can i conclude that this is a
purely hardware problem?

this is the bugcheck analysis:

*******************************************************************


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.
Arguments:
Arg1: c03e6688, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: f99a2bb4, current process (virtual address for lock type 3, or PTE)
Arg4: 0c26e860, virtual address that could not be in-paged

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

BUGCHECK_STR: 0x7a_c000000e

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

DISK_HARDWARE_ERROR: There was error with disk hardware

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f5fa4494 805258ca 00000003 f5fa47c4 c03e6688
nt!RtlpBreakWithStatusInstruction
f5fa44e0 80526160 00000003 f99a2bb4 c03e6688 nt!KiBugCheckDebugBreak+0x19
f5fa48ac 805266db 0000007a c03e6688 c000000e nt!KeBugCheck2+0x46d
f5fa48cc 8051abc0 0000007a c03e6688 c000000e nt!KeBugCheckEx+0x19
f5fa48f4 804f0da4 80d6da50 c03e6688 f99a2bb4
nt!MiWaitForInPageComplete+0x1c3
f5fa4968 804f530c 81543290 f99a2bb4 c03e6688 nt!MiDispatchFault+0x29e
f5fa49b8 804dcc5e 00000000 f99a2bb4 00000000 nt!MmAccessFault+0x5bb
f5fa49b8 f99a2bb4 00000000 f99a2bb4 00000000 nt!KiTrap0E+0xb8
f5fa4a40 804eca36 81782030 81639420 f5fa4abc atapi!IdePortDispatchPnp
f5fa4a50 8056b1ed 00000000 8178edd0 8178edd0 nt!IopfCallDriver+0x31
f5fa4a7c 804d7745 81782030 f5fa4a98 8178eeb0 nt!IopSynchronousCall+0xb8
f5fa4abc 805542be 00000000 8178f630 00000001 nt!IopQueryDeviceRelations+0x39
f5fa4ad0 8055abfe 8178edd0 00000001 8178edd0 nt!PipEnumerateDevice+0x20
f5fa4d18 8055af62 8178edd0 00000001 00000000 nt!PipProcessDevNodeTree+0x1b1
f5fa4d4c 804d7125 00000003 80549fc0 8054eddc nt!PiProcessReenumeration+0x5e
f5fa4d74 804ed629 00000000 00000000 813ea020 nt!PipDeviceActionWorker+0x133
f5fa4dac 8057c73a 00000000 00000000 00000000 nt!ExpWorkerThread+0xfe
f5fa4ddc 805124c1 804ed556 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
atapi!IdePortDispatchPnp+0
f99a2bb4 0000 add [eax],al

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: atapi!IdePortDispatchPnp+0

MODULE_NAME: atapi

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6ddb04

STACK_COMMAND: kb

BUCKET_ID: 0x7a_c000000e_atapi!IdePortDispatchPnp+0

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

Ampsi

—
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

thanks, Tony.

Ampsi

----- Original Message -----
From: “Tony Mason”
To: “File Systems Developers”
Sent: Tuesday, May 27, 2003 17:31
Subject: [ntfsd] RE: KERNEL_DATA_INPAGE_ERROR

Ampsi,

I assume if it is a software problem, you will see it again.

The trace shows you are in MiWaitForInpageComplete. Thus, the Memory
Manager is attempting to retrieve the contents of the page (that is the
“inpage” operation). It would not do this if the virtual address were
invalid, only if it were valid. If the page were present in memory, it would
not need to fetch the data contents from the disk. Hence, the address is
valid, but the data is not currently in memory.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Ampsi [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Monday, May 26, 2003 11:29 PM
To: File Systems Developers
Subject: [ntfsd] RE: KERNEL_DATA_INPAGE_ERROR

thanks, Tony.

unfortunately i did not save the dump.

btw, how did you know that the memory is valid but not present?

Ampsi

----- Original Message -----
From: “Tony Mason”
To: “File Systems Developers”
Sent: Monday, May 26, 2003 19:41
Subject: [ntfsd] RE: KERNEL_DATA_INPAGE_ERROR

This doesn’t look like a typical disk read error; instead it looks more like
a device removal error (did you remove the driver from which you had
booted?)

The IDE drive attempts to access memory - the memory is VALID, but not
present, so the memory manager issues a paging I/O to fetch it (you don’t
show us the PTE here, try doing “!pte c03e6688” to see information about the
page for the faulting operation.) But the paging I/O fails to complete
because the device is gone. This could happen if someone disconnected a
physical disk on which a paging file was stored (for example).

That seems more likely given the earlier steps in that stack - PnP is
re-enumerating the device relations (looking for new or missing devices)
because of some change in configuration.

Another possibility is that your filter driver made it appear as if the
system had reconfigured in some way.

But neither of these sound like a typical hardware failure.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Ampsi [mailto:xxxxx@pmail.ntu.edu.sg]
Sent: Sunday, May 25, 2003 11:42 PM
To: File Systems Developers
Subject: [ntfsd] KERNEL_DATA_INPAGE_ERROR

hi, i have encountered a KERNEL_DATA_INPAGE_ERROR while testing my filter
driver. the status is STATUS_NO_SUCH_DEVICE. can i conclude that this is a
purely hardware problem?

this is the bugcheck analysis:

*******************************************************************


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.
Arguments:
Arg1: c03e6688, lock type that was held (value 1,2,3, or PTE address)
Arg2: c000000e, error status (normally i/o status code)
Arg3: f99a2bb4, current process (virtual address for lock type 3, or PTE)
Arg4: 0c26e860, virtual address that could not be in-paged

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

BUGCHECK_STR: 0x7a_c000000e

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

DISK_HARDWARE_ERROR: There was error with disk hardware

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f5fa4494 805258ca 00000003 f5fa47c4 c03e6688
nt!RtlpBreakWithStatusInstruction
f5fa44e0 80526160 00000003 f99a2bb4 c03e6688 nt!KiBugCheckDebugBreak+0x19
f5fa48ac 805266db 0000007a c03e6688 c000000e nt!KeBugCheck2+0x46d
f5fa48cc 8051abc0 0000007a c03e6688 c000000e nt!KeBugCheckEx+0x19
f5fa48f4 804f0da4 80d6da50 c03e6688 f99a2bb4
nt!MiWaitForInPageComplete+0x1c3
f5fa4968 804f530c 81543290 f99a2bb4 c03e6688 nt!MiDispatchFault+0x29e
f5fa49b8 804dcc5e 00000000 f99a2bb4 00000000 nt!MmAccessFault+0x5bb
f5fa49b8 f99a2bb4 00000000 f99a2bb4 00000000 nt!KiTrap0E+0xb8
f5fa4a40 804eca36 81782030 81639420 f5fa4abc atapi!IdePortDispatchPnp
f5fa4a50 8056b1ed 00000000 8178edd0 8178edd0 nt!IopfCallDriver+0x31
f5fa4a7c 804d7745 81782030 f5fa4a98 8178eeb0 nt!IopSynchronousCall+0xb8
f5fa4abc 805542be 00000000 8178f630 00000001 nt!IopQueryDeviceRelations+0x39
f5fa4ad0 8055abfe 8178edd0 00000001 8178edd0 nt!PipEnumerateDevice+0x20
f5fa4d18 8055af62 8178edd0 00000001 00000000 nt!PipProcessDevNodeTree+0x1b1
f5fa4d4c 804d7125 00000003 80549fc0 8054eddc nt!PiProcessReenumeration+0x5e
f5fa4d74 804ed629 00000000 00000000 813ea020 nt!PipDeviceActionWorker+0x133
f5fa4dac 8057c73a 00000000 00000000 00000000 nt!ExpWorkerThread+0xfe
f5fa4ddc 805124c1 804ed556 80000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
atapi!IdePortDispatchPnp+0
f99a2bb4 0000 add [eax],al

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: atapi!IdePortDispatchPnp+0

MODULE_NAME: atapi

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6ddb04

STACK_COMMAND: kb

BUCKET_ID: 0x7a_c000000e_atapi!IdePortDispatchPnp+0

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

Ampsi

—
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to ntfsd as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

—
You are currently subscribed to ntfsd as: xxxxx@pmail.ntu.edu.sg
To unsubscribe send a blank email to xxxxx@lists.osr.com