> For the complete documentation index, see [llms.txt](https://desync-4.gitbook.io/desync-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://desync-4.gitbook.io/desync-docs/russkii/english/troubleshooting-and-support/bsod-blue-screen.md).

# BSOD — blue screen

If Windows shows a blue screen while launching or using DESYNC, create a ticket in [@desync\_support\_bot](https://t.me/desync_support_bot). Support will determine the solution after reviewing the materials.

## Example

The photo shows CRITICAL\_PROCESS\_DIED. Your stop code may differ; photograph the entire screen so it is readable.

![](https://content.gitbook.com/content/2IqdwbRpQj7CdFx59AIG/blobs/5zij3WTdHLzGMHqOV9EU/spaces%2FnitGYSBvlczRLpWdhsJO%2Fuploads%2FyHcChJp0JtChxufYgRp9%2FDESYNC_BSOD_CRITICAL_PROCESS_DIED.png?alt=media\&token=f243dd71%20deed%204110%209b86%20d34edf631d83)

## What support needs

* Whether the BSOD occurs before or after opening the game. Specify the exact stage: loader launch, cheat launch, opening the game, pressing F2 or playing.
* The stop code and any filename shown. Attach a photo or video.
* Loader logs, following the [log instructions](/desync-docs/russkii/english/troubleshooting-and-support.md). If you cannot obtain them, say so in the ticket.

## Complete dump — only at support's request

The minidump is sent with logs. Prepare a complete dump only when support requests it. Logs from the same crash must accompany it.

The dump may take tens of gigabytes; its size depends on RAM. With 32 GB of RAM, for example, a complete dump may be around 32 GB. Make room on the Windows drive for both the page file and dump. If space is limited, tell support before reproducing the issue.

### Enable a complete dump in Windows 10 / 11

Do this after support requests it. Administrator privileges may be needed.

1. Press Win + R, enter sysdm.cpl and press Enter.
2. Open Advanced → Startup and Recovery → Settings.
3. Under Write debugging information, select Complete memory dump.
4. Keep the dump path as **%SystemRoot%\MEMORY.DMP** and click OK.
5. In System Properties, open Advanced → Performance → Settings → Advanced → Virtual memory → Change.
6. Enable Automatically manage paging file size for all drives and confirm with OK. If a specialist previously configured the page file, check with support before changing it.
7. Save open files and restart the PC to apply the settings.

Select Complete memory dump specifically. Active memory dump is a different type. If the required option is missing, send support a screenshot of the window.

### Obtain the file after a crash

1. Enable logging and restart the loader using the [support instructions](/desync-docs/russkii/english/troubleshooting-and-support.md). Reproduce the BSOD only as agreed with support.
2. Wait for data collection to finish on the blue screen. Do not manually power off or restart while data is being written.
3. After Windows starts, press Win + R, enter %SystemRoot% and find MEMORY.DMP, usually **C:\Windows\MEMORY.DMP**. Check that its modification time matches the relevant crash.
4. Tell support that the file is ready and send logs from the same attempt. If no dump appeared, report that.

### Provide the dump

Because of the file size, support usually connects remotely to examine it on your PC. Agree on the time and connection method in your ticket. Transfer the file separately only if instructed.

A dump can contain data from open applications. Do not publish it; provide it only to trusted support handling your ticket. Another BSOD can overwrite MEMORY.DMP, so report the completed file before further tests.