DUMP DATA - Kernel_stack_inpage_error

Hi,

I also have the random reboot and blue screen problem in few months. Could anyone help me?

The OS is Windows XP SP1. Followings are the mini-dump information from WinDbg.

------------------
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Thu Sep 09 08:08:32 2004
System Uptime: 0 days 2:01:02.686
Loading Kernel Symbols
................................................................................................


kd> !analyze -v;r;kv;lmtn;.logclose
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first and second arguments are 0, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck willl run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: c00000a3, status code
Arg2: c00000a3, i/o status code
Arg3: 00000000, page file number
Arg4: 006fd000, offset into page file

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


ERROR_CODE: (NTSTATUS) 0xc00000a3 - {Drive Not Ready} The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed.

BUGCHECK_STR: 0x77_c00000a3

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80519ecb to 805266db

STACK_TEXT:
f89bccf8 80519ecb 00000077 c00000a3 c00000a3 nt!KeBugCheckEx+0x19
f89bcd68 804eb206 c03d7aa0 c03d7aa0 00000001 nt!MiMakeOutswappedPageResident+0x363
f89bcd90 804eb223 819a2500 00000000 81fc5b30 nt!MmInPageKernelStack+0xe9
f89bcda4 804eb0b9 81e585b8 8057c73a 00000000 nt!KiInSwapKernelStacks+0x12
f89bcdac 8057c73a 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89
f89bcddc 805124c1 804eb035 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+363
80519ecb cc int 3

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiMakeOutswappedPageResident+363

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

BUCKET_ID: 0x77_c00000a3_nt!MiMakeOutswappedPageResident+363

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

eax=ffdff13c ebx=00000077 ecx=00000000 edx=c00000a3 esi=00004a68 edi=006fd080
eip=805266db esp=f89bcce0 ebp=f89bccf8 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x19:
805266db 5d pop ebp
ChildEBP RetAddr Args to Child
f89bccf8 80519ecb 00000077 c00000a3 c00000a3 nt!KeBugCheckEx+0x19 (FPO: [Non-Fpo])
f89bcd68 804eb206 c03d7aa0 c03d7aa0 00000001 nt!MiMakeOutswappedPageResident+0x363 (FPO: [Non-Fpo])
f89bcd90 804eb223 819a2500 00000000 81fc5b30 nt!MmInPageKernelStack+0xe9 (FPO: [EBP 0x819a2520] [1,1,4])
f89bcda4 804eb0b9 81e585b8 8057c73a 00000000 nt!KiInSwapKernelStacks+0x12 (FPO: [1,0,3])
f89bcdac 8057c73a 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89 (FPO: [1,0,0])
f89bcddc 805124c1 804eb035 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start end module name
804d4000 806c6980 nt ntoskrnl.exe Thu Aug 29 10:03:24 2002 (3D6DE35C)
806c7000 806e6380 hal halaacpi.dll Thu Aug 29 09:05:02 2002 (3D6DD5AE)
bf800000 bf9bac80 win32k win32k.sys Thu Aug 29 10:14:13 2002 (3D6DE5E5)
bff30000 bff51800 atidrae atidrae.dll Fri Aug 17 22:55:59 2001 (3B7D92EF)
bff80000 bff90d80 dxg dxg.sys Thu Aug 29 11:40:42 2002 (3D6DFA2A)
f5c85000 f5c87f80 mouhid mouhid.sys Fri Aug 17 21:47:57 2001 (3B7D82FD)
f5e89000 f5e8b580 hidusb hidusb.sys Fri Aug 17 22:02:16 2001 (3B7D8658)
f5ead000 f5efda80 srv srv.sys Sat Aug 18 02:32:06 2001 (3B7DC596)
f5f4e000 f5f78280 mrxdav mrxdav.sys Fri Aug 17 21:50:20 2001 (3B7D838C)
f5f95000 f5f98760 imbdrv imbdrv.sys Tue Sep 25 03:49:01 2001 (3BAFF09D)
f6069000 f6089380 afd afd.sys Thu Aug 29 10:01:13 2002 (3D6DE2D9)
f68b2000 f68c4700 dump_Fasttrak dump_Fasttrak.sys Fri Apr 25 09:20:35 2003 (3EA8EFD3)
f68c5000 f6928800 mrxsmb mrxsmb.sys Thu Aug 29 09:59:51 2002 (3D6DE287)
f6929000 f6950e00 rdbss rdbss.sys Thu Aug 29 09:58:48 2002 (3D6DE248)
f6951000 f6977580 netbt netbt.sys Thu Aug 29 10:01:56 2002 (3D6DE304)
f6978000 f69c9480 tcpip tcpip.sys Thu Aug 29 09:58:10 2002 (3D6DE222)
f6a4a000 f6a58900 Cdfs Cdfs.SYS Thu Aug 29 09:58:50 2002 (3D6DE24A)
f6cb0000 f6cb8700 HIDCLASS HIDCLASS.SYS Thu Aug 29 09:32:40 2002 (3D6DDC28)
f6d4b000 f6d4d900 Dxapi Dxapi.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
f6d4f000 f6d53000 watchdog watchdog.sys Thu Aug 29 09:32:20 2002 (3D6DDC14)
f6dcc000 f6dd4200 wanarp wanarp.sys Fri Aug 17 21:55:23 2001 (3B7D84BB)
f6ddc000 f6de4880 Fips Fips.SYS Sat Aug 18 02:31:49 2001 (3B7DC585)
f6dec000 f6df4180 netbios netbios.sys Thu Aug 29 09:35:45 2002 (3D6DDCE1)
f6e0c000 f6e1a280 ipsec ipsec.sys Thu Aug 29 10:07:19 2002 (3D6DE447)
f7e5a000 f7e5c280 rasacd rasacd.sys Fri Aug 17 21:55:39 2001 (3B7D84CB)
f7eb3000 f7ed4780 update update.sys Sat Aug 18 04:53:56 2001 (3B7DE6D4)
f7ed5000 f7f01880 rdpdr rdpdr.sys Thu Aug 29 09:06:34 2002 (3D6DD60A)
f80f2000 f80f5380 dump_scsiport dump_scsiport.sys Thu Aug 29 09:27:54 2002 (3D6DDB0A)
f810a000 f810d000 ndisuio ndisuio.sys Thu Aug 29 09:35:40 2002 (3D6DDCDC)
f81f4000 f8204200 psched psched.sys Thu Aug 29 09:35:54 2002 (3D6DDCEA)
f8205000 f821a600 ndiswan ndiswan.sys Thu Aug 29 09:58:38 2002 (3D6DE23E)
f821b000 f823c180 USBPORT USBPORT.SYS Thu Aug 29 09:32:49 2002 (3D6DDC31)
f8277000 f8297280 ks ks.sys Thu Aug 29 10:13:40 2002 (3D6DE5C4)
f8298000 f82bd600 e100b325 e100b325.sys Tue Oct 28 20:09:53 2003 (3F9ECD11)
f82be000 f82ddc00 e1000325 e1000325.sys Tue Oct 28 22:51:03 2003 (3F9EF2D7)
f82de000 f82ef500 VIDEOPRT VIDEOPRT.SYS Thu Aug 29 09:32:03 2002 (3D6DDC03)
f82f0000 f8302580 atimpae atimpae.sys Thu Jun 14 00:41:46 2001 (3B27FA3A)
f838f000 f83a8680 Mup Mup.sys Thu Aug 29 10:12:53 2002 (3D6DE595)
f83a9000 f83d1e80 NDIS NDIS.sys Thu Aug 29 10:09:23 2002 (3D6DE4C3)
f83d2000 f845b300 Ntfs Ntfs.sys Thu Aug 29 10:13:37 2002 (3D6DE5C1)
f845c000 f846f780 KSecDD KSecDD.sys Fri Aug 17 21:50:01 2001 (3B7D8379)
f8470000 f8480e80 sr sr.sys Thu Aug 29 09:17:56 2002 (3D6DD8B4)
f8481000 f8497080 SCSIPORT SCSIPORT.SYS Thu Aug 29 09:27:47 2002 (3D6DDB03)
f8498000 f84aa700 Fasttrak Fasttrak.sys Fri Apr 25 09:20:35 2003 (3EA8EFD3)
f84ab000 f84c0380 atapi atapi.sys Thu Aug 29 09:27:48 2002 (3D6DDB04)
f84c1000 f84e4b80 dmio dmio.sys Fri Aug 17 21:58:27 2001 (3B7D8573)
f84e5000 f8503880 ftdisk ftdisk.sys Fri Aug 17 21:52:41 2001 (3B7D8419)
f8504000 f852fc80 ACPI ACPI.sys Thu Aug 29 09:09:03 2002 (3D6DD69F)
f8551000 f8560600 pci pci.sys Thu Aug 29 09:09:10 2002 (3D6DD6A6)
f8561000 f8569c00 isapnp isapnp.sys Fri Aug 17 21:58:01 2001 (3B7D8559)
f8571000 f857a280 MountMgr MountMgr.sys Fri Aug 17 21:47:36 2001 (3B7D82E8)
f8581000 f858d000 VolSnap VolSnap.sys Fri Aug 17 21:53:19 2001 (3B7D843F)
f8591000 f8599400 disk disk.sys Thu Aug 29 09:27:56 2002 (3D6DDB0C)
f85a1000 f85ac500 CLASSPNP CLASSPNP.SYS Thu Aug 29 10:08:42 2002 (3D6DE49A)
f8641000 f864a400 termdd termdd.sys Thu Aug 29 09:40:32 2002 (3D6DDE00)
f8661000 f866db00 usbhub usbhub.sys Thu Aug 29 09:32:49 2002 (3D6DDC31)
f8671000 f867a480 NDProxy NDProxy.SYS Fri Aug 17 21:55:30 2001 (3B7D84C2)
f8731000 f873d780 i8042prt i8042prt.sys Thu Aug 29 10:06:37 2002 (3D6DE41D)
f8751000 f8760400 serial serial.sys Thu Aug 29 10:08:27 2002 (3D6DE48B)
f8761000 f876ab80 imapi imapi.sys Thu Aug 29 09:28:05 2002 (3D6DDB15)
f8771000 f877c980 cdrom cdrom.sys Thu Aug 29 09:27:55 2002 (3D6DDB0B)
f8781000 f878ed00 redbook redbook.sys Thu Aug 29 09:27:45 2002 (3D6DDB01)
f8791000 f879cd00 rasl2tp rasl2tp.sys Thu Aug 29 10:06:36 2002 (3D6DE41C)
f87a1000 f87aa800 raspppoe raspppoe.sys Fri Aug 17 21:55:33 2001 (3B7D84C5)
f87b1000 f87bc500 raspptp raspptp.sys Thu Aug 29 10:12:46 2002 (3D6DE58E)
f87c1000 f87c9400 msgpc msgpc.sys Fri Aug 17 21:54:19 2001 (3B7D847B)
f87d1000 f87d6c80 PCIIDEX PCIIDEX.SYS Thu Aug 29 09:27:47 2002 (3D6DDB03)
f87d9000 f87dd900 PartMgr PartMgr.sys Sat Aug 18 02:32:23 2001 (3B7DC5A7)
f87f9000 f87fd580 ptilink ptilink.sys Fri Aug 17 21:49:53 2001 (3B7D8371)
f8801000 f8805080 raspti raspti.sys Fri Aug 17 21:55:32 2001 (3B7D84C4)
f8829000 f882dd00 flpydisk flpydisk.sys Thu Aug 29 09:27:43 2002 (3D6DDAFF)
f88d1000 f88d6c80 HIDPARSE HIDPARSE.SYS Fri Aug 17 22:02:04 2001 (3B7D864C)
f8909000 f890dd00 vga vga.sys Thu Aug 29 09:32:03 2002 (3D6DDC03)
f8911000 f8918780 processr processr.sys Thu Aug 29 09:05:03 2002 (3D6DD5AF)
f8919000 f891d680 Msfs Msfs.SYS Fri Aug 17 21:50:02 2001 (3B7D837A)
f8921000 f8922000 fdc fdc.sys unavailable (00000000)
f8929000 f8930380 Npfs Npfs.SYS Fri Aug 17 21:50:03 2001 (3B7D837B)
f8931000 f8936600 mouclass mouclass.sys Thu Aug 29 09:27:00 2002 (3D6DDAD4)
f8939000 f893eb80 kbdclass kbdclass.sys Thu Aug 29 09:26:59 2002 (3D6DDAD3)
f8961000 f8964000 BOOTVID BOOTVID.dll Fri Aug 17 21:49:09 2001 (3B7D8345)
f8a15000 f8a18a80 serenum serenum.sys Fri Aug 17 21:50:13 2001 (3B7D8385)
f8a1d000 f8a20d80 usbohci usbohci.sys Thu Aug 29 09:32:48 2002 (3D6DDC30)
f8a21000 f8a23580 ndistapi ndistapi.sys Fri Aug 17 21:55:29 2001 (3B7D84C1)
f8a25000 f8a28f80 TDI TDI.SYS Fri Aug 17 21:57:25 2001 (3B7D8535)
f8a51000 f8a52b80 kdcom kdcom.dll Fri Aug 17 21:49:10 2001 (3B7D8346)
f8a53000 f8a54100 WMILIB WMILIB.SYS Fri Aug 17 22:07:23 2001 (3B7D878B)
f8a55000 f8a56700 dmload dmload.sys Fri Aug 17 21:58:15 2001 (3B7D8567)
f8a6d000 f8a6e280 USBD USBD.SYS Fri Aug 17 22:02:58 2001 (3B7D8682)
f8aa1000 f8aa2f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 21:49:37 2001 (3B7D8361)
f8aa3000 f8aa4080 Beep Beep.SYS Fri Aug 17 21:47:33 2001 (3B7D82E5)
f8aa5000 f8aa6080 mnmdd mnmdd.SYS Fri Aug 17 21:57:28 2001 (3B7D8538)
f8aa7000 f8aa8080 RDPCDD RDPCDD.sys Fri Aug 17 21:46:56 2001 (3B7D82C0)
f8b19000 f8b19d00 pciide pciide.sys Fri Aug 17 21:51:49 2001 (3B7D83E5)
f8b1d000 f8b1db80 Null Null.SYS Fri Aug 17 21:47:39 2001 (3B7D82EB)
f8b1f000 f8b1fd00 dxgthk dxgthk.sys Fri Aug 17 21:53:12 2001 (3B7D8438)
f8b8c000 f8b8cc00 audstub audstub.sys Fri Aug 17 21:59:40 2001 (3B7D85BC)
f8ba9000 f8ba9f00 swenum swenum.sys Fri Aug 17 21:48:47 2001 (3B7D832F)

Unloaded modules:
f6be8000 f6beb000 mouhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f5f3b000 f5f4e000 Parport.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7e5e000 f7e62000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f88c9000 f88ce000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000

--------------

Thanks,
Delphine

 

ERROR_CODE: (NTSTATUS) 0xc00000a3 - {Drive Not Ready} The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed.


Something is not well with your Hard drive subsystem that your pagefile resides on.

 

Hi Arie and Joe,

For post rule:
Sorry and now I already know that. Because I am new from here, and I saw other people also did that and My English is too poor to read lots of post rules . Actually I spent a lot of time to decide just post there yesterday.

For response content:
hmm...I already read those documents before and know what you mean. But what I confuse is the BSOD appear randomly and my system can work well after reboot. And those documents specifies that may relates with kinds of hardware, such as hard disk, failed memory hardware, memory modules, Level 2 (L2) SRAM cache, video adapter RAM, a crack, a scratched trace, or a defective component on the motherboard. So many possibilities...

I really don't know how to get the point to solve the problem.

I saw Joe's other posts, and I think Joe seems to can guess the most possible failure component.

And from the bugcheck "Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+363 ) ", does it mean I should guess Main Memory first?

Thank you.

Delphine

 

No, the problem is with your physical hard drive. Windows can take memory and store it on your hard drive to make room for other running programs. This operation failed to read the data from the hard drive and put it back into your RAM. The error code generated was 0xc00000a3 - {Drive Not Ready}. This means that windows asked the drive controller to read the data, and the controller returned 'the drive is not ready'.
I would do several things here. Back up your important data immediatly, in case the drive is about to fail. Remove and reinstall all the hard drive cabling, power and data. Check for updates to bios, and system drivers. Those are the painless things. Run chkdsk or another drive checker. If you have the resources, i would consider changing the hard drive, and or the controller.

It would be interesting to know if all the blue screens have this same message, or if your getting other crashes that could indicate something else.

What was the last change you made before this problem started happening.

 

Hi Joe,

"drive controller" means the disk controller, right? or Windows what controller?

Yeah. I got few times mini-dumps and always got the same messages. No any change before this problem started happening. But the system is running heavy loading testing.

hmm...That system was built on a span IDE raid. Maybe it's the raid controller bug or driver bug? But it crash on !nt not driver.....?

Another question, What does "the page file number = 00000000" mean?
Arg1: c00000a3, status code
Arg2: c00000a3, i/o status code
Arg3: 00000000, page file number
Arg4: 006fd000, offset into page file

 

Thats an important piece of information. My diagnosis was based on assumption that you had normal disks. I would certainly think that this IDE raid controller (or its software driver) could be the culprit.
Have you checked for an updated driver and firmware?

page file 0000000 is the first pagefile (zero based counting)

 

Yes. I already got the latest version driver and firmware on my machine. I think I should tell a truth and that explains I can't guess that was caused by cables or disks, but I am afraid that would make nobody to help me . Actually what I meet now is from our company mass production machines... many machines have the same conditions, and our HW Engineer has changed kinds of components but still can't solve. But the models do work for the previous production....


I am thinking about pagefile....
1. So... from the dump data, !nt want to access page file 0, but it can't get page file 0, am I right?

2. Is "page file number = 00000000" reasonable?

3. If my another mini-dump also has the same third argument( pagefile 0 ), is it possible? I just thought this, but I didn't have older mini-dump on hand, if it's a problem, I will pay attention on it.

 

1. So... from the dump data, !nt want to access page file 0, but it can't get page file 0, am I right?
This is correct, when it tried to read data out of the pagefile, disk subsystem (software driver or hardware, impossible to tell which one) sent back a 'disk is not ready'

2. Is "page file number = 00000000" reasonable?Yes, you can have more than one page file, but in this context, the first one is number 0, the second is number 1, etc etc.

3. If my another mini-dump also has the same third argument( pagefile 0 ), is it possible? I just thought this, but I didn't have older mini-dump on hand, if it's a problem, I will pay attention on it.
See above, the problem is not the pagefile itself, but the IO subsystem.

 

Thanks Joe.

For point 3.
Yeah, I understand actually it's a subsystem problem. But I think since a page file number maps to a address located actually in disk, is it has large possibility that failure always occurs while accessing page file 0? Or......maybe kernel data always swap to the disk address mapped by page file 0?