Avoiding SYSTEM THREADED EXCEPTION NOT HANDLED in httpd.sys and windows reboot

Question

ASP.NET Core MVC5 application is running from Visual Studio 2019.

Chrome and Edge show

::NET HTTP_PROTOCOL_ERROR

in console window for different js file requests from wwwroot .
After few requests Windows 10 re-boots with blue screen containing

SYSTEM THREADED EXCEPTION NOT HANDLED in httpd.sys

Windows event log contains

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          26.06.2021 0:07.17
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      dell2
Description:
Computer was re-booted after crash. Crash data: 0x0000007e (0xffffffffc0000005, 0xfffff80554ebb729, 0xffffed0edf6057d8, 0xffffed0edf605010). Memory dump was created in: C:\WINDOWS\MEMORY.DMP. MEssage ID: 4b236ed9-f074-49f9-8844-21121441dba7.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-06-25T21:07:17.3281757Z" />
    <EventRecordID>54508</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>dell2</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">0x0000007e (0xffffffffc0000005, 0xfffff80554ebb729, 0xffffed0edf6057d8, 0xffffed0edf605010)</Data>
    <Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
    <Data Name="param3">4b236ed9-f074-49f9-8844-21121441dba7</Data>
  </EventData>
</Event>

How to fix this ?

It looks like this is caused by http/2.
How to disable http/2 in kestrel ?

How to examine Chrome or Edge logs to find what exactly causes the issue?
I installed all Windows 10, Visual Studio 2019 and .NET 5 updates but problem persists. Using FireFox it seems to work.