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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-06-22T05:11:49+00:00

    I disabled the HTTP service in the Registry, Rebooted my machine, replaced the file and enable it again.

    It's been a couple hours and the system is stable so far. I'll edit this post if the problem persists.

    tl;dr:

    Replacing http.sys worked like a charm

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-06-22T11:27:38+00:00

    Same issue here as well. 21H1, latest Visual Studio.

    Breaks even on Edge and Firefox when diagnosing a site through IISExpress.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-06-22T13:47:44+00:00

    This doesn't seem related to VS2019 or it's versions, nor IIS Express. I use neither and this is crashing me. I was able to roll back the windows update, but it put other things in a bad way. Whatever happened to HTTP.sys, it's a noticeable amount smaller in file size. Will go searching for the PR, does that exist? Who's running this show?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-06-22T15:40:41+00:00

    Has this been reported at all at Send feedback to Microsoft with the Feedback Hub app ?

    I don't want to create a duplicate.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-06-22T16:15:11+00:00

    I updated VS to 16.10.2 hoping this would help but got the same BSOD within half an hour. I realize this might not be unique to VS as others have also mentioned, but for me, it only ever happens when I'm debugging a web application.

    Was this answer helpful?

    0 comments