How to fix Video Scheduler Internal Error (BSOD)

Keneth 0

Hello, my laptop has been freezing and entering the BSOD when using the browser and some games. I tried a clean install of my graphics card and it still has the error. All drivers updated. I've been trying to fix it for 2 months.
My laptop is a Lenovo with Nvidia GTX 1050 and Intel Core i5 8300H CPU, and Intel UHD 630 IGPU. Windows 11.
I haven't had any problems playing and crashing last year. This happens most frequently with Genshin Impact, it freezes on the seizure warning and closes to BSOD. I want to add my minidump file here but i dont know how to.
How do i fix this??

2 answers

Wesley Li 5,170 Reputation points

2024-05-10T15:58:26.14+00:00

Hello,

What is the specific error code for BSOD?

The QA forum cannot add minidump files, but you can take screenshots or copy them here.
Please sign in to rate this answer.
Keneth 0 Reputation points

2024-05-10T16:05:57.67+00:00

Hello! Here is the file dump.

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: 0000000000000005, The subtype of the BugCheck:

Arg2: ffffbf847a0ef000

Arg3: ffffbf8476803010

Arg4: 0000000000003de2

Debugging Details:

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec Value: 1936 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 152515 Key : Analysis.Init.CPU.mSec Value: 499 Key : Analysis.Init.Elapsed.mSec Value: 249587 Key : Analysis.Memory.CommitPeak.Mb Value: 110 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Timestamp Value: 2022-05-06T12:50:00Z Key : WER.OS.Version Value: 10.0.22621.1

FILE_IN_CAB: 051024-33796-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_CODE: 119

BUGCHECK_P1: 5

BUGCHECK_P2: ffffbf847a0ef000

BUGCHECK_P3: ffffbf8476803010

BUGCHECK_P4: 3de2

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: GenshinImpact.exe

DPC_STACK_BASE: FFFFF80428EC3FB0

STACK_TEXT:

fffff80428ec2098 fffff8044b225685 : 0000000000000119 0000000000000005 ffffbf847a0ef000 ffffbf8476803010 : nt!KeBugCheckEx

fffff80428ec20a0 fffff8043131b11b : fffff80428ec230a ffffbf84697ff3a0 ffffbf84697ff3a8 ffffbf84697ff3b0 : watchdog!WdLogSingleEntry5+0x3b45

fffff80428ec2150 fffff804313047ef : ffffbf8479b5f000 ffffbf847a0ef000 fffff80428ec2410 ffffbf847a0ef000 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x25f

fffff80428ec21d0 fffff804312edb0d : 0000000000003de2 fffff8046e802690 ffffbf8479b5f000 0000000000000006 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x16b3f

fffff80428ec2250 fffff8044ad9fdb5 : ffffbf847a8e8030 ffffbf845fc023b9 a0c89468663de8e2 0000c06fc0000648 : dxgmms2!VidSchDdiNotifyInterrupt+0xcd

fffff80428ec22b0 fffff8046e82096f : ffffbf847a8e8030 ffffbf847b66a000 fffff8040000000e fffff80400000000 : dxgkrnl!DxgNotifyInterruptCB+0x95

fffff80428ec2320 ffffbf847a8e8030 : ffffbf847b66a000 fffff8040000000e fffff80400000000 fffff8046e8208f1 : nvlddmkm+0xba096f

fffff80428ec2328 ffffbf847b66a000 : fffff8040000000e fffff80400000000 fffff8046e8208f1 ffffbf847b66a000 : 0xffffbf84`7a8e8030

fffff80428ec2330 fffff8040000000e : fffff80400000000 fffff8046e8208f1 ffffbf847b66a000 0000000000000000 : 0xffffbf84`7b66a000

fffff80428ec2338 fffff80400000000 : fffff8046e8208f1 ffffbf847b66a000 0000000000000000 0000000000000000 : 0xfffff804`0000000e

fffff80428ec2340 fffff8046e8208f1 : ffffbf847b66a000 0000000000000000 0000000000000000 0000000000000000 : 0xfffff804`00000000

fffff80428ec2348 ffffbf847b66a000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nvlddmkm+0xba08f1

fffff80428ec2350 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 ffffbf847a8e8030 : 0xffffbf84`7b66a000

SYMBOL_NAME: nvlddmkm+ba096f

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: ba096f

FAILURE_BUCKET_ID: 0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_nvlddmkm!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {55a61c3c-91b1-e527-dcff-f2f0d7348227}

Followup: MachineOwner

Keneth 0 Reputation points

2024-05-10T16:08:01.3633333+00:00

Also this one,

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: ffff83886d2df010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff801ab7b8b40, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvltig.inf_amd64_00cc3a692c57c34d\nvlddmkm.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for nvlddmkm.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec Value: 3265 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 84652 Key : Analysis.Init.CPU.mSec Value: 358 Key : Analysis.Init.Elapsed.mSec Value: 18144 Key : Analysis.Memory.CommitPeak.Mb Value: 108 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Timestamp Value: 2022-05-06T12:50:00Z Key : WER.OS.Version Value: 10.0.22621.1 ```FILE_IN_CAB: 051024-32562-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: 116 BUGCHECK_P1: ffff83886d2df010 BUGCHECK_P2: fffff801ab7b8b40 BUGCHECK_P3: ffffffffc000009a BUGCHECK_P4: 4 VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff83886d2df010 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: 0000000000000004 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffff818c`d56cf768 fffff801`9650c5ae : 00000000`00000116 ffff8388`6d2df010 fffff801`ab7b8b40 ffffffff`c000009a : nt!KeBugCheckEx ffff818c`d56cf770 fffff801`964be1b2 : fffff801`ab7b8b40 ffff8388`6376d6a0 00000000`00000080 ffff8388`6376d760 : dxgkrnl!TdrBugcheckOnTimeout+0xfe ffff818c`d56cf7b0 fffff801`964b6659 : ffff8388`63774000 ffff8388`64e51040 ffff8388`63774b50 ffff8388`63774b50 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a ffff818c`d56cf7e0 fffff801`9650bd05 : 00000000`37980100 ffff8388`64e51040 00000000`00000000 fffff801`77ec16e0 : dxgkrnl!DXGADAPTER::Reset+0x60d ffff818c`d56cf890 fffff801`9650be62 : 00000000`00000000 fffff801`7b613c40 ffff8388`4f0fd000 fffff801`7b749ac0 : dxgkrnl!TdrResetFromTimeout+0x15 ffff818c`d56cf8c0 fffff801`7acd6dd5 : ffff8388`64e51040 ffff8388`4f0aec50 ffff8388`00000000 ffff8388`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22 ffff818c`d56cf900 fffff801`7ad6d937 : ffff8388`64e51040 00000000`00000b72 ffff8388`64e51040 fffff801`7acd6c80 : nt!ExpWorkerThread+0x155 ffff818c`d56cfaf0 fffff801`7ae1d1b4 : fffff801`744bc180 ffff8388`64e51040 fffff801`7ad6d8e0 00000000`00000000 : nt!PspSystemThreadStartup+0x57 ffff818c`d56cfb40 00000000`00000000 : ffff818c`d56d0000 ffff818c`d56c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nvlddmkm+1498b40 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd} Followup: MachineOwner --------- ADDITIONAL INFO: My laptop is a lenovo originally windows 10, i recently updated it to windows 11. Incase thats the reason for the errors.
Sign in to comment
Docs 15,151 Reputation points

2024-05-10T18:00:56.51+00:00

Please run the V2 log collector and post a share link using drop box, or google drive.

BSOD - Posting Instructions - Windows 10 Forums (tenforums.com)

BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)

Make sure that links are available without sign in.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Share via

How to fix Video Scheduler Internal Error (BSOD)

2 answers