A
Alex
Question:
When I tried to use Office LiveMeeting 2007 Record Manager to save my
meeting recording, the vista will be crashed (Blue screen APC_INDEX_MISMATCH).
Environment:
My machine is Dell D620
OS is Vista 32 business with SP1 . Graphics driver is latest one.
(User profiles , such as my documents, have been moved to disk D , not disk
C as default).
The following is the information:
=========================================================
From Memory Dump File:
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 00000000, address of system function (system call)
Arg2: 7ffdf000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000ffff, Thread->KernelApcDisable
Arg4: 00000000, Previous KernelApcDisable
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: 81c3c000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47c78851
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x1
LAST_CONTROL_TRANSFER: from 815f1294 to 81cf517f
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
9d238614 815f1294 0000005f 9d238690 0000001c nt!KeSetTimerEx+0xb2b
9d238658 815f1259 0000005f 9d238690 0000001c
win32k!PATHOBJ_bCloseFigure+0x3f1d
9d238674 815e7c36 9d238690 0000001c 9d2386b0
win32k!PATHOBJ_bCloseFigure+0x3ee2
9d2386b4 81534027 00426a28 fdb22148 00000000
win32k!PATHOBJ_bPolyBezierTo+0x6760
9d238764 815319c7 9d238c8c 9d2387f4 9d238804 win32k!FONTOBJ_pxoGetXform+0x6ce
9d2389ac 8168cce7 9d238c8c ffa16f20 9d2389cc win32k!EngCreatePalette+0x2b42
9d2389f4 81530451 9d238c8c 9d238ca8 fe233bc0
win32k!XLATEOBJ_hGetColorTransform+0x25bc0
9d238a0c 815790b3 9d238c8c 00000000 9d238cac win32k!EngCreatePalette+0x15cc
9d238a50 816104e7 00000001 9d238a78 9d238cac win32k!EngUnlockSurface+0xb847
9d238cf0 8161030a b1211cab 0000300c 00000001 win32k!EngDeleteSurface+0x3fc9
9d238d44 81c93a7a b1211cab 0000300c 00000001 win32k!EngDeleteSurface+0x3dec
9d238d64 775a9a94 badb0d00 001d985c 00000000 nt!ZwQueryLicenseValue+0xc02
9d238d68 badb0d00 001d985c 00000000 00000000 0x775a9a94
9d238d6c 001d985c 00000000 00000000 00000000 0xbadb0d00
9d238d70 00000000 00000000 00000000 00000000 0x1d985c
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!PATHOBJ_bCloseFigure+3f1d
815f1294 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
SYMBOL_NAME: win32k!PATHOBJ_bCloseFigure+3f1d
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
==========================
Can anyone tell me the reason and how to solve it?
Thanks
--
Alex
When I tried to use Office LiveMeeting 2007 Record Manager to save my
meeting recording, the vista will be crashed (Blue screen APC_INDEX_MISMATCH).
Environment:
My machine is Dell D620
OS is Vista 32 business with SP1 . Graphics driver is latest one.
(User profiles , such as my documents, have been moved to disk D , not disk
C as default).
The following is the information:
=========================================================
From Memory Dump File:
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 00000000, address of system function (system call)
Arg2: 7ffdf000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000ffff, Thread->KernelApcDisable
Arg4: 00000000, Previous KernelApcDisable
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: 81c3c000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47c78851
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x1
LAST_CONTROL_TRANSFER: from 815f1294 to 81cf517f
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
9d238614 815f1294 0000005f 9d238690 0000001c nt!KeSetTimerEx+0xb2b
9d238658 815f1259 0000005f 9d238690 0000001c
win32k!PATHOBJ_bCloseFigure+0x3f1d
9d238674 815e7c36 9d238690 0000001c 9d2386b0
win32k!PATHOBJ_bCloseFigure+0x3ee2
9d2386b4 81534027 00426a28 fdb22148 00000000
win32k!PATHOBJ_bPolyBezierTo+0x6760
9d238764 815319c7 9d238c8c 9d2387f4 9d238804 win32k!FONTOBJ_pxoGetXform+0x6ce
9d2389ac 8168cce7 9d238c8c ffa16f20 9d2389cc win32k!EngCreatePalette+0x2b42
9d2389f4 81530451 9d238c8c 9d238ca8 fe233bc0
win32k!XLATEOBJ_hGetColorTransform+0x25bc0
9d238a0c 815790b3 9d238c8c 00000000 9d238cac win32k!EngCreatePalette+0x15cc
9d238a50 816104e7 00000001 9d238a78 9d238cac win32k!EngUnlockSurface+0xb847
9d238cf0 8161030a b1211cab 0000300c 00000001 win32k!EngDeleteSurface+0x3fc9
9d238d44 81c93a7a b1211cab 0000300c 00000001 win32k!EngDeleteSurface+0x3dec
9d238d64 775a9a94 badb0d00 001d985c 00000000 nt!ZwQueryLicenseValue+0xc02
9d238d68 badb0d00 001d985c 00000000 00000000 0x775a9a94
9d238d6c 001d985c 00000000 00000000 00000000 0xbadb0d00
9d238d70 00000000 00000000 00000000 00000000 0x1d985c
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!PATHOBJ_bCloseFigure+3f1d
815f1294 8bf0 mov esi,eax
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: win32k.sys
SYMBOL_NAME: win32k!PATHOBJ_bCloseFigure+3f1d
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
==========================
Can anyone tell me the reason and how to solve it?
Thanks
--
Alex