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 No comments

70 answers

Sort by: Most helpful
  1. 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 No comments
  2. 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 No comments
  3. 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 No comments
  4. Anonymous
    2021-06-22T00:34:12+00:00

    Exact same combo giving me 0-3 BSOD a day with HTTP.sys, since mid June 2021

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-06-21T17:08:35+00:00

    I have the same Issue.

    Visual Studio 2019, web app for .net Framework 4.8 and Google Chrome

    The blue screen apears when I'm debuggin with Chrome tools open, and hit the refresh button.

    I'm using Edge since this problem, and aparently it's gonne...

    so maybe the problem es Chrome...

    Was this answer helpful?

    0 comments No comments