Sistem düzgün kapatılmadan yeniden başlatılmış. Bu hatanın nedeni sistemin yanıt vermeyi durdurması, kilitlenmesi veya beklenmeyen bir şekilde güç kaybına uğramış olması olabilir. Bunun çözümü nedir bilen var mıdır acaba ?

Question

Sistem düzgün kapatılmadan yeniden başlatılmış. Bu hatanın nedeni sistemin yanıt vermeyi durdurması, kilitlenmesi veya beklenmeyen bir şekilde güç kaybına uğramış olması olabilir. Bunun çözümü nedir bilen var mıdır acaba ?

mustafa deniz 20

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

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

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

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 44

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


Loading Dump File [C:\Windows\Minidump\072125-20484-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: 
Windows 10 Kernel Version 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`a6800000 PsLoadedModuleList = 0xfffff800`a76f4b80
Debug session time: Mon Jul 21 03:08:21.103 2025 (UTC + 3:00)
System Uptime: 0 days 4:15:53.862
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`04f97018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`a6d00450 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffda81`170b5070=00000000000000f7
21: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`04f97018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.................

************* Symbol Loading Error Summary **************
Module name            Error
nvlddmkm               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.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer.  This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned.  This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and BugCheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 000017647f141adf, Actual security check cookie from the stack
Arg2: 000017647f141aa7, Expected security check cookie
Arg3: ffffe89b80ebe558, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 890

    Key  : Analysis.Elapsed.mSec
    Value: 1657

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xf7

    Key  : Bugcheck.Code.TargetModel
    Value: 0xf7

    Key  : Dump.Attributes.AsUlong
    Value: 0x31808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0xF7_MISSING_GSFRAME_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {2ffeac14-357b-96a5-98b2-2e606f12e8c0}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    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: 0x3f7

    Key  : Stack.Pointer
    Value: PRCBException


BUGCHECK_CODE:  f7

BUGCHECK_P1: 17647f141adf

BUGCHECK_P2: 17647f141aa7

BUGCHECK_P3: ffffe89b80ebe558

BUGCHECK_P4: 0

FILE_IN_CAB:  072125-20484-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x31808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa40815e38080

SECURITY_COOKIE:  Expected 000017647f141aa7 found 000017647f141adf

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  metin2client.e

STACK_TEXT:  
ffffda81`170b5068 fffff800`6c3b1a67     : 00000000`000000f7 fffffd8a`65e76639 00001764`7f141aa7 ffffe89b`80ebe558 : nt!KeBugCheckEx
ffffda81`170b5070 00000000`000000f7     : fffffd8a`65e76639 00001764`7f141aa7 ffffe89b`80ebe558 00000000`00000000 : nvlddmkm+0xd1a67
ffffda81`170b5078 fffffd8a`65e76639     : 00001764`7f141aa7 ffffe89b`80ebe558 00000000`00000000 fffff800`6d6778fc : 0xf7
ffffda81`170b5080 00001764`7f141aa7     : ffffe89b`80ebe558 00000000`00000000 fffff800`6d6778fc ffffda81`170b51a0 : 0xfffffd8a`65e76639
ffffda81`170b5088 ffffe89b`80ebe558     : 00000000`00000000 fffff800`6d6778fc ffffda81`170b51a0 fffff800`6c3ac7fa : 0x00001764`7f141aa7
ffffda81`170b5090 00000000`00000000     : fffff800`6d6778fc ffffda81`170b51a0 fffff800`6c3ac7fa ffffda81`170b5158 : 0xffffe89b`80ebe558


SYMBOL_NAME:  nvlddmkm+d1a67

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffa40818131080; .thread 0xffffa40815e38080 ; kb

BUCKET_ID_FUNC_OFFSET:  d1a67

FAILURE_BUCKET_ID:  0xF7_MISSING_GSFRAME_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2ffeac14-357b-96a5-98b2-2e606f12e8c0}

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

21: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer.  This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned.  This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and BugCheck call is the one that overran its local
variable(s).
Arguments:
Arg1: 000017647f141adf, Actual security check cookie from the stack
Arg2: 000017647f141aa7, Expected security check cookie
Arg3: ffffe89b80ebe558, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 812

    Key  : Analysis.Elapsed.mSec
    Value: 832

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xf7

    Key  : Bugcheck.Code.TargetModel
    Value: 0xf7

    Key  : Dump.Attributes.AsUlong
    Value: 0x31808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0xF7_MISSING_GSFRAME_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {2ffeac14-357b-96a5-98b2-2e606f12e8c0}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    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: 0x3f7

    Key  : Stack.Pointer
    Value: PRCBException


BUGCHECK_CODE:  f7

BUGCHECK_P1: 17647f141adf

BUGCHECK_P2: 17647f141aa7

BUGCHECK_P3: ffffe89b80ebe558

BUGCHECK_P4: 0

FILE_IN_CAB:  072125-20484-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x31808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa40815e38080

SECURITY_COOKIE:  Expected 000017647f141aa7 found 000017647f141adf

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  metin2client.e

STACK_TEXT:  
ffffda81`170b5068 fffff800`6c3b1a67     : 00000000`000000f7 fffffd8a`65e76639 00001764`7f141aa7 ffffe89b`80ebe558 : nt!KeBugCheckEx
ffffda81`170b5070 00000000`000000f7     : fffffd8a`65e76639 00001764`7f141aa7 ffffe89b`80ebe558 00000000`00000000 : nvlddmkm+0xd1a67
ffffda81`170b5078 fffffd8a`65e76639     : 00001764`7f141aa7 ffffe89b`80ebe558 00000000`00000000 fffff800`6d6778fc : 0xf7
ffffda81`170b5080 00001764`7f141aa7     : ffffe89b`80ebe558 00000000`00000000 fffff800`6d6778fc ffffda81`170b51a0 : 0xfffffd8a`65e76639
ffffda81`170b5088 ffffe89b`80ebe558     : 00000000`00000000 fffff800`6d6778fc ffffda81`170b51a0 fffff800`6c3ac7fa : 0x00001764`7f141aa7
ffffda81`170b5090 00000000`00000000     : fffff800`6d6778fc ffffda81`170b51a0 fffff800`6c3ac7fa ffffda81`170b5158 : 0xffffe89b`80ebe558


SYMBOL_NAME:  nvlddmkm+d1a67

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffa40818131080; .thread 0xffffa40815e38080 ; kb

BUCKET_ID_FUNC_OFFSET:  d1a67

FAILURE_BUCKET_ID:  0xF7_MISSING_GSFRAME_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2ffeac14-357b-96a5-98b2-2e606f12e8c0}

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

mustafa deniz 20 Saygınlık puanı

2025-07-21T01:34:04.9133333+00:00

bu şekilde bir minidump hatası alıyorum bilgisayarım donuyor kendini yeniden başlatıyor 5 dk sonra metin2 16 pencerede açıyorum ve 30 dakika sonra donuyor kendiliğinden yeniden başlatıyor sebebi nedir.

Soru yazarı tarafından kabul edilen yanıt

0 ek yanıt

Yanıtınız

mustafa deniz 20 Saygınlık puanı

2025-07-21T01:34:04.9133333+00:00

bu şekilde bir minidump hatası alıyorum bilgisayarım donuyor kendini yeniden başlatıyor 5 dk sonra metin2 16 pencerede açıyorum ve 30 dakika sonra donuyor kendiliğinden yeniden başlatıyor sebebi nedir.

Answer 1

Merhaba, ben Bernard, bir Windows kullanıcısıyım. Yardım etmekten mutluluk duyarım!

Sahip olduğunuz DMP loglarını kontrol edip analiz ettikten sonra Nvidia ekran kartı sürücünüz olan nvlddmkm.sys bir hata oluşuyor. Sorunu çözebilmemiz için lütfen aşağıdaki adımları izleyin:

Nvidia sürücüsünün temiz bir kurulumunu çalıştıralım. Bu, DDU yapmaktan veya sürücüyü güncellemekten farklıdır, çünkü bu, tüm girişleri kaldıracak ve bunları uyumlu olanlarla değiştirecektir. Lütfen aşağıdaki bağlantıdan adımları izleyin:

https://nvidia.custhelp.com/app/answers/detail/a_id/10/~/geforce-experience-driver-installation-failed.-how-do-i-manually-clean-install#:~:text=%20How%20do%20I%20manually%20clean%20install%20the,installation%20process%2C%20close%20any%20programs%20which...%20More%20

Türkçe çeviri linki: https://translated.turbopages.org/proxy_u/en-tr.en.31502b9b-687d9f86-a2322a28-74722d776562/https/nvidia.custhelp.com/app/answers/detail/a_id/10/~/geforce-experience-driver-installation-failed.-how-do-i-manually-clean-install#:~:text=%20How%20do%20I%20manually%20clean%20install%20the,installation%20process%2C%20close%20any%20programs%20which...%20More%20

Not: Bu, Microsoft'a ait olmayan bir web sitesidir. Sayfanın doğru ve güvenli bilgiler sağladığı görülüyor. Sitede, sıklıkla PUP (Potansiyel Olarak İstenmeyen Ürünler) olarak sınıflandırılan ürünlerin reklamını yapabilecek reklamlara dikkat edin. İndirmeye ve kurmaya karar vermeden önce sitede reklamı yapılan herhangi bir ürünü iyice araştırın.

Ek not: Sorun devam ederse, GPU'yu çıkarmanızı ve mevcut başka bir PCIe bağlantı noktasına yerleştirmenizi öneririm (Masaüstü kullanıyorsanız veya harici GPU kullanıyorsanız başka bir bağlantı noktası kullanıyorsanız), ancak her şey başarısız olursa, donanımla ilgili herhangi bir sorun olup olmadığını fiziksel olarak kontrol etmek için yerel bir teknisyenle iletişime geçmenizi öneririm.

Nasıl gittiğini bana bildirin ve umarım bu yardımcı olur.

Aracılığıyla paylaş

Sistem düzgün kapatılmadan yeniden başlatılmış. Bu hatanın nedeni sistemin yanıt vermeyi durdurması, kilitlenmesi veya beklenmeyen bir şekilde güç kaybına uğramış olması olabilir. Bunun çözümü nedir bilen var mıdır acaba ?

0 ek yanıt

Yanıtınız