windowsserver2008蓝屏，使用WinDbg分析蓝屏MEMORY.DMP原因

• 问题

• 

  

  0

  登录进行投票

  Use !analyze -v to get detailed debugging information.
  
  BugCheck C4, {91, 0, fffffab028541b60, 0}
  
  Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
  
  Followup: MachineOwner
  ---------
  
  16.0: kd:x86> !analyze -v
  ****************************************
  *                                                                             *
  *                        Bugcheck Analysis                          *
  *                                                                             *
  ****************************************
  
  DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
  A device driver attempting to corrupt the system has been caught.  This is
  because the driver was specified in the registry as being suspect (by the
  administrator) and the kernel has enabled substantial checking of this driver.
  If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
  be among the most commonly seen crashes.
  Arguments:
  Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
      the operating system. The only supported way to extend a kernel
      mode stack is by using KeExpandKernelStackAndCallout.
  Arg2: 0000000000000000
  Arg3: fffffab028541b60
  Arg4: 0000000000000000
  
  Debugging Details:
  ------------------
  
  
  BUGCHECK_STR:  0xc4_91
  
  DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
  
  CURRENT_IRQL:  0
  
  LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000
  
  STACK_TEXT:  
  00000000 00000000 00000000 00000000 00000000 0x0
  
  
  STACK_COMMAND:  kb
  
  SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
  
  FOLLOWUP_NAME:  MachineOwner
  
  MODULE_NAME: Unknown_Module
  
  IMAGE_NAME:  Unknown_Image
  
  DEBUG_FLR_IMAGE_TIMESTAMP:  0
  
  BUCKET_ID:  INVALID_KERNEL_CONTEXT
  
  Followup: MachineOwner
  ---------
  
  

  2019年7月17日 6:29

  回复

  |

  引用