电脑蓝屏

[dongxinnian]

每次打开英雄联盟，一会电脑屏幕就卡死，然后蓝屏，蓝屏代码VIDEO-SCHEDULER-INTERNAL_ERROR

[WDH]

建议更换不同版本显卡驱动测试，找到一个适合的不一定就是最新的驱动。

[dongxinnian]

有的时候可以用，关机了一次，就又不行了

[hlin]

先将系统检测更新到最新版，然后卸载所有带有优化和清理功能的第三方软件，然后将游戏也卸载掉，再卸载重装一下显卡驱动，用GeForce experience下载安装，安装的时候选择自定义安装，勾选执行清洁安装，然后重装游戏，看一下是否还会蓝屏。

[dongxinnian]

还是会出现蓝屏，重装之后，是好的，然后关了一下机，打开又不行了。除了玩游戏，其他使用电脑的时候一切正常

[dongxinnian]

这是蓝屏文件

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


Loading Dump File [C:\Windows\Minidump\020322-12359-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`81c00000 PsLoadedModuleList = 0xfffff800`8282a1b0
Debug session time: Thu Feb  3 12:32:01.456 2022 (UTC + 8:00)
System Uptime: 0 days 0:27:31.293
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 -vnt!KeBugCheckEx:
fffff800`81ff73b0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa48f`7db47790=0000000000000119
3: 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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffffa48f7db47860
Arg4: ffff930fe72b3c90

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2280

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 23166

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

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

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


FILE_IN_CAB:  020322-12359-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffffa48f7db47860

BUGCHECK_P4: ffff930fe72b3c90

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffa48f`7db47788 fffff800`9d9c3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffa48f`7db47860 : nt!KeBugCheckEx
ffffa48f`7db47790 fffff800`a0268399     : ffff930f`e72b0000 00000000`c000000d ffffa48f`7db47899 00000000`00000003 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffa48f`7db477d0 fffff800`a02e4b9d     : ffff930f`00000000 ffff930f`e72b3c90 ffff930f`e71c5000 ffff930f`edc8b880 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
ffffa48f`7db47900 fffff800`a02ed51a     : ffff930f`edc8b880 ffff930f`c82bf200 00000000`00000000 fffff800`a02ed2c0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffa48f`7db47a80 fffff800`a02ed38a     : ffff930f`e71c5400 fffff800`a02ed2c0 ffff930f`e71c5000 fffff800`7f855100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffa48f`7db47ad0 fffff800`81f55a05     : ffff930f`e71c8280 fffff800`00000001 ffff930f`e71c5000 000fa4ef`b59bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffffa48f`7db47b10 fffff800`81ffea08     : fffff800`7f855180 ffff930f`e71c8280 fffff800`81f559b0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x55
ffffa48f`7db47b60 00000000`00000000     : ffffa48f`7db48000 ffffa48f`7db41000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+a99

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1490

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  a99

FAILURE_BUCKET_ID:  0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9a11bf9c-270e-962e-7a82-3efdab93c10e}

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