help reading mini dump

[redjordi]

Hi,

I have gotten 4 times the BSOD in the last couple of days. It did not happen after any software nor hardware install or change. The hard disk also makes a lot of noise. This is what the WindDbg is reading on one of the minidumps (the others are basically the same):

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini041106-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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 2600.xpsp_sp2_gdr.050301-1519

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420

Debug session time: Tue Apr 11 07:23:46.760 2006 (GMT+1)

System Uptime: 0 days 6:16:42.320

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, 52d000}

Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+362 )

Followup: MachineOwner

---------

kd>

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: 0052d000, offset into page file

Debugging Details:

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

ERROR_CODE: (NTSTATUS) 0xc000000e - Se ha especificado un dispositivo inexistente.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x77_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80520b96 to 8053331e

STACK_TEXT:

f9ccbcf0 80520b96 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b

f9ccbd60 804e80c6 c02c8f88 c02c8f88 00000001 nt!MiMakeOutswappedPageResident+0x362

f9ccbd8c 804e6b39 00220298 00000000 8132f2a0 nt!MmInPageKernelStack+0xf0

f9ccbda4 804e6b1c 812202f8 8057be15 00000000 nt!KiInSwapKernelStacks+0x16

f9ccbdac 8057be15 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x89

f9ccbddc 804fa4da 804e6a98 00000000 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

nt!MiMakeOutswappedPageResident+362

80520b96 cc int 3

FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiMakeOutswappedPageResident+362

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+362

BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+362

Followup: MachineOwner

---------

any help in telling me what this means?

thanks in advance

[Mordac85]

Read and all will be revealed!

BugCheck 77, {c000000e, c000000e, 0, 52d000}

Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+362 )

And also more detail:

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: 0052d000, offset into page file

And the pièces de résistance:

ERROR_CODE: (NTSTATUS) 0xc000000e - Se ha especificado un dispositivo inexistente.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x77_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80520b96 to 8053331e

Looks like a disk error. Considering the strange noises, your drive is most likely on it's death bed. If it sounds like clicking noises or scratches, grab your data while you still can and order a replacement.

[cluberti]

This is a pretty obvious bugcheck, and Mordac hit the nail on the head - it's spelled out for you in the bugcheck's analyze -v statement. Get yourself a new hard disk while you still can get your data off of it!

[redjordi]

thanks a lot, this is what I already feared, but I was abit confussed by the reference to memory corruption and I thought (had the hope) it could be a problem with the RAM memory, rather than the HD. In the meantime I memtested the computer and it found no errors.

will get a new HD

funny thing is currently I am working on my computer, but I guess it won't last for very long.

[Mordac85]

It will probably die just when you start copying your data out. Drives seem to be uncanny at picking the absolute worst time to give up the ghost.