BleepingComputer.com: Blue screen :kernel_stack_inpage error

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\<removed>\Mini081411-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Aug 15 03:53:47.718 2011 (GMT+10)
System Uptime: 0 days 3:30:18.430
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {c0000056, c0000056, 0, 41f000}

Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+4f5 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* 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 arguments is 0 or 1, 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 will 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: c0000056, status code
Arg2: c0000056, i/o status code
Arg3: 00000000, page file number
Arg4: 0041f000, offset into page file

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


ERROR_CODE: (NTSTATUS) 0xc0000056 - A non close operation has been requested of a file object with a delete pending.

BUGCHECK_STR: 0x77_c0000056

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: SYSTEM

LAST_CONTROL_TRANSFER: from 80511fa9 to 804f9f43

STACK_TEXT:
b8523cdc 80511fa9 00000077 c0000056 c0000056 nt!KeBugCheckEx+0x1b
b8523d50 80512e1b c05973d8 00038bd0 00000001 nt!MiMakeOutswappedPageResident+0x4f5
b8523d8c 8053fdd6 00a45658 00000000 8a6f56d8 nt!MmInPageKernelStack+0x149
b8523da4 805402a6 897c3130 805cffa8 00000000 nt!KiInSwapKernelStacks+0x16
b8523dac 805cffa8 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
b8523ddc 8054615e 8054022a 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+4f5
80511fa9 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiMakeOutswappedPageResident+4f5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4d00d46f

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_c0000056_nt!MiMakeOutswappedPageResident+4f5

BUCKET_ID: 0x77_c0000056_nt!MiMakeOutswappedPageResident+4f5

Followup: MachineOwner

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\<removed>\Mini081311-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Aug 13 19:00:51.578 2011 (GMT+10)
System Uptime: 0 days 0:42:54.288
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {c000000e, c000000e, 0, b5f000}

Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+4f5 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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 arguments is 0 or 1, 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 will 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: c000000e, status code
Arg2: c000000e, i/o status code
Arg3: 00000000, page file number
Arg4: 00b5f000, offset into page file

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: 0x77_c000000e

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: SYSTEM

LAST_CONTROL_TRANSFER: from 80511fa9 to 804f9f43

STACK_TEXT:
b8523cdc 80511fa9 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
b8523d50 80512e1b c05c27d8 00078cfb 00000001 nt!MiMakeOutswappedPageResident+0x4f5
b8523d8c 8053fdd6 006fd640 00000000 8a6f56d8 nt!MmInPageKernelStack+0x149
b8523da4 805402a6 8a6fd6a0 805cffa8 00000000 nt!KiInSwapKernelStacks+0x16
b8523dac 805cffa8 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
b8523ddc 8054615e 8054022a 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+4f5
80511fa9 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiMakeOutswappedPageResident+4f5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4d00d46f

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+4f5

BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+4f5

Followup: MachineOwner

This post has been edited by AustrAlien: 19 August 2011 - 06:26 AM

im abcd, on 18 August 2011 - 12:48 PM, said:

I would suggest that you start a new topic to deal with the above mentioned error messages in Event Viewer, particularly since you seem to think they are all related to a game that you use. (I don't do games.)

I posted the full minidump debugging reports for your interest. It would appear that the BSODs involved some sort of memory corruption, most likely in the paging file. Since the problem seems to have resolved itself, I am not sure whether you wish to pursue the matter any further or are content to leave sleeping dogs lie. Let me know if you wish to continue with the investigation: We could check out your paging file setup .... etc.

I think i found the key to this problem of "atapi" and "disk" errors .
I had a .txt file on my pc with a tutorial which told to change the Mode from "pio" to "dma" transfer mode in device manager .So i am now changing the dma mode to pio mode in ide/ata/atapi controllers by going to advanced settings and making the mode device 0 mode to "pio"

Will tell you the results .

<<So i am now changing the dma mode to pio mode in ide/ata/atapi controllers by going to advanced settings and making the mode device 0 mode to "pio">>

Doing so...will probably only create problems for the system. PIO is an outdated election, while DMA has been the standard for years now. Unless you have very old hardware, the DMA settings should be employed.

DMA Mode for ATA-ATAPI Devices in Windows XP - http://www.microsoft.com/whdc/device/storage/IDE-DMA.mspx

DMA reverts to PIO Windows Problem Solver - http://winhlp.com/node/10

DMA Settings In XP - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q310751

Louis

Ok i changed to pio mode and the "disk" errors stopped coming .But the game still lags ?

But i haven't made "pio" mode for all of them .


These are my controllers .

primary ide channel ( Device 0 =dma if available ,device 1 =dma if available )
primary ide channel ( Device 0 =pio mode ,device 1 =dma if available )
secondary ide channel ( Device 0 =dma if available ,device 1 =dma if available )
secondary ide channel ( Device 0 =pio mode ,device 1 =dma if available )