電腦在運行遊戲時候無故黑屏無反應, 已經重設Window一次, 但仍再次發生

更新 - 2023 JUNE 2 0833

運行最新暗黑破壞神4時又再出現黑屏。

更新 - 2023 JUNE 2 0258

我在網上找到一個方法

NVIDIA控制面板->管理3D設定->廣域設定->執行緒最佳化->關閉

改用這個設定後，電腦能夠順利運行「霍格華茲的傳承」超過20分鐘而無出現黑屏

以下為設定的截圖

我不清楚解決的原因

亦不確定這是暫時性，還是已解決了問題

如果有人有同樣的情況，可以先嘗試這個方法。

萬一黑屏情況繼續發生，我會回來這邊報告。

謝謝!

社群的大家好，我的電腦在運行遊戲時，無論是需求較高的「霍格華茲的傳承」，抑或是需求較低的「英雄聯盟」，都會隨機發生黑屏的情況，所有按鍵失靈，只有散熱風扇繼續運作。

我在數天前曾經重設Window，重新安裝顯示卡驅動程式，當時再次運行「霍格華茲的遺產」20分鐘後無發生任何問題。直到今晚，我在運行「英雄聯盟」首次黑屏，重啟電腦後，運行「霍格華茲的遺產」約5分鐘後黑屏。

Event Viewer中找到以下錯誤訊息：

電腦已經在檢查錯誤後重新啟動。檢查的錯誤是: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8071231c340, 0x0000000000000000)。傾印的資料已儲存於: C:\WINDOWS\MEMORY.DMP。報告識別碼: 18e67f78-06e3-439b-8b18-60f47ca41113。

MEMORY.DMP為一個容量達2.41GB的檔案。

我亦在 C:\Windows\Minidump 中找到 .dmp檔案，用WinDbg打開後複製了以下內容：

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false

   - Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

************* Waiting for Debugger Extensions Gallery to Initialize **************
.
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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

Loading Dump File [C:\Users\sheka\Desktop\060223-7843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff807`11600000 PsLoadedModuleList = 0xfffff807`122134d0
Debug session time: Fri Jun  2 00:16:28.564 2023 (UTC + 8:00)
System Uptime: 0 days 0:14:51.251
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`11a2c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd781`6b4bccd0=0000000000000133
2: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8071231c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 999

    Key  : Analysis.Elapsed.mSec
    Value: 7901

    Key  : Analysis.IO.Other.Mb
    Value: 9

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 28

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8071231c340

BUGCHECK_P4: 0

FILE_IN_CAB:  060223-7843-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff88bafc5ee30 -- (.trap 0xfffff88bafc5ee30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff88bafc5f150
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8073d04b3a0 rsp=fffff88bafc5efc0 rbp=0000000000000005
 r8=000000000000001b  r9=0000000000000003 r10=00000000ffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nvlddmkm+0xab3a0:
fffff807`3d04b3a0 eb98            jmp     nvlddmkm+0xab33a (fffff807`3d04b33a)
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffd781`6b4bccc8 fffff807`1189baf1     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`1231c340 : nt!KeBugCheckEx
ffffd781`6b4bccd0 fffff807`1189b36c     : 000002f1`ee628572 00000000`0000ded0 00000000`0000decf 00000000`00000202 : nt!KeAccumulateTicks+0x231
ffffd781`6b4bcd30 fffff807`11899421     : 00000000`00000000 ffffd781`6c149900 ffffd781`6b4a2180 00000000`00000000 : nt!KiUpdateRunTime+0xcc
ffffd781`6b4bcea0 fffff807`11898e39     : fffff807`1225fdc0 ffffd781`6c149970 ffffd781`6c149970 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
ffffd781`6b4bcf40 fffff807`11920c6c     : 00000002`1351ffeb ffffe78c`1f35c200 ffffe78c`1f35c2b0 00000000`00000000 : nt!HalpTimerClockInterrupt+0x109
ffffd781`6b4bcf70 fffff807`11a2e24a     : fffff88b`afc5eeb0 ffffe78c`1f35c200 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffd781`6b4bcfb0 fffff807`11a2eab7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff88b`afc5ee30 fffff807`3d04b3a0     : ffffe78c`46dcc000 00000000`00000000 ffffe78c`46eb4000 ffffe78c`46dcc000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff88b`afc5efc0 ffffe78c`46dcc000     : 00000000`00000000 ffffe78c`46eb4000 ffffe78c`46dcc000 00000000`00000000 : nvlddmkm+0xab3a0
fffff88b`afc5efc8 00000000`00000000     : ffffe78c`46eb4000 ffffe78c`46dcc000 00000000`00000000 fffff807`3d04b244 : 0xffffe78c`46dcc000

SYMBOL_NAME:  nvlddmkm+ab3a0

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  ab3a0

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

請問各位，這是硬體問題，還是軟件的問題? 電腦基本資訊：
OS: Windows 11 家用版

CPU: 12th Gen Intel(R) Core(TM) i7-12700K 3.60 GHz

Display Card: RTX 3080

謝謝。