Waiting for pipe \\.\pipe\win2k3 Waiting to reconnect... Connected to Windows Server 2003 3790 x86 compatible target at (Fri May 22 01:11:46.843 2020 (UTC - 4:00)), ptr64 FALSE Kernel Debugger connection established. Symbol search path is: C:\ac97 Executable search path is: C:\ac97\ *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe - Windows Server 2003 Kernel Version 3790 UP Free x86 compatible Built by: 3790.srv03_sp2_qfe.150316-2035 Machine Name: Kernel base = 0x80800000 PsLoadedModuleList = 0x808aae88 System Uptime: not available WARNING: Inaccessible path: 'C:\ac97\driver\objchk_wnet_x86\i386' WARNING: Inaccessible path: 'C:\ac97\driver' IPRT: RTMpPoke => rtMpPokeCpuUsingDpc vgdrvHeartbeatInit: Setting up heartbeat to trigger every 2000 milliseconds vgdrvNtSetupDevice: Device is ready! IPRT: RTMpPoke => rtMpPokeCpuUsingDpc IPRT: RTMpPoke => rtMpPokeCpuUsingDpc *** Fatal System Error: 0x0000007e (0xC0000005,0x89FBB46B,0xF78EE950,0xF78EE64C) 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 2003 3790 x86 compatible target at (Fri May 22 01:11:52.812 2020 (UTC - 4:00)), ptr64 FALSE Loading Kernel Symbols ......................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7E, {c0000005, 89fbb46b, f78ee950, f78ee64c} *** No owner thread found for resource 808a9960 *** No owner thread found for resource 808a9960 *** No owner thread found for resource 808a9960 Probably caused by : ntoskrnl.exe ( nt!PipProcessDevNodeTree+1a4 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 8081deee cc int 3 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: 89fbb46b, The address that the exception occurred at Arg3: f78ee950, Exception Record Address Arg4: f78ee64c, Context Record Address Debugging Details: ------------------ *** No owner thread found for resource 808a9960 *** No owner thread found for resource 808a9960 *** No owner thread found for resource 808a9960 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: +52302faf009edec0 89fbb46b 8900 mov dword ptr [eax],eax EXCEPTION_RECORD: f78ee950 -- (.exr 0xfffffffff78ee950) ExceptionAddress: 89fbb46b ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000001 Parameter[1]: 00000001 Attempt to write to address 00000001 CONTEXT: f78ee64c -- (.cxr 0xfffffffff78ee64c) eax=00000001 ebx=000000fb ecx=00000000 edx=00000000 esi=89fc0c80 edi=89eb9d68 eip=89fbb46b esp=f78eea18 ebp=e1362b78 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202 89fbb46b 8900 mov dword ptr [eax],eax ds:0023:00000001=???????? Resetting default scope DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000001 EXCEPTION_PARAMETER2: 00000001 WRITE_ADDRESS: 00000001 FOLLOWUP_IP: nt!PipProcessDevNodeTree+1a4 808e7aa7 85c0 test eax,eax FAILED_INSTRUCTION_ADDRESS: +52302faf009edec0 89fbb46b 8900 mov dword ptr [eax],eax BUGCHECK_STR: 0x7E LOCK_ADDRESS: 808a99e0 -- (!locks 808a99e0) NTSDEXTS: Unable to resolve ntdll!RtlCriticalSectionList NTSDEXTS: Please check your symbols PNP_TRIAGE: Lock address : 0x808a99e0 Thread Count : 1 Thread address: 0x89f98020 Thread wait : 0x1c4 LAST_CONTROL_TRANSFER: from 8087619b to 8081deee STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. f78eea14 ba6e000f 00000004 00000001 89e191f0 0x89fbb46b f78eead4 808e7aa7 00000000 02000001 f78eed00 AC97SMPL!PinDataRangesMicStream (AC97SMPL+0xa00f) f78eed30 808cf042 89f85cd8 00000001 00000000 nt!PipProcessDevNodeTree+0x1a4 f78eed58 8080abb6 00000003 89f98020 808b25fc nt!PiProcessStartSystemDevices+0x3a f78eed80 8082092b 00000000 00000000 89f98020 nt!PipDeviceActionWorker+0x186 f78eedac 809079cb 00000000 00000000 00000000 nt!ExpWorkerThread+0xeb f78eeddc 808284bd 8082086e 00000001 00000000 nt!PspSystemThreadStartup+0x2e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!PipProcessDevNodeTree+1a4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntoskrnl.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5507c485 STACK_COMMAND: .cxr 0xfffffffff78ee64c ; kb FAILURE_BUCKET_ID: 0x7E_BAD_IP_nt!PipProcessDevNodeTree+1a4 BUCKET_ID: 0x7E_BAD_IP_nt!PipProcessDevNodeTree+1a4 Followup: MachineOwner ---------