질문과 답변

윈 도 우 블루스크린이 뜹니다 도움좀 주세요!!

2016.12.28 19:54

아이우히히 조회:1030

글카를 이번에 구입한 1060 6gb 제품이구요! Xsplit 같은 프로그램은 안쓰고 그냥 지포스 익스피리언스에서 브로드캐스트(스트리밍)메뉴 를 통해서 유투브 방송을 좀 해봤습니다. 그제까지는 꽤 오래해도 괜찮았는데 오늘 갑자기!


5~10분정도 지나면 화면이 멈추고 블루스크린이 뜨더군요! 비교적 저사양게임인 히오스같은게임에선 문제가 안생겼고 고사양게임이라고 할 수 있는

플래닛코스터, 폴아웃4 같은 게임에서 문제가 발생하더군요!


MEMORY.DMP 파일을 그래서 어떻게 분석방법을 찾아서 분석을 해봤는데 도통 알 수가 있어야죠... 그래서 질문 드립니다!


아래 분석내용 보고 해결법이나 컴퓨터에 문제가 있는건지 알려주시면 좋겠습니다! 아니면 그냥 초기화를 한번 해볼까 합니다..


-----------------------

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
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 Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
Machine Name:
Kernel base = 0xfffff803`e708d000 PsLoadedModuleList = 0xfffff803`e7392060
Debug session time: Wed Dec 28 18:37:38.536 2016 (UTC + 9:00)
System Uptime: 0 days 0:46:46.250
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, 0}
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e04c3 )
Followup:     MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
 component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
Debugging Details:
------------------

DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING:  14393.576.amd64fre.rs1_release_inmarket.161208-2252
SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.
SYSTEM_SKU:  To Be Filled By O.E.M.
SYSTEM_VERSION:  To Be Filled By O.E.M.
BIOS_VENDOR:  American Megatrends Inc.
BIOS_VERSION:  P2.50
BIOS_DATE:  12/11/2015
BASEBOARD_MANUFACTURER:  ASRock
BASEBOARD_PRODUCT:  B85M Pro4
BASEBOARD_VERSION:                       
DUMP_TYPE:  1
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: dab
CPU_VENDOR:  GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x133
PROCESS_NAME:  System
CURRENT_IRQL:  d
ANALYSIS_SESSION_HOST:  DESKTOP-3E1VSDR
ANALYSIS_SESSION_TIME:  12-28-2016 18:52:54.0163
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER:  from fffff803e722cfa6 to fffff803e71d76f0
STACK_TEXT: 
fffff803`e8d53d88 fffff803`e722cfa6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff803`e8d53d90 fffff803`e7158b99 : 000008fe`be56163c 000008fe`be561283 fffff780`00000320 fffff803`e7066490 : nt! ?? ::FNODOBFM::`string'+0x46416
fffff803`e8d53df0 fffff803`e701b366 : fffff803`e8d45710 fffff803`e70663e0 00000000`00000002 000008fe`be561283 : nt!KeClockInterruptNotify+0x469
fffff803`e8d53f40 fffff803`e70e45d6 : fffff803`e70663e0 00000000`00000008 fffff803`e8d53f50 00000000`0000000c : hal!HalpTimerClockInterrupt+0x56
fffff803`e8d53f70 fffff803`e71d8d6a : fffff803`e8d45790 ffffe58a`63d7a6d8 00000000`000001f4 00000000`00000002 : nt!KiCallInterruptServiceRoutine+0x106
fffff803`e8d53fb0 fffff803`e71d91b7 : 00000000`00000000 00000000`00000000 ffffe58a`67f54640 fffff803`e70ee1ec : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff803`e8d45710 fffff803`e715cb13 : 000008ee`731fe354 fffff803`e7100d1a 00000000`01000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`e8d458a0 fffff803`e7100d42 : 00000000`00000002 fffff803`e70eeb60 00000001`ffffffff 00000000`00000002 : nt!KxWaitForSpinLockAndAcquire+0x23
fffff803`e8d458d0 fffff80e`28a504c3 : 00000000`00000000 00000000`00342394 ffffffff`ffffffff ffffe58a`641c7ee0 : nt!KeAcquireSpinLockRaiseToDpc+0x32
fffff803`e8d45900 fffff80e`28a503ba : ffffe58a`63c6d760 00000000`00000001 00000000`00000002 00000000`00000001 : nvlddmkm+0xe04c3
fffff803`e8d459b0 fffff803`e70f04e0 : ffffe58a`63c6d760 ffffe58a`63c6d760 00000000`00140001 00000000`00000002 : nvlddmkm+0xe03ba
fffff803`e8d459e0 fffff803`e71da77a : 00000000`00000000 fffff803`e73cf180 fffff803`e744a940 ffffe58a`6774d800 : nt!KiRetireDpcList+0x440
fffff803`e8d45c60 00000000`00000000 : fffff803`e8d46000 fffff803`e8d40000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb
THREAD_SHA1_HASH_MOD_FUNC:  d71430fcaa3af92dfbf2aa947d89648abf6925a7
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e78da993d4c9d151971b5b07de2972fa2def4c75
THREAD_SHA1_HASH_MOD:  a1796d30e61453b9ecde348cbe3607e17f5d61c3
FOLLOWUP_IP:
nvlddmkm+e04c3
fffff80e`28a504c3 488b4df7        mov     rcx,qword ptr [rbp-9]
FAULT_INSTR_CODE:  f74d8b48
SYMBOL_STACK_INDEX:  9
SYMBOL_NAME:  nvlddmkm+e04c3
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  584d9744
BUCKET_ID_FUNC_OFFSET:  e04c3
FAILURE_BUCKET_ID:  0x133_DPC_nvlddmkm!unknown_function
BUCKET_ID:  0x133_DPC_nvlddmkm!unknown_function
PRIMARY_PROBLEM_CLASS:  0x133_DPC_nvlddmkm!unknown_function
TARGET_TIME:  2016-12-28T09:37:38.000Z
OSBUILD:  14393
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:  2016-12-09 18:23:02
BUILDDATESTAMP_STR:  161208-2252
BUILDLAB_STR:  rs1_release_inmarket
BUILDOSVER_STR:  10.0.14393.576.amd64fre.rs1_release_inmarket.161208-2252
ANALYSIS_SESSION_ELAPSED_TIME: 463
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x133_dpc_nvlddmkm!unknown_function
FAILURE_ID_HASH:  {15c3af0e-5564-7a80-2e26-65b5115ecc4d}
Followup:     MachineOwner
---------
https://windowsforum.kr/qna/8157555 홈으로 위로 목록
홈으로 위로 목록
홈으로 위로 목록
XE1.11.6 Layout1.4.8