*** Fatal System Error: 0x0000007e (0xC0000005,0x00000180,0x83589624,0x83589320) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows Server 2008/Windows Vista 6001 x86 compatible target at (Sun Sep 6 20:28:13.217 2009 (GMT-6)), ptr64 FALSE Loading Kernel Symbols ............ Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ................................................... ......................................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, 180, 83589624, 83589320} Probably caused by : xenpci.sys ( xenpci+c765 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 816f3514 cc int 3 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) 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. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 00000180, The address that the exception occurred at Arg3: 83589624, Exception Record Address Arg4: 83589320, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: +199952f00a8dfe0 00000180 ?? ??? EXCEPTION_RECORD: 83589624 -- (.exr 0xffffffff83589624) ExceptionAddress: 00000180 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000008 Parameter[1]: 00000180 Attempt to execute non-executable address 00000180 CONTEXT: 83589320 -- (.cxr 0xffffffff83589320) eax=00000180 ebx=00000007 ecx=83589718 edx=00000000 esi=8535f010 edi=825dbbcc eip=00000180 esp=835896ec ebp=835896fc iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 00000180 ?? ??? Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 00000008 EXCEPTION_PARAMETER2: 00000180 WRITE_ADDRESS: 00000180 FOLLOWUP_IP: xenpci+c765 82b28765 8945f8 mov dword ptr [ebp-8],eax FAILED_INSTRUCTION_ADDRESS: +199952f00a8dfe0 00000180 ?? ??? BUGCHECK_STR: 0x7E LOCK_ADDRESS: 8176f5e0 -- (!locks 8176f5e0) Resource @ nt!PiEngineLock (0x8176f5e0) Exclusively owned Contention Count = 2 Threads: 848a9580-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x8176f5e0 Thread Count : 1 Thread address: 0x848a9580 Thread wait : 0xa4ce LAST_CONTROL_TRANSFER: from 817082d7 to 816f3514 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 835896e8 82b28765 0000030f 01ebd286 00000000 0x180 835896fc 82b1fb6f 854661c8 00000007 83589718 xenpci+0xc765 83589728 82b1f82b 854661c8 00000004 00000004 xenpci+0x3b6f 83589744 825bf5f0 7ab99ff8 00000005 8535f010 xenpci+0x382b 8358975c 825bf50b 8535f010 825db900 8535f010 Wdf01000!FxPkgPnp::PowerD0Starting+0x2d 835897d4 825c0c97 00000316 00000000 8535f010 Wdf01000!FxPkgPnp::PowerEnterNewState+0x169 835897fc 825c1047 83589814 00000501 825dce74 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x22a 83589820 825c5597 00000000 8535f010 835898a8 Wdf01000!FxPkgPnp::PowerProcessEvent+0x20d 83589830 825c649a 8535f010 825dc9e0 8535f010 Wdf01000!FxPkgPnp::PowerPolStarting+0x1d 835898a8 825c6ff3 00000501 00000000 8535f010 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x169 835898d0 825c772f 835898e8 00000000 00000000 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x21e 835898f4 825c4257 00000000 00000008 8535f010 Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x218 83589910 825c3038 8535f010 825dc270 8535f010 Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0xf4 83589938 825c3d8c 00000108 8535f0b0 8535f010 Wdf01000!FxPkgPnp::PnpEnterNewState+0x15c 83589960 825c40b9 83589978 8535f010 825db7a0 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1f5 83589988 825baa09 00000002 835899b8 825bbbcf Wdf01000!FxPkgPnp::PnpProcessEvent+0x1cf 83589994 825bbbcf 8535f010 835899b4 8535fac0 Wdf01000!FxPkgPnp::_PnpStartDevice+0x23 835899b8 825a5665 8535fac0 835899e0 825a5888 Wdf01000!FxPkgPnp::Dispatch+0x2a6 835899c4 825a5888 853524f0 8535fac0 8535fb78 Wdf01000!FxDevice::Dispatch+0x7f 835899e0 816f7053 853524f0 8535fac0 83589a5c Wdf01000!FxDevice::DispatchWithLock+0x7b 835899f8 8179f605 00000000 84a20b70 853dfbb0 nt!IofCallDriver+0x63 83589a14 8164712a 83589a38 81646f47 853dfbb0 nt!PnpAsynchronousCall+0x96 83589a60 817a04f6 81646f47 853dfbb0 84a21ea8 nt!PnpStartDevice+0xb7 83589abc 817a03b1 853dfbb0 0000003c 00000000 nt!PnpStartDeviceNode+0x13a 83589ad8 8179d4db 00000000 00000000 84a21ea8 nt!PipProcessStartPhase1+0x65 83589cd4 818b8bdd 84a21ea8 8542f128 83589d00 nt!PipProcessDevNodeTree+0x187 83589d08 81646ac6 8173d13c 848a9580 8176d500 nt!PiRestartDevice+0x8a 83589d44 8167341d 00000000 00000000 848a9580 nt!PnpDeviceActionWorker+0x1bc 83589d7c 81810a1c 00000000 66e3aa71 00000000 nt!ExpWorkerThread+0xfd 83589dc0 81669a3e 81673320 00000001 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: xenpci+c765 FOLLOWUP_NAME: MachineOwner MODULE_NAME: xenpci IMAGE_NAME: xenpci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5da99a STACK_COMMAND: .cxr 0xffffffff83589320 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_xenpci+c765 BUCKET_ID: 0x7E_BAD_IP_xenpci+c765 Followup: MachineOwner ---------