Solved Video Scheduler Internal Error black screen crashes

  • Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Welcome to our Community
Wanting to join the rest of our members? Feel free to sign up today.
Sign up
Status
Not open for further replies.

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
Hello, my pc is blackscreening after 5 to 10 mins into a game. VIDEO_SCHEDULER_INTERNAL_ERROR (119) is the minidump analysis on the crashes. However, most of the time the pc does not crash the game simply loops audio and the screens turn off. i am positive this is not a cable or monitor error. I will include a speccy link and all of the trouble shooting methods i have tried. Thx SPECCY: http://speccy.piriform.com/results/NIO5G1UKO2ANT5e13XrwFBJ

PC SPECS:
gpu nvidia 1070 asus turbo 8gb
cpu intel i5 7600k 3.8ghz
psu Corsair rm 650x gold 80 plus
ram 16gb 2x8
mobo asrock asrock 270m-itx/ac
storage 1tb hdd 240gb ssd
pc age 1 year 11 months


Attempted fixes:
Clean installing and trying diffent nvidia drivers with DDU
Changing game settings
Monitoring Temps
Updating all drivers
Checking clock speeds of gpu cpu
Verifying registry
checking for virus
reseating gpu
reinstalling windows 10
clearing cmos
reseating ram
updating mobo bios
installing new psu
running memtest
changing power settings
turning off xmp
 

Attachments

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
3,302
482
56
Welcome to PCHF vande096,

Stop any overclocking asap, the best way to do this is by restoring the MBs default factory settings in the BIOS.

We are going to have to do a bit of work here by the looks of things so the following for your information first.

Speccy info first;

Windows 10 Home 64-bit
Computer type: Desktop
Installation Date: 12/20/2018 8:39:46 PM

After clean installing Windows, did you then install the drivers for the MB and starting with the chipset drivers first.

Power Profile
Active power scheme: Ultimate Performance

This is a form of overclocking that is known to cause overheating which in turn leads to instability, change the setting to Balanced in the Windows Power Plan.

Scheduler
12/23/2018 10:12 PM;: AvastUpdateTaskMachineUA
12/23/2018 10:17 PM;: GoogleUpdateTaskMachineUA
12/24/2018 2:17 AM;: GoogleUpdateTaskMachineCore

12/24/2018 3:12 AM;: AvastUpdateTaskMachineCore
12/24/2018 10:11 AM;: IUM-F1E24CA0-B63E-4F13-A9E3-4ADE3BFF3473
12/24/2018 4:29 PM;: IntelSURQC-Upgrade-86621605-2a0b-4128-8ffc-15514c247132
12/24/2018 7:15 PM;: OneDrive Standalone Update Task-S-1-5-21-457641620-3306163222-536632250-1001
AsrAPPShop
CCleanerSkipUAC
Driver Booster Scheduler
Driver Booster SkipUAC (Ryan)

IntelSURQC-Upgrade-86621605-2a0b-4128-8ffc-15514c247132-Logon
MSIAfterburner


Avast.

Windows 8, 8.1 and 10 come with an improved Windows Defender, it offers the same real-time anti-virus/anti-malware protection as Microsoft Security Essentials. Windows Defender also shares the same malware signature definitions as Microsoft Security Essentials, and Forefront Endpoint Protection. Technically, Microsoft Security Essentials has not been renamed Windows Defender, or combined with it in Windows 8, 8.1 and 10.

Having more than one AV installed on your computer is bad, it will slow down the computer, cause internet connection problems and leave you with no AV protection at all if they cancel each other out as they fight for resources.

If any AV product that you have is a paid for version you should always make sure that you have a copy of the product key kept somewhere safe just in case you ever wish to reinstall it.

Avast clean removal info here

Driver Booster.

Nothing should be allowed to search for and/or install updates on a computer, it is one sure fire way of you ending up with issues, some companies are worse than others but fwiw you will not find any reputable tech or tech forum recommend the use of anything from this company.

Once Windows has been installed, you install the necessary drivers for the MB and other hardware and then leave well alone, drivers should not be allowed to auto update and you should never update any driver/s unless the new drivers are intended to resolve a specific issue that you are having, installing the new drivers can actually cause you the very issues that they are intended to resolve and uninstalling the new drivers may not resolve the problem/s.

CCleaner, Google Updater, IntelSURQC-Upgrade and MSI Afterburner.

As above regarding them not being allowed to auto update but in addition something that is flagged up in your crash dmp necessitates the mention of them, the info below in red are what are shown to have caused the issue/s, I say issues because we can see at least two, watchdog!WdLogEvent5_WdCriticalError+0xdb and dxgmms2!VidSchiWorkerThread+0xca, the first can be both CPU and GPU related, overclocking could trigger this, the second issue is self explanatory in that it is related to DirectX, there are only a couple of drivers that are failing to load according to your crash dmp one of them being specifically related to your GPU, this driver is nvlddmkm.sys, more significantly is the driver WinRing0x64. which if I was able to count it correctly failed to load 44 times, there is little to no information on this driver but what there is names both Google and Intel by name, se DRT info here


DDITIONAL_DEBUG_TEXT:

Use '!findthebuild' command to search for the target build information.

If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: dxgmms2

FAULTING_MODULE: fffff8001b49b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x119

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800317440db to fffff8001b64cb40

STACK_TEXT:
ffffc102`0e39f778 fffff800`317440db : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffc102`0e39f860 : nt+0x1b1b40
ffffc102`0e39f780 fffff800`342cb3e8 : 00000000`00000000 ffffd989`f0dd4000 ffffc102`0e39f8c0 ffffd989`f0dd4000 : watchdog!WdLogEvent5_WdCriticalError+0xdb
ffffc102`0e39f7c0 fffff800`3432594d : ffffd989`00000000 ffffd989`f0dd6bd0 ffffd989`f59e2000 ffffd989`f67d6050 : dxgmms2!VidSchiSendToExecutionQueue+0x15578
ffffc102`0e39f900 fffff800`34335285 : ffffd989`f67d6050 ffffd989`f338e010 00000000`00000000 ffffd989`f338e010 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffc102`0e39fa80 fffff800`343350fa : ffffd989`f59e2400 fffff800`34335030 ffffd989`f59e2000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffffc102`0e39fad0 fffff800`1b52a625 : ffffd989`f4a5d040 fffff800`00000001 ffffd989`f59e2000 ffffd989`f46ee000 : dxgmms2!VidSchiWorkerThread+0xca
ffffc102`0e39fb10 ffffd989`f4a5d040 : fffff800`00000001 ffffd989`f59e2000 ffffd989`f46ee000 ffffc680`00000001 : nt+0x8f625
ffffc102`0e39fb18 fffff800`00000001 : ffffd989`f59e2000 ffffd989`f46ee000 ffffc680`00000001 00000000`00000000 : 0xffffd989`f4a5d040
ffffc102`0e39fb20 ffffd989`f59e2000 : ffffd989`f46ee000 ffffc680`00000001 00000000`00000000 00000000`00000002 : 0xfffff800`00000001
ffffc102`0e39fb28 ffffd989`f46ee000 : ffffc680`00000001 00000000`00000000 00000000`00000002 00000000`00000001 : 0xffffd989`f59e2000
ffffc102`0e39fb30 ffffc680`00000001 : 00000000`00000000 00000000`00000002 00000000`00000001 ffffc680`c8989100 : 0xffffd989`f46ee000
ffffc102`0e39fb38 00000000`00000000 : 00000000`00000002 00000000`00000001 ffffc680`c8989100 fffff800`1b653f9c : 0xffffc680`00000001


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+15578
fffff800`342cb3e8 0f1f440000 nop dword ptr [rax+rax]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+15578

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgmms2.sys

BUCKET_ID: WRONG_SYMBOLS

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

The C: partition where Windows is located, don`t let it go below 24% or you risk Windows becoming corrupt;

Partition 1
Partition ID: Disk #1, Partition #1
Disk Letter: C:
File System: NTFS
Volume Serial Number: 6628A845
Size: 222 GB
Used Space: 170 GB (76%)
Free Space: 52 GB (24%)

For Windows to be able to run efficiently and to be able to update you need to have between 20 and 25% of the partition or drive available as free storage space at all times, if you don`t you risk Windows becoming corrupt or not being able to update which puts you at risk of malware attack.

Data only storage devices should not be allowed to get any lower than 10% of free storage space of the full capacity of the drive/partition on the drive.
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
Okay thank you for your detailed answer. I uninstalled Avast with pc in safe mode. Also, uninstalled driver booster. I probably messed something up when I reinstalled windows. If I were to do a clean install of windows how would you recommend updating the mb and hardware drivers? would using a program Such as Snappy driver installer be acceptable? https://sdi-tool.org/ Also my GPU is factory oc'd would that be an issue in this case if i set to default.
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
So just to be safe I did a clean install of windows and downloaded the drivers from the manufacturers website starting with the chip set drivers. After setting everything up turning power mode back to balanced and resetting bios I ran a furmark test and the screens froze then shutoff per usual. I am starting to thing this is a hardware issue and this is my last resort before taking it in to have it looked at. Ill include another speccy after reinstallhttp://speccy.piriform.com/results/6ZBxoJOKuGQXJhucuoAiz27.
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
3,302
482
56
A clean install of Windows and how you installed the MBs drivers was spot on so well done with that (y)

From my reply #2;

more significantly is the driver WinRing0x64. which if I was able to count it correctly failed to load 44 times, there is little to no information on this driver but what there is names both Google and Intel by name, se DRT info here
Did you read the info at the link regarding the WinRing0x64 driver, shortcut to info here reason that I ask if you have read the info is because since the clean install of Windows and the MB drivers you have also installed third party drivers from Corsair + the CCleaner program, neither may be responsible but at the same time one or both could be, you would have been better to test the computer when having just installed Windows and the MB drivers.

I ran a furmark test and the screens froze then shutoff per usual.
Overheating and a power supply issue would be the usual suspects with this behaviour but for now can I just ask you to do the following;

Your MB is the smaller ITX type, what case do you have and how many chassis fans does it have.

Uninstall and temporarily stop using the Corsair USB devices, uninstall CCleaner, restart and test, if things go ok, post back and let us know, if still the same problem, leave the Corsair device/s disconnected and uninstalled, the same for CCleaner, physically remove the GTX 1070 from the MB, hook up the display to an appropriate video port on the MB, test then post back with an update for us.

When inside the case removing the GPU, please check that all internal connections are secure (especially the modular ones from the PSU).
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
I did read the link I must have installed cccleaner on accident when installing speccy, it is gone now. Also I uninstalled the Icue corsair software.
I have a Ibuypower revolt 2 case with a singlefan water cooler for cpu and 1 case fan. The gpu is a single fan blower that sends heat out back of case.
I also have tried disabling the dedicated gpu and using the onboard video for test and pc still crashes.
I will try to disconnect but i recently upgraded my psu and installed it a month ago because I thought that was my problem.
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
What do I test with the 1070 off? I obviously cant play the games or run futuremark to see.
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
So I removed gpu properly and tried reseating it. It powers on and fan spins but the pc wont recognize that the gpu is there. i went to the bios and made sure it was enabled but it isnt coming up on the device manager list. PCIe cable is in card is in mobo slot and locked, and card is powered on. I have taken my gpu out several times before and also when i replaced the psu. Am I causing this error or is this a hardware issue?
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
3,302
482
56
What do I test with the 1070 off? I obviously cant play the games or run futuremark to see.
Try watching videos and running Valley benchmark (free) which you can download from here

You must remove the 1070 from the MB first, we are trying to test your other hardware here, MB, CPU and integrated video etc, not the 1070.
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
Sorry to keep you guys in the dark haven't had my pc for a week. So I have decided to turn this into something positive and upgrade my components. I ordered a new cpu mobo liquid cooler and case that isnt mini itx so i have some space. I removed all the parts from the case and have setup the mobo for testing outside. I also reseated the cpu and cooler with new paste. Good news, the gpu was detected.. everything booted up fine however crashing issues still happening on the furmark and 3d mark tests. So hopefully ill have the new system installed on thursday and can post an update. If that does nothing ill be looking at RMAing the new psu i just got a month ago.
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
Here are the new parts coming in this week.

MSI MPG Z390 GAMING EDGE AC LGA 1151 (300 Series) Intel Z390 HDMI SATA 6Gb/s USB 3.1 ATX Intel Motherboard

Intel Core i5-9600K Coffee Lake 6-Core 3.7 GHz (4.6 GHz Turbo) LGA 1151 (300 Series) 95W BX80684I59600K Desktop Processor Intel UHD Graphics 630

Cooler Master MasterLiquid Lite ML240L RGB AIO CPU Liquid Cooler Dual 120mm RGB

Corsair Carbide Series 275R (CC-9011131-WW) White Steel, Plastic, Acrylic ATX Mid Tower Gaming Case
 

phillpower2

Autonomous Admin
Administrator
Support Team
Sep 9, 2016
3,302
482
56
Any update for us? This thread will be closed if not replied to within 48hrs.
 

vande096

PCHF Member
PCHF Member
Dec 24, 2018
9
1
22
looks like it turned out to be a gpu error. not sure what about it was bad possible vram. I replaced that as well and now it works like a charm. Thanks for the help everyone.
 
  • Like
Reactions: jmarket
Status
Not open for further replies.