*** Fatal System Error: 0x0000007e (0xC0000005,0x00000180,0x88185624,0x88185320) 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 16:43:33.120 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, 88185624, 88185320} Probably caused by : xenpci.sys ( xenpci+c765 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 81700514 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: 88185624, Exception Record Address Arg4: 88185320, 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: +1b8952f00a8dfe0 00000180 ?? ??? EXCEPTION_RECORD: 88185624 -- (.exr 0xffffffff88185624) ExceptionAddress: 00000180 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000008 Parameter[1]: 00000180 Attempt to execute non-executable address 00000180 CONTEXT: 88185320 -- (.cxr 0xffffffff88185320) eax=00000180 ebx=00000007 ecx=88185718 edx=00000000 esi=83e63388 edi=871dfbcc eip=00000180 esp=881856ec ebp=881856fc 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 8fd60765 8945f8 mov dword ptr [ebp-8],eax FAILED_INSTRUCTION_ADDRESS: +1b8952f00a8dfe0 00000180 ?? ??? BUGCHECK_STR: 0x7E LOCK_ADDRESS: 8177c5e0 -- (!locks 8177c5e0) Resource @ nt!PiEngineLock (0x8177c5e0) Exclusively owned Contention Count = 1 Threads: 832a9ad0-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x8177c5e0 Thread Count : 1 Thread address: 0x832a9ad0 Thread wait : 0x8dc7 LAST_CONTROL_TRANSFER: from 817152d7 to 81700514 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 881856e8 8fd60765 0000030f 07ce1ee2 00000000 0x180 881856fc 8fd57b6f 83e8f1c8 00000007 88185718 xenpci+0xc765 88185728 8fd5782b 83e8f1c8 00000004 00000004 xenpci+0x3b6f 88185744 871c35f0 7c170ff8 00000005 83e63388 xenpci+0x382b 8818575c 871c350b 83e63388 871df900 83e63388 Wdf01000!FxPkgPnp::PowerD0Starting+0x2d 881857d4 871c4c97 00000316 00000000 83e63388 Wdf01000!FxPkgPnp::PowerEnterNewState+0x169 881857fc 871c5047 88185814 00000501 871e0e74 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x22a 88185820 871c9597 00000000 83e63388 881858a8 Wdf01000!FxPkgPnp::PowerProcessEvent+0x20d 88185830 871ca49a 83e63388 871e09e0 83e63388 Wdf01000!FxPkgPnp::PowerPolStarting+0x1d 881858a8 871caff3 00000501 00000000 83e63388 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x169 881858d0 871cb72f 881858e8 00000000 00000000 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x21e 881858f4 871c8257 00000000 00000008 83e63388 Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x218 88185910 871c7038 83e63388 871e0270 83e63388 Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0xf4 88185938 871c7d8c 00000108 83e63428 83e63388 Wdf01000!FxPkgPnp::PnpEnterNewState+0x15c 88185960 871c80b9 88185978 83e63388 871df7a0 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1f5 88185988 871bea09 00000002 881859b8 871bfbcf Wdf01000!FxPkgPnp::PnpProcessEvent+0x1cf 88185994 871bfbcf 83e63388 881859b4 83e0d008 Wdf01000!FxPkgPnp::_PnpStartDevice+0x23 881859b8 871a9665 83e0d008 881859e0 871a9888 Wdf01000!FxPkgPnp::Dispatch+0x2a6 881859c4 871a9888 83d972b8 83e0d008 83e0d0c0 Wdf01000!FxDevice::Dispatch+0x7f 881859e0 81704053 83d972b8 83e0d008 88185a5c Wdf01000!FxDevice::DispatchWithLock+0x7b 881859f8 817ac605 00000000 8341eb70 83e71408 nt!IofCallDriver+0x63 88185a14 8165412a 88185a38 81653f47 83e71408 nt!PnpAsynchronousCall+0x96 88185a60 817ad4f6 81653f47 83e71408 8341f008 nt!PnpStartDevice+0xb7 88185abc 817ad3b1 83e71408 0000003c 00000000 nt!PnpStartDeviceNode+0x13a 88185ad8 817aa4db 00000000 00000000 8341f008 nt!PipProcessStartPhase1+0x65 88185cd4 818c5bdd 8341f008 83cfb400 88185d00 nt!PipProcessDevNodeTree+0x187 88185d08 81653ac6 8174a13c 832a9ad0 8177a500 nt!PiRestartDevice+0x8a 88185d44 8168041d 00000000 00000000 832a9ad0 nt!PnpDeviceActionWorker+0x1bc 88185d7c 8181da1c 00000000 ac863c0d 00000000 nt!ExpWorkerThread+0xfd 88185dc0 81676a3e 81680320 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 0xffffffff88185320 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_xenpci+c765 BUCKET_ID: 0x7E_BAD_IP_xenpci+c765 Followup: MachineOwner --------- 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: 88185624, Exception Record Address Arg4: 88185320, 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: +1b8952f00a8dfe0 00000180 ?? ??? EXCEPTION_RECORD: 88185624 -- (.exr 0xffffffff88185624) ExceptionAddress: 00000180 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000008 Parameter[1]: 00000180 Attempt to execute non-executable address 00000180 CONTEXT: 88185320 -- (.cxr 0xffffffff88185320) eax=00000180 ebx=00000007 ecx=88185718 edx=00000000 esi=83e63388 edi=871dfbcc eip=00000180 esp=881856ec ebp=881856fc 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 8fd60765 8945f8 mov dword ptr [ebp-8],eax FAILED_INSTRUCTION_ADDRESS: +1b8952f00a8dfe0 00000180 ?? ??? BUGCHECK_STR: 0x7E LOCK_ADDRESS: 8177c5e0 -- (!locks 8177c5e0) Resource @ nt!PiEngineLock (0x8177c5e0) Exclusively owned Contention Count = 1 Threads: 832a9ad0-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x8177c5e0 Thread Count : 1 Thread address: 0x832a9ad0 Thread wait : 0x8dc7 LAST_CONTROL_TRANSFER: from 817152d7 to 81700514 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 881856e8 8fd60765 0000030f 07ce1ee2 00000000 0x180 881856fc 8fd57b6f 83e8f1c8 00000007 88185718 xenpci+0xc765 88185728 8fd5782b 83e8f1c8 00000004 00000004 xenpci+0x3b6f 88185744 871c35f0 7c170ff8 00000005 83e63388 xenpci+0x382b 8818575c 871c350b 83e63388 871df900 83e63388 Wdf01000!FxPkgPnp::PowerD0Starting+0x2d 881857d4 871c4c97 00000316 00000000 83e63388 Wdf01000!FxPkgPnp::PowerEnterNewState+0x169 881857fc 871c5047 88185814 00000501 871e0e74 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x22a 88185820 871c9597 00000000 83e63388 881858a8 Wdf01000!FxPkgPnp::PowerProcessEvent+0x20d 88185830 871ca49a 83e63388 871e09e0 83e63388 Wdf01000!FxPkgPnp::PowerPolStarting+0x1d 881858a8 871caff3 00000501 00000000 83e63388 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x169 881858d0 871cb72f 881858e8 00000000 00000000 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x21e 881858f4 871c8257 00000000 00000008 83e63388 Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x218 88185910 871c7038 83e63388 871e0270 83e63388 Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0xf4 88185938 871c7d8c 00000108 83e63428 83e63388 Wdf01000!FxPkgPnp::PnpEnterNewState+0x15c 88185960 871c80b9 88185978 83e63388 871df7a0 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1f5 88185988 871bea09 00000002 881859b8 871bfbcf Wdf01000!FxPkgPnp::PnpProcessEvent+0x1cf 88185994 871bfbcf 83e63388 881859b4 83e0d008 Wdf01000!FxPkgPnp::_PnpStartDevice+0x23 881859b8 871a9665 83e0d008 881859e0 871a9888 Wdf01000!FxPkgPnp::Dispatch+0x2a6 881859c4 871a9888 83d972b8 83e0d008 83e0d0c0 Wdf01000!FxDevice::Dispatch+0x7f 881859e0 81704053 83d972b8 83e0d008 88185a5c Wdf01000!FxDevice::DispatchWithLock+0x7b 881859f8 817ac605 00000000 8341eb70 83e71408 nt!IofCallDriver+0x63 88185a14 8165412a 88185a38 81653f47 83e71408 nt!PnpAsynchronousCall+0x96 88185a60 817ad4f6 81653f47 83e71408 8341f008 nt!PnpStartDevice+0xb7 88185abc 817ad3b1 83e71408 0000003c 00000000 nt!PnpStartDeviceNode+0x13a 88185ad8 817aa4db 00000000 00000000 8341f008 nt!PipProcessStartPhase1+0x65 88185cd4 818c5bdd 8341f008 83cfb400 88185d00 nt!PipProcessDevNodeTree+0x187 88185d08 81653ac6 8174a13c 832a9ad0 8177a500 nt!PiRestartDevice+0x8a 88185d44 8168041d 00000000 00000000 832a9ad0 nt!PnpDeviceActionWorker+0x1bc 88185d7c 8181da1c 00000000 ac863c0d 00000000 nt!ExpWorkerThread+0xfd 88185dc0 81676a3e 81680320 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 0xffffffff88185320 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_xenpci+c765 BUCKET_ID: 0x7E_BAD_IP_xenpci+c765 Followup: MachineOwner ---------