*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001624fa1, The address that the exception occurred at
Arg3: fffff8800379a208, Exception Record Address
Arg4: fffff88003799a60, Context Record Address
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.23392.amd64fre.win7sp1_ldr.160317-0600
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff88001624fa1
BUGCHECK_P3: fffff8800379a208
BUGCHECK_P4: fffff88003799a60
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
FAULTING_IP:
pcw!PcwCreateInstance+29
fffff880`01624fa1 44394a1c cmp dword ptr [rdx+1Ch],r9d
EXCEPTION_RECORD: fffff8800379a208 -- (.exr 0xfffff8800379a208)
ExceptionAddress: fffff88001624fa1 (pcw!PcwCreateInstance+0x0000000000000029)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000001c
Attempt to read from address 000000000000001c
CONTEXT: fffff88003799a60 -- (.cxr 0xfffff88003799a60)
rax=fffff8800379a498 rbx=0000000000000000 rcx=fffffa80098e3be0
rdx=0000000000000000 rsi=0000000000000001 rdi=fffffa80098e3be8
rip=fffff88001624fa1 rsp=fffff8800379a440 rbp=0000000000000000
r8=fffffa80098e3be8 r9=0000000000000001 r10=fffffa80098e3be0
r11=fffff88001628030 r12=fffff88007f72fb0 r13=fffffa80098e3be0
r14=fffffa80098e3be8 r15=fffff88007f730d4
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
pcw!PcwCreateInstance+0x29:
fffff880`01624fa1 44394a1c cmp dword ptr [rdx+1Ch],r9d ds:002b:00000000`0000001c=????????
Resetting default scope
CPU_COUNT: 8
CPU_MHZ: d40
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1C'00000000 (cache) 19'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 000000000000001c
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fb100
Unable to get MmSystemRangeStart
000000000000001c
FOLLOWUP_IP:
pcw!PcwCreateInstance+29
fffff880`01624fa1 44394a1c cmp dword ptr [rdx+1Ch],r9d
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
ANALYSIS_SESSION_HOST:
ANALYSIS_SESSION_TIME: 04-20-2016 11:58:10.0871
ANALYSIS_VERSION:
LAST_CONTROL_TRANSFER: from fffff80003652db1 to fffff88001624fa1
STACK_TEXT:
fffff880`0379a440 fffff800`03652db1 : 00000000`00000000 fffffa80`066fea10 00000000`00000000 fffffa80`098e3be8 : pcw!PcwCreateInstance+0x29
fffff880`0379a4a0 fffff880`07f88d6f : 00000000`00000009 00000000`00000000 fffffa80`066fea10 00000000`00000000 : nt!PcwCreateInstance+0x51
fffff880`0379a4e0 00000000`00000009 : 00000000`00000000 fffffa80`066fea10 00000000`00000000 fffff880`0379a550 : iusb3xhc+0x93d6f
fffff880`0379a4e8 00000000`00000000 : fffffa80`066fea10 00000000`00000000 fffff880`0379a550 fffff880`0379a5b0 : 0x9
THREAD_SHA1_HASH_MOD_FUNC: aeb6313b6242d1849b9923704a4cfe5beb00168c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3f9a6ac7dafa1730e3147744096045885739ee8a
THREAD_SHA1_HASH_MOD: f10bef32fb666286bf81c890fa6237af4d173fa8
FAULT_INSTR_CODE: 1c4a3944
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: pcw!PcwCreateInstance+29
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: pcw
IMAGE_NAME: pcw.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0ff
IMAGE_VERSION: 6.1.7600.16385
STACK_COMMAND: .cxr 0xfffff88003799a60 ; kb
FAILURE_BUCKET_ID: X64_0x7E_pcw!PcwCreateInstance+29
BUCKET_ID: X64_0x7E_pcw!PcwCreateInstance+29
PRIMARY_PROBLEM_CLASS: X64_0x7E_pcw!PcwCreateInstance+29
TARGET_TIME: 2016-04-20T06:36:47.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-03-17 22:43:02
BUILDDATESTAMP_STR: 160317-0600
BUILDLAB_STR: win7sp1_ldr
BUILDOSVER_STR: 6.1.7601.23392.amd64fre.win7sp1_ldr.160317-0600
ANALYSIS_SESSION_ELAPSED_TIME: 2e3
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_pcw!pcwcreateinstance+29
FAILURE_ID_HASH: {f9021004-a9eb-3774-61a3-3d8b4ee9a48b}
Followup: MachineOwner
---------