RTX 3060 Ti sistem kendi kendine restart atıyor

BannedForLive

Decapat
Katılım
23 Nisan 2023
Mesajlar
36
Daha fazla  
Sistem Özellikleri
AMD Ryzen 5 7600X, Asus Dual RTX 3060 Tİ, XPG Lancer 32 GB RAM, Asus Rog Strix B650-A Gaming Wifi Anakart, Arctic Liquid Freezer III 360mm Sıvı Soğutucu
Cinsiyet
Erkek
Minidump Rapor Linki
https://drive.google.com/file/d/19sze5UObWx060cq7YrjMNTuBBQGwAgvM/view?usp=sharing
RAM
XPG Lancer 32 GB (2X16) 5600MHz CL36 Ram
SSD veya HDD modeli
Adata Legend 850 1TB Okuma (5000MB) Yazma (3200MB)
Ekran kartı
Asus Dual RTX 3060 Ti GDDR6X 8 GB
Anakart
Asus Rog Strix B650-A Gaming WiFi
İşlemci
Ryzen 5 7600X
Merhaba direkt konuya gireceğim. Son birkaç haftadır bilgisayar oyun oynarken ya da Google'da takılırken hatta masaüstünde boştayken bile kendi kendine birden restart atıyor, ancak herhangi bir hata vermiyor. Birden görüntü gidiyor ama kasa ışıkları yanmaya devam ediyor. Daha sonra tekrar açılıyor, hiçbir şey olmamış gibi. Bu tamamen rastgele bir zamanda oluyor bazen PC açıldıktan 10 dakika sonra bazen oyundayken 1-2 saatlik kullanımda bazense 3-5 saatlik kullanımda. Umarım yardımcı olabilirsiniz minidump dosyaları: Yeni klasör.rar
 
Son düzenleyen: Moderatör:
Güç kaynağında sorun olabilir veya RAM'in 1 tanesini çıkar ve öyle kullan dene.
Psumu yeni değiştirdim,kaliteli bir psuya geçtim. sorunum düzelmedi, o yüzden konu açtım minidump dosyası paylaştım. sistemim yeni ve güncel bundan dolayı minidump dosyası okuyabilecek biri lazım.
 
Format at atabiliyorsan bende de oluyordu ama benimki kendi kendine düzeldi istiyorsan bekle düzelmezse format at.

1) Öncelikle eski bir Windows sürümünü kullanıyorsunuz, lütfen Windows Update aracılığıyla daha iyi sürümlere geçiş yapın.

2) SteelSeries Engine kaldırın.

3) Ekran kartı sürücünüzü DDU ile kaldırıp güncel ve WHQL logolu bir sürücü indirin. DDU rehberi ve sürücüyü indireceğiniz website aşağıda yer alıyor.

Site: https://www.amd.com/en/support

Rehber: DDU ile Sürücü Kaldırma Rehberi

ilk minidump:

Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\serve\AppData\Local\Temp\Rar$DIa16824.5269.rartemp\080524-17734-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff802`6de00000 PsLoadedModuleList = 0xfffff802`6ea13510
Debug session time: Mon Aug 5 05:30:02.361 2024 (UTC + 3:00)
System Uptime: 0 days 11:33:00.122
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`6e215df0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff802`6a65a580=00000000000000b8
0: kd> !analyze -v
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: ffffad897ab43080, Original thread which is the cause of the failure
Arg2: fffff8026eb4c700, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 14296

Key : Analysis.Elapsed.mSec
Value: 26809

Key : Analysis.IO.Other.Mb
Value: 22

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 32

Key : Analysis.Init.CPU.mSec
Value: 3624

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xb8

Key : Bugcheck.Code.TargetModel
Value: 0xb8

Key : Dump.Attributes.AsUlong
Value: 1808

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: 0xB8_nt!SwapContext

Key : Failure.Hash
Value: {7aaf43d6-72cc-fa8c-17fb-e140c3359586}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7


BUGCHECK_CODE: b8

BUGCHECK_P1: ffffad897ab43080

BUGCHECK_P2: fffff8026eb4c700

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 080524-17734-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffad897ab43080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff802`6a65a578 fffff802`6e21fde6 : 00000000`000000b8 ffffad89`7ab43080 fffff802`6eb4c700 00000000`00000000 : nt!KeBugCheckEx
fffff802`6a65a580 fffff802`6e21aed6 : 00000000`00000000 fffff802`6eb4c700 ffffad89`81e5a080 ffffad89`81e5c080 : nt!SwapContext+0x686
fffff802`6a65a5c0 00000000`00000000 : fffff802`6a65b000 fffff802`6a654000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x176


SYMBOL_NAME: nt!SwapContext+686

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3880

STACK_COMMAND: .process /r /p 0xffffad8981a9a0c0; .thread 0xffffad897ab43080 ; kb

BUCKET_ID_FUNC_OFFSET: 686

FAILURE_BUCKET_ID: 0xB8_nt!SwapContext

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7aaf43d6-72cc-fa8c-17fb-e140c3359586}

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

@Enes3078 e teşekkürler

2. minidump

Microsoft (R) Windows Debugger Version 10.0.27668.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\serve\AppData\Local\Temp\Rar$DIa16824.5624.rartemp\082624-18531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff807`6a000000 PsLoadedModuleList = 0xfffff807`6ac134f0
Debug session time: Mon Aug 26 23:03:14.991 2024 (UTC + 3:00)
System Uptime: 0 days 7:36:29.752
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols

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+0x415cb0:
fffff807`6a415cb0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff807`68b73810=0000000000000044
0: kd> !analyze -v
*******************************************************************************
  • *
  • Bugcheck Analysis *
  • *
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffcd0544586010, Address of the IRP
Arg2: 0000000000001347
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

***** 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!_KTHREAD *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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!_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 *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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!_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!_IRP *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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 *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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!_KTHREAD *
  • *

*************************************************************************
*************************************************************************
* *
  • *
  • 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: 171

Key : Analysis.Elapsed.mSec
Value: 330

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x44

Key : Bugcheck.Code.TargetModel
Value: 0x44

Key : Dump.Attributes.AsUlong
Value: 1808

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_061231-102850_459790E2_nt_wrong_symbols!459790E21047000

Key : Failure.Hash
Value: {fad5c093-05e3-b17b-68bb-a8907382b72a}


BUGCHECK_CODE: 44

BUGCHECK_P1: ffffcd0544586010

BUGCHECK_P2: 1347

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 082624-18531-01.dmp

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

WRONG_SYMBOLS_TIMESTAMP: 459790e2

WRONG_SYMBOLS_SIZE: 1047000

FAULTING_MODULE: fffff8076a000000 nt

DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD: fffff8076ad4c700

IRP_ADDRESS: ffffcd0544586010

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
fffff807`68b73808 fffff807`6a441f57 : 00000000`00000044 ffffcd05`44586010 00000000`00001347 00000000`00000000 : nt+0x415cb0
fffff807`68b73810 00000000`00000044 : ffffcd05`44586010 00000000`00001347 00000000`00000000 00000000`00000000 : nt+0x441f57
fffff807`68b73818 ffffcd05`44586010 : 00000000`00001347 00000000`00000000 00000000`00000000 ffffcd05`35f70000 : 0x44
fffff807`68b73820 00000000`00001347 : 00000000`00000000 00000000`00000000 ffffcd05`35f70000 00000000`00000000 : 0xffffcd05`44586010
fffff807`68b73828 00000000`00000000 : 00000000`00000000 ffffcd05`35f70000 00000000`00000000 00000000`00000000 : 0x1347


STACK_COMMAND: .thread /r /p 0xfffff8076ad4c700 ; kb

EXCEPTION_CODE_STR: 459790E2

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!459790E21047000

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_TIMESTAMP_061231-102850_459790E2_nt_wrong_symbols!459790E21047000

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fad5c093-05e3-b17b-68bb-a8907382b72a}

Followup: MachineOwner
---------
 
Son düzenleme:

Windows'um BIOS'um ekran kartım sürücülerim hepsi şu anda güncel. Son Minidump'a bakabilir misiniz 28 Ağustos tarihli. Ayrıca SteelSeries Engine klavyem için kullanmam gerekiyor neden kaldırmam gerektiğini anlamadım. Hem de ben AMD ekran kartı kullanmıyorum.
 
Son düzenleme:
Son düzenleme:
Olur bakarım
 
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…