使用自动更新安装侯蓝屏。

• 问题

• 

  

  0

  登录进行投票

  通WINDOWS UPDATE获取更新后安装更新时蓝屏。
  
  问题签名
  问题事件名称: BlueScreen
  OS 版本: 6.0.6001.2.1.0.768.2
  区域设置 ID: 2052
  
  Mini062109-06.dmp
  sysdata.xml
  Version.txt
  关于该问题的额外信息
  BCCode: 1000008e
  BCP1: C0000005
  BCP2: 83289AFA
  BCP3: 8EFF9BE0
  BCP4: 00000000
  OS Version: 6_0_6001
  Service Pack: 1_0
  Product: 768_1
  服务器信息: e4f04726-77d5-4334-85e9-761c63f00ca9
  
  
  
  Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
  Copyright (c) Microsoft Corporation. All rights reserved.

  
  Loading Dump File [C:\Windows\Minidump\Mini062109-06.dmp]
  Mini Kernel Dump File: Only registers and stack trace are available

  Symbol search path is: *** Invalid ***
  ****************************************************************************
  * Symbol loading may be unreliable without a symbol search path.           *
  * Use .symfix to have the debugger choose a symbol path.                   *
  * After setting your symbol path, use .reload to refresh symbol locations. *
  ****************************************************************************
  Executable search path is:
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************
  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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
  Product: WinNt, suite: TerminalServer SingleUserTS Personal
  Machine Name:
  Kernel base = 0x8324c000 PsLoadedModuleList = 0x83363c70
  Debug session time: Sun Jun 21 20:03:52.708 2009 (GMT+8)
  System Uptime: 0 days 0:30:00.698
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************
  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, 83289afa, 8eff9be0, 0}

  *** WARNING: Unable to verify timestamp for mssmbios.sys
  *** ERROR: Module load completed but symbols could not be loaded for mssmbios.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                                     ***
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  ***    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                                     ***
  ***                                                                   ***
  *************************************************************************
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************
  Probably caused by : ntkrnlpa.exe ( nt+3dafa )

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

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

  KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
  This is a very common bugcheck.  Usually the exception address pinpoints
  the driver/function that caused the problem.  Always note this address
  as well as the link date of the driver/image that contains this address.
  Some common problems are exception code 0x80000003.  This means a hard
  coded breakpoint or assertion was hit, but this system was booted
  /NODEBUG.  This is not supposed to happen as developers should never have
  hardcoded breakpoints in retail code, but ...
  If this happens, make sure a debugger gets connected, and the
  system is booted /DEBUG.  This will let us see why this breakpoint is
  happening.
  Arguments:
  Arg1: c0000005, The exception code that was not handled
  Arg2: 83289afa, The address that the exception occurred at
  Arg3: 8eff9be0, Trap Frame
  Arg4: 00000000

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

  ***** 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                                     ***
  ***                                                                   ***
  *************************************************************************
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************

  ADDITIONAL_DEBUG_TEXT: 
  Use '!findthebuild' command to search for the target build information.
  If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

  MODULE_NAME: nt

  FAULTING_MODULE: 8324c000 nt

  DEBUG_FLR_IMAGE_TIMESTAMP:  49ac8fb4

  EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

  FAULTING_IP:
  nt+3dafa
  83289afa 3b510c          cmp     edx,dword ptr [ecx+0Ch]

  TRAP_FRAME:  8eff9be0 -- (.trap 0xffffffff8eff9be0)
  ErrCode = 00000000
  eax=37313733 ebx=82581660 ecx=37313733 edx=00000800 esi=82581898 edi=8257da48
  eip=83289afa esp=8eff9c54 ebp=8eff9c54 iopl=0         nv up ei pl nz na pe nc
  cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
  nt+0x3dafa:
  83289afa 3b510c          cmp     edx,dword ptr [ecx+0Ch] ds:0023:3731373f=????????
  Resetting default scope

  CUSTOMER_CRASH_COUNT:  6

  DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

  BUGCHECK_STR:  0x8E

  CURRENT_IRQL:  0

  LAST_CONTROL_TRANSFER:  from 833085f5 to 83289afa

  STACK_TEXT: 
  WARNING: Stack unwind information not available. Following frames may be wrong.
  8eff9c54 833085f5 8eff9c64 00000000 8256c2f8 nt+0x3dafa
  8eff9c68 83470ad5 82d9cd04 82d9cd04 b7450fc8 nt+0xbc5f5
  8eff9cc4 8344514b 82581660 00800000 00000000 nt+0x224ad5
  8eff9cd8 83447ff4 82581660 00800000 b7450fb0 nt+0x1f914b
  8eff9d18 83466dac b7450fc8 00000000 b7450fc8 nt+0x1fbff4
  8eff9d50 832a3a1a 00000084 00000000 00800000 nt+0x21adac
  8eff9d64 770f9a94 badb0d00 01faf618 00000000 nt+0x57a1a
  8eff9d68 badb0d00 01faf618 00000000 00000000 0x770f9a94
  8eff9d6c 01faf618 00000000 00000000 00000000 0xbadb0d00
  8eff9d70 00000000 00000000 00000000 00000000 0x1faf618

  
  STACK_COMMAND:  kb

  FOLLOWUP_IP:
  nt+3dafa
  83289afa 3b510c          cmp     edx,dword ptr [ecx+0Ch]

  SYMBOL_STACK_INDEX:  0

  SYMBOL_NAME:  nt+3dafa

  FOLLOWUP_NAME:  MachineOwner

  IMAGE_NAME:  ntkrnlpa.exe

  BUCKET_ID:  WRONG_SYMBOLS

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

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

  KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
  This is a very common bugcheck.  Usually the exception address pinpoints
  the driver/function that caused the problem.  Always note this address
  as well as the link date of the driver/image that contains this address.
  Some common problems are exception code 0x80000003.  This means a hard
  coded breakpoint or assertion was hit, but this system was booted
  /NODEBUG.  This is not supposed to happen as developers should never have
  hardcoded breakpoints in retail code, but ...
  If this happens, make sure a debugger gets connected, and the
  system is booted /DEBUG.  This will let us see why this breakpoint is
  happening.
  Arguments:
  Arg1: c0000005, The exception code that was not handled
  Arg2: 83289afa, The address that the exception occurred at
  Arg3: 8eff9be0, Trap Frame
  Arg4: 00000000

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

  ***** 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                                     ***
  ***                                                                   ***
  *************************************************************************
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************
  *********************************************************************
  * Symbols can not be loaded because symbol path is not initialized. *
  *                                                                   *
  * The Symbol Path can be set by:                                    *
  *   using the _NT_SYMBOL_PATH environment variable.                 *
  *   using the -y <symbol_path> argument when starting the debugger. *
  *   using .sympath and .sympath+                                    *
  *********************************************************************

  ADDITIONAL_DEBUG_TEXT: 
  Use '!findthebuild' command to search for the target build information.
  If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

  MODULE_NAME: nt

  FAULTING_MODULE: 8324c000 nt

  DEBUG_FLR_IMAGE_TIMESTAMP:  49ac8fb4

  EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

  FAULTING_IP:
  nt+3dafa
  83289afa 3b510c          cmp     edx,dword ptr [ecx+0Ch]

  TRAP_FRAME:  8eff9be0 -- (.trap 0xffffffff8eff9be0)
  ErrCode = 00000000
  eax=37313733 ebx=82581660 ecx=37313733 edx=00000800 esi=82581898 edi=8257da48
  eip=83289afa esp=8eff9c54 ebp=8eff9c54 iopl=0         nv up ei pl nz na pe nc
  cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
  nt+0x3dafa:
  83289afa 3b510c          cmp     edx,dword ptr [ecx+0Ch] ds:0023:3731373f=????????
  Resetting default scope

  CUSTOMER_CRASH_COUNT:  6

  DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

  BUGCHECK_STR:  0x8E

  CURRENT_IRQL:  0

  LAST_CONTROL_TRANSFER:  from 833085f5 to 83289afa

  STACK_TEXT: 
  WARNING: Stack unwind information not available. Following frames may be wrong.
  8eff9c54 833085f5 8eff9c64 00000000 8256c2f8 nt+0x3dafa
  8eff9c68 83470ad5 82d9cd04 82d9cd04 b7450fc8 nt+0xbc5f5
  8eff9cc4 8344514b 82581660 00800000 00000000 nt+0x224ad5
  8eff9cd8 83447ff4 82581660 00800000 b7450fb0 nt+0x1f914b
  8eff9d18 83466dac b7450fc8 00000000 b7450fc8 nt+0x1fbff4
  8eff9d50 832a3a1a 00000084 00000000 00800000 nt+0x21adac
  8eff9d64 770f9a94 badb0d00 01faf618 00000000 nt+0x57a1a
  8eff9d68 badb0d00 01faf618 00000000 00000000 0x770f9a94
  8eff9d6c 01faf618 00000000 00000000 00000000 0xbadb0d00
  8eff9d70 00000000 00000000 00000000 00000000 0x1faf618

  
  STACK_COMMAND:  kb

  FOLLOWUP_IP:
  nt+3dafa
  83289afa 3b510c          cmp     edx,dword ptr [ecx+0Ch]

  SYMBOL_STACK_INDEX:  0

  SYMBOL_NAME:  nt+3dafa

  FOLLOWUP_NAME:  MachineOwner

  IMAGE_NAME:  ntkrnlpa.exe

  BUCKET_ID:  WRONG_SYMBOLS

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

  0: kd> lmvm nt
  start    end        module name
  8324c000 83605000   nt       T (no symbols)          
      Loaded symbol image file: ntkrnlpa.exe
      Image path: \SystemRoot\system32\ntkrnlpa.exe
      Image name: ntkrnlpa.exe
      Timestamp:        Tue Mar 03 10:02:28 2009 (49AC8FB4)
      CheckSum:         0036FB1F
      ImageSize:        003B9000
      Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
  0: kd> .trap 0xffffffff8eff9be0
  ErrCode = 00000000
  eax=37313733 ebx=82581660 ecx=37313733 edx=00000800 esi=82581898 edi=8257da48
  eip=83289afa esp=8eff9c54 ebp=8eff9c54 iopl=0         nv up ei pl nz na pe nc
  cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
  nt+0x3dafa:
  83289afa 3b510c          cmp     edx,dword ptr [ecx+0Ch] ds:0023:3731373f=????????

   

  • 已编辑 流幕 2009年6月21日 13:27

  2009年6月21日 12:58

  回复

  |

  引用