Blue screen: HTTP.sys error

Anonymous
2021-06-16T14:33:13+00:00

recently started getting blue screen error when running Visual Studio 2019 and IIS Express application

msinfo:

https://1drv.ms/u/s!AgLJxHDVN__BhSnnjqW37EXiiXZ8?e=uin5sb

minidumps:

https://1drv.ms/u/s!AgLJxHDVN__BhSjD62yp8R-oqm1X?e=hlhbWE

thanks

Windows for home | Windows 10 | Performance and system failures

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

70 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-07-22T17:02:45+00:00

    I have this version 10.0.19041.1110 installed and no BSOD issues so far, though I have been doing more back end work lately so not using it as heavily as when this thread was started.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-07-22T16:11:19+00:00

    I have this version now installed for 2 days and it has apparently solved the issue. I, nor my collegues, have had the BSOD once since installing it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2021-07-22T15:50:32+00:00

    Hello, I have heard in another forum that the latest version of http.sys, version 10.0.19041.1110 released 7/13/2021, is "good". Can anyone confirm if they are still having BSOD crashes after updating to this version? You can check your version by looking in C:\WINDOWS\System32\drivers folder. Thanks!

    Image

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2021-07-22T14:51:44+00:00

    I managed to at least build without crashing this time, so hopefully this work around really works. Fingers crossed because this is ridiculous that Microsoft hasn't already pushed out a fix for something this disastrous. Thank you for the swift reply!

    Was this answer helpful?

    0 comments