MSI Pulse GL66 11UX laptopta VIDEO_TDR_FAILURE mavi ekran hatası

İşletim sistemi
Windows 10

Tgruly2

Yoctopat
Katılım
9 Aralık 2021
Mesajlar
1
Daha fazla  
Cinsiyet
Erkek
RAM
SK Hynix HMA81GS6DJR8N-XN 8 GB RAM
SSD veya HDD modeli
512 GB SSD
Ekran kartı
RTX 3050
Anakart
MS-1582
İşlemci
i7 11800H
Bilgisayarımda iki kez mavi ekran hatası aldım, ikisi de farklı hatalardı.
Bilgisayarın markası MSI Pulse GL 66.

Sistem özellikleri:
  • i7 11800H.
  • RTX 3050 4 GB.
  • 8 GB RAM.
  • 512 GB SSD.
minidump rar dosyası
 
Son düzenleyen: Moderatör:
Öncelikle Technopat Sosyal'e hoş geldiniz. Şimdi sizden ricam aşağıda belirteceğim adımları uygulayın ve 3 gün sonra sonucu bildirin. 3 gün içinde sorun devam etmezse çözüldü demektir.

1) Aşağıdaki Bluetooth sürücüsünü indirip kurun.

2) Aşağıdaki sürücüyü indirin ve daha sonra DDU işlemini uygulayın. Sistem yeniden başladığında da indirdiğiniz sürücüyü kurarsınız.



Kod:
*******************************************************************************
*                                                                             *
*                        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: ffffd182886d8890
Arg3: ffffd18288fccda0
Arg4: ffff8c8ec00918e0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6374

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 24109

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

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

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


FILE_IN_CAB:  110621-8906-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  10e

BUGCHECK_P1: 2d

BUGCHECK_P2: ffffd182886d8890

BUGCHECK_P3: ffffd18288fccda0

BUGCHECK_P4: ffff8c8ec00918e0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8c8e`c0091868 fffff801`2d213ad0     : 00000000`0000010e 00000000`0000002d ffffd182`886d8890 ffffd182`88fccda0 : nt!KeBugCheckEx
ffff8c8e`c0091870 fffff801`2f0e93e1     : ffffd182`88fccda0 00000000`00000001 00000000`00000001 fffff801`12a079f3 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8c8e`c00918b0 fffff801`2f16f0b5     : ffffd182`88fccda0 ffffd182`886d8890 ffffd182`886d8890 00000000`00000000 : dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+0x24d
ffff8c8e`c0091930 fffff801`2f164c07     : ffffd182`889e9be0 ffff8c8e`c0091a40 00000000`00000000 ffff8c8e`c0091b18 : dxgmms2!VIDMM_GLOBAL::BuildMdlForAllocInCpuHostAperture+0xe5
ffff8c8e`c0091970 fffff801`2f13d484     : 00000000`00000000 00000000`00000002 ffffbd0a`78514000 ffffd182`889e9be0 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetCpuVisibleAddress+0x27763
ffff8c8e`c00919b0 fffff801`2f1407ea     : 00000000`00000000 ffffd182`88fd2da0 00000000`00000002 ffffbd0a`7830be10 : dxgmms2!VIDMM_PAGE_TABLE_BASE::GetDriverUpdateAddress+0xb8
ffff8c8e`c0091a40 fffff801`2f164f8a     : 00000000`00000000 00000000`00000000 00000000`00000002 ffff8c8e`c0091f60 : dxgmms2!VIDMM_PAGE_TABLE::UpdatePageTableInvalidate+0x4a
ffff8c8e`c0091b10 fffff801`2f13b8bd     : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x279a2
ffff8c8e`c0091bb0 fffff801`2f163dce     : 00000000`00000002 ffffd182`892cb5d0 ffffaa01`41580101 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x77d
ffff8c8e`c0091d20 fffff801`2f13ab7a     : 00000000`00000000 ffffd182`892cb5d0 00000000`00001000 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x28c8e
ffff8c8e`c0091e90 fffff801`2f16de98     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2f6
ffff8c8e`c0092010 fffff801`2f165920     : 00000000`00000000 00000000`00000000 00000000`00000076 ffffd182`83cba300 : dxgmms2!VIDMM_GLOBAL::InitPagingProcessVaSpace+0x183c8
ffff8c8e`c0092180 fffff801`2f14cc62     : ffffd182`892cbe10 ffff8c8e`00000001 00000000`00000001 ffffd182`888cb470 : dxgmms2!VIDMM_GLOBAL: ProcessSystemCommand+0x277d4
ffff8c8e`c0092300 fffff801`2f156809     : ffffd182`888cb400 ffffbd0a`6cf11001 00000000`00000000 00000000`06ee6b00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1462
ffff8c8e`c00924e0 fffff801`12b55855     : ffffbd0a`6cf11080 fffff801`2f156800 ffffd182`888cb400 001fe4ff`bd9bbfff : dxgmms2!VidMmWorkerThreadProc+0x9
ffff8c8e`c0092510 fffff801`12bfe8f8     : ffffaa01`41d40180 ffffbd0a`6cf11080 fffff801`12b55800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8c8e`c0092560 00000000`00000000     : ffff8c8e`c0093000 ffff8c8e`c008c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VIDMM_CPU_HOST_APERTURE::MapRange+24d

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1261

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  24d

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}

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9702d50f9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff802a2eb6368, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 7390

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 23201

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

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

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


FILE_IN_CAB:  120921-9390-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  116

BUGCHECK_P1: ffff9702d50f9010

BUGCHECK_P2: fffff802a2eb6368

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff9702d50f9010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffa802`f42a2318 fffff802`9b33665e     : 00000000`00000116 ffff9702`d50f9010 fffff802`a2eb6368 ffffffff`c000009a : nt!KeBugCheckEx
ffffa802`f42a2320 fffff802`9b2e6e44     : fffff802`a2eb6368 ffff9702`d24191c0 00000000`00002000 ffff9702`d2419280 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffa802`f42a2360 fffff802`9b2df97c     : ffff9702`d241a000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffa802`f42a2390 fffff802`9b335d85     : 00000000`00000100 ffff9702`d241aa70 00000000`00000000 00000000`00000100 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffa802`f42a2410 fffff802`9b335ef7     : fffff802`83325440 00000000`00000000 00000000`00000000 00000000`00000100 : dxgkrnl!TdrResetFromTimeout+0x15
ffffa802`f42a2440 fffff802`828b8515     : ffff9702`d7447040 fffff802`9b335ed0 ffff9702`c30a6a60 ffff9702`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffa802`f42a2470 fffff802`82955855     : ffff9702`d7447040 00000000`00000080 ffff9702`c30e1080 001fe4ff`bd9bbfff : nt!ExpWorkerThread+0x105
ffffa802`f42a2510 fffff802`829fe8f8     : ffffc300`7a399180 ffff9702`d7447040 fffff802`82955800 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffa802`f42a2560 00000000`00000000     : ffffa802`f42a3000 ffffa802`f429c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nvlddmkm+df6368

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup:     MachineOwner
---------
 
Son düzenleme:

Yeni konular

Geri
Yukarı