Çözüldü Predator PHN16-71 "DPC_WATCHDOG_VIOLATION" Mavi ekran hatası

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

Peace86

Başarılı
Katılım
8 Şubat 2024
Mesajlar
77
Çözümler
1
Beğeniler
16
  • Anakart:
  • İşlemci: i7-13700HX
  • Ekran Kartı: RTX4060 Laptop GPU
  • İşletim Sistemi: Windows 11 Home 64 Bit
Öncelikle herkese iyi akşamlar. Dün Windows 11 kurup tüm yazılım ve sürücü güncellemelerini yaptığım dizüstü bilgisayarımda mavi ekran hatası alıyorum. Başka bir forumda DDU ile güvenli modda ekran kartlarının sürücülerini kaldırarak tekrar yüklemem söylendi ve yaptım. Önce NVIDIA sürücüsünü güvenli modda kaldırdım ve güncelden bir önceki sürücüyü yükledim sonra aynı işlemi Intel sürücüsü için de uyguladım ama hatanın kaynağını çözemedim. Hatayı almaya da devam ediyorum. 7 Şubat tarihli olanlar eski hatalar, 8 Şubat tarihli olanlar ise güvenli modda sürücüleri kaldırdıktan sonra aldığım hatalar. Ayrıca en son bugün aldığım mavi ekran hatasına ait dosyayı da yükledim. Yardımlarınız için şimdiden teşekkürler.

Minidump dosya linki: MiniDump Dosya Linki.
 
Son düzenleme:
Çözüm
Tamamdır deneyeceğim, teşekkürler.

BIOS güncellemesi ve temiz kurulum sonrası hâlâ mavi ekran almaya devam ettiğim için bilgisayarı iade ettim. Aynı sorun sizde de varsa ve BIOS güncellemesi ile temiz kurulum sorununuzu çözmüyorsa iade ya da değişim talep edin derim.
Tarihe göre sırala Puana göre sırala
İlk önerim BIOS sürümünü 1.15'e güncellemen:

Kod: 
Machine ID Information [From Smbios 3.4, DMIVersion 0, Size=3435]
BiosMajorRelease = 1
BiosMinorRelease = 13
FirmwareMajorRelease = 1
FirmwareMinorRelease = 5
BiosVendor = INSYDE Corp.
BiosVersion = V1.13
BiosReleaseDate = 09/07/2023
SystemManufacturer = Acer
SystemProductName = Predator PHN16-71
SystemFamily = Predator Helios Neo 16
SystemVersion = V1.13
SystemSKU = 0000000000000000
BaseBoardManufacturer = RPL
BaseBoardProduct = Compass_RTX
BaseBoardVersion = V1.13

Hatalara bakacak olursak donanımsal gibi. Ürünü servise göndermende fayda var. GPU olmasa bile GPU belleklerine reballing yapılması gerekebilir.

Kod: 
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: ffff808a43ed3cf0
Arg3: ffff808a41be52b0
Arg4: ffffc28f3750f2d0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3264

    Key  : Analysis.Elapsed.mSec
    Value: 12202

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x10e

    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: 0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

    Key  : Failure.Hash
    Value: {e24407bd-c019-66cd-5bed-5339a6b0e6f7}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    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:  10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffff808a43ed3cf0

BUGCHECK_P3: ffff808a41be52b0

BUGCHECK_P4: ffffc28f3750f2d0

FILE_IN_CAB:  020824-18734-01 - YENI.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT: 
ffffc28f`3750f1e8 fffff805`62a95685     : 00000000`0000010e 00000000`0000002d ffff808a`43ed3cf0 ffff808a`41be52b0 : nt!KeBugCheckEx
ffffc28f`3750f1f0 fffff805`931b3608     : ffff808a`41be5200 ffffdd8b`37ff4770 ffffdd8b`37ff4778 ffffdd8b`37ff4780 : watchdog!WdLogSingleEntry5+0x3b45
ffffc28f`3750f2a0 fffff805`9326018d     : ffff808a`41be52b0 ffff808a`43ed3cf0 ffff808a`43ed3cf0 00000000`00000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0x220
ffffc28f`3750f320 fffff805`93242360     : ffff808a`43f0f590 ffffc28f`3750f4f8 00000000`00000000 ffffc28f`3750f4f0 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xf9
ffffc28f`3750f380 fffff805`9322deba     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x2a9c0
ffffc28f`3750f420 fffff805`93253513     : ffffdd8b`00000000 00000000`00000000 ffff808a`43f0f590 fffff805`46e6a102 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
ffffc28f`3750f4f0 fffff805`93252ed8     : ffff808a`43e55080 00000000`00000001 00000000`00000000 ffffdd8b`41cf06c0 : dxgmms2!VIDMM_PAGE_TABLE::EvictPageTable+0x2ea6b
ffffc28f`3750f530 fffff805`93252f89     : 00000000`000007fe ffff808a`44c43bd0 00000000`00040000 ffff808a`44c43b01 : dxgmms2!VIDMM_PAGE_DIRECTORY::EvictPageDirectory+0x2f548
ffffc28f`3750f620 fffff805`931adbbe     : 00000000`00000000 ffff808a`44c43bd0 00000000`00000000 00000000`00000001 : dxgmms2!VIDMM_PAGE_DIRECTORY::EvictPageDirectory+0x2f5f9
ffffc28f`3750f710 fffff805`9325b6e6     : 00000000`00000021 ffffdd8b`41c716a8 00000000`00000000 fffff805`62646f00 : dxgmms2!CVirtualAddressAllocator::EvictRootPageTable+0x2e
ffffc28f`3750f750 fffff805`93225d86     : 00000000`00000021 ffffc28f`3750f851 ffff808a`44c44e90 ffffdd8b`41dd6000 : dxgmms2!VIDMM_GLOBAL::PurgePageTables+0x29f5e
ffffc28f`3750f7a0 fffff805`93237f57     : ffff808a`44d146e8 ffffdd8b`324dc768 ffff808a`43fbc9f0 ffffdd8b`324dc778 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x6c6
ffffc28f`3750f8b0 fffff805`93236629     : ffff808a`42a180b0 ffffdd8b`2e99f001 ffffdd8b`41cde300 7c000060`00000000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1917
ffffc28f`3750fb00 fffff805`46f07317     : ffffdd8b`41cde340 fffff805`93236620 ffff808a`42a180b0 006fe47f`b19bbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffffc28f`3750fb30 fffff805`4701bc54     : ffff9081`b3391180 ffffdd8b`41cde340 fffff805`46f072c0 00bf0825`8d00d55b : nt!PspSystemThreadStartup+0x57
ffffc28f`3750fb80 00000000`00000000     : ffffc28f`37510000 ffffc28f`37509000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+220

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.3073

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  220

FAILURE_BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e24407bd-c019-66cd-5bed-5339a6b0e6f7}

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8015711c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2452

    Key  : Analysis.Elapsed.mSec
    Value: 5598

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    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: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

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

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8015711c340

BUGCHECK_P4: 0

FILE_IN_CAB:  020724-18015-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffb180`9e66b9e8 fffff801`56612bb9     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`5711c340 : nt!KeBugCheckEx
ffffb180`9e66b9f0 fffff801`56612421     : 000003d0`3a54b876 00000000`0001c435 00000000`0001c434 00000000`00000000 : nt!KeAccumulateTicks+0x239
ffffb180`9e66ba50 fffff801`5660fa2f     : 00000000`00000018 00000000`00001388 00000000`0001c400 00000000`00010d89 : nt!KiUpdateRunTime+0xd1
ffffb180`9e66bc00 fffff801`56610618     : 00000000`00000000 ffffb180`9f171b00 ffffb180`9e651180 00000000`00000000 : nt!KiUpdateTime+0x63f
ffffb180`9e66bea0 fffff801`5660feda     : fffff801`5705fee0 ffffb180`9f171bf0 ffffb180`9f171bf0 00000000`00000002 : nt!KeClockInterruptNotify+0x228
ffffb180`9e66bf40 fffff801`56724cdc     : 00000004`362865f5 ffff8909`9bb648a0 ffff8909`9bb64950 fffffc08`8051eaa0 : nt!HalpTimerClockInterrupt+0x10a
ffffb180`9e66bf70 fffff801`56818d7a     : fffffc08`8051ee50 ffff8909`9bb648a0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffb180`9e66bfb0 fffff801`56819627     : 00000000`00000000 00000000`00000000 00000000`00000000 00001f80`0000020c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffc08`8051edd0 fffff801`ab01542e     : fffffc08`8051f1a0 fffffc08`8051f150 ffff8909`b93e7000 ffff781e`d654b89c : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffc08`8051ef60 fffffc08`8051f1a0     : fffffc08`8051f150 ffff8909`b93e7000 ffff781e`d654b89c 00000000`00000001 : nvlddmkm+0xd542e
fffffc08`8051ef68 fffffc08`8051f150     : ffff8909`b93e7000 ffff781e`d654b89c 00000000`00000001 fffff801`aaffe4b5 : 0xfffffc08`8051f1a0
fffffc08`8051ef70 ffff8909`b93e7000     : ffff781e`d654b89c 00000000`00000001 fffff801`aaffe4b5 ffff8909`b93e7000 : 0xfffffc08`8051f150
fffffc08`8051ef78 ffff781e`d654b89c     : 00000000`00000001 fffff801`aaffe4b5 ffff8909`b93e7000 00000000`00000000 : 0xffff8909`b93e7000
fffffc08`8051ef80 00000000`00000001     : fffff801`aaffe4b5 ffff8909`b93e7000 00000000`00000000 00000000`00000000 : 0xffff781e`d654b89c
fffffc08`8051ef88 fffff801`aaffe4b5     : ffff8909`b93e7000 00000000`00000000 00000000`00000000 00000000`00000001 : 0x1
fffffc08`8051ef90 ffff8909`b93e7000     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000004 : nvlddmkm+0xbe4b5
fffffc08`8051ef98 00000000`00000000     : 00000000`00000000 00000000`00000001 00000000`00000004 00000000`00000000 : 0xffff8909`b93e7000


SYMBOL_NAME:  nvlddmkm+d542e

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  d542e

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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: ffffe386a50e76b0
Arg3: ffffe386a34d4970
Arg4: ffff808af350ee30

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2718

    Key  : Analysis.Elapsed.mSec
    Value: 10895

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x10e

    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: 0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

    Key  : Failure.Hash
    Value: {e24407bd-c019-66cd-5bed-5339a6b0e6f7}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

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

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    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:  10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffe386a50e76b0

BUGCHECK_P3: ffffe386a34d4970

BUGCHECK_P4: ffff808af350ee30

FILE_IN_CAB:  020724-18046-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff808a`f350ed48 fffff807`42695685     : 00000000`0000010e 00000000`0000002d ffffe386`a50e76b0 ffffe386`a34d4970 : nt!KeBugCheckEx
ffff808a`f350ed50 fffff807`2a273608     : ffffe386`a34d4900 ffffab88`ba3f9440 ffffab88`ba3f9448 ffffab88`ba3f9450 : watchdog!WdLogSingleEntry5+0x3b45
ffff808a`f350ee00 fffff807`2a32018d     : ffffe386`a34d4970 ffffe386`a50e76b0 ffffe386`a50e76b0 00000000`00000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0x220
ffff808a`f350ee80 fffff807`2a302360     : ffffe386`a50b6c50 ffff808a`f350f058 00000000`00000000 ffff808a`f350f050 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xf9
ffff808a`f350eee0 fffff807`2a2edeba     : 00000000`00000000 fffff807`248ee2bb ffffab88`c2e40028 00000000`00000205 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0x2a9c0
ffff808a`f350ef80 fffff807`2a2d8588     : 00000000`00000000 00000000`00000000 00000000`00000002 ffffe386`a34d4bb0 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
ffff808a`f350f050 fffff807`2a2d63da     : ffff808a`f350f240 ffffe386`a54719c0 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x568
ffff808a`f350f130 fffff807`2a2d6b43     : ffffe386`a11c7d40 ffffe386`a54719c0 ffff808a`f350f590 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x9ea
ffff808a`f350f2f0 fffff807`2a2d44f4     : ffffe386`a11c7c00 ffffe386`a54719c0 ffff808a`f350f590 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x1153
ffff808a`f350f4b0 fffff807`2a30146d     : 00000000`00000000 ffff4dd9`d9847e3c fffff807`2a290fc0 ffffab88`c2e36000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x684
ffff808a`f350f640 fffff807`2a2e5f21     : fffff807`252ffe10 fffff807`252ffe08 00000000`00000000 ffffe386`a54719c0 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x469
ffff808a`f350f7a0 fffff807`2a2f7f57     : ffffe386`a5530db8 ffffab88`b8dff668 ffffe386`a5418ea0 ffffab88`b8dff678 : dxgmms2!VIDMM_GLOBAL::ProcessSystemCommand+0x861
ffff808a`f350f8b0 fffff807`2a2f6629     : ffffe386`a1ec5100 ffffab88`af9b7001 ffffab88`c2e13000 00000000`00000000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1917
ffff808a`f350fb00 fffff807`24907317     : ffffab88`c2e130c0 fffff807`2a2f6620 ffffe386`a1ec5100 006fe47f`b19bbdff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff808a`f350fb30 fffff807`24a1bc54     : ffff8381`69e51180 ffffab88`c2e130c0 fffff807`249072c0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
ffff808a`f350fb80 00000000`00000000     : ffff808a`f3510000 ffff808a`f3509000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+220

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.22621.3073

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  220

FAILURE_BUCKET_ID:  0x10e_2d_dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e24407bd-c019-66cd-5bed-5339a6b0e6f7}
 
Artı 0 Eksi
[CODE highlight="1,19"]Current DPC: nvlddmkm+0xBF990 (Normal DPC)

Debugger Saved IRQL: 13

Cumulative DPC Time Limit: 0.000 seconds

Current Cumulative DPC Time: 0.000 seconds

Single DPC Time Limit: 0.000 seconds

Current Single DPC Time: 0.000 seconds

dt nt!_ISRDPCSTATS ffff89099bb64950

IsrActive: TRPending DPCs:
----------------------------------------
CPU Type KDPC Function

10: Normal : 0xffff8909b8bc9b30 0xfffff801aafff990 nvlddmkm

10: Threaded: 0xffffb1809e659758 0xfffff80156979bc0 nt!KiDpcWatchdog[/CODE]

[CODE highlight="5,7"]0xffffb1809e66ba08 : 0xfffff8015711c340 : nt!KeDpcWatchdogProfileGlobalTriageBlock

0xffffb1809e66ba48 : 0xfffff80156612421 : nt!KiUpdateRunTime+0xd1

Unable to load image igdkmdn64.sys, Win32 error 0n2

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

0xffffb1809e66bac8 : 0xfffff801567c50bb : nt!HalpHvCounterQueryCounter+0x1b

0xffffb1809e66bb50 : 0xfffff8015673c810 : nt!PpmCheckPeriodicStart

0xffffb1809e66bb88 : 0xfffff801567c50bb : nt!HalpHvCounterQueryCounter+0x1b[/CODE]

Kod: 
10: Kd> KnL
00 ffffb180'9E66B9E8 fffff801'56612BB9 NT! KeBugCheckEx

01 ffffb180'9E66B9F0 fffff801'56612421 NT! KeAccumulateTicks+0x239

02 ffffb180'9E66BA50 fffff801'5660FA2F NT! KiUpdateRunTime+0xd1

03 ffffb180'9E66BC00 fffff801'56610618 NT! KiUpdateTime+0x63F

04 ffffb180'9E66BEA0 fffff801'5660FEDA NT! KeClockInterruptNotify+0x228

05 ffffb180'9E66BF40 fffff801'56724CDC NT! HalpTimerClockInterrupt+0x10a

06 ffffb180'9E66BF70 fffff801'56818D7A NT! KiCallInterruptServiceRoutine+0x9C

07 ffffb180'9E66BFB0 fffff801'56819627 NT! KiInterruptSubDispatchNoLockNoEtw+0xfa

08 fffffc08'8051EDD0 fffff801'AB01542E NT! KiInterruptDispatchNoLockNoEtw+0x37

09 fffffc08'8051EF60 fffffc08'8051F1A0 nvlddmkm+0xd542e

0A fffffc08'8051EF68 fffffc08'8051F150 0xfffffc08`8051f1a0

0B fffffc08'8051EF70 ffff8909'B93e7000 0xfffffc08`8051f150

0C fffffc08'8051EF78 ffff781e'D654B89C 0xffff8909`b93e7000

0D fffffc08'8051EF80 00000000'00000001 0xffff781e`d654b89c

0E fffffc08'8051EF88 fffff801'aaffe4b5 0x1

0F fffffc08'8051EF90 ffff8909'B93e7000 nvlddmkm+0xbe4b5

10 fffffc08'8051EF98 00000000'00000000 0xffff8909`b93e7000

Şu laptoplardaki DPC hatası inanılmaz kafa karıştırıcı bir şey, ekran kartı hatası olarak duruyor. Ki durmakla kalmıyor zaten ilk attığım DPC kısmına bakarsan direkt ekran kartı temelli bir hata. Sürücüyü kaldırmak, güncellemek gibi yöntemlerin işe yaradığı da oluyor ama herkeste işe yaramadığı da oluyor.

Sendeki problemleri sıraladım DPC olarak, NVIDIA ve Intel ekran kartların sırayla hata vermiş. Zaten ikisini de denemişsin. Bir diğer sorun ise işlemci temelli kesmelere yanıt vermeme problemi ki bu problem çoğu yerde donanımsal problem olarak geçiyor. Daha sonra Hyper v temelli hataların olması da var. İşlemcinin güç yönetimi ile ilgili çağrılar da var.

Bu hata temelli önerilecek şeylerin birçoğunu denemişsin zaten, geriye bana kalan söylem de şu: Hyper V'i kapatmanı öneririm.

Yönetim olayları kısmını paylaş: Rehber: Olay Görüntüleyicisi Raporu Almak

Bir diğer hata ve yeni hatalar diye nitelendirdiğin hata kodu da bu:

Kod: 
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: ffffe386a50e76b0
Arg3: ffffe386a34d4970
Arg4: ffff808af350ee30

Detaya inmeden sebebi söylüyorum direkt, tekrardan ekran kartın.
Kod: 
10: Kd>!devnode

DevNode 0xffffb506fb8e2a60 for PDO 0xffffb506fb2e20a0

 Parent 0xffffb506f9febb60 Sibling 0xffffb506fcff2010 Child 0000000000

 InstancePath is "PCI\VEN_10DE&DEV_28E0&SUBSYS_3C9017AA"

 ServiceName is "nvlddmkm"

Detaya inilirse bana kalırsa ekran kartın, bellek yönetimi ile ilgili problemler yaşıyor olması muhtemel. Sadece kendi belleği değil sistemdeki fiziksel bellek de buna dahil. tabii 8.kısımda işaretlediğim işlemci güç yönetimi ile ilgili çağrıya da dikkat edebilirsin. Bu direkt donanımsal sorun olarak duruyor ama ekran kartı mıdır işlemci midir bilmiyorum.

[CODE highlight="8"]0xffff808af350ef78 : 0xfffff8072a2edeba : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
0xffff808af350ef88 : 0xfffff807248ee2bb : nt!ExReleasePushLockExclusiveEx+0x3b
0xffff808af350efb8 : 0xfffff8072a2c4064 : dxgmms2!VIDMM_GLOBAL:ageInPageTableOrDirectory+0x5c
0xffff808af350efc8 : 0xfffff8072a326688 : dxgmms2!VIDMM_GLOBAL::RecordPageMappingHistory+0xe4
0xffff808af350f048 : 0xfffff8072a2d8588 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x568
0xffff808af350f098 : 0xfffff8072a2c4064 : dxgmms2!VIDMM_GLOBAL:ageInPageTableOrDirectory+0x5c
0xffff808af350f128 : 0xfffff8072a2d63da : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x9ea
0xffff808af350f168 : 0xfffff80756771b01 : intelppm!ComputeProcessorEnergyMsr+0x141
0xffff808af350f348 : 0xfffff8072a25c4d2 : dxgmms2!wil_details_FeatureReporting_ReportUsageToServiceDirect+0xe2
0xffff808af350f3f8 : 0xfffff8072a25c3cb : dxgmms2!wil_details_FeatureReporting_ReportUsageToService+0x2f
0xffff808af350f458 : 0xfffff8072a25d342 : dxgmms2!Feature_DxgkGpuVaIoMmu__private_IsEnabled+0x56
[/CODE]

Daha önce yaşadığın 2.hatayı yaşayan biri BIOS güncellemesi yapıp ardından temiz kurulum yaparak sorunu çözdüğünü söylemiş. Haberin olsun.
Kod: 
BiosReleaseDate = 09/07/2023
SystemManufacturer = Acer
SystemProductName = Predator PHN16-71
SystemFamily = Predator Helios Neo 16
SystemVersion = V1.13
 
Son düzenleme:
Artı 0 Eksi
BIOS sürümünü yaklaşık bir saat önce güncelledim. Bildiğim kadarıyla reballing cihazın ömrünü azaltan bir şey. Cihaz birkaç günlük olduğu için pek taraftarı değilim açıkçası. BIOS güncellemesinden sonra mavi ekran almazsam yine de servise göndermeme gerek var mı?

Dediğiniz Hyper-V'yi bulamadım. Olay dosyalarını da Google Drive klasörüne ekledim. Link: Gdrive.
 
Son düzenleme:
Artı 0 Eksi

Sanallaştırma yazılımını çalıştırmak için Hyper-V'yi devre dışı bırakma - Windows Client

Sanallaştırma uygulamalarının Hyper-V, Device Guard ve Credential Guard ile birlikte çalışmama sorununu açıklar. Bir çözüm sağlanır.
learn.microsoft.com

Olay raporlarında işlemciyle ilgili olarak en azından doğru tahmini yaptığımı görüyorum. Kernel-Processor-Power hataları var bolca. Bu bize işlemcinin ya da çekirdeğinin tam hızlarda çalışmayı destekleyemediğini gösteriyor. Normalde böyle bir hatayı çok görüyor muyum diye sorarsan hayır. Sana tavsiyem BIOS update + temiz bir kurulum. Sorun çözülmezse servis görmesi gerekiyor cihazın.
 
Artı 0 Eksi
Tamamdır deneyeceğim, teşekkürler.

BIOS güncellemesi ve temiz kurulum sonrası hâlâ mavi ekran almaya devam ettiğim için bilgisayarı iade ettim. Aynı sorun sizde de varsa ve BIOS güncellemesi ile temiz kurulum sorununuzu çözmüyorsa iade ya da değişim talep edin derim.
 
Son düzenleme:
Artı 0 Eksi
Çözüm
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru Soru
Windows 11 "IRQL_NOT_LESS_OR_EQUAL" mavi ekran hatası
Mesaj
2
Görüntüleme
79
Musabbs
A
  • Soru Soru
Monster Tulpar T7'de DPC_WATCHDOG_VIOLATION (133) hatası
Mesaj
1
Görüntüleme
91
YASEDEM
E
  • Soru Soru
Monster Tulpar T7'de VIDEO_DXGKRNL_FATAL_ERROR 0x113 mavi ekran hatası
Mesaj
2
Görüntüleme
86
Emir Çip
E
  • Soru Soru
R7 7800X3D & B650 Eagle sistem açılırken mavi ekran hatası veriyor
Mesaj
2
Görüntüleme
73
X99
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…