WinDbg sürekli nt_wrong_symbols hatası veriyor

VENGEANCE ANGEL · 24 Mart 2024

Herkese merhaba,.
Hangi DMP dosyasını açsam, aynı senaryo. Nt_wrong_symbols hatası veriyor. Hiçbir DMP dosyasını analiz edemiyorum. Bunun sebebi nedir ve nasıl çözerim?

Symnoisy sympath gibi komutları girmeme rağmen düzelmedi. Aşağıya örnek bir DMP dosyası bıraktım.

Bilgisayarı yeni formatladım ve Store'dan en güncel sürümü kurdum.
@claus

************* Preparing the environment for debugger extensions gallery repositories **************
Extensionrepository : Implicit.
Useexperimentalfeaturefornugetshare : True.
Allownugetexeupdate : True.
Nonınteractivenuget : True.
Allownugetmscredentialproviderınstall : True.
Allowparallelınitializationoflocalrepositories : True.
Enableredirecttov8jsprovider : False.
-- Configuring repositories.
----> Repository : Localınstalled, enabled: True.
----> Repository : Userextensions, enabled: True.

>>>>>>>>> Preparing the environment for debugger extensions gallery repositories completed, duration 0.000 seconds.

Genişletmek için tıkla...

Genişletmek için tıkla...

Genişletmek için tıkla...

************* Waiting for debugger extensions gallery to ınitialize **************

>>>>>>>>> Waiting for debugger extensions gallery to ınitialize completed, duration 0.015 seconds.

Genişletmek için tıkla...

Genişletmek için tıkla...

Genişletmek için tıkla...

----> Repository : Userextensions, enabled: True, packages count: 0
----> Repository : Localınstalled, enabled: True, packages count: 41.

Microsoft (r) Windows debugger version 10.0.27553.1004 AMD64.
Copyright (C) Microsoft Corporation. All rights reserved.

Loading dump file [C:\Users\VENGEANCE ANGEL\Downloads\032424-11734-01.dmp]
Mini kernel dump file: Only registers and stack trace are available.

************* Path validation summary **************
Response time (ms) location.
Ok C:\symbols
Symbol Search path is: C:\symbols
Executable Search path is:
Unable to load image ntoskrnl.exe, Win32 error 0N2.
*** Warnıng: Unable to verify timestamp for ntoskrnl.exe
Windows 10 kernel version 22621 MP (16 procs) Free X64.
Product: Winnt, Suite: Terminalserver singleuserts.
Kernel base = 0xfffff807`12000000 psloadedmodulelist = 0xfffff807`12c13530
Debug session time: Sun mar 24 21:05:07.931 2024 (utc + 3:00)
System uptime: 0 days 4:33:33.740
Unable to load image ntoskrnl.exe, Win32 error 0N2.
*** Warnıng: Unable to verify timestamp for ntoskrnl.exe
Loading kernel symbols.
...............................................................
................................................................
................................................................
.....................
Loading user symbols.
Peb is paged out (peb.ldr = 0000007C'2FA41018). Type ".hh dbgerr001" for details.
Loading unloaded module list.
.............

************* Symbol loading error summary **************
Module name error.
Ntoskrnl the System cannot find the file specified.

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol Search path (.sympath) is correct.
For analysis of this file, run !analyze -v
NT+0x4177F0:
Fffff807'124177F0 48894C2408 mov qword ptr [rsp+8],rcx SS:ffffd001'DD5dbcb0 = 0000000000020001.
1: Kd> !analyze -v
*******************************************************************************

*
Bugcheck analysis *
*

*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011.
Arg2: 00000000002F60D0.
Arg3: 0000000000001003.
Arg4: FFFFE70001405C40.

Debugging details:
------------------

*** Warnıng: Unable to verify timestamp for mssmbios.sys
***** Kernel symbols are wrong. Please fix symbols to do analysis.

*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_ımage_dos_header *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_eprocess *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_kprcb *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_kprcb *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_kprcb *
*

*************************************************************************
*************************************************************************
* *

*
either you specified an unqualified symbol, or your debugger *
doesn't have Full symbol information. Unqualified symbol *
resolution is turned off by default. Please either specify a *
fully qualified symbol module!symbolname, or enable resolution *
of unqualified symbols by typing ".symopt- 100". Note that *
enabling unqualified symbol resolution with network symbol *
server shares in the symbol path may cause the debugger to *
appear to hang for long periods of time when an incorrect *
symbol name is typed or the network symbol server is down. *
*
for some commands to work properly, your symbol path *
must point to .pdb files that have Full type information. *
*
certain .pdb files (such as the public OS symbols) do not *
contain the required information. Contact the group that *
provided you with these symbols if you need this command to *
work. *
*
type referenced: NT!_kprcb *
*

*************************************************************************

Key_values_strıng: 1

Key : Analysis.CPU.msec
Value: 30.

Key : Analysis.elapsed.msec
Value: 32.

Key : Analysis.I

ther.MB
Value: 0

Key : Analysis.IO.read.MB
Value: 0

Key : Analysis.IO.write.MB
Value: 0

Key : Analysis.ınit.CPU.msec
Value: 109.

Key : Analysis.ınit.elapsed.msec
Value: 8063.

Key : Analysis.Memory.commitpeak.MB
Value: 102.

Key : Bugcheck.code.legacyapı
Value: 0x20001.

Key : Bugcheck.code.targetmodel
Value: 0x20001.

Key : Dump.attributes.asulong
Value: 808.

Key : Dump.attributes.kernelgeneratedtriagedump
Value: 1

Key : Failure.bucket
Value: Wrong_symbols_X64_TIMestamP_090628-151711_4A478977_nt_wrong_symbols!4A4789771047000

Key : Failure.hash
Value: {B3C68284-4B26-10C9-76A2-A72eecb650A4}

Bugcheck_code: 20001.

Bugcheck_p1: 11.

Bugcheck_p2: 2F60D0.

Bugcheck_p3: 1003.

Bugcheck_p4: FFFFE70001405C40.

Fıle_ın_cab: 032424-11734-01.dmp

Addıtıonal_debug_text:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

Wrong_symbols_tımestamp: 4A478977.

Wrong_symbols_sıze: 1047000.

Faultıng_module: FFFFF80712000000 NT.

Dump_fıle_attrıbutes: 0x808.
Kernel generated triage dump.

Customer_crash_count: 1

Stack_text:
Ffffd001'DD5dbca8 fffff807'12545311 : 00000000'00020001 00000000'00000011 00000000'002F60D0 00000000'00001003 : NT+0x4177F0
Ffffd001'DD5dbcb0 00000000'00020001 : 00000000'00000011 00000000'002F60D0 00000000'00001003 ffffe700'01405C40 : NT+0x545311
Ffffd001'DD5dbcb8 00000000'00000011 : 00000000'002F60D0 00000000'00001003 ffffe700'01405C40 00000000'00000082 : 0x20001.
Ffffd001'DD5dbcc0 00000000'002F60D0 : 00000000'00001003 ffffe700'01405C40 00000000'00000082 ffffad87'6188E540 : 0x11.
Ffffd001'DD5dbcc8 00000000'00001003 : Ffffe700'01405C40 00000000'00000082 ffffad87'6188E540 fffff807'1249A390 : 0x2f60d0.
Ffffd001'DD5dbcd0 ffffe700'01405C40 : 00000000'00000082 ffffad87'6188E540 fffff807'1249A390 00000000'00000100 : 0x1003.
Ffffd001'DD5dbcd8 00000000'00000082 : Ffffad87'6188E540 fffff807'1249A390 00000000'00000100 fffff807'122b2D7C : 0xffffe700`01405c40
Ffffd001'DD5dbce0 ffffad87'6188E540 : Fffff807'1249A390 00000000'00000100 fffff807'122b2D7C ffffd001'DD5bc340 : 0x82.
Ffffd001'DD5dbce8 fffff807'1249A390 : 00000000'00000100 fffff807'122b2D7C ffffd001'DD5bc340 ffffd001'DD5DBD30 : 0xffffad87`6188e540
Ffffd001'DD5dbcf0 00000000'00000100 : Fffff807'122b2D7C ffffd001'DD5bc340 ffffd001'DD5DBD30 00000000'00000000 : NT+0x49A390
Ffffd001'DD5dbcf8 fffff807'122b2D7C : Ffffd001'DD5bc340 ffffd001'DD5DBD30 00000000'00000000 00000000'00000000 : 0x100.
Ffffd001'DD5DBD00 ffffd001'DD5bc340 : Ffffd001'DD5DBD30 00000000'00000000 00000000'00000000 00000000'00000000 : NT+0x2b2D7C
Ffffd001'DD5DBD08 ffffd001'DD5DBD30 : 00000000'00000000 00000000'00000000 00000000'00000000 fffff807'12425742 : 0xffffd001`dd5bc340
Ffffd001'DD5DBD10 00000000'00000000 : 00000000'00000000 00000000'00000000 fffff807'12425742 00000000'00000100 : 0xffffd001`dd5dbd30

Stack_command: .cxr; .ecxr ; KB.

Exceptıon_code_str: 4A478977.

Exceptıon_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!4A4789771047000

Faılure_bucket_ıd: Wrong_symbols_X64_TIMestamP_090628-151711_4A478977_nt_wrong_symbols!4A4789771047000

Osplatform_type: X64.

Osname: Windows 10.

Faılure_ıd_hash: {B3C68284-4B26-10C9-76A2-A72eecb650A4}

Followup: Machineowner.
---------

Spyhis · 25 Mart 2024

Bu sorunun çözümü için sembolleri tekrardan yüklemen gerekli. Sympath , .Symfix gibi komutlar var ama kesin çözüm direkt olarak yüklemek.
WinDbg üzerinden yüklemek için komut yerine yazman gerek.

Kod:

.sympath cache*C:\MySymbols;srv*https://msdl.microsoft.com/download/symbols

Veya direkt olarak symbol erişim kutusuna bunu yazabilirsin.

Kod:

cache*C:\MySymbols;srv*https://msdl.microsoft.com/download/symbols

Symbols for Windows Debugging - Windows drivers

Symbols for the Windows debuggers (WinDbg, KD, CDB, and NTSD) are available from a public symbol server.

learn.microsoft.com

Symbol Path for Windows Debuggers - Windows drivers

Learn how the symbol path specifies locations where Windows debuggers, such as WinDbg, KD, CDB, and NTST, look for symbol files.

learn.microsoft.com

WinDbg sürekli nt_wrong_symbols hatası veriyor

Ayrıntılı düzenleme

VENGEANCE ANGEL

Kilopat

Spyhis

Kilopat

Symbols for Windows Debugging - Windows drivers

Symbol Path for Windows Debuggers - Windows drivers

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz