Guard32.dl cause crashing


FOLLOWUP_IP: 
guard32+bb04
1000bb04 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  guard32+bb04

FOLLOWUP_NAME:  MachineOwner

STACK_COMMAND:  ~15s ; kb

BUCKET_ID:  WRONG_SYMBOLS

WATSON_IBUCKET:  1233420418

WATSON_IBUCKETTABLE:  1

IMAGE_NAME:  C:\WINDOWS\system32\guard32.dll


this occurs often now >:(

Here is more information


0000000 ??              ???

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000
   ExceptionCode: 80000007 (Wake debugger)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  0000000f

BUGCHECK_STR:  80000007

PROCESS_NAME:  wmiprvse.exe

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: guard32

FAULTING_MODULE: 7c900000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP:  4a0386ee

ERROR_CODE: (NTSTATUS) 0x80000007 - {Kernel Debugger Awakened}  the system debugger was awakened by an interrupt.

EXCEPTION_CODE: (HRESULT) 0x80000007 (2147483655) - Operation aborted

DERIVED_WAIT_CHAIN:  

Dl Eid Cid     WaitType
-- --- ------- --------------------------
   0   8c.278 Speculated (Triage)    -->
   15  8c.8bc Event                  

WAIT_CHAIN_COMMAND:  ~0s;k;;~15s;k;;

BLOCKING_THREAD:  000008bc

DEFAULT_BUCKET_ID:  APPLICATION_HANG_BlockedOn_EventHandle

PRIMARY_PROBLEM_CLASS:  APPLICATION_HANG_BlockedOn_EventHandle

LAST_CONTROL_TRANSFER:  from 7c802542 to 7c90e514


Do you have a minidump file? Are you sure the crash is related to CIS?