Hello Warthunder Team. You have a serious bug that leads to a BSOD in “War Thunder”. This error occurs when starting the game in the loading screen. I was able to rule out all errors in my hardware. I then read out the memorydumb file. There I was given the following result.
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: 000000000000a000, The subtype of the BugCheck:
Arg2: ffffad035faa2950
Arg3: 0000000000000000
Arg4: 0000000000000001
Debugging Details:
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3124
Key : Analysis.Elapsed.mSec
Value: 12023
Key : Analysis.IO.Other.Mb
Value: 24
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 30
Key : Analysis.Init.CPU.mSec
Value: 1452
Key : Analysis.Init.Elapsed.mSec
Value: 80955
Key : Analysis.Memory.CommitPeak.Mb
Value: 110
Key : Bugcheck.Code.LegacyAPI
Value: 0x119
Key : Bugcheck.Code.TargetModel
Value: 0x119
Key : Failure.Bucket
Value: 0x119_a000_VIDSCH_RESET_HW_ENGINE_SUSPEND_dxgmms2!VidSchiResetHwEngine
Key : Failure.Hash
Value: {95884248-9389-91d4-05c4-d0b1411f9702}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 119
BUGCHECK_P1: a000
BUGCHECK_P2: ffffad035faa2950
BUGCHECK_P3: 0
BUGCHECK_P4: 1
FILE_IN_CAB: 060724-6687-01.dmp
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffe8237f37638 fffff80756a33ad0 : 0000000000000119 000000000000a000 ffffad035faa2950 0000000000000000 : nt!KeBugCheckEx
fffffe8237f37640 fffff8075655c0eb : ffffad0360d6b010 ffffad035ddde000 ffffad035ddde000 ffffad035dda8000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe8237f37680 fffff807565f028e : ffffad035ddde001 0000000000000000 ffffad035ddde000 fffffe8237f37908 : dxgmms2!VidSchiResetHwEngine+0x6ab
fffffe8237f37830 fffff807565c49db : ffffad035dda8000 0000000000000001 0000000000000000 0000000000000000 : dxgmms2!VidSchiResetEngines+0xaa
fffffe8237f37880 fffff807565a0412 : fffffe8237f37901 000000000016b8dd 0000000000989680 0000000000000001 : dxgmms2!VidSchiCheckHwProgress+0x2459b
fffffe8237f378f0 fffff8075652b3aa : 0000000000000000 ffffad035dda8000 fffffe8237f37a19 0000000000000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
fffffe8237f379c0 fffff807565af475 : ffffad035dd82400 ffffad035dda8000 ffffad035dd824a0 ffffad035de4e620 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
fffffe8237f37a80 fffff807565af42a : ffffad035dda8400 fffff807565af360 ffffad035dda8000 ffffda01828a6100 : dxgmms2!VidSchiRun_PriorityTable+0x35
fffffe8237f37ad0 fffff8073e948c55 : ffffad035dd44080 fffff80700000001 ffffad035dda8000 000fa4efbd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffffe8237f37b10 fffff8073ea068f8 : ffffda01828a6180 ffffad035dd44080 fffff8073e948c00 046b7b30fffffff8 : nt!PspSystemThreadStartup+0x55
fffffe8237f37b60 0000000000000000 : fffffe8237f38000 fffffe8237f31000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiResetHwEngine+6ab
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.4474
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 6ab
FAILURE_BUCKET_ID: 0x119_a000_VIDSCH_RESET_HW_ENGINE_SUSPEND_dxgmms2!VidSchiResetHwEngine
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {95884248-9389-91d4-05c4-d0b1411f9702}
Followup: MachineOwner