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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801439070a1, The address that the exception occurred at
Arg3: ffffa682da5f6298, Exception Record Address
Arg4: ffffa682da5f5a80, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 0
Key : Analysis.Elapsed.mSec
Value: 652
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 140
Key : Analysis.Init.Elapsed.mSec
Value: 11278
Key : Analysis.Memory.CommitPeak.Mb
Value: 51
Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007e
Key : Bugcheck.Code.TargetModel
Value: 0x1000007e
Key : Dump.Attributes.AsUlong
Value: 21008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: WRONG_SYMBOLS_X64_TIMESTAMP_110626-041421_4E06B21D_nt_wrong_symbols!4E06B21D144F000
Key : Failure.Hash
Value: {be2f3339-efc5-b57e-bf60-4f05cddbf1c8}
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff801439070a1
BUGCHECK_P3: ffffa682da5f6298
BUGCHECK_P4: ffffa682da5f5a80
FILE_IN_CAB: 102124-9125-01.dmp
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
WRONG_SYMBOLS_TIMESTAMP: 4e06b21d
WRONG_SYMBOLS_SIZE: 144f000
FAULTING_MODULE: fffff80199000000 nt
DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump
FAULTING_THREAD: ffffe502b4d5c180
EXCEPTION_RECORD: ffffa682da5f6298 -- (.exr 0xffffa682da5f6298)
ExceptionAddress: fffff801439070a1 (igdkmdnd64+0x00000000004370a1)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000100000000
Attempt to read from address 0000000100000000
CONTEXT: ffffa682da5f5a80 -- (.cxr 0xffffa682da5f5a80)
rax=ffffe502ac348028 rbx=ffffe502b238bcd0 rcx=ffffe502b26a7000
rdx=ffffe502b238bcd0 rsi=ffffc28332d51190 rdi=ffffe502b26a7000
rip=fffff801439070a1 rsp=ffffa682da5f64d0 rbp=0000000100000000
r8=0000000000000000 r9=ffffe502bfa9f9e0 r10=ffffe502ac348000
r11=ffffa682da5f6798 r12=ffffe502b238bc00 r13=0000000000000001
r14=ffffe502bfa9f9e0 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
igdkmdnd64+0x4370a1:
fffff801`439070a1 488b6d00 mov rbp,qword ptr [rbp] ss:0018:00000001`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
EXCEPTION_STR: WRONG_SYMBOLS
STACK_TEXT:
ffffa682`da5f64d0 00000000`00000000 : 00000000`00000000 00000000`0000006c 00000000`00022244 00000000`000bddbc : igdkmdnd64+0x4370a1
STACK_COMMAND: .cxr 0xffffa682da5f5a80 ; kb
EXCEPTION_CODE_STR: 4E06B21D
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
SYMBOL_NAME: nt_wrong_symbols!4E06B21D144F000
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_TIMESTAMP_110626-041421_4E06B21D_nt_wrong_symbols!4E06B21D144F000
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {be2f3339-efc5-b57e-bf60-4f05cddbf1c8}
Followup: MachineOwner
---------
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 133740015420773439
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : USB\VID_2717&PID_FF40\CUV8OJS8Q8N7QCKF
VetoString :
drive.google.com
