Myself and my coworkers have also been having this issue since 06/08/2021
Internally we have narrowed down the issue to these two updates.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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
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.
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.
I had this same exact issue. Windows 10 Home - 20H2 update, VS2019, IIS Express, Chrome. On debugging, would get BSOD.
As suggested, replace http.sys (using safe mode) with version 10.0.19041.985 seems to resolve the BSOD.
http.sys version 10.0.19041.1023 seems to cause the error in question.
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.
Fernando, running the site in Local IIS seems to be a valid workaround for me. I haven’t had any crashes with it. You may want to try it, even though brentdowdy has experienced crashes even with that, too..
OC and XMP are not enabled
System event logs (excluding Information entries) for today (in this timeframe there were multiple blue screens, as seen in the Critical entries which indicate rebooting)