Windows 10: VIDEO SCHEDULER INTERNAL ERROR constantly after s

Hello Community!

It's been almost 3 years ever since I've had this computer and so far, I've been able to fix most problems that come once in a while with a few tweaks and forum research, but this one is being one of my biggest challenges ever.

I've been having this problem ever since in a while, or at least part of it. Whenever I was to put my laptop to sleep, the second I try to boot it up I would either get a black screen Using the Graphic Restart Shortcut, WINDOWS+CTRL+SHIFT+B, wouldn't solve the issue, or a very sluggish PC that would take up to 10 min to open a single app, forcing me to shut down the system in either ways. I was getting rather annoyed with this, but since it was something that happened every once in a while, I ended up trying to forget about it and "let it slide". These last few weeks it was getting out of hand since every single time I were to put it to sleep, it would happen the same thing over and over again, forcing me to shut down the system.

I used the command:

> powercfg sleepstudy


And concluded, from what I could understand, that I had the VIDEO SCHEDULER INTERNAL ERROR with parameter 1- 0x2. A quick research would lead me to all types of forums and sites trying to find a solution to this problem.

All the forums I visited along with other helping sites, all share the same solutions over and over again:


- Update Display Drivers I have Driver Booster to keep everything updated.
- Remove / Uninstall Display Drivers I have used the DDU and did a clean install with all the updated drivers.
- Update your Windows / Check for updates I recently just updated my system to the last available public version of Windows 10.
- Change the Display Driver Settings Normally they recommend changing the Physx to "Default" which in my case, is.
- Execute the following commands:


chkdsk /f /r

sfc /scannow

DISM /Online /Cleanup-Image /CheckHealth Along with more 2 commands related to DISM


- Fix Registry Errors Did it using CCleaner and using a CMD Script made by Microsoft with a few other helpful commands.

- Run Windows Memory Diagnostic No errors found.


In conclusion, I've done all of the things I've read on forums and helping sites and still have the problem. This being said, my last resource would be to try and find help here, where I could share my experience and questions in hopes to seek help along with leaving this thread for other people having the same problem as mine to come and see, later on, a solution for their problem.


Files about my system information:

DMP File

Output of MSinfo32

AIDA64 Extreme Output with more Information

Thank you all for your time, and hopefully, my post was clear with just enough information for anyone to try and help me determine what am I missing.

:)

 

Constant BSOD in VR: Video Scheduler Internal Error

Did you create a restore point if so you can restore it from when your system is working fine if not you can follow this steps actually work for me..
Solution 1. Reinstall the driver if you have A discrete GPU
Solution 2. Install motherboard chipset if you have integrated GPU.
https://www.errorsolutions.tech/error/video-scheduler-internal-error/

 

video scheduler internal error (windows10 X64)

Windows10 blue screen error causes: video Scheduler internal error, how to solve?

Windows10 蓝屏，报错原 ：video scheduler internal error，怎么解决？

 

Video Scheduler Internal Error

hello everyone, i am getting BSOD error code for video scheduler internal error from past few days. The things started after updating the driver. whenever i start something which consumes CPU power the display goes off and shows us the error.

I have visited and read many discussions regarding how to fix it out. Even i took my computer to repair store, they claimed that something wrong with the graphics card. Removed the graphic card but still the same.

been searched on the internet, i have followed several methods to fix out the error video scheduler internal error from

this website. But, those things gives relieves for about few hours. And again it shows the error.