Çözüldü Bilgisayar durduk yere siyah ekran verdi ve yeniden başladı

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

Guneyxz

Becerikli
Katılım
19 Temmuz 2025
Mesajlar
256
Çözümler
2
Beğeniler
88
Yer
Antalya/Finike
Merhaba bilgisayarım ders çalışırken(arkada oyun indiriyordum) bir anda siyah ekran verdi. Üstünde "Your device ran into(devamını okuyamadım)" yazıyordu ve restart attı. Hiçbir şey olmamış gibi devam etti. Sizce incelemem gereken bir sorun mu, yoksa klasik AMD sürücüleri deyip geçmem mi lazım? Yardımcı olacaklara teşekkürler.
 
Çözüm
2
KERNEL_SECURITY_CHECK_FAILURE (139) hatası almışsın.
Sorunu analiz etmeye devam ediyorum. WinDBG analizi böyle:
Kod: 
************* 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.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Users\Valerian\Desktop\010126-13046-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 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff803`b7c00000 PsLoadedModuleList = 0xfffff803`b8af5010
Debug session time: Thu Jan  1 21:22:31.284 2026 (UTC + 3:00)
System Uptime: 2 days 1:44:47.132
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ac`97c39018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...............................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`b80fb310 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff803`4a6dfab0=0000000000000139
0: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ac`97c39018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...............................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 000000000000000a, Indirect call guard check detected invalid control transfer.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2500

    Key  : Analysis.Elapsed.mSec
    Value: 8438

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Bugcheck.Code.TargetModel
    Value: 0x139

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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: 0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck

    Key  : Failure.Hash
    Value: {391a5384-38fb-03d6-baa8-4a74bc53c199}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

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

    Key  : WER.System.BIOSRevision
    Value: 5.35.0.0


BUGCHECK_CODE:  139

BUGCHECK_P1: a

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  010126-13046-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb484ad3f2080

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)
Resetting default scope

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

DPC_STACK_BASE:  FFFFF8034A6DFFB0

STACK_TEXT:
fffff803`4a6dfaa8 fffff803`b82ab11e     : 00000000`00000139 00000000`0000000a 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff803`4a6dfab0 fffff803`b7ed1212     : 00000000`00000008 fffff803`46b5e180 fffff803`00000000 00000000`00000004 : nt!guard_icall_bugcheck+0x1e
fffff803`4a6dfae0 fffff803`b7ece04e     : fffff803`4a6dfe20 ffffb484`0000000f 00000070`1dab7465 ffffb484`ad3f2080 : nt!KiExecuteAllDpcs+0x692
fffff803`4a6dfd20 fffff803`b82a9e05     : 00000000`00000000 fffff803`46b5e180 ffffb484`ad3f2080 ffffb484`7c36e050 : nt!KiRetireDpcList+0x43e
fffff803`4a6dffb0 fffff803`b82a9daf     : ffffd689`2a4cba60 fffff803`b7ebb865 ffffffff`ffffff87 fffff803`b82a95d2 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffd689`2a4cb970 fffff803`b7ebb865     : ffffffff`ffffff87 fffff803`b82a95d2 00000000`01000010 00000000`00000282 : nt!KiPlatformSwapStacksAndCallReturn
ffffd689`2a4cb980 fffff803`b82a95db     : ffffb484`7821d070 ffffb484`7c36e050 ffffb484`7c36e001 ffffb484`7c36e050 : nt!KiDispatchInterrupt+0x65
ffffd689`2a4cb9b0 fffff803`b82a4274     : 000001a0`fc19addb ffffd689`2a4cba60 000001a0`fc19aec5 000269d2`5273d87b : nt!KiDpcInterruptBypass+0x1b
ffffd689`2a4cb9e0 fffff803`b8055e12     : fffff803`95516b44 00000000`00000003 00000000`00000058 00000000`45303130 : nt!KiInterruptDispatch+0x64
ffffd689`2a4cbb78 fffff803`95516b44     : 00000000`00000003 00000000`00000058 00000000`45303130 fffffa45`7dd317b0 : nt!KeInitializeDpc+0x2
ffffd689`2a4cbb80 00000000`00000003     : 00000000`00000058 00000000`45303130 fffffa45`7dd317b0 ffffb484`7c36e050 : amdkmdag+0x4f6b44
ffffd689`2a4cbb88 00000000`00000058     : 00000000`45303130 fffffa45`7dd317b0 ffffb484`7c36e050 fffff803`955b7a34 : 0x3
ffffd689`2a4cbb90 00000000`45303130     : fffffa45`7dd317b0 ffffb484`7c36e050 fffff803`955b7a34 ffffb484`7c36e001 : 0x58
ffffd689`2a4cbb98 fffffa45`7dd317b0     : ffffb484`7c36e050 fffff803`955b7a34 ffffb484`7c36e001 ffffb484`7c36e000 : 0x45303130
ffffd689`2a4cbba0 ffffb484`7c36e050     : fffff803`955b7a34 ffffb484`7c36e001 ffffb484`7c36e000 00000000`00000001 : 0xfffffa45`7dd317b0
ffffd689`2a4cbba8 fffff803`955b7a34     : ffffb484`7c36e001 ffffb484`7c36e000 00000000`00000001 00000000`00000000 : 0xffffb484`7c36e050
ffffd689`2a4cbbb0 ffffb484`7c36e001     : ffffb484`7c36e000 00000000`00000001 00000000`00000000 00000000`00000000 : amdkmdag+0x597a34
ffffd689`2a4cbbb8 ffffb484`7c36e000     : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffb484`7c36e001
ffffd689`2a4cbbc0 00000000`00000001     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : 0xffffb484`7c36e000
ffffd689`2a4cbbc8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : 0x1


SYMBOL_NAME:  nt!guard_icall_bugcheck+1e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.7462

STACK_COMMAND: .process /r /p 0xffffb484a099a080; .thread 0xffffb484ad3f2080 ; kb

BUCKET_ID_FUNC_OFFSET:  1e

FAILURE_BUCKET_ID:  0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {391a5384-38fb-03d6-baa8-4a74bc53c199}

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

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

*** WARNING: Unable to verify timestamp for amdkmdag.sys

amdkmdag.sys AMD marka ekran kartlarının sürücüsüdür. Ekran kartına Overclock yaptıysan iptal et. Sürücüyü DDU ile kaldırıp yeniden yükle. @Guneyxz
Tarihe göre sırala Puana göre sırala
"C:\Windows\Minidump" konumunda .dmp uzantılı dosya var mı?
 
Artı 0 Eksi
Guneyxz dedi:
Var hocam.
Genişletmek için tıkla...

Rehber Konu 'Minidump Dosyaları Nasıl Paylaşılır?'

Mavi ekran hatası aldığınızda DMP uzantılı Minidump dosyaları oluşur. Bu mini bellek döküm dosyalarının analiziyle mavi ekran hatalarının sebebi genelde tespit edilebilir.

Dosyaları paylaşmak için C:\Windows\Minidump dizinine gidip buradaki dosyaları kopyalayın. Sonrasında ister doğrudan masaüstüne, ister masaüstündeki bir klasöre yapıştırın ve yapıştırdığınız dosyalara sağ tıklayıp "ZIP dosyasına sıkıştır" seçeneğini seçin.

Bu aşamadan sonra oluşan ZIP dosyasını güvenilir bir dosya paylaşım servisi aracılığıyla paylaşabilirsiniz. Birkaç popüler servis:
 
Artı 0 Eksi
Dosyaya erişim izni vermelisin. Google Drive'a gir, dosyaya sağ tıklayıp "Paylaş" seçeneğini seç.
Çıkan pencerede "Bağlantıyı bilen herkes olarak değiştir" seçeneğini seç.

 
Artı 0 Eksi
Artı 0 Eksi
KERNEL_SECURITY_CHECK_FAILURE (139) hatası almışsın.
Sorunu analiz etmeye devam ediyorum. WinDBG analizi böyle:
Kod: 
************* 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.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Users\Valerian\Desktop\010126-13046-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 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff803`b7c00000 PsLoadedModuleList = 0xfffff803`b8af5010
Debug session time: Thu Jan  1 21:22:31.284 2026 (UTC + 3:00)
System Uptime: 2 days 1:44:47.132
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ac`97c39018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...............................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`b80fb310 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff803`4a6dfab0=0000000000000139
0: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ac`97c39018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...............................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 000000000000000a, Indirect call guard check detected invalid control transfer.
Arg2: 0000000000000000, Address of the trap frame for the exception that caused the BugCheck
Arg3: 0000000000000000, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2500

    Key  : Analysis.Elapsed.mSec
    Value: 8438

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Bugcheck.Code.TargetModel
    Value: 0x139

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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: 0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck

    Key  : Failure.Hash
    Value: {391a5384-38fb-03d6-baa8-4a74bc53c199}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

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

    Key  : WER.System.BIOSRevision
    Value: 5.35.0.0


BUGCHECK_CODE:  139

BUGCHECK_P1: a

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  010126-13046-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb484ad3f2080

TRAP_FRAME:  0000000000000000 -- (.trap 0x0)
Resetting default scope

EXCEPTION_RECORD:  0000000000000000 -- (.exr 0x0)
Cannot read Exception record @ 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

DPC_STACK_BASE:  FFFFF8034A6DFFB0

STACK_TEXT:
fffff803`4a6dfaa8 fffff803`b82ab11e     : 00000000`00000139 00000000`0000000a 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff803`4a6dfab0 fffff803`b7ed1212     : 00000000`00000008 fffff803`46b5e180 fffff803`00000000 00000000`00000004 : nt!guard_icall_bugcheck+0x1e
fffff803`4a6dfae0 fffff803`b7ece04e     : fffff803`4a6dfe20 ffffb484`0000000f 00000070`1dab7465 ffffb484`ad3f2080 : nt!KiExecuteAllDpcs+0x692
fffff803`4a6dfd20 fffff803`b82a9e05     : 00000000`00000000 fffff803`46b5e180 ffffb484`ad3f2080 ffffb484`7c36e050 : nt!KiRetireDpcList+0x43e
fffff803`4a6dffb0 fffff803`b82a9daf     : ffffd689`2a4cba60 fffff803`b7ebb865 ffffffff`ffffff87 fffff803`b82a95d2 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffd689`2a4cb970 fffff803`b7ebb865     : ffffffff`ffffff87 fffff803`b82a95d2 00000000`01000010 00000000`00000282 : nt!KiPlatformSwapStacksAndCallReturn
ffffd689`2a4cb980 fffff803`b82a95db     : ffffb484`7821d070 ffffb484`7c36e050 ffffb484`7c36e001 ffffb484`7c36e050 : nt!KiDispatchInterrupt+0x65
ffffd689`2a4cb9b0 fffff803`b82a4274     : 000001a0`fc19addb ffffd689`2a4cba60 000001a0`fc19aec5 000269d2`5273d87b : nt!KiDpcInterruptBypass+0x1b
ffffd689`2a4cb9e0 fffff803`b8055e12     : fffff803`95516b44 00000000`00000003 00000000`00000058 00000000`45303130 : nt!KiInterruptDispatch+0x64
ffffd689`2a4cbb78 fffff803`95516b44     : 00000000`00000003 00000000`00000058 00000000`45303130 fffffa45`7dd317b0 : nt!KeInitializeDpc+0x2
ffffd689`2a4cbb80 00000000`00000003     : 00000000`00000058 00000000`45303130 fffffa45`7dd317b0 ffffb484`7c36e050 : amdkmdag+0x4f6b44
ffffd689`2a4cbb88 00000000`00000058     : 00000000`45303130 fffffa45`7dd317b0 ffffb484`7c36e050 fffff803`955b7a34 : 0x3
ffffd689`2a4cbb90 00000000`45303130     : fffffa45`7dd317b0 ffffb484`7c36e050 fffff803`955b7a34 ffffb484`7c36e001 : 0x58
ffffd689`2a4cbb98 fffffa45`7dd317b0     : ffffb484`7c36e050 fffff803`955b7a34 ffffb484`7c36e001 ffffb484`7c36e000 : 0x45303130
ffffd689`2a4cbba0 ffffb484`7c36e050     : fffff803`955b7a34 ffffb484`7c36e001 ffffb484`7c36e000 00000000`00000001 : 0xfffffa45`7dd317b0
ffffd689`2a4cbba8 fffff803`955b7a34     : ffffb484`7c36e001 ffffb484`7c36e000 00000000`00000001 00000000`00000000 : 0xffffb484`7c36e050
ffffd689`2a4cbbb0 ffffb484`7c36e001     : ffffb484`7c36e000 00000000`00000001 00000000`00000000 00000000`00000000 : amdkmdag+0x597a34
ffffd689`2a4cbbb8 ffffb484`7c36e000     : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffb484`7c36e001
ffffd689`2a4cbbc0 00000000`00000001     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : 0xffffb484`7c36e000
ffffd689`2a4cbbc8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : 0x1


SYMBOL_NAME:  nt!guard_icall_bugcheck+1e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.7462

STACK_COMMAND: .process /r /p 0xffffb484a099a080; .thread 0xffffb484ad3f2080 ; kb

BUCKET_ID_FUNC_OFFSET:  1e

FAILURE_BUCKET_ID:  0x139_a_GUARD_ICALL_CHECK_FAILURE_nt!guard_icall_bugcheck

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {391a5384-38fb-03d6-baa8-4a74bc53c199}

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

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

*** WARNING: Unable to verify timestamp for amdkmdag.sys

amdkmdag.sys AMD marka ekran kartlarının sürücüsüdür. Ekran kartına Overclock yaptıysan iptal et. Sürücüyü DDU ile kaldırıp yeniden yükle. @Guneyxz
 
Son düzenleme:
Artı 0 Eksi
Çözüm

Sağ olun hocam overclock yapmamıştım sürücüyü silip yükleyeyim.
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

D
  • Soru Soru
R5 5500 & Arc B580 sistemi yeniden başlatınca siyah ekran kalıyor
Mesaj
7
Görüntüleme
113
theodore bagwell
B
  • Soru Soru
Bilgisayar açıldıktan sonra siyah ekran verdi ve CMD açıldı
Mesaj
2
Görüntüleme
110
BatuhanDN
B
  • Soru Soru
Google ve Discord'ta anlık siyah ekran sorunu
Mesaj
4
Görüntüleme
80
efebatiin
  • Soru Soru
ASUS Prime H610M-A sistemde ağır yükte siyah ekran ve M.2 SSD'nin BIOS'ta kaybolması
Mesaj
2
Görüntüleme
75
Payzer
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…