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-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 No comments
  2. Anonymous
    2021-07-16T23:39:35+00:00

    It does seem they released a new http.sys on 7/13/2021

    NEW GOOD HTTP.SYS:

    10.0.19041.1110

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-06-23T20:06:16+00:00

    We are also having this issue here. Being reported by many of our VS software developers. Same problem, https.sys and VS 2019 with IIS Express or regular ISS doesn't make a difference. BSOD crash on refresh. Systems are fully patched, latest 20H2 or 21H1 and VS 2019. Primarily impacts Google Chrome, and to a lesser degree Firefox and Edge. Issue started for us around 6/15.

    Multiple threads about this issue on Microsoft help forums, Stack Exchange, and developercommunity.visualstudio.com. We've tried removing KB5003637 and KB5004476 (suggested in some forums, only helped temporarily), disabling HTTP/2 seems to be the best "workaround" at this time. Heard some people have had success pulling an old version of http.sys from an archive to replace the "broken version". I've also heard running Fiddler (debugging proxy) to "intercept" Internet traffic between VS and the browser works.  Can't upgrade to .NET 5 at this time.

    Have been researching for days, even provided one user a new computer.  Still had same issue on new machine.  Would really appreciate a solution from MS.

    A few other threads on this topic:

    https://developercommunity.visualstudio.com/t/httpsys-blue-screen-when-debugging-a-we/1457526

    https://developercommunity.visualstudio.com/t/Failed-to-load-resource:-net::ERR_HTTP2_/1446262#T-N1453712

    https://answers.microsoft.com/en-us/windows/forum/all/frequent-bsod-since-updating-windows/d856e886-a3f6-4472-9992-9510f1770e32

    https://docs.microsoft.com/en-us/answers/questions/440339/kb5003637-and-the-new-kb5004476-gives-error-34fail.html

    https://docs.microsoft.com/en-us/answers/questions/442669/windows-10-pro-21h1-httpsys-kernel-module-bugcheck.html

    https://stackoverflow.com/questions/67911570/failed-to-load-resource-neterr-http2-protocol-error-for-react-app-after-upg

    Image

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-06-21T23:19:41+00:00

    I had a lot of issues today while debugging with VS and Chrome/Edge. So I got multiple laptop crashes and BSOD messages with Http.sys. I initially thought about certain Google drive chrome extensions and Dell updates, but that didn't solve the problem. In the end I also updated VS to the latest Version 16.10.2. From that moment on, no more blue screen ;-)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No 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 No comments