WSL1 STOP Error in Windows Server 2022 (MEMORY_MANAGEMENT)

[DesktopECHO]

Windows Version

4.4.0-22000-Microsoft

WSL Version

0.0.0.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

4.4.0-22000-Microsoft

Distro Version

Any

Other Software

https://sh.rustup.rs

Repro Steps

Windows 11 BugCheck occurs randomly.

Easily reproducible steps:

• Install rust using rustup as follows: curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
• System will BSOD before installation completes.

This issue existed in Windows 11 RTM and was fixed in 21H2, but has not been fixed in Server 2022.

Expected Behavior

BugCheck-free computing

Actual Behavior

BugCheck

Diagnostic Logs

An example of the bugcheck with other software:

WinDBG-seamonkey.txt
WinDBG-spotify.txt
WinDBG-WebKitWebProcess.txt

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• WSL stops working with memory integrity turned OFF (#8485), similarity score: 0.80
• I can not allocate ram memory for WSL2 (#9786), similarity score: 0.76

Closed similar issues:

• WSL1 STOP Error in Windows 11 / Server 2022 (MEMORY_MANAGEMENT) (#7480), similarity score: 0.98
• WSL appears to leak memory in a way that even after exiting, the memory is not recoverable by Windows. (#3049), similarity score: 0.78
• The WSL system cannot be started due to memory occupation (#10361), similarity score: 0.77

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[OneBlue]

Thank you @DesktopECHO. Can you follow these instructions to capture and share the BSOD dump with us ?

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!