On Thu, Feb 3, 2011 at 11:12 AM, Kelli Sterley
<[email protected]> wrote:
> I am trying to decipher a memory dump on a Win2003 server.
> From everything I can read within, it looks like bad memory.
Bad memory can cause just about any error, but that would not be my
first guess. Here are the relevant parts:
> BugCheck 77, {c000009d, c000009d, 0, 1277000}
The STOP/BugCheck code, and it's four parameters.
> KERNEL_STACK_INPAGE_ERROR (77)
The kernel encountered an error trying to read a page in from a page
file on disk.
> Arg1: c000009d, status code
> Arg2: c000009d, i/o status code
> Arg3: 00000000, page file number
> Arg4: 01277000, offset into page file
What the four parameters mean. Normally, one has to look up the
status codes using a tool like ERR.EXE or Google, but in this case,
the debugger provides the needed clue:
> An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR)
The disk subsystem reported a device data error (this is what the
kernel saw to cause the STOP 0x77). This code usually means a bad
block on disk, but can also mean a faulty cable or controller. Start
looking there.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin
