Thanks Laszlo, I just made that change. In the mean time I tried to use
Windbg to read my latest dump file. I don't know if I did it right or not and
I really don't know what it is telling me but I'm going to post it below.
Maybe someone can make some sense out of it for me.
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini011108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\windows\symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Fri Jan 11 00:03:07.526 2008 (GMT-8)
System Uptime: 1 days 16:37:26.916
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntkrnlpa.exe
Loading Kernel Symbols
.....................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 99adb724, 99253c14, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
MODULE_NAME: win32k
FAULTING_MODULE: 81c00000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 46d4d163
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx
referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+ffffffff99adb724
99adb724 ?? ???
TRAP_FRAME: 99253c14 -- (.trap 0xffffffff99253c14)
ErrCode = 00000002
eax=00000001 ebx=00000000 ecx=95adb944 edx=08b77970 esi=00000001 edi=00000000
eip=99adb724 esp=99253c88 ebp=99253c90 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
99adb724 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from ff5b41d0 to 99adb724
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
99253c84 ff5b41d0 00000000 99253ce8 95ad9976 0x99adb724
99253c90 95ad9976 000025ff 00000000 00000001 0xff5b41d0
99253ce8 95add983 81253d18 000025ff 00000000
win32k!xxxRealInternalGetMessage+0x4f4
99253d4c 81c8caaa 0160ff44 00000000 00000000 win32k!NtUserGetMessage+0x85
99253d64 77740f34 badb0d00 0160fef4 00000000 nt+0x8caaa
99253d68 badb0d00 0160fef4 00000000 00000000 0x77740f34
99253d6c 0160fef4 00000000 00000000 00000000 0xbadb0d00
99253d70 00000000 00000000 00000000 00000000 0x160fef4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!xxxRealInternalGetMessage+4f4
95ad9976 ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: win32k!xxxRealInternalGetMessage+4f4
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
3: kd> lmvm win32k
start end module name
95a00000 95bff000 win32k M (pdb symbols)
C:\windows\symbols\sys\win32k.pdb
Loaded symbol image file: win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Tue Aug 28 18:52:35 2007 (46D4D163)
CheckSum: 001F53A2
ImageSize: 001FF000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0