Not Monitored
Tag not monitored by Microsoft.
37,795 questions
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I recently encountered a blue screen error with the message "wrong symbols." I've included a YAML log that contains additional details about the error. Can anyone help me troubleshoot this issue?
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 624
Key : Analysis.Elapsed.mSec
Value: 3167
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: 249
Key : Analysis.Init.Elapsed.mSec
Value: 10753
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : Bugcheck.Code.LegacyAPI
Value: 0x116
Key : Bugcheck.Code.TargetModel
Value: 0x116
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: WRONG_SYMBOLS_X64_10.0.19041.4170_(WinBuild.160101.0800)_TIMESTAMP_030216-020508_3E4EF1D4_nt_wrong_symbols!3E4EF1D41046000
Key : Failure.Hash
Value: {09d06c2d-34c6-2c59-3b4b-31357f0bc30c}
BUGCHECK_CODE: 116
BUGCHECK_P1: ffff9d8fb97e7010
BUGCHECK_P2: fffff808ea653670
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
FILE_IN_CAB: 032424-11437-01.dmp
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
WRONG_SYMBOLS_TIMESTAMP: 3e4ef1d4
WRONG_SYMBOLS_SIZE: 1046000
FAULTING_MODULE: fffff80608800000 nt
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff9d8fb97e7010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000004
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffff8803`c806fa18 fffff806`0c5564de : 00000000`00000116 ffff9d8f`b97e7010 fffff808`ea653670 ffffffff`c000009a : nt!KeBugCheckEx
ffff8803`c806fa20 fffff806`0c506a84 : fffff808`ea653670 ffff9d8f`c2ac58e0 00000000`00002000 ffff9d8f`c2ac59a0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8803`c806fa60 fffff806`0c4ff5bc : ffff9d8f`c2ba9000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffff8803`c806fa90 fffff806`0c555c05 : 00000000`00000100 ffff9d8f`c2ba9a70 00000000`c55c0f10 fffff806`22b64d85 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffff8803`c806fb10 fffff806`0c555d77 : fffff806`09525440 ffff9d8f`c55c0f10 00000000`00000000 00000000`00000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8803`c806fb40 fffff806`08ac4695 : ffff9d8f`bb340040 fffff806`0c555d50 ffff9d8f`a5ae0ce0 fffff806`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8803`c806fb70 fffff806`08b078c5 : ffff9d8f`bb340040 00000000`00000080 ffff9d8f`a5a67040 00000000`00000000 : nt!ExTryQueueWorkItem+0x5b25
ffff8803`c806fc10 fffff806`08c067b8 : fffff806`03f95180 ffff9d8f`bb340040 fffff806`08b07870 ffffafd7`0b15cacb : nt!IoCancelIrp+0x105
ffff8803`c806fc60 00000000`00000000 : ffff8803`c8070000 ffff8803`c806a000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x78d8
STACK_COMMAND: .cxr; .ecxr ; kb
EXCEPTION_CODE_STR: 3E4EF1D4
EXCEPTION_STR: WRONG_SYMBOLS
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
SYMBOL_NAME: nt_wrong_symbols!3E4EF1D41046000
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_10.0.19041.4170_(WinBuild.160101.0800)_TIMESTAMP_030216-020508_3E4EF1D4_nt_wrong_symbols!3E4EF1D41046000
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {09d06c2d-34c6-2c59-3b4b-31357f0bc30c}
Followup: MachineOwner
---------