Çözüldü WinDbg Sürekli NT_WRONG_SYMBOLS Hatası Veriyor

VENGEANCE ANGEL · 24 Mart 2024

Herkese merhabalar.
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.
@bicy

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, 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...

Küçültmek için tıkla...

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds

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

Küçültmek için tıkla...

----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, 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
*** WARNING: 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
*** WARNING: 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:
------------------

*** WARNING: 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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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!_IMAGE_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_STRING: 1

Key : Analysis.CPU.mSec
Value: 30

Key : Analysis.Elapsed.mSec
Value: 32

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: 109

Key : Analysis.Init.Elapsed.mSec
Value: 8063

Key : Analysis.Memory.CommitPeak.Mb
Value: 102

Key : Bugcheck.Code.LegacyAPI
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

FILE_IN_CAB: 032424-11734-01.dmp

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 4a478977

WRONG_SYMBOLS_SIZE: 1047000

FAULTING_MODULE: fffff80712000000 nt

DUMP_FILE_ATTRIBUTES: 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

EXCEPTION_CODE_STR: 4A478977

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!4A4789771047000

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_TIMESTAMP_090628-151711_4A478977_nt_wrong_symbols!4A4789771047000

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b3c68284-4b26-10c9-76a2-a72eecb650a4}

Followup: MachineOwner
---------

bicy · 24 Mart 2024

Windbg>Settings>Debugging settings>Symbol path kutusuna cache*C:\MySymbols;srv*https://msdl.microsoft.com/download/symbols yapıştırıp dener misin bir tekrardan?

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

VENGEANCE ANGEL · 24 Mart 2024

bicy dedi:
Windbg>Settings>Debugging settings>Symbol path kutusuna cache*C:\MySymbols;srv*https://msdl.microsoft.com/download/symbols yapıştırıp dener misin bir tekrardan?

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

Ban yemeyeceğimi bilsem, teşekkür etmek amaçlı çok şey söylemek isterdim. Teşekkür ederim. İyi akşamlar.

Çözüldü WinDbg Sürekli NT_WRONG_SYMBOLS Hatası Veriyor

Detaylar

VENGEANCE ANGEL

Üstün

bicy

Symbol Path for Windows Debuggers - Windows drivers

bicy

Mavi Ekran Destek

Symbol Path for Windows Debuggers - Windows drivers

VENGEANCE ANGEL

Üstün

Symbol Path for Windows Debuggers - Windows drivers

Benzer konular

Yeni konular

Yeni mesajlar