Windows 10: Can any one please help me out with this issue VIDEO_SCHEDULER_INTERNAL_ERROR.

Hello everyone,

I got this issue VIDEO_SCHEDULER_INTERNAL_ERROR after updating my windows since then blue screen appears and my laptop restarts. The mentioned issue appears when ever i launch a game so i clean install my laptop with the version windows 10 home 64 bit version. After clean installation when i install all the other required applications i installed steam and as well. Again the issue started appearing on my screen i have been trying all the way since three days by doing hardware checks and reinstalling display drivers as mentioned but there is no use. I'm pasting the Bug check Analysis report as well my laptop information.

Please guide me step by step.

Thanks in advance!!








Microsoft (R) Windows Debugger Version 10.0.18362.1 X86

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\stdj2\Desktop\101919-33484-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 18362 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff807`3de00000 PsLoadedModuleList = 0xfffff807`3e248210

Debug session time: Sat Oct 19 11:42:33.462 2019 (UTC + 5:30)

System Uptime: 0 days 14:06:32.366

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

2: 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: ffffed8857aca960

Arg4: ffffc9074e8089d0



Debugging Details:

------------------





KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 10.0.18362.418 (WinBuild.160101.0800)



DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump



DUMP_TYPE: 2



BUGCHECK_P1: 2



BUGCHECK_P2: ffffffffc000000d



BUGCHECK_P3: ffffed8857aca960



BUGCHECK_P4: ffffc9074e8089d0



CPU_COUNT: 4



CPU_MHZ: a22



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 45



CPU_STEPPING: 1



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



BUGCHECK_STR: 0x119



PROCESS_NAME: System



CURRENT_IRQL: 0



ANALYSIS_SESSION_HOST: DESKTOP-GDLC82N



ANALYSIS_SESSION_TIME: 10-19-2019 13:58:11.0171



ANALYSIS_VERSION: 10.0.18362.1 x86fre



LAST_CONTROL_TRANSFER: from fffff807554841a0 to fffff8073dfc1220



STACK_TEXT:

ffffed88`57aca888 fffff807`554841a0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffed88`57aca960 : nt!KeBugCheckEx

ffffed88`57aca890 fffff807`5bfaabf8 : 00000000`00000000 ffffc907`4e805000 ffffed88`57aca999 ffffc907`4e805000 : watchdog!WdLogEvent5_WdCriticalError+0xe0

ffffed88`57aca8d0 fffff807`5c008684 : ffffc907`00000000 ffffc907`4e8089d0 ffffc907`4e7c0000 ffffc907`547db930 : dxgmms2!VidSchiSendToExecutionQueue+0x14a08

ffffed88`57acaa00 fffff807`5c019ad5 : ffffc907`4e7b69a0 ffffc907`4e7c0000 00000000`00000000 ffffc907`4e81f620 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4

ffffed88`57acab80 fffff807`5c01994a : ffffc907`4e7c0400 fffff807`5c019880 ffffc907`4e7c0000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175

ffffed88`57acabd0 fffff807`3df2a725 : ffffc907`4e7b5080 fffff807`00000001 ffffc907`4e7c0000 00002425`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca

ffffed88`57acac10 fffff807`3dfc886a : fffff807`3c869180 ffffc907`4e7b5080 fffff807`3df2a6d0 734a7a54`e505762d : nt!PspSystemThreadStartup+0x55

ffffed88`57acac60 00000000`00000000 : ffffed88`57acb000 ffffed88`57ac5000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a





THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2831a16f72eb580b94422779b5b1b484064cfb6f



THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4



FOLLOWUP_IP:

dxgmms2!VidSchiSendToExecutionQueue+14a08

fffff807`5bfaabf8 cc int 3



FAULT_INSTR_CODE: b60f41cc



SYMBOL_STACK_INDEX: 2



SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14a08



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: dxgmms2



IMAGE_NAME: dxgmms2.sys



DEBUG_FLR_IMAGE_TIMESTAMP: 0



IMAGE_VERSION: 10.0.18362.418



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 14a08



FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue



BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue



PRIMARY_PROBLEM_CLASS: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue



TARGET_TIME: 2019-10-19T06:12:33.000Z



OSBUILD: 18362



OSSERVICEPACK: 418



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 784



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: unknown_date



BUILDDATESTAMP_STR: 160101.0800



BUILDLAB_STR: WinBuild



BUILDOSVER_STR: 10.0.18362.418



ANALYSIS_SESSION_ELAPSED_TIME: 3b7b



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue



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



Followup: MachineOwner

---------

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

help to remote connect

not sure how to use both programs u 2 suggested, i need more helpful steps thanks

 

Edge Search Does Not Permit Change of Region


I got these suggestions from the Microsoft Community forum.No. 1 worked for me:

Thank you for posting the query on Microsoft Community. I am glad to assist you on this.
We have reproduce the issue here and we are able to access non-regional search for google using Microsoft Edge.
I would suggest you to try the below steps and check if it helps.
Step 1:
Clear browsing data option of Microsoft Edge and check if you face the issue. To do so perform the steps below.

1. Click on the More actions icon next to the feedback icon present on top right corner of the Project Spartan homepage.
2. Select Settings and click on Choose what to clear.
3. Check the boxes Browsing history, Cookies and saved website data and Cached data and files and click on Clear.

Step 2:
I suggest you to create a new user account and check if the issue occurs.

1. Go to Settings.
2. Choose Accounts and then select Family and other users.
3. Select add someone else on this PC.
4. Enter a user name and hit next.
5. Click on Finish.
6. Sign out from the current Account and Log into the new account.

Step 3:
It could also happen because of network issue. I suggest you to try with different network connection and check if it helps.