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-06-18T16:02:35+00:00

    I tried that, but it says I don't have the update installed.

    Strange, because when I look to Settings > Windows Update > Update history, I can see the update there.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-06-18T16:01:54+00:00

    Run the project as a console app instead of IIS Express - it should not throw BSODs.

    Was this answer helpful?

    0 comments
  3. Sumit 44,316 Reputation points Volunteer Moderator
    2021-06-18T15:54:49+00:00

    Jarno, I see that you had a feature update installed on 14th, as well as CU on 12th.

    Can you try uninstalling KB5003637?

    In the search,

    type cmd, right-click it and choose run as administrator.

    Execute this command.

    wusa /uninstall /kb:5003637

    Keep us posted.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-06-18T15:46:14+00:00

    I've exactly the same issue. It started after june 8th update.

    It mainly happens when I reload a page that's running from IIS Express.

    Now it's really hard for me to develop without having a BSOD.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-06-18T08:45:46+00:00

    Thanks. I could not find anything else apart from IIS error. Has the issue raised after Patch Tuesday updates aka after 8th?

    Please check for updates on Ethernet and WiFi drivers.

    Indeed, it has started happening "just lately". I believe it has started happening after June 8th at least for the vast majority of us.

    After June 8th, I've installed the following updates (omitting driver updates, because all those were updated after the BSODs started):

    Thanks,

    Jarno

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments