Add instructions on how to share a kernel dump (#9071)

Blue committed Oct 31, 2022 at 19:48 UTC 47ee90835519eb62aa918cf3d333c217919104ca
1 file changed +20
CONTRIBUTING.md
+20
@@ -2,6 +2,7 @@ Please provide as much information as possible when reporting a bug or filing an
2
3 ## Important: Reporting BSODs and Security issues
4 **Do not open GitHub issues for Windows crashes (BSODs) or security issues.**. Instead, send Windows crashes or other security-related issues to secure@microsoft.com.
5 +See the `10) Reporting a Windows crash (BSOD)` section below for detailed instructions.
6
7 ## Reporting issues in Windows Console or WSL text rendering/user experience
8 Note that WSL distro's launch in the Windows Console (unless you have taken steps to launch a 3rd party console/terminal). Therefore, *please file UI/UX related issues in the [Windows Console issue tracker](https://github.com/microsoft/console)*.
@@ -181,3 +182,22 @@ To collect WSL logs follow these steps:
182 - Get a link to your feedback item by clicking on 'Share my Feedback' and post that link to the Github thread so we can easily get to your feedback!
183
184 ![GIF Of networking instructions](img/networkinglog4.gif)
185 +
186 +
187 +### 10) Reporting a Windows crash (BSOD)
188 +
189 +To collect a kernel crash dump, first run the following command in an elevated command prompt:
190 +
191 +```
192 +reg.exe add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl /v AlwaysKeepMemoryDump /t REG_DWORD /d 1 /f
193 +```
194 +
195 +Then reproduce the issue, and let the machine crash and reboot.
196 +
197 +After reboot, the kernel dump will be in `%SystemRoot%\MEMORY.DMP` (unless this path has been overriden in the advanced system settings).
198 +
199 +Please send this dump to: secure@microsoft.com .
200 +Make sure that the email body contains:
201 +
202 +- The Github issue number, if any
203 +- That this dump is destinated to the WSL team