Window 블루스크린 오류

익명
2021-12-21T13:27:48+00:00

안녕하세요

오류 관련 로그를 찾아 혹시 해결방법 아시는 지 문의드립니다.

window dump 파일에서 오류 내용 전달 드립니다.

파일 용량이 크다보니 파일 첨부 어려운 점 양해 부탁드리겠습니다.

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

Loading Dump File [C:\Users\dhfhf\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`71800000 PsLoadedModuleList = 0xfffff805`7242a1b0
Debug session time: Mon Dec 20 16:19:32.527 2021 (UTC + 9:00)
System Uptime: 0 days 1:32:10.904
Loading Kernel Symbols
...............................................................
................................................................
....................................................Page 2a5fb2 not present in the dump file. Type ".hh dbgerr004" for details
............
................................................................
.....
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000b0`bae9d018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`71bf70d0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffeb8c`5fbe6b20=000000000000010e
7: kd> !analyze
*******************************************************************************
*                                                                             *
*                        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: 000000000000002a, The subtype of the BugCheck:
Arg2: ffffc908670fb370
Arg3: 0000000000000001
Arg4: 0000000000000000

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

BUGCHECK_CODE:  10e

BUGCHECK_P1: 2a

BUGCHECK_P2: ffffc908670fb370

BUGCHECK_P3: 1

BUGCHECK_P4: 0

PROCESS_NAME:  dwm.exe

SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+910

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

FAILURE_BUCKET_ID:  0x10e_2a_dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation

FAILURE_ID_HASH:  {55362b6d-c6cc-f758-6075-3157c7d24132}

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

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 000000000000002a, The subtype of the BugCheck:
Arg2: ffffc908670fb370
Arg3: 0000000000000001
Arg4: 0000000000000000

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3390

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3395

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

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

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

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  10e

BUGCHECK_P1: 2a

BUGCHECK_P2: ffffc908670fb370

BUGCHECK_P3: 1

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  dwm.exe

STACK_TEXT:  
ffffeb8c`5fbe6b18 fffff805`77713ad0     : 00000000`0000010e 00000000`0000002a ffffc908`670fb370 00000000`00000001 : nt!KeBugCheckEx
ffffeb8c`5fbe6b20 fffff805`7a293a70     : ffffa00a`9e1e7da0 ffffc908`670fb370 00000000`00000000 ffffc908`5bf1dc20 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffeb8c`5fbe6b60 fffff805`7a293154     : 00000000`00000000 fffff805`77364328 ffffc908`5b4f27d0 ffffa00a`81f27e10 : dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+0x910
ffffeb8c`5fbe6d90 fffff805`7a23182a     : ffffc908`5bc64560 fffff805`77487a49 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::DestroyAllocation+0xc
ffffeb8c`5fbe6dc0 fffff805`77487d92     : ffffa00a`81f27df0 00000000`00000002 ffffa00a`00000000 ffffa00a`81f27e10 : dxgmms2!VidMmDestroyAllocation+0x1a
ffffeb8c`5fbe6df0 fffff805`77487c1e     : ffffa00a`81f27df0 ffffa00a`9f19ba50 00000000`00000001 ffffa00a`9f19ba50 : dxgkrnl!DXGSHAREDRESOURCE::DestroyCoreAllocations+0x14a
ffffeb8c`5fbe6e70 fffff805`7748760f     : ffffc908`76cb8a58 ffffeb8c`00000000 ffffa00a`9f19ba00 00000000`00000001 : dxgkrnl!DXGSHAREDRESOURCE::Destroy+0xe
ffffeb8c`5fbe6ea0 fffff805`77486f0e     : 00000000`00000001 ffffa00a`7bfb1010 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x69b
ffffeb8c`5fbe7040 fffff805`77469e53     : 00000000`00000001 00000000`00000000 ffffa00a`7bfb1010 ffffa00a`7bfb1010 : dxgkrnl!DXGDEVICE::DestroyResource+0x5e
ffffeb8c`5fbe7080 fffff805`774692b1     : 00000000`00000000 ffffa00a`9f19ba50 ffffc908`00000001 ffffa00a`902c8cd0 : dxgkrnl!DXGDEVICE::TerminateAllocations+0x8c3
ffffeb8c`5fbe7120 fffff805`7746aa1a     : ffffc908`52a24598 ffffeb8c`5fbe7630 00000000`00000000 ffffa00a`7bfb1010 : dxgkrnl!DxgkDestroyAllocationInternal+0xe41
ffffeb8c`5fbe7530 fffff805`7746adbb     : 000000b0`bb1fef00 00000000`00000000 ffffc908`67922e70 fffff805`71a0827e : dxgkrnl!DxgkDestroyAllocationHelper+0x9ba
ffffeb8c`5fbe7a20 fffff805`71c08ab8     : ffffc908`5b4f20c0 ffffc908`5b4f20c0 00000223`fff7ec10 ffffc908`67922e70 : dxgkrnl!DxgkDestroyAllocation2+0x21b
ffffeb8c`5fbe7b00 00007ffb`077a49c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000b0`bb1fee68 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`077a49c4

SYMBOL_NAME:  dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation+910

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1415

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  910

FAILURE_BUCKET_ID:  0x10e_2a_dxgmms2!VIDMM_GLOBAL::DestroyOneAllocation

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {55362b6d-c6cc-f758-6075-3157c7d24132}

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

감사합니다.

가정용 Windows | Windows 10 | 디바이스 및 드라이버

잠긴 질문. 이 질문은 Microsoft 지원 커뮤니티에서 마이그레이션되었습니다. 질문이 도움이 되었는지 여부에 대해 응답할 수는 있지만, 메모나 회신을 추가하거나 질문을 따를 수는 없습니다.

댓글 0개

답변 2개

정렬 기준: 가장 유용함
가장 유용함 최신순 등록순
  1. 익명
    2021-12-21T14:54:34+00:00

    Hello

    Thank you so much

    I will try that way

    I hope it will work :)

    Thank you so much

    have a good day :)

    이 대답이 도움이 되었나요?

    댓글 0개
  2. DaveM121 936.6K 평판 포인트 독립 자문가
    2021-12-21T14:03:51+00:00

    저희는 사용자를 위하여 번역된 내용을 제공하고 있습니다. 문법적 오류가 있더라도 양해바랍니다.

    안녕하세요철

    나는 데이브, 나는이 당신을 도울 것입니다.

    덤프 파일 인쇄물은 시스템 충돌을 일으키는 비디오 카드의 장치 드라이버임을 나타냅니다.

    당신은 완전히 널리 사용할 수있는 무료 DDU 유틸리티를 사용하여 현재 비디오 카드 장치 드라이버를 제거한 다음 PC를 다시 시작하고 제조 업체의 웹 사이트에서 PC의 지원 페이지로 이동하여 권장버전의 비디오 장치 드라이버를 다운로드하여 설치하도록 설치해야합니다.

    이 대답이 도움이 되었나요?

    댓글 0개