Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Opened \\.\COM5 Waiting to reconnect... Connected to Windows Server 2008/Windows Vista 6002 x86 compatible target at (Sat Sep 5 21:40:06.015 2009 (GMT-6)), ptr64 FALSE Kernel Debugger connection established. Symbol search path is: \\Beta\scratch\nick\xen\win-pvdrivers.hg;http://msdl.microsoft.com/download/symbols Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6002 MP (1 procs) Free x86 compatible Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830 Machine Name: Kernel base = 0x8161b000 PsLoadedModuleList = 0x81732c70 System Uptime: not available WARNING: Inaccessible path: 'Z:\documents\Temp\win-pvdrivers.hg' *** Fatal System Error: 0x0000007e (0xC0000005,0x00000180,0x805A04A4,0x805A01A0) 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 6002 x86 compatible target at (Sat Sep 5 21:43:54.507 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, 805a04a4, 805a01a0} Probably caused by : xenpci.sys ( xenpci+27ff ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 816c6a98 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: 805a04a4, Exception Record Address Arg4: 805a01a0, 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: +1e7952f00d2dfe0 00000180 ?? ??? EXCEPTION_RECORD: 805a04a4 -- (.exr 0xffffffff805a04a4) ExceptionAddress: 00000180 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000008 Parameter[1]: 00000180 Attempt to execute non-executable address 00000180 CONTEXT: 805a01a0 -- (.cxr 0xffffffff805a01a0) eax=00000180 ebx=00000007 ecx=805a0590 edx=00000065 esi=838671c8 edi=874993fe eip=00000180 esp=805a056c ebp=805a057c iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202 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+27ff 8748d7ff 8945fc mov dword ptr [ebp-4],eax FAILED_INSTRUCTION_ADDRESS: +1e7952f00d2dfe0 00000180 ?? ??? BUGCHECK_STR: 0x7E LOCK_ADDRESS: 8174f600 -- (!locks 8174f600) Resource @ nt!PiEngineLock (0x8174f600) Exclusively owned Threads: 836613f0-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x8174f600 Thread Count : 1 Thread address: 0x836613f0 Thread wait : 0x158 LAST_CONTROL_TRANSFER: from 816e8c83 to 816c6a98 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 805a0568 8748d7ff 00000000 00000000 000f3000 0x180 805a057c 8748da93 00000007 805a0590 87499b18 xenpci+0x27ff 805a05a0 8748e468 8746cbcc 83828470 0000030f xenpci+0x2a93 805a05b4 874505f0 7c798ff8 00000005 83828470 xenpci+0x3468 805a05cc 8745050b 83828470 8746c900 83828470 Wdf01000!FxPkgPnp::PowerD0Starting+0x2d 805a0644 87451c97 00000316 00000000 83828470 Wdf01000!FxPkgPnp::PowerEnterNewState+0x169 805a066c 87452047 805a0684 00000501 8746de74 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x22a 805a0690 87456597 00000000 83828470 805a0718 Wdf01000!FxPkgPnp::PowerProcessEvent+0x20d 805a06a0 8745749a 83828470 8746d9e0 83828470 Wdf01000!FxPkgPnp::PowerPolStarting+0x1d 805a0718 87457ff3 00000501 00000000 83828470 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x169 805a0740 8745872f 805a0758 00000000 00000000 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x21e 805a0764 87455257 00000000 00000008 83828470 Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x218 805a0780 87454038 83828470 8746d270 83828470 Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0xf4 805a07a8 87454d8c 00000108 83828510 83828470 Wdf01000!FxPkgPnp::PnpEnterNewState+0x15c 805a07d0 874550b9 805a07e8 83828470 8746c7a0 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1f5 805a07f8 8744ba09 00000002 805a0828 8744cbcf Wdf01000!FxPkgPnp::PnpProcessEvent+0x1cf 805a0804 8744cbcf 83828470 805a0824 837c05e0 Wdf01000!FxPkgPnp::_PnpStartDevice+0x23 805a0828 87436665 837c05e0 805a0850 87436888 Wdf01000!FxPkgPnp::Dispatch+0x2a6 805a0834 87436888 8389fe10 837c05e0 837c0698 Wdf01000!FxDevice::Dispatch+0x7f 805a0850 8165f976 8389fe10 837c05e0 805a08cc Wdf01000!FxDevice::DispatchWithLock+0x7b 805a0868 817803ad 00000000 8381fb70 83829e50 nt!IofCallDriver+0x63 805a0884 81627d1d 805a08a8 81627b6e 83829e50 nt!PnpAsynchronousCall+0x96 805a08d0 81780fbe 81627b6e 83829e50 8381ebe8 nt!PnpStartDevice+0xb7 805a092c 81780e79 83829e50 0000003c 00000000 nt!PnpStartDeviceNode+0x13a 805a0948 8177ca52 00000000 00000001 8174d550 nt!PipProcessStartPhase1+0x65 805a0b44 816275c9 836b04d0 00000000 805a0b88 nt!PipProcessDevNodeTree+0x187 805a0b9c 816274d9 00000000 83826cf0 8836cc48 nt!PnpDeviceActionWorker+0xde 805a0bb8 81968296 00000000 00000007 00000000 nt!PnpRequestDeviceAction+0x127 805a0c34 8197730e 8080f5b8 80824fc8 00000000 nt!IopInitializeBootDrivers+0x3b0 805a0c94 8197af5f 8080f5b8 83661718 836613f0 nt!IoInitSystem+0x5af 805a0d74 8177436d 805a0dc0 817f0c42 8080f5b8 nt!Phase1InitializationDiscard+0xb15 805a0d7c 817f0c42 8080f5b8 c207a9cc 00000000 nt!Phase1Initialization+0xd 805a0dc0 81659efe 81774360 8080f5b8 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: xenpci+27ff FOLLOWUP_NAME: MachineOwner MODULE_NAME: xenpci IMAGE_NAME: xenpci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5da8c0 STACK_COMMAND: .cxr 0xffffffff805a01a0 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_xenpci+27ff BUCKET_ID: 0x7E_BAD_IP_xenpci+27ff 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: 805a04a4, Exception Record Address Arg4: 805a01a0, 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: +1e7952f00d2dfe0 00000180 ?? ??? EXCEPTION_RECORD: 805a04a4 -- (.exr 0xffffffff805a04a4) ExceptionAddress: 00000180 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000008 Parameter[1]: 00000180 Attempt to execute non-executable address 00000180 CONTEXT: 805a01a0 -- (.cxr 0xffffffff805a01a0) eax=00000180 ebx=00000007 ecx=805a0590 edx=00000065 esi=838671c8 edi=874993fe eip=00000180 esp=805a056c ebp=805a057c iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202 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+27ff 8748d7ff 8945fc mov dword ptr [ebp-4],eax FAILED_INSTRUCTION_ADDRESS: +1e7952f00d2dfe0 00000180 ?? ??? BUGCHECK_STR: 0x7E LOCK_ADDRESS: 8174f600 -- (!locks 8174f600) Resource @ nt!PiEngineLock (0x8174f600) Exclusively owned Threads: 836613f0-01<*> 1 total locks, 1 locks currently held PNP_TRIAGE: Lock address : 0x8174f600 Thread Count : 1 Thread address: 0x836613f0 Thread wait : 0x158 LAST_CONTROL_TRANSFER: from 816e8c83 to 816c6a98 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 805a0568 8748d7ff 00000000 00000000 000f3000 0x180 805a057c 8748da93 00000007 805a0590 87499b18 xenpci+0x27ff 805a05a0 8748e468 8746cbcc 83828470 0000030f xenpci+0x2a93 805a05b4 874505f0 7c798ff8 00000005 83828470 xenpci+0x3468 805a05cc 8745050b 83828470 8746c900 83828470 Wdf01000!FxPkgPnp::PowerD0Starting+0x2d 805a0644 87451c97 00000316 00000000 83828470 Wdf01000!FxPkgPnp::PowerEnterNewState+0x169 805a066c 87452047 805a0684 00000501 8746de74 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x22a 805a0690 87456597 00000000 83828470 805a0718 Wdf01000!FxPkgPnp::PowerProcessEvent+0x20d 805a06a0 8745749a 83828470 8746d9e0 83828470 Wdf01000!FxPkgPnp::PowerPolStarting+0x1d 805a0718 87457ff3 00000501 00000000 83828470 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x169 805a0740 8745872f 805a0758 00000000 00000000 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x21e 805a0764 87455257 00000000 00000008 83828470 Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x218 805a0780 87454038 83828470 8746d270 83828470 Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0xf4 805a07a8 87454d8c 00000108 83828510 83828470 Wdf01000!FxPkgPnp::PnpEnterNewState+0x15c 805a07d0 874550b9 805a07e8 83828470 8746c7a0 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x1f5 805a07f8 8744ba09 00000002 805a0828 8744cbcf Wdf01000!FxPkgPnp::PnpProcessEvent+0x1cf 805a0804 8744cbcf 83828470 805a0824 837c05e0 Wdf01000!FxPkgPnp::_PnpStartDevice+0x23 805a0828 87436665 837c05e0 805a0850 87436888 Wdf01000!FxPkgPnp::Dispatch+0x2a6 805a0834 87436888 8389fe10 837c05e0 837c0698 Wdf01000!FxDevice::Dispatch+0x7f 805a0850 8165f976 8389fe10 837c05e0 805a08cc Wdf01000!FxDevice::DispatchWithLock+0x7b 805a0868 817803ad 00000000 8381fb70 83829e50 nt!IofCallDriver+0x63 805a0884 81627d1d 805a08a8 81627b6e 83829e50 nt!PnpAsynchronousCall+0x96 805a08d0 81780fbe 81627b6e 83829e50 8381ebe8 nt!PnpStartDevice+0xb7 805a092c 81780e79 83829e50 0000003c 00000000 nt!PnpStartDeviceNode+0x13a 805a0948 8177ca52 00000000 00000001 8174d550 nt!PipProcessStartPhase1+0x65 805a0b44 816275c9 836b04d0 00000000 805a0b88 nt!PipProcessDevNodeTree+0x187 805a0b9c 816274d9 00000000 83826cf0 8836cc48 nt!PnpDeviceActionWorker+0xde 805a0bb8 81968296 00000000 00000007 00000000 nt!PnpRequestDeviceAction+0x127 805a0c34 8197730e 8080f5b8 80824fc8 00000000 nt!IopInitializeBootDrivers+0x3b0 805a0c94 8197af5f 8080f5b8 83661718 836613f0 nt!IoInitSystem+0x5af 805a0d74 8177436d 805a0dc0 817f0c42 8080f5b8 nt!Phase1InitializationDiscard+0xb15 805a0d7c 817f0c42 8080f5b8 c207a9cc 00000000 nt!Phase1Initialization+0xd 805a0dc0 81659efe 81774360 8080f5b8 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: xenpci+27ff FOLLOWUP_NAME: MachineOwner MODULE_NAME: xenpci IMAGE_NAME: xenpci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5da8c0 STACK_COMMAND: .cxr 0xffffffff805a01a0 ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_xenpci+27ff BUCKET_ID: 0x7E_BAD_IP_xenpci+27ff Followup: MachineOwner ---------