I came here while searching on the blue dump problem I am facing with my laptop. Could you help me CPC or anyone else who knows it.
I am seeing this problem since last couple of months, and I observed that it never happens while I work on the laptop, but occurs when the laptop is idle. I guess the problem could be when laptop tries to shut off the harddisk as per the power saver options, so right now I am giving it a try by keeping "Always On" option selected. Meanwhile, I have this log pulled out from WinDbg debugger. Please reply with your comments.
Here is the WinDbg log to look at:
I am seeing this problem since last couple of months, and I observed that it never happens while I work on the laptop, but occurs when the laptop is idle. I guess the problem could be when laptop tries to shut off the harddisk as per the power saver options, so right now I am giving it a try by keeping "Always On" option selected. Meanwhile, I have this log pulled out from WinDbg debugger. Please reply with your comments.
Here is the WinDbg log to look at:
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\WINDOWS\Minidump\Mini010407-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: c:\windows\i386
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp.050928-1517
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a5a0
Debug session time: Thu Jan 4 09:31:55.562 2007 (GMT+5)
System Uptime: 2 days 8:43:06.130
Loading Kernel Symbols
......................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 77, {1, d0d0d0d, 0, aa48395c}
Probably caused by : memory_corruption ( nt!MmInPageKernelStack+119 )
Followup: MachineOwner
---------
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: 00000001, (page was retrieved from disk)
Arg2: 0d0d0d0d, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: aa48395c, address of signature on kernel stack
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
BUGCHECK_STR: 0x77_1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 80520f51 to 805334b6
STACK_TEXT:
f89bbd68 80520f51 00000077 00000001 0d0d0d0d nt!KeBugCheckEx+0x1b
f89bbd8c 804e6b39 009d7020 00000000 823c38b8 nt!MmInPageKernelStack+0x119
f89bbda4 804e6b1c f9220e08 8057bf95 00000000 nt!KiInSwapKernelStacks+0x16
f89bbdac 8057bf95 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89
f89bbddc 804f94b2 804e6a98 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmInPageKernelStack+119
80520f51 6a00 push 0
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 433b2f93
SYMBOL_NAME: nt!MmInPageKernelStack+119
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+119
BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+119
Followup: MachineOwner
---------
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: 00000001, (page was retrieved from disk)
Arg2: 0d0d0d0d, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: aa48395c, address of signature on kernel stack
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
BUGCHECK_STR: 0x77_1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 80520f51 to 805334b6
STACK_TEXT:
f89bbd68 80520f51 00000077 00000001 0d0d0d0d nt!KeBugCheckEx+0x1b
f89bbd8c 804e6b39 009d7020 00000000 823c38b8 nt!MmInPageKernelStack+0x119
f89bbda4 804e6b1c f9220e08 8057bf95 00000000 nt!KiInSwapKernelStacks+0x16
f89bbdac 8057bf95 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89
f89bbddc 804f94b2 804e6a98 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmInPageKernelStack+119
80520f51 6a00 push 0
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 433b2f93
SYMBOL_NAME: nt!MmInPageKernelStack+119
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+119
BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+119
Followup: MachineOwner
---------
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: 00000001, (page was retrieved from disk)
Arg2: 0d0d0d0d, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: aa48395c, address of signature on kernel stack
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
BUGCHECK_STR: 0x77_1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 80520f51 to 805334b6
STACK_TEXT:
f89bbd68 80520f51 00000077 00000001 0d0d0d0d nt!KeBugCheckEx+0x1b
f89bbd8c 804e6b39 009d7020 00000000 823c38b8 nt!MmInPageKernelStack+0x119
f89bbda4 804e6b1c f9220e08 8057bf95 00000000 nt!KiInSwapKernelStacks+0x16
f89bbdac 8057bf95 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89
f89bbddc 804f94b2 804e6a98 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmInPageKernelStack+119
80520f51 6a00 push 0
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 433b2f93
SYMBOL_NAME: nt!MmInPageKernelStack+119
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+119
BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+119
Followup: MachineOwner
---------
