From Large Memory Dump: ================================================================================== 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: 808144c9, The address that the exception occurred at Arg3: f7922b6c, Exception Record Address Arg4: f7922868, 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: nt!FsRtlAcquireFileForModWriteEx+189 808144c9 8b7e08 mov edi,dword ptr [esi+8] EXCEPTION_RECORD: f7922b6c -- (.exr 0xfffffffff7922b6c) Cannot read Exception record @ f7922b6c CONTEXT: f7922868 -- (.cxr 0xfffffffff7922868) Unable to read context, Win32 error 0n38 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x7E PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 00000000 to 80826dc7 STACK_TEXT: f7922678 00000000 00000000 00000000 00000000 nt!KeBugCheckEx+0x1b FOLLOWUP_IP: nt!FsRtlAcquireFileForModWriteEx+189 808144c9 8b7e08 mov edi,dword ptr [esi+8] SYMBOL_NAME: nt!FsRtlAcquireFileForModWriteEx+189 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlpa.exe DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710 STACK_COMMAND: .cxr 0xfffffffff7922868 ; kb FAILURE_BUCKET_ID: 0x7E_nt!FsRtlAcquireFileForModWriteEx+189 BUCKET_ID: 0x7E_nt!FsRtlAcquireFileForModWriteEx+189 Followup: MachineOwner --------- From Minidump: =================================================================================== 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: 808144c9, The address that the exception occurred at Arg3: f7922b6c, Exception Record Address Arg4: f7922868, 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: nt!FsRtlAcquireFileForModWriteEx+189 808144c9 8b7e08 mov edi,dword ptr [esi+8] EXCEPTION_RECORD: f7922b6c -- (.exr 0xfffffffff7922b6c) ExceptionAddress: 00000000 ExceptionCode: 00000000 ExceptionFlags: 00000000 NumberParameters: 0 CONTEXT: f7922868 -- (.cxr 0xfffffffff7922868) eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=00000000 eip=00000000 esp=00000000 ebp=00000000 iopl=0 nv up di pl nz na po nc cs=0000 ss=0010 ds=0000 es=0000 fs=0000 gs=0000 efl=00000000 00000000 0000 add byte ptr [eax],al ds:00000000=00 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x7E CURRENT_IRQL: 0 EXCEPTION_STR: 0x0 LAST_CONTROL_TRANSFER: from 00000000 to 80826dc7 STACK_TEXT: f7922678 00000000 00000000 00000000 00000000 nt!KeBugCheckEx+0x1b STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nt!FsRtlAcquireFileForModWriteEx+189 808144c9 8b7e08 mov edi,dword ptr [esi+8] SYMBOL_NAME: nt!FsRtlAcquireFileForModWriteEx+189 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlpa.exe DEBUG_FLR_IMAGE_TIMESTAMP: 45d69710 FAILURE_BUCKET_ID: 0x7E_nt!FsRtlAcquireFileForModWriteEx+189 BUCKET_ID: 0x7E_nt!FsRtlAcquireFileForModWriteEx+189 Followup: MachineOwner ---------