Re: HELP! Calling old DrvEnablePDEV in the MS mirror driver, bluescreened when rebooting,

From: lucy (losemind_at_yahoo.com)
Date: 08/24/04 

Date: Mon, 23 Aug 2004 18:16:52 -0700

output from windbg command "!analyze -v". complete information attached...
anybody saves me? Tahnk you so much

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

Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini082304-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp2.031208-2000
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c230
Debug session time: Mon Aug 23 15:39:38 2004
System Uptime: 0 days 0:00:22.093
Loading Kernel Symbols
............................................................................
.................................
Loading unloaded module list
..
Loading User Symbols
****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*
****************************************************************************
***

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e2c3f304, 1, bf84e4f8, 2}

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!PDEVOBJ::PDEVOBJ+16e )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: e2c3f304, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf84e4f8, If non-zero, the instruction address which referenced the
bad memory
 address.
Arg4: 00000002, (reserved)

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

Could not read faulting driver name

WRITE_ADDRESS: e2c3f304

FAULTING_IP:
win32k!PDEVOBJ::PDEVOBJ+16e
bf84e4f8 898104030000 mov [ecx+0x304],eax

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from bf808788 to bf84e4f8

STACK_TEXT:
a6037a48 bf808788 e1864628 e1c35178 00000000 win32k!PDEVOBJ::PDEVOBJ+0x16e
a6037a9c bf8048e3 e16f66c0 e197d758 e1c35178 win32k!hCreateHDEV+0x2cb
a6037c00 bf804245 00000000 00000000 00000001 win32k!DrvCreateMDEV+0x3ea
a6037cf4 bf809cda 00000000 00000000 00000000
win32k!DrvChangeDisplaySettings+0x29e
a6037d4c bf809d98 80531244 00050000 00000064 win32k!InitVideo+0x31
a6037ddc 80535986 8060368c 00000004 00000000 win32k!NtUserInitialize+0x86
a6037df0 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

FOLLOWUP_IP:
win32k!PDEVOBJ::PDEVOBJ+16e
bf84e4f8 898104030000 mov [ecx+0x304],eax

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!PDEVOBJ::PDEVOBJ+16e

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3f73195d

STACK_COMMAND: kb

BUCKET_ID: 0x50_W_win32k!PDEVOBJ::PDEVOBJ+16e

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

Relevant Pages
Loading