Job스러운생각
BSOD 프리징 현상. 게임하다 괜히 꺼지는 현상 추적
Stockcamper
2025. 4. 12. 22:43
그놈의 dune을 보지 말았어야 했다
괜히 dune게임을 해보겠다고 며칠 빠져서 해보다가
한번씩 꺼지는 문제 때문에 이거저거 하다보니 이력이 꽤나 쌓였다
dune spice war게임 중 30분에 한번씩 프리징, 재부팅 현상 발생
얘만 그런가보다 했는데 commandos origin에서도 동일 증상.
처음엔 그냥 껐다켰다 반복하다가 해외사례를 검색해보니 OpenGL오류로 의심되어 directX로 변경해보라 함
런타임 설치해봤으나 시간이 조금 바뀔 뿐. 다시 멈춤
모니터를 1에서 2로 변경하니 증상이 완화됨
그래도 한번 멈추면 해결안됨
전체 성능을 low로 변경하니 조금 나아짐
그래도 1~2시간 즐기면 멈춤
메모리 덤프만 떠질 뿐, 이벤트 뷰어에는 표시되지 않음
windows에서 dump로 만든 memory.dmp의 분석내용
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 43
Microsoft (R) Windows Debugger Version 10.0.27793.1000 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.
Primary dump contents written successfully
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 26100.1.amd64fre.ge_release.240331-1435
Kernel base = 0xfffff804`d0600000 PsLoadedModuleList = 0xfffff804`d14f49c0
Debug session time: Thu Apr 10 15:24:21.244 2025 (UTC + 9:00)
System Uptime: 0 days 0:18:49.960
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`d0ab5520 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff980f`a7ecf810=0000000000000116
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe6861d51e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8047c5b4930, 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 \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9d15b9aa9e1c885b\nvlddmkm.sys, Win32 error 0n2
Page 13d230 not present in the dump file. Type ".hh dbgerr004" for details
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1437
Key : Analysis.Elapsed.mSec
Value: 2851
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 3
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 796
Key : Analysis.Init.Elapsed.mSec
Value: 1150410
Key : Analysis.Memory.CommitPeak.Mb
Value: 109
Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000
Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre
Key : Analysis.Version.Ext
Value: 1.2410.2.2
Key : Bugcheck.Code.KiBugCheckData
Value: 0x116
Key : Bugcheck.Code.LegacyAPI
Value: 0x116
Key : Bugcheck.Code.TargetModel
Value: 0x116
Key : Dump.Attributes.AsUlong
Value: 0x21800
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 100
Key : Failure.Bucket
Value: 0x116_IMAGE_nvlddmkm.sys
Key : Failure.Exception.IP.Address
Value: 0xfffff8047c5b4930
Key : Failure.Exception.IP.Module
Value: nvlddmkm
Key : Failure.Exception.IP.Offset
Value: 0x1874930
Key : Failure.Hash
Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84
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: 55185662
Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe
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: 0x3f7
Key : SecureKernel.HalpHvciEnabled
Value: 1
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffe6861d51e010
BUGCHECK_P2: fffff8047c5b4930
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
FILE_IN_CAB: MEMORY.DMP
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21800
FAULTING_THREAD: ffffe686017ed380
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe6861d51e010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000004
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff980f`a7ecf808 fffff804`625815ad : 00000000`00000116 ffffe686`1d51e010 fffff804`7c5b4930 ffffffff`c000009a : nt!KeBugCheckEx
ffff980f`a7ecf810 fffff804`6280657e : fffff804`7c5b4930 ffffe685`f5529010 00000000`00002000 ffffe685`f55290d0 : dxgkrnl!TdrBugcheckOnTimeout+0x101
ffff980f`a7ecf850 fffff804`625903dd : ffffe685`f5526000 00000000`00000000 00000000`00000004 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a
ffff980f`a7ecf880 fffff804`625c6ac5 : ffff8081`5ec50180 ffffe686`017ed380 ffffe686`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x589
ffff980f`a7ecf910 fffff804`625c6c22 : ffffe685`ee509260 ffffe685`e85bc9f0 00000000`00000000 ffffe685`e85a8000 : dxgkrnl!TdrResetFromTimeout+0x15
ffff980f`a7ecf940 fffff804`d093bf92 : ffffe686`017ed380 ffffe685`e8624c20 ffffe685`e8624c00 ffffe685`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffff980f`a7ecf980 fffff804`d0a4d1fa : ffffe686`017ed380 ffffe686`017ed380 fffff804`d093bde0 ffffe685`e8624c20 : nt!ExpWorkerThread+0x1b2
ffff980f`a7ecfb30 fffff804`d0c7ca94 : ffff8081`5efc1180 ffffe686`017ed380 fffff804`d0a4d1a0 ffffab09`22cc8c10 : nt!PspSystemThreadStartup+0x5a
ffff980f`a7ecfb80 00000000`00000000 : ffff980f`a7ed0000 ffff980f`a7ec9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: nvlddmkm+1874930
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .process /r /p 0xffffe685e84d3040; .thread 0xffffe686017ed380 ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
이 내용을 토대로 보면
nvlddmkm.sys의 문제인데
그래픽카드 문제로 의심되나 다른 게임에선 문제없음.
유사사례를 검색하면 nvidia의 문제 혹은 cuda의 문제, 케이블 문제 등이 의심됨
하나씩 테스트 해야
PCI express의 최대절전을 최대 성능으로 변경하는 것부터 테스트했는데 효과없음
DDU로 그래픽카드를 완전 제거 후
DP케이블 빼고 HDMI로만 실행
그래픽카드 제거, 청소,
램제거, 청소
그래픽카드 PCI express파워선 괜히 좌우 변경
현재는 이렇게 5가지를 했더니 일단 안 멈춤
5가지를 하나씩 했어야 했는데 동시에 해서 원인을 나중에 못찾을까 우려듬
그냥 메모용으로 포스팅
반응형