Can anyone help me resolve this issue? I am not a very tech savvy guy. Computer will crash after first start up soon after I start up my game. After it BSODs and restarts, no further issues. Computer is still usable but this is very frustrating. Thanks in advance.
Loading Dump File [C:\Windows\Minidump\120822-9421-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 22000 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff80150e00000 PsLoadedModuleList = 0xfffff801
51a297b0
Debug session time: Thu Dec 8 18:00:32.582 2022 (UTC - 5:00)
System Uptime: 28 days 23:50:44.894
Loading Kernel Symbols
...............................................................
................................................................
..............................................................
Loading User Symbols
Loading unloaded module list
.......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8015121acf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801
4db946f0=0000000000000133
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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80151b05330, 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: 2280
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4312
Key : Analysis.IO.Other.Mb
Value: 12
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 34
Key : Analysis.Init.CPU.mSec
Value: 827
Key : Analysis.Init.Elapsed.mSec
Value: 78104
Key : Analysis.Memory.CommitPeak.Mb
Value: 107
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.KiBugCheckData
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
FILE_IN_CAB: 120822-9421-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80151b05330
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8014db94d00 -- (.trap 0xfffff8014db94d00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff801511b2b00 rbx=0000000000000000 rcx=000000000000188e
rdx=000000000000188e rsi=0000000000000000 rdi=0000000000000000
rip=fffff801511b2bf9 rsp=fffff8014db94e98 rbp=ffffe405f21e9bb0
r8=fffff8014db94f10 r9=0000000000000001 r10=fffff801511b2bf0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!HalpAcpiPmRegisterReadPort+0x9:
fffff801511b2bf9 418800 mov byte ptr [r8],al ds:fffff801
4db94f10=00
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff8014db94e98 fffff801
511b1eb9 : ffffe405f0a14d50 00000000
00000d90 ffffe4060003cdc0 00000000
00000000 : nt!HalpAcpiPmRegisterReadPort+0x9
fffff8014db94ea0 fffff801
53f1ff22 : 000000000000000e 00000000
00000f43 0000000000000000 fffff801
5102f1bd : nt!HalpAcpiPmRegisterRead+0x39
fffff8014db94ed0 fffff801
53f57eb0 : 0000000000000000 ffff8680
befe3dc0 fffff8016a9d0c90 00000000
0000b201 : ACPI!ACPIReadGpeStatusRegister+0x66
fffff8014db94f10 fffff801
5100d3de : ffff8680befe3dc0 ffff8680
befe3e70 ffff8680befe3330 fffff801
5121c510 : ACPI!ACPIInterruptServiceRoutine+0x50
fffff8014db94f50 fffff801
5121c67f : fffff8014db84d90 ffff8680
befe3dc0 0000000000000001 ffffe406
0003cdc0 : nt!KiCallInterruptServiceRoutine+0x1ae
fffff8014db94f90 fffff801
5121c947 : ffffe405fe769050 fffff801
7a1fda8d ffffe405fe769050 fffff801
79e95edf : nt!KiInterruptSubDispatch+0x11f
fffff8014db84d10 fffff801
5110fd3c : fffff801500f0942 00000000
00000002 ffffe4060003c6e0 00000000
00000002 : nt!KiInterruptDispatch+0x37
fffff8014db84ea8 fffff801
500f0942 : 0000000000000002 ffffe406
0003c6e0 0000000000000002 fffffff6
00000002 : nt!KzRaiseIrql+0xc
fffff8014db84eb0 fffff801
500efd95 : ffffe4060003c000 ffffe406
06ece290 0000000000000000 fffff801
4db85170 : dxgmms2!VidSchiSignalRegisteredEvent+0x32
fffff8014db84f00 fffff801
500ef6f4 : fffff8014db85170 00000000
00000001 0000000000000005 ab6ebaa6
daff4801 : dxgmms2!VidSchiUnreferenceDisplayingAllocations+0x205
fffff8014db84fc0 fffff801
500ef380 : 0000000000000000 00000000
00000000 0000000000000000 00000000
00000000 : dxgmms2!VidSchiUnreferenceDisplayingAllocationsForThisEntry+0x20
fffff8014db84ff0 fffff801
500e3f12 : 0000000000001ae0 fffff801
00000001 fffff8014db852d0 fffff801
4db85150 : dxgmms2!VidSchiProcessVsyncCompletedFlipEntry+0x140
fffff8014db850d0 fffff801
500e53ec : 0000000000000000 00000470
90ba6d73 ffff8680befe3330 00000000
00040488 : dxgmms2!VidSchiProcessDpcVSyncCookie+0x632
fffff8014db85360 fffff801
6a97e9aa : ffffe405fc2df030 fffff801
4db85449 ffffe405fc3b7520 fffff801
510b644d : dxgmms2!VidSchDdiNotifyDpc+0x20c
fffff8014db853d0 fffff801
79e428f9 : ffffe405fc2df030 00000000
00000000 ffffe405fc2df030 ffffe405
fc3b4000 : dxgkrnl!DxgNotifyDpcCB+0x9a
fffff8014db854b0 ffffe405
fc2df030 : 0000000000000000 ffffe405
fc2df030 ffffe405fc3b4000 fffff801
79e4287e : nvlddmkm+0x628f9
fffff8014db854b8 00000000
00000000 : ffffe405fc2df030 ffffe405
fc3b4000 fffff80179e4287e ffffe405
fc3b4000 : 0xffffe405`fc2df030
STACK_COMMAND: .trap 0xfffff8014db94d00 ; kb
SYMBOL_NAME: dxgmms2!VidSchiSignalRegisteredEvent+32
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.22000.975
BUCKET_ID_FUNC_OFFSET: 32
FAILURE_BUCKET_ID: 0x133_ISR_dxgmms2!VidSchiSignalRegisteredEvent
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ccb28f05-8512-6d18-e82b-1931141c0514}
Followup: MachineOwner
---------