Windows 10 Black Screen Crashes

[DELETED11152024]

System Manufacturer?
Custom built PC
Laptop or Desktop?
Desktop
Exact model number (if laptop, check label on bottom)
n/a
OS ? (Windows 10, 8.1, 8, 7, Vista)
Windows 10
x86 (32bit) or x64 (64bit)?
64bit
(Only for Vista, Windows 7) Service pack?
n/a
What was original installed OS on system?
Windows 10.
Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Windows 10 installation media I created. So I'm unsure.
Age of system? (hardware)
Less than 1 year for all components.
Age of OS installation?
Reinstalled many times troubleshooting. So not very old.
Have you re-installed the OS?
Yes.
CPU
Ryzen 7 5800x and Ryzen 5 3600
RAM (brand, EXACT model, what slots are you using?)
Crucial Ballistix 32GB Kit (2x16GB) 3600 BL2K16G36C16U4B-M16FE
Both slots (only two available, ITX board)
Video Card
Nvidia RTX 3070 Founder Edition
MotherBoard - (if NOT a laptop)
Gigabyte B550i Aorus Pro Ax (rev 1.0)
Power Supply - brand & wattage (if laptop, skip this one)
Corsair SF750 Platinum
Is driver verifier enabled or disabled?
Disabled
What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
Windows defender, malwarebytes, spybot
Are you using proxy, vpn, ipfilters or similar software?
No
Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
No
Are you currently under/overclocking? Are there overclocking software installed on your system?
Only changed the ram speed with XMP profile. PC still crashes even at stock ram configuration. Other bios settings are stock.

 

[DELETED11152024]

http://speccy.piriform.com/results/YLDom1wP0j3sNapY3AXX6hS

 

[Enes3078]

Hi, can you uninstall your display driver via DDU? There is a guide for usage: Utilizing DDU Display Driver Uninstaller Properly

After that don't forget to setup your last GPU driver from NVIDIA.

Also, if you are using Razer's program, delete it.

*******************************************************************************
*                                                                             *
*                        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: ffff8e0ba6cba960
Arg4: ffffe38fc433f3d0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5093

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14562

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

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

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


FILE_IN_CAB:  031922-6406-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  119

BUGCHECK_P1: 2

BUGCHECK_P2: ffffffffc000000d

BUGCHECK_P3: ffff8e0ba6cba960

BUGCHECK_P4: ffffe38fc433f3d0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffff8e0b`a6cba888 fffff804`779b3ad0     : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8e0b`a6cba960 : nt!KeBugCheckEx
ffff8e0b`a6cba890 fffff804`79bd8399     : ffffe38f`c433c000 00000000`c000000d ffff8e0b`a6cba999 00000000`00000005 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8e0b`a6cba8d0 fffff804`79c54b9d     : ffffe38f`00000000 ffffe38f`c433f3d0 ffffe38f`c424b000 ffffe38f`d2eba010 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
ffff8e0b`a6cbaa00 fffff804`79c5d51a     : ffffe38f`d2eba010 ffffe38f`c424b000 00000000`00000000 ffffe38f`c4315620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff8e0b`a6cbab80 fffff804`79c5d38a     : ffffe38f`c424b400 fffff804`79c5d2c0 ffffe38f`c424b000 ffffcc81`48bc0100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff8e0b`a6cbabd0 fffff804`67355a15     : ffffe38f`c4256380 fffff804`00000001 ffffe38f`c424b000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff8e0b`a6cbac10 fffff804`673fec78     : ffffcc81`48bc0180 ffffe38f`c4256380 fffff804`673559c0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8e0b`a6cbac60 00000000`00000000     : ffff8e0b`a6cbb000 ffff8e0b`a6cb5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  dxgmms2!VidSchiSendToExecutionQueue+a99

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.1178

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
---------

 

[zbook]

Hi

N1NJA_HaMSTERS,​

Eleven days have passed since the opening post.

How is the computer performance?


Other computer problems were seen in the logs.

When available please update the status.