BSOD BugCheck, STOP: 0x000000C5 (0x00000004, 0xD0000002, 0x00000001, 0x8089BCE3))

[Jeff Graber]

I get the following error
BugCheck, STOP: 0x000000C5 (0x00000004, 0xD0000002, 0x00000001, 0x8089BCE3))

I have the 8.11 PSP

[karim h]

Jeff, have you run the minidump/kernel dump through Windbg? Can you post the output of the !analyze -v

[Jeff Graber]

Attached is the output of lananlze -v

[Jeff Graber]

Loading Dump File [C:\WINDOWS\Minidump\Mini120808-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:\i386
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.080813-1204
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af9c8
Debug session time: Mon Dec 8 08:49:46.654 2008 (GMT-5)
System Uptime: 3 days 17:58:24.500
Loading Kernel Symbols
...................................................................................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 0, 0, 0}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+173 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 00000000, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0

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


BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME: VVServer.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 80865ba5 to 8087c4a0

STACK_TEXT:
a866998c 80865ba5 0000004e 00000099 00000000 nt!KeBugCheckEx+0x1b
a86699b8 808885c1 0000001c ffffffff c03aed38 nt!MiRestoreTransitionPte+0x173
a86699d0 8086b6cd 00000000 80867fe4 00000000 nt!MiRemovePageFromList+0xd1
a86699d8 80867fe4 00000000 dc637000 00001000 nt!MiRemoveAnyPage+0x68
a8669a8c 8082b3a0 dc637000 0756db20 00000000 nt!MmCopyToCachedPage+0x437
a8669b1c 8082aba1 867eb008 0756db20 a8669b50 nt!CcMapAndCopy+0x1b2
a8669ba0 f7b8352f 86e3e260 029f2000 00010000 nt!CcFastCopyWrite+0x229
a8669c04 f70a0ca2 86e3e260 a8669c74 00010000 Ntfs!NtfsCopyWriteA+0x1fb
a8669c38 f70ada2f 00000004 00000000 a8669c6c fltMgr!FltpPerformFastIoCall+0x230
a8669c8c 8091dc7e 86e3e260 a8669cd0 00010000 fltMgr!FltpFastIoWrite+0xa9
a8669d38 80833bef 00001bdc 00000000 00000000 nt!NtWriteFile+0x317
a8669d38 7c8285ec 00001bdc 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
09d7f4ec 00000000 00000000 00000000 00000000 0x7c8285ec


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiRestoreTransitionPte+173
80865ba5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiRestoreTransitionPte+173

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a2bc85

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_99_nt!MiRestoreTransitionPte+173

BUCKET_ID: 0x4E_99_nt!MiRestoreTransitionPte+173

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

[karim h]

Have you installed any new hardware recently? RAM, CPU, Mezzanine cards?

1. Run Insight Diagnostics see if it picks up anything.

2. Run the blade in minimum hardware configuration (no mezz, min RAM, min CPU)


** MSDN Explanation
Error Message:

STOP: 0x0000004E (parameter, parameter, parameter, parameter) PFN_LIST_CORRUPT
Explanation:

This is a Windows 2000 Executive character-mode STOP message. It indicates the memory management page file number (PFN) list is corrupted.
User Action:

If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.