컴퓨터 부팅시 화면깨지면서 재부팅현상 (블루스크린메모리덤프첨부)

Question

제목대로 부팅시 암호입력후 바탕화면으로 넘어가면서 화면이 깨진뒤 본체에 그래픽카드 cpu팬등에는 전원이 들어온상태로 화면에 신호없음이 잡히고 재부팅됩니다.

블루스클린메모리덤프 첨부합니다..까보긴했는데 뭔지모르겠네요^^;

Microsoft (R) Windows Debugger Version 10.0.16299.15 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\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 15063 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 15063.0.amd64fre.rs2_release.170317-1834

Machine Name:

Kernel base = 0xfffff8036da13000 PsLoadedModuleList = 0xfffff8036dd5f5c0

Debug session time: Sat Oct 28 22:02:00.562 2017 (UTC + 9:00)

System Uptime: 0 days 0:00:21.262

Loading Kernel Symbols

...............................................................

......Page d7060 not present in the dump file. Type ".hh dbgerr004" for details

..........................................................

............................................................

Loading User Symbols

Loading unloaded module list

........

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

Use !analyze -v to get detailed debugging information.

BugCheck 119, {5, ffffc40a0b5b3000, ffffc40a0b619ad0, 346}

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrFaultedPacket+23e )

Followup:     MachineOwner

---

0: kd> !analyze -v

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

VIDEO_SCHEDULER_INTERNAL_ERROR (119)

The video scheduler has detected that fatal violation has occurred. This resulted

in a condition that video scheduler can no longer progress. Any other values after

parameter 1 must be individually examined according to the subtype.

Arguments:

Arg1: 0000000000000005, The subtype of the bugcheck:

Arg2: ffffc40a0b5b3000

Arg3: ffffc40a0b619ad0

Arg4: 0000000000000346

Debugging Details:

---

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7A37

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.40

BIOS_DATE:  04/28/2017

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  B350M MORTAR (MS-7A37)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  1

BUGCHECK_P1: 5

BUGCHECK_P2: ffffc40a0b5b3000

BUGCHECK_P3: ffffc40a0b619ad0

BUGCHECK_P4: 346

CPU_COUNT: 10

CPU_MHZ: bb8

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  9

ANALYSIS_SESSION_HOST:  DESKTOP-63L2GRO

ANALYSIS_SESSION_TIME:  10-29-2017 01:11:57.0797

ANALYSIS_VERSION: 10.0.16299.15 x86fre

EXCEPTION_RECORD:  fffff803f6ef7160 -- (.exr 0xfffff803f6ef7160)

ExceptionAddress: ccccccccccc3c032

   ExceptionCode: 8348c033

  ExceptionFlags: ccc328c4

NumberParameters: -858993460

   Parameter[0]: cccccc0000430be9

   Parameter[1]: cccccccccccccccc

   Parameter[2]: 001303e828ec8348

   Parameter[3]: 42eee928c4834800

   Parameter[4]: cccccccccccc0000

   Parameter[5]: cccccccccccccccc

   Parameter[6]: 83485708245c8948

   Parameter[7]: 87d98b48c03320ec

   Parameter[8]: 01f883000089a705

   Parameter[9]: 00895b0d8d484b75

   Parameter[10]: fdbf000012c6e800

   Parameter[11]: 894a0d8d48ffffff

   Parameter[12]: d08b48c723480000

   Parameter[13]: 3d834800001307e8

   Parameter[14]: 481e740000008947

LAST_CONTROL_TRANSFER:  from fffff803f2fd355e to fffff8036db7f580

STACK_TEXT:  

fffff8036c8799d8 fffff803f2fd355e : 0000000000000119 0000000000000005 ffffc40a0b5b3000 ffffc40a0b619ad0 : nt!KeBugCheckEx

fffff8036c8799e0 fffff803f2de6962 : ffffc40a0b656000 ffffc40a0b5b3000 ffffc40a0b5b3000 fffff8036c879b30 : watchdog!WdLogEvent5_WdCriticalError+0xce

fffff8036c879a20 fffff803f2ddb17a : ffffc40a0b57d0c0 ffffc40a0b1987b0 ffffc40a0b5b3000 0000000000000000 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x23e

fffff8036c879aa0 fffff803f2dcad0d : fffff80300000346 ffffc40a0929e030 ffffc40a0b57d0c0 fffff803f78f40b4 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x1044a

fffff8036c879af0 fffff803f2ffb944 : ffffc40a0929e030 0000000000000000 0000000000000001 0000000a00000345 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d

fffff8036c879b20 fffff803f4338ae3 : ffffc40a09cea758 fffff803f78f40b4 0000000000000400 0000000000000001 : dxgkrnl!DxgNotifyInterruptCB+0x74

fffff8036c879b50 fffff803f791a5c5 : ffffc40a09cea758 ffff850100000346 ffffc40a0aa36000 ffffc40a09ce7000 : atikmpag+0x48ae3

fffff8036c879c00 fffff803f791a724 : 0000000000000880 ffffc40a0ab91000 ffffc40a0aa36000 0000000000000000 : atikmdag+0x12a5c5

fffff8036c879ca0 fffff803f792b55e : ffffc40a0b188580 fffff8036c879db9 0000000000000000 ffffc40a0abc5cd0 : atikmdag+0x12a724

fffff8036c879cd0 fffff803f78aae3d : fffff8036c879d80 ffffc40a0abc5cd0 ffffc40a0aba2180 fffff8036da853a1 : atikmdag+0x13b55e

fffff8036c879d00 fffff803f78ab6f8 : ffffc40a0abc5cd0 fffff8036c879da8 0000000000000000 0000000000000000 : atikmdag+0xbae3d

fffff8036c879d30 fffff803f78b02cd : ffffc40a0afdc008 ffffc40a0aba1008 ffffc40a00000000 fffff80300000000 : atikmdag+0xbb6f8

fffff8036c879e20 fffff803f78b63b1 : ffffc40a0ab91000 ffff8501e0160830 ffff8501e0160780 0000000000000000 : atikmdag+0xc02cd

fffff8036c879e70 fffff803f78a8637 : ffffc40a0ab91000 0000000000000001 ffffc40a06a3f1a0 0000000000000000 : atikmdag+0xc63b1

fffff8036c879ea0 fffff803f78252df : ffffc40a06919240 0000000000000000 ffff8501df65d830 00000000ffffffff : atikmdag+0xb8637

fffff8036c879ed0 fffff803f42fc6f2 : 0000000000000000 0000000000000000 0000000000000000 0000000000000001 : atikmdag+0x352df

fffff8036c879f00 fffff803f2ffb998 : 0000000000000282 fffff8036db00f9d 0000001d0b18880a 00000000ffffffff : atikmpag+0xc6f2

fffff8036c879f30 fffff8036da22685 : ffff8501e0160780 fffff8036da22685 ffff8501df65d780 0000000000000000 : dxgkrnl!DpiFdoMessageInterruptRoutine+0x38

fffff8036c879f60 fffff8036db809bf : fffff8036c86b740 ffff8501e0160780 0000000003c1bcd4 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5

fffff8036c879fa0 fffff8036db80c67 : ffffc40a0aa98840 ffffc40a0abed8d0 0000000000000000 0000000000000000 : nt!KiInterruptSubDispatch+0x10f

fffff8036c86b6c0 fffff803f6efb492 : fffff803f6ef7160 0000000000000000 0000000000000000 ffffc40a0a909010 : nt!KiInterruptDispatch+0x37

fffff8036c86b858 fffff803f6ef7160 : 0000000000000000 0000000000000000 ffffc40a0a909010 fffff8036c82e180 : amdppm!C1Halt+0x2

fffff8036c86b860 fffff8036da89ac9 : 0000000000000000 0000000000000069 0000000000000000 000000000000002a : amdppm!AcpiCStateIdleExecute+0x20

fffff8036c86b890 fffff8036da89323 : 0000000000008c00 ffffc40a05bd5800 0000000000000002 ffff886bd88f16e9 : nt!PpmIdleExecuteTransition+0x619

fffff8036c86bb00 fffff8036db825fc : 0000000000000000 fffff8036c82e180 fffff8036de0ca40 ffffc40a0b798080 : nt!PoIdle+0x343

fffff8036c86bc60 0000000000000000 : fffff8036c86c000 fffff8036c866000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x2c

THREAD_SHA1_HASH_MOD_FUNC:  385cbb6df3626ed63ca26f0f58571b35722d716e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  79cc8ed410fe3f074cd79c36211295a1980fbaa3

THREAD_SHA1_HASH_MOD:  817b02c1147738f2717a75ee98059576175e9909

FOLLOWUP_IP: 

dxgmms2!VidSchiProcessIsrFaultedPacket+23e

fffff803`f2de6962 cc              int     3

FAULT_INSTR_CODE:  cccccccc

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiProcessIsrFaultedPacket+23e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c0a8147

IMAGE_VERSION:  10.0.15063.674

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  23e

FAILURE_BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_dxgmms2!VidSchiProcessIsrFaultedPacket

BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_dxgmms2!VidSchiProcessIsrFaultedPacket

PRIMARY_PROBLEM_CLASS:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_dxgmms2!VidSchiProcessIsrFaultedPacket

TARGET_TIME:  2017-10-28T13:02:00.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-09-29 16:20:26

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  de3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x119_5_driver_faulted_system_command_dxgmms2!vidschiprocessisrfaultedpacket

FAILURE_ID_HASH:  {8a2196f9-e81f-1cf4-52f5-61b7dae1d7c0}

Followup:     MachineOwner

---

Answer 1

안녕하세요? DoYounKim 님,

Microsoft Community 사이트를 방문해 주셔서 감사합니다.

Windows 10 사용 중 PC 부팅시 화면 이상 증상과 함께 재부팅되는 문제로 문의하셨습니다.

위와 같은 해당 증상은 다양한 원인들로 발생 가능합니다. 아래 안내되는 작업 방법들을 차례대로 진행해 보신 후 문제가 해결

되는지 확인하시기 바랍니다.

작업 방법 A. 블루 스크린 오류 문제 해결

작업 방법 B. Windows 구성 요소 저장소에서 파일 손상 검사

1. Windows 로고 키 + X 키를 누른 후 명령 프롬프트(관리자)를 클릭합니다.
2. 명령 프롬프트에서 아래 명령을 입력하고 Enter 키를 누릅니다.
3. Dism /online /cleanup-image /restorehealth

* PC 환경에 따라 시스템 검사 시간이 오래 소요될 수 있습니다.

4. 검사가 완료되면 명령 프롬프트에 아래 명령을 입력하고 Enter 키를 누릅니다.

sfc /scannow

5. 검사가 완료되면 컴퓨터를 다시 시작하여 문제점을 확인합니다.

**작업 방법 C. 클린 부팅:**클린 부팅을 수행하면 문제를 일으키는 어떤 충돌을 해결하거나 그 원인을 확인할 수도 있습니다.

1. 검색 혹은 시작, 검색 버튼을 눌러 검색 상자에 msconfig 를 입력합니다.
2. 시스템 구성 대화 상자의 서비스 탭에서, 모든 Microsoft 서비스 숨기기 확인란을 선택하거나 클릭하고 모두 사용 안 함을

탭 하거나 클릭합니다.

3. 시스템 구성 대화상자 시작프로그램 탭을 누르거나 작업관리자 열기를 클릭합니다.
4. 작업관리자의 시작프로그램 탭에서 각 시작항목에 대한 항목을 선택하고 사용 안 함을 클릭합니다.
5. 작업관리자를 닫습니다.
6. 시스템 구성 대화상자에서 확인을 누르고 컴퓨터를 다시 시작합니다.

조속히 문제가 해결되길 바라며 관련된 추가 질문이 있으실 경우 [응답] 버튼을 눌러 질문해 주시기 바랍니다.

감사합니다.