Rider backend crash. Windows. Capture crash dump using Windows Error Reporting.

Symptom

At some point the "A Critical Failure Has Occurred" dialog appears. When that happens Rider becomes almost unusable: completion stops working, syntax highlighting is gone, refactorings don't work, etc:

Question:

How to capture the Rider backend crash dump so the Rider team can narrow down the issue?

How to:

To diagnose this problem, a full process dump of a crash is needed. Capture using the below instruction:

1. Download files attached to this article;
2. Run the attached enable_dumps file (enable_dumps_rider.reg) . This will add registry settings that collect dumps on Rider backend crash.
3. Create a folder at C:\JetDumps
4. Reproduce the crash
5. Locate the dump. It will be located in the C:\JetDumps folder. It could take a bit of time for it to appear after the crash, up to a minute. You can check your Task Manager for the "Windows Error Reporting" process - if there is one and it's active, it means that the dump is still being produced.
6. Archive it the dump to zip/7z/rar. Dumps are typically large and typically highly compressible.
7. Upload the generated archive to the Uploads Service and share the Upload ID (shown at the end of the upload process) in the corresponding YouTrack issue, Support request or thread.
8. Run the attached disable_dumps file (disable_dumps_rider.reg). It will remove registry settings added on step one.

If the dump doesn't generate in 5 minutes, capture the dump the way described in Rider backend crash. Linux/MacOs/Windows. Capture crash dump using DOTNET_ env variables

Upload the dump to the Uploads service and share the Upload ID with the support team.