Exact same combo giving me 0-3 BSOD a day with HTTP.sys, since mid June 2021
Blue screen: HTTP.sys error
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.
70 answers
Sort by: Newest
-
Anonymous
2021-06-22T00:34:12+00:00 -
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 ;-)
-
Anonymous
2021-06-21T17:11:39+00:00 I wasn't able to replace the http.sys directly, but on a fresh boot (before launching vs2019) I was able to rename http.sys to http_.sys (or some similar backup name) - then I put the "good" http.sys in place and I no longer get blue screen.
I tried this for about a week and no blue screen.
I tested some more by putting the "bad" http.sys back in place and got a blue screen within a couple hours.
I think it has something to do with Microsoft's fix for this vulnerability, but I have not tried to work on this any further after figuring out the http.sys trick. Zero Day Initiative — CVE-2021-31166: A Wormable Code Execution Bug in HTTP.sys
Maybe a rushed patch? Either way, Microsoft, Please fix this.
-
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...