windbg分析蓝屏memory.dmp后显示video_scheduler_internal_error，如何解决？

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


Loading Dump File [C:\Windows\Minidump\050321-13812-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff807`72400000 PsLoadedModuleList = 0xfffff807`7302a3d0
Debug session time: Mon May  3 19:51:09.980 2021 (UTC + 8:00)
System Uptime: 0 days 0:02:54.045
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`727f5e40 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbc00`29f48f20=0000000000000119
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: 0000000000000e00, The subtype of the BugCheck:
Arg2: ffffbe0550c9a000
Arg3: ffffbe0550cd5620
Arg4: ffffbe0550cd5928

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4624

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14954

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

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

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  119

BUGCHECK_P1: e00

BUGCHECK_P2: ffffbe0550c9a000

BUGCHECK_P3: ffffbe0550cd5620

BUGCHECK_P4: ffffbe0550cd5928

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffbc00`29f48f18 fffff807`89483ad0     : 00000000`00000119 00000000`00000e00 ffffbe05`50c9a000 ffffbe05`50cd5620 : nt!KeBugCheckEx
ffffbc00`29f48f20 fffff807`89aea562     : ffffbe05`50c9a000 00000000`00000000 ffffbc00`29f49370 ffffbe05`52cda010 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffbc00`29f48f60 fffff807`89aeabd1     : ffffbe05`50cd5620 ffffbc00`29f49150 ffffbe05`57c46000 ffffbe05`50c9a000 : dxgmms2!VidSchiAllocatePacketFromGuaranteedPacketPool+0x11e
ffffbc00`29f48f90 fffff807`89aeaf70     : ffffbc00`29f49370 ffffbc00`00000000 ffffbc00`29f49150 ffffbe05`57c46000 : dxgmms2!VidSchiEnqueueDeviceCommandToWorkerThreadAtDpc+0x5d
ffffbc00`29f49050 fffff807`89adeda8     : 00000000`00000000 00000000`00001100 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiExecuteMmIoFlipMultiPlaneOverlay3+0x2a4
ffffbc00`29f491a0 fffff807`89acd1c7     : ffffbe05`50c9c048 00000000`00989680 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiExecuteMmIoFlip+0x10e28
ffffbc00`29f49c30 fffff807`89aececd     : ffffbc00`29f4a0c0 ffffbe05`50caa000 00000000`00000000 fffff807`00000001 : dxgmms2!VidSchUnwaitFlipQueue+0x507
ffffbc00`29f49cd0 fffff807`89ad7841     : ffffbc00`29f4a0c0 ffffbe05`571049b0 00000000`00000000 fffff807`00000000 : dxgmms2!VidSchiSubmitIndependentFlip+0x971
ffffbc00`29f49dc0 fffff807`89aefcc1     : 00000000`00000001 00000000`00000000 ffffbe05`563eaa20 ffffbe05`57c3e1c0 : dxgmms2!VidSchiProcessPresentHistoryToken+0x151b1
ffffbc00`29f49e90 fffff807`89af2061     : 00000000`00000000 ffffbc00`29f4a0c0 ffffbc00`29f4a0c0 ffffbe05`50c9a000 : dxgmms2!VidSchiFlushPendingTokenList+0xe9
ffffbc00`29f49ef0 fffff807`89ad9021     : ffffbe05`50c9a000 00000000`00000000 ffffbe05`57c3e1c0 ffffbe05`5238c1a0 : dxgmms2!VidSchiTryEnterIndependentFlip+0x3d
ffffbc00`29f49f20 fffff807`89aefa08     : ffffbc00`29f4a0c0 ffffbe05`57c3e218 00000000`00000000 ffffbe05`57c30000 : dxgmms2!VidSchiCompleteFlipEntry+0x15401
ffffbc00`29f4a050 fffff807`89b4d471     : ffffbe05`50f8aa00 ffffbe05`4dd6b950 ffffbe05`50d688c0 ffffbe05`50cd5620 : dxgmms2!VidSchiExecuteMmIoFlipAtPassiveLevel+0x368
ffffbc00`29f4aa80 fffff807`89b4d29a     : ffffbe05`50c9a400 fffff807`89b4d1d0 ffffbe05`50c9a000 ffffa381`6d2c0100 : dxgmms2!VidSchiRun_PriorityTable+0x1c1
ffffbc00`29f4aad0 fffff807`72717e85     : ffffbe05`50c943c0 fffff807`00000001 ffffbe05`50c9a000 000fa46f`b19bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffffbc00`29f4ab10 fffff807`727fd498     : ffffa381`6d2c0180 ffffbe05`50c943c0 fffff807`72717e30 00000000`80000002 : nt!PspSystemThreadStartup+0x55
ffffbc00`29f4ab60 00000000`00000000     : ffffbc00`29f4b000 ffffbc00`29f44000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiAllocatePacketFromGuaranteedPacketPool+11e

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.928

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11e

FAILURE_BUCKET_ID:  0x119_e00_UNKNOWN_dxgmms2!VidSchiAllocatePacketFromGuaranteedPacketPool

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {56d0fc26-28d6-4f29-b7c5-92f73ee710af}

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

0: kd> lmvm dxgmms2
Browse full module list
start             end                 module name
fffff807`89ac0000 fffff807`89ba1000   dxgmms2  # (pdb symbols)          C:\ProgramData\Dbg\sym\dxgmms2.pdb\E7143AD57C3B498C28DF28D3782E92D81\dxgmms2.pdb
    Loaded symbol image file: dxgmms2.sys
    Mapped memory image file: C:\ProgramData\Dbg\sym\dxgmms2.sys\338A6BFAe1000\dxgmms2.sys
    Image path: dxgmms2.sys
    Image name: dxgmms2.sys
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        338A6BFA (This is a reproducible build file hash, not a timestamp)
    CheckSum:         000E9F28
    ImageSize:        000E1000
    File version:     10.0.19041.928
    Product version:  10.0.19041.928
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms2.sys
        OriginalFilename: dxgmms2.sys
        ProductVersion:   10.0.19041.928
        FileVersion:      10.0.19041.928 (WinBuild.160101.0800)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.      HiIamDave,anIndependentAdvisor,Iwillhelpyouwiththis.YourprintoutindicatesitisthedevicedriveronyourvideocardthatiscausingthecrashesCompletelyuninstallyourvideocarddevicedriverswiththewidelyavailablefreeutilityDDURestartyourPC,thengotothesupportpageforyourPConthemanufacturerswebsite,thenformthere,downloadandinstalltheversionofvideocarddevicedriverstheyrecommend___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。