Excalibur G770 laptop mavi ekran hatası veriyor

Ferrdinox · 2 Ekim 2025

Videonuzu izledikten sonra adım adım yaptım incelerseniz nasıl bir şey yapmam gerektiğini öğrenmiş olurum

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.047 seconds

   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 45

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


Loading Dump File [C:\Windows\Minidump\093025-34625-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`d6200000 PsLoadedModuleList = 0xfffff800`d70f4e70
Debug session time: Tue Sep 30 14:08:10.556 2025 (UTC + 3:00)
System Uptime: 0 days 18:06:36.613
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

Loading unloaded module list
.......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`d66f9280 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffd89`6cee6ee0=000000000000010e
0: kd> !analyze -v
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

Loading unloaded module list
.......................
*******************************************************************************
*
Bugcheck Analysis                                    *
*

*******************************************************************************

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000002d, The subtype of the BugCheck:
Arg2: ffffa68aac2c78f0
Arg3: ffffa68aac4026a0
Arg4: fffffd896cee6fd0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3500

    Key  : Analysis.Elapsed.mSec
    Value: 25430

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27920.1001

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x10e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x10e

    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: 0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

    Key  : Failure.Hash
    Value: {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

    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.24.0.0


BUGCHECK_CODE:  10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffa68aac2c78f0

BUGCHECK_P3: ffffa68aac4026a0

BUGCHECK_P4: fffffd896cee6fd0

FILE_IN_CAB:  093025-34625-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc80d51e5a340

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
fffffd89`6cee6ed8 fffff800`68171316     : 00000000`0000010e 00000000`0000002d ffffa68a`ac2c78f0 ffffa68a`ac4026a0 : nt!KeBugCheckEx
fffffd89`6cee6ee0 fffff800`8bd4b11e     : ffffa68a`965b1da0 ffffa68a`ac2c78f0 ffffa68a`ad01f9b0 ffffc80d`51a5f250 : watchdog!WdLogSingleEntry5+0x156
fffffd89`6cee6f70 fffff800`8bd4a0ea     : ffffa68a`00010000 ffffc80d`51a5f250 fffffd89`6cee7150 ffffa68a`b5074f10 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x57e
fffffd89`6cee7050 fffff800`8bd49f70     : ffff7972`7464dee8 00000000`00000002 ffffa68a`ac3acdc0 ffffc80d`5407a000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x66
fffffd89`6cee70c0 fffff800`8bd600b0     : 00000000`00000000 00000000`00000000 00000000`00000057 00000000`00000200 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x50
fffffd89`6cee7190 fffff800`8bd610b7     : fffffd89`6cee7650 ffffa68a`ac3acdc0 fffffd89`6cee7650 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0xa30
fffffd89`6cee7280 fffff800`8bd6125f     : 00000000`00000002 ffffa68a`ac3acdc0 fffffd89`6cee7650 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xcf7
fffffd89`6cee7400 fffff800`8bd4ec77     : 00000000`40000000 ffffa68a`ac3acdc0 fffffd89`6cee7650 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0xe9f
fffffd89`6cee7580 fffff800`8bd94315     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x9b7
fffffd89`6cee7710 fffff800`8bd6e8c0     : 00000000`00000000 00000000`00000000 fffffd89`6cee7900 fffff800`d649ad10 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x211
fffffd89`6cee78b0 fffff800`8bd6ccef     : ffffa68a`a08e8de0 ffffa68a`ac3ad3f0 ffffa68a`ac3ad3f0 00000000`00000000 : dxgmms2!VIDMM_GLOBAL:rocessSystemCommand+0x500
fffffd89`6cee79b0 fffff800`8bd82a3f     : ffffa68a`ac3ad3f0 fffffd89`6cee7ac9 fffff800`8bcee260 ffffc80d`54083c20 : dxgmms2!VidMmSubmitPacket+0x15f
fffffd89`6cee7a10 fffff800`d6687c2a     : ffffc80d`51e5a301 fffff800`8bd82300 ffff9300`8ca09100 066fe47f`b19bbd02 : dxgmms2!VidMmWorkerThreadProc+0x69f
fffffd89`6cee7b30 fffff800`d68a0b24     : ffff9300`8ca09180 ffffc80d`51e5a340 fffff800`d6687bd0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffffd89`6cee7b80 00000000`00000000     : fffffd89`6cee8000 fffffd89`6cee1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+57e

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.26100.6584

STACK_COMMAND: .process /r /p 0xffffc80d414d8040; .thread 0xffffc80d51e5a340 ; kb

BUCKET_ID_FUNC_OFFSET:  57e

FAILURE_BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ca00cb12-3ce5-2e41-c763-7f0f8a8fbadd}

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

739192 · 18 Ekim 2025

1.çözüm: Ekran kartı sürücünüzü DDU ile silip tekrar yükleyin.
2.çözüm: Komut Istemi'ni (CMD) yönetici olarak çalıştırın ve SFC /scannow komutunu girin. İşlem bittikten sonra sistemi yeniden başlatın.
3.Ekran kartın arızalı olabilir.
4.RAM'ler arızalı olabilir Windows bellek tanılama aracını veya MemTest86 gibi bir yazılımı kullanarak RAM'lerinizi test edin.

Excalibur G770 laptop mavi ekran hatası veriyor

Ayrıntılı düzenleme

Ferrdinox

Femtopat

739192

Decapat

Benzer konular

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz