Servisten gelen bilgisayar mavi ekran veriyor

bariyilmaz8 · Bugün 11:14

Ürünümün ekranı kırıktı, serviste değişti. Geldikten sonra bazen mavi ekran vermeye başladı. Acaba yazılımsal mı donanımsal mı bakabilir miyiz?

061026-26390-01.dmp

drive.google.com

Hasan Merkit · Bugün 11:21

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.437 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Users\hasanmerkit\Downloads\061026-26390-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`dba00000 PsLoadedModuleList = 0xfffff804`dc8f52d0
Debug session time: Wed Jun 10 20:16:36.166 2026 (UTC + 3:00)
System Uptime: 22 days 5:20:20.203
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000db`6a251018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`dbef8450 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff978d`1d047100=000000000000000a
6: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000db`6a251018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff804dbc40d80, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3140

    Key  : Analysis.Elapsed.mSec
    Value: 4268

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    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: AV_nt!MiAcquirePageListLock

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff804dbc40d80

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x240d80

    Key  : Failure.Hash
    Value: {5dbc715e-ae10-58a3-9e00-eef195474437}

    Key  : Faulting.IP.Type
    Value: Paged

    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  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  a

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff804dbc40d80

FILE_IN_CAB:  061026-26390-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe78115720080

WRITE_ADDRESS: fffff804dc9c54d8: Unable to get MiVisibleState
 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  dwm.exe

IP_IN_PAGED_CODE:
nt!MiAcquirePageListLock+90
fffff804`dbc40d80 880b            mov     byte ptr [rbx],cl

STACK_TEXT:
ffff978d`1d0470f8 fffff804`dc0bcee9     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff978d`1d047100 fffff804`dc0b81a8     : ffff978d`1d047300 ffffe781`15631920 00000000`00000001 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff978d`1d047240 fffff804`dbc40d80     : 00000000`00000000 ffffe781`017dd000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x468
ffff978d`1d0473d0 fffff804`dbcf1707     : fffff804`dc839aa0 00000000`00000100 00000000`0085c6db 00000000`00000001 : nt!MiAcquirePageListLock+0x90
ffff978d`1d047460 fffff804`dbc48252     : 00000000`00000000 ffffaf80`03163230 ffff978d`1d047638 00000000`00000000 : nt!MiUnlinkPageFromListEx+0x1f7
ffff978d`1d047550 fffff804`dbc473f7     : 00000008`5c6db860 ffffc08e`da6ad290 00000000`00000000 00000000`00000000 : nt!MiHandleTransitionFault+0x122
ffff978d`1d0475e0 fffff804`dbceb28d     : fffff804`00000000 ffffc08e`da6ad290 00000000`00000003 00000000`00000000 : nt!MiResolveTransitionFault+0x177
ffff978d`1d0476a0 fffff804`dbce9bfc     : ffff978d`1d0477c0 00000000`00000000 ffff978d`1d047778 fffff97f`05560002 : nt!MiResolveProtoPteFault+0x64d
ffff978d`1d047740 fffff804`dbc43a76     : 00000000`00000000 ffff978d`00000100 00007fff`040c27f0 ffffc08e`da6ad290 : nt!MiDispatchFault+0x1fc
ffff978d`1d0478b0 fffff804`dc0b80cb     : ffffe781`15720080 000002bb`95144b00 00000000`8000ffff 000002bb`ab226800 : nt!MmAccessFault+0x226
ffff978d`1d047a20 00007fff`040c27f0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
000000db`6a67de88 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`040c27f0


SYMBOL_NAME:  nt!MiAcquirePageListLock+90

MODULE_NAME: nt

IMAGE_VERSION:  10.0.26100.8457

STACK_COMMAND: .process /r /p 0xffffe781155cc080; .thread /r /p 0xffffe78115720080 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  90

FAILURE_BUCKET_ID:  AV_nt!MiAcquirePageListLock

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5dbc715e-ae10-58a3-9e00-eef195474437}

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

Çöken işlem: dwm.exe
Birkaç olasılık var. RAM, GPU, sürücüler. Önce RAM testi yapmanızı tavsiye ederim.

bariyilmaz8 · Bugün 11:23

Minidump dosyasını hangi servis ile paylaşmam gerekir? İndirilip bakılması için. @Hasan Merkit

Hasan Merkit · Bugün 11:25

bariyilmaz8 dedi:
Minidump dosyasını hangi servis ile paylaşmam gerekir? İndirilip bakılması için.

Sonraki sefere bu konudaki servisleri tercih edin.

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

14 Aralık 2023

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:

Yandex...

İlk mesajınızı Google Drive linki ile güncelledim.

bariyilmaz8 · Bugün 11:29

Çok teşekkürler.

Hasan Merkit dedi:

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.437 seconds
 ----> Repository : UserExtensions, Enabled: true, Packages count: 0
 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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

Loading Dump File [C:\Users\hasanmerkit\Downloads\061026-26390-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff804`dba00000 PsLoadedModuleList = 0xfffff804`dc8f52d0
Debug session time: Wed Jun 10 20:16:36.166 2026 (UTC + 3:00)
System Uptime: 22 days 5:20:20.203
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000db`6a251018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`dbef8450 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff978d`1d047100=000000000000000a
6: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000db`6a251018). Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff804dbc40d80, address which referenced memory

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

KEY_VALUES_STRING: 1

 Key : Analysis.CPU.mSec
 Value: 3140

 Key : Analysis.Elapsed.mSec
 Value: 4268

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

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

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

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

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

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

 Key : Analysis.Version.DbgEng
 Value: 10.0.29547.1002

 Key : Analysis.Version.Description
 Value: 10.2602.27.2 amd64fre

 Key : Analysis.Version.Ext
 Value: 1.2602.27.2

 Key : Bugcheck.Code.LegacyAPI
 Value: 0xa

 Key : Bugcheck.Code.TargetModel
 Value: 0xa

 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: AV_nt!MiAcquirePageListLock

 Key : Failure.Exception.IP.Address
 Value: 0xfffff804dbc40d80

 Key : Failure.Exception.IP.Module
 Value: nt

 Key : Failure.Exception.IP.Offset
 Value: 0x240d80

 Key : Failure.Hash
 Value: {5dbc715e-ae10-58a3-9e00-eef195474437}

 Key : Faulting.IP.Type
 Value: Paged

 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 : WER.System.BIOSRevision
 Value: 5.27.0.0

BUGCHECK_CODE: a

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff804dbc40d80

FILE_IN_CAB: 061026-26390-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x21808
 Kernel Generated Triage Dump

FAULTING_THREAD: ffffe78115720080

WRITE_ADDRESS: fffff804dc9c54d8: Unable to get MiVisibleState
 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

IP_IN_PAGED_CODE:
nt!MiAcquirePageListLock+90
fffff804`dbc40d80 880b mov byte ptr [rbx],cl

STACK_TEXT:
ffff978d`1d0470f8 fffff804`dc0bcee9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff978d`1d047100 fffff804`dc0b81a8 : ffff978d`1d047300 ffffe781`15631920 00000000`00000001 00000000`00000001 : nt!KiBugCheckDispatch+0x69
ffff978d`1d047240 fffff804`dbc40d80 : 00000000`00000000 ffffe781`017dd000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x468
ffff978d`1d0473d0 fffff804`dbcf1707 : fffff804`dc839aa0 00000000`00000100 00000000`0085c6db 00000000`00000001 : nt!MiAcquirePageListLock+0x90
ffff978d`1d047460 fffff804`dbc48252 : 00000000`00000000 ffffaf80`03163230 ffff978d`1d047638 00000000`00000000 : nt!MiUnlinkPageFromListEx+0x1f7
ffff978d`1d047550 fffff804`dbc473f7 : 00000008`5c6db860 ffffc08e`da6ad290 00000000`00000000 00000000`00000000 : nt!MiHandleTransitionFault+0x122
ffff978d`1d0475e0 fffff804`dbceb28d : fffff804`00000000 ffffc08e`da6ad290 00000000`00000003 00000000`00000000 : nt!MiResolveTransitionFault+0x177
ffff978d`1d0476a0 fffff804`dbce9bfc : ffff978d`1d0477c0 00000000`00000000 ffff978d`1d047778 fffff97f`05560002 : nt!MiResolveProtoPteFault+0x64d
ffff978d`1d047740 fffff804`dbc43a76 : 00000000`00000000 ffff978d`00000100 00007fff`040c27f0 ffffc08e`da6ad290 : nt!MiDispatchFault+0x1fc
ffff978d`1d0478b0 fffff804`dc0b80cb : ffffe781`15720080 000002bb`95144b00 00000000`8000ffff 000002bb`ab226800 : nt!MmAccessFault+0x226
ffff978d`1d047a20 00007fff`040c27f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
000000db`6a67de88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`040c27f0

SYMBOL_NAME: nt!MiAcquirePageListLock+90

MODULE_NAME: nt

IMAGE_VERSION: 10.0.26100.8457

STACK_COMMAND: .process /r /p 0xffffe781155cc080; .thread /r /p 0xffffe78115720080 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 90

FAILURE_BUCKET_ID: AV_nt!MiAcquirePageListLock

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5dbc715e-ae10-58a3-9e00-eef195474437}

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

Çöken işlem: dwm.exe
Birkaç olasılık var. RAM, GPU, sürücüler. Önce RAM testi yapmanızı tavsiye ederim.

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

Dediklerinizi yapacağım birazdan. Duruma bakacağım tekrardan.

@Hasan Merkit Birde son bir soru olarak. Sürücülerden spesifik olarak belirli bir sürücü hatası görünüyor mu? RAM ile onları deneyeceğim çünkü. Ekran kartı haricinde.

Hasan Merkit · Bugün 11:51

bariyilmaz8 dedi:
Çok teşekkürler.

Dediklerinizi yapacağım birazdan. Duruma bakacağım tekrardan.

@Hasan Merkit Birde son bir soru olarak. Sürücülerden spesifik olarak belirli bir sürücü hatası görünüyor mu? RAM ile onları deneyeceğim çünkü. Ekran kartı haricinde.

Hayır, bu analizde özellikle bir sürücü söylemek zor. Ama dwm.exe genelde GPU yüzünden çökebiliyor.

bicy · 29 dakika önce

Rich (BB code):

xffff978d1d047858 : 0xfffff804dbcb06e2 : nt!KeLeaveCriticalRegion+0x12
0xffff978d1d0478a8 : 0xfffff804dbc43a76 : nt!MmAccessFault+0x226 // Bellek ?
0xffff978d1d0478e8 : 0xfffff8046dd1a01e : dxgkrnl!CCompositionFrameCollection::FindCompositionFrame+0x9e 
0xffff978d1d047a18 : 0xfffff804dc0b80cb : nt!KiPageFault+0x38b // sayfa hatası
0xffff978d1d047a20 : 0xffffe78115720080 :  Trap @ ffff978d1d047a20

Mantık güzel, ama dosya tam değil. Olay DWM içinde patlamış ki bu doğru ama stack'ler bomboş. Bunun 2 ihtimali olabilir: ya raw stack'te olduğu gibi sorun GPU'nun işaretlediğim kısmında olduğu gibi CCompositionFrameCollection içinden FindCompositionFrame seçerken +0x9e offsetinde bir şeye çarptı (dosyaya göre null adres erişimi) ve çöktü. Sonrasında sistem toparladığı için bu log ana stack'te kayıtlanmadı ya da direkt olarak bu o an orada çalışan bir komuttu. Ya da

Rich (BB code):

6: kd> k
 # Child-SP          RetAddr               Call Site
00 ffff978d`1d0470f8 fffff804`dc0bcee9     nt!KeBugCheckEx // Mavi ekran
01 ffff978d`1d047100 fffff804`dc0b81a8     nt!KiBugCheckDispatch+0x69
02 ffff978d`1d047240 fffff804`dbc40d80     nt!KiPageFault+0x468 // Tekrar sayfa hatası 
03 ffff978d`1d0473d0 fffff804`dbcf1707     nt!MiAcquirePageListLock+0x90 // RAM sayfasını kilitle (Birden fazla olay birbirine girmesin)
04 ffff978d`1d047460 fffff804`dbc48252     nt!MiUnlinkPageFromListEx+0x1f7 // Kullanılan ya da cachte bulunan bellek sayfasını boşalt (Yeni durum için)
05 ffff978d`1d047550 fffff804`dbc473f7     nt!MiHandleTransitionFault+0x122 // Geçişi ele al (İlgili belleğin durumu)
06 ffff978d`1d0475e0 fffff804`dbceb28d     nt!MiResolveTransitionFault+0x177 
07 ffff978d`1d0476a0 fffff804`dbce9bfc     nt!MiResolveProtoPteFault+0x64d
08 ffff978d`1d047740 fffff804`dbc43a76     nt!MiDispatchFault+0x1fc // Hataları işle 
09 ffff978d`1d0478b0 fffff804`dc0b80cb     nt!MmAccessFault+0x226 // Bellek erişim hatası
0a ffff978d`1d047a20 00007fff`040c27f0     nt!KiPageFault+0x38b // Sayfa hatası - CPU
0b 000000db`6a67de88 00000000`00000000     0x00007fff`040c27f0

Ana stack'in durumu da bu. Zaten boşa çıkarılan bir bellek sistemin çökmesine neden oluyorsa ya bu direkt bellek yönetimindeki bir hatadan kaynaklanıyordur ya da raw stack'ten yola çıkaran bir sürücünün o bellek yapısını bozduğu çıkarımı yapılıyordur. Burada gideceğin sürücü de haliyle NVIDIA sürücüsü.

Rich (BB code):

6: kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff804`897e0000 fffff804`8f546000   nvlddmkm   (deferred)             
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Fri Mar 14 20:40:17 2025 (67D46A01)
    CheckSum:         05B7EA12
    ImageSize:        05D66000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Bu dosya 3 gün öncesine ait, güncelledin mi bilmiyorum ama sürücüyü güncellemeyi deneyerek başlayabilirsin.

Servisten gelen bilgisayar mavi ekran veriyor

Detaylar

bariyilmaz8

Becerikli

061026-26390-01.dmp

Hasan Merkit

Moderasyon Üyesi

bariyilmaz8

Becerikli

Hasan Merkit

Moderasyon Üyesi

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

bariyilmaz8

Becerikli

Hasan Merkit

Moderasyon Üyesi

bicy

Mavi Ekran Destek

Benzer konular

Yeni konular

Yeni mesajlar