Video Scheduler Internal Error (BSoD)

Question

Video Scheduler Internal Error (BSoD)

Anonymous

A bit over 2 weeks ago I experienced a blue screen (stop code VIDEO_SCHEDULER_INTERNAL_ERROR) after closing Firefox (I was watching a stream VOD and was just about to close down my computer for the night). Earlier in the day after playing a game I experienced some graphical artifacts, which involved the nvidia software/driver having to restart but recovered. That's all quite atypical, so I decided to update my graphics drivers (they were pretty out of date, as it turned out). All well and good until 2 nights ago. I had played quite a lot of video games in between the initial BSoD and now, but suddenly while playing some Halo with a friend I had another blue screen. This one was quick and threw me off. I didn't notice the stop code, and no minidump was made. Presumably something is still wrong.

Here is the minidump I did get: https://drive.google.com/file/d/1HnKcZL3nBDQGhp-MEZWZK8Zmy4LWQ1ek/view?usp=sharing

I haven't done too much yet to try and fix things. I played a few more hours of Halo last night as well as some Elden Ring. No issues. So whatever my problem is, it's evidently not easily reproducible (yet).

Some things worth noting:

I keep getting this error:

Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).

Checking online, this is super common. There appears to be a very technical workaround for it, but presumably this shouldn't be the culprit. Still, any blue screen helper mentions making sure Windows is up to date. I'd love for it to be, but Microsoft is really expecting a lot on this one (I'm a programmer for a living, and the steps to fix the issue are still unsettling to me).

Lastly on 6/7 (a few days after the original BSoD) while playing a VR game, I experienced no perceptible issues. I decided to check my Event Viewer though, since I have been to see if I catch anything, and I see a series of these errors:

The device, \Device\Harddisk1\DR1, has a bad block. (Event ID 7)

Which... doesn't look good. It definitely could be related, but I'm hoping my minidump will be enlightening on that. I haven't had the error ever before or after that. Using Samsung Magician, both of my SSDs show good health, but that doesn't mean much. I plan on running scans, but they will take a bit and not getting the error sense then makes me wonder if it's a false alarm or something the drivers already fixed on their own.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

9 answers

Answer 1

Anonymous

Dear Joe!

Thanks for your reply!

If you have any new blue screen mini dump file, you can send it under this thread and I will help you analyze it.

Thank you for your understanding and support!

Best Regards,

Yang

0 comments

Answer 2

Anonymous

As mentioned in my original post, I did experience another blue screen, though no minidump was created. This was after updating my graphics cards, about 14 days after the original BSoD.

0 comments

Answer 3

Dear Joe!

Thank you for your feedback!

I understand that you have not encountered any new blue screen issues after updating your graphics card driver. You can temporarily stop dealing with driver issues.

If you encounter other problems, the Microsoft Community welcomes you at any time.

Best Regards,

Yang

Answer 4

I tried searching for KB5034441 at the link and nothing came up. From checking the web, and based on Microsoft's own support page on the patch, it sure looks like the fix involves manually resizing my partition. Namely the update requires ~1000 MB, but a standard Windows 10 installation (which mine is) is less than that. Here is the article: https://support.microsoft.com/en-gb/topic/kb5034441-windows-recovery-environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024-62c04204-aaa5-4fee-a02a-2fdea17075a8 See the part under 0x80070643 - ERROR_INSTALL_FAILURE.

It's good to hear that it's likely graphics driver related, or at least in part. Since updating my drivers apparently didn't completely fix the problem, maybe I need to fully reinstall my drivers using DDU? I've seen that come up a lot when tracking down solutions for different BSoDs, including ones like this. Any other suggestions would be greatly appreciated. There is nothing quite like the anxiety of not knowing if your computer is broken. It's a combination of frustrating and hopeless, while also technically not being hopeless even if it feels that way (so many variables).

Answer 5

Hi, Joe Waller1!

Welcome to the Microsoft community and thank you for asking your question in the community!

Based on your description, I understand that you have three system problems. I will explain them in order.

First, understand the contents of the dmp file you provided. The dmp file you provided shows that the process that caused the blue screen is "dxgmms2.sys", which is a graphics driver-related process in the device. This problem is most likely caused by an incompatible graphics driver installed in your device. So you updated and installed your graphics driver to solve this problem, and you did it right.

About the update you mentioned, error code 0x8024200B. It usually occurs when trying to install Windows updates and may prevent users from successfully updating their operating systems. This error can be caused by a variety of reasons, including corrupted temporary files, outdated drivers, corrupted Windows updates, or missing system files. You can try to manually download and install the update in the Microsoft Update Catalog. Search and download the update patch that is suitable for your system architecture and OS build version, and then install it manually. The following is the website link: Microsoft Update Catalog

Finally, regarding your Event ID 7 error

The device, \Device\Harddisk1\DR1, has a bad block. (Event ID 7)

It may be caused by bad sectors in the disk, but generally speaking, SSDs will not have such errors. It may be a system false alarm. You have used Samsung's magician software to detect it and there is no problem. It should be fine, but it is still recommended that you back up important data regularly to prevent data loss.

Thank you for your understanding and support! Please let me know if I have misunderstood. Tell us the results and we will get back to you as soon as possible. We look forward to hearing from you.

Best regards,

Yang.Z - MSFT | Microsoft Community Support Specialist

Share via

Video Scheduler Internal Error (BSoD)

9 answers