#Critical System Crash (Hard Shutdown) When Opening/Zooming Map (Key M)

1 messages Β· Page 1 of 1 (latest)

high obsidian
#

Description
While playing Windrose, the system experiences a hard shutdown (no BSOD) when opening the map using the M key, especially when zooming in or out. The crash is severe enough to instantly reboot Windows.

This appears to be related to map rendering, zoom level changes, or GPU load spikes.

Repro Steps

  1. Launch Windrose from Steam
  2. Load into a Server
  3. Press M to open the map
  4. Zoom in or zoom out on the map
  5. System crashes instantly

What Happens
● Game runs normally before the event
● Pressing M opens the map
● When zooming (in or out):
● No error message
● System powers off

Actual Result
● Full system crash (Kernel-Power event)
● powers offSystem Immediate powers off
● No crash dialog or BSOD

Frequency
● Reproduced multiple times
● Strongly tied to:
Pressing M (map open)
Zooming interaction on the map
● Not random β€” highly reproducible

System Specs
● Laptop: ASUS ROG Strix G16 (G614PR_G614PR)
● OS: Windows 11 Home (Version 25H2, Build 26200.8246)
● CPU: AMD Ryzen 9 8940HX with Radeon Graphics
● RAM: 32 GB (5200 MT/s)
● GPU: NVIDIA GeForce RTX 5070 Ti Laptop GPU (12 GB VRAM)
● Driver: NVIDIA Game Ready Driver 596.21 (Apr 16, 2026)
● Storage: ~1 TB SSD
● Display: 3440 Γ— 1440 @ 180 Hz, VRR enabled

Windows Event Viewer (Relevant Log)
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 4/20/2026 12:53:34 PM
Event ID: 41
Level: Critical

Description:
The system has rebooted without cleanly shutting down first.
BugcheckCode: 0
BugcheckParameter1: 0x0
BugcheckParameter2: 0x0
BugcheckParameter3: 0x0
BugcheckParameter4: 0x0
WHEABootErrorCount: 0

earnest mirage
#

Thanks for the report. can you also provide your game logs, DxDiag and save?

And while we're looking at it - please check the troubleshooting list that helps with a lot of crashing related issues:

  1. File verification through Steam + reinstallation
  2. https://playwindrose.com/faq/#faq-crash
dull topazBOT
#
BUG REPORTING GUIDE

Please share your game logs, game saves, crash dumps, and DxDiag. These are essential for diagnosing and fixing bugs.

HOW TO FIND LOGS

Game logs are located here:
C:\Users\%USERNAME%\AppData\Local\R5\Saved\Logs

Server logs are located here:
R5\Builds\WindowsServer\R5\Saved\Logs

To get there, open Steam, find Windrose in your library, right-click it, then go to Manage β†’ Browse local files. From there, archive the files in the Logs folder and share them with us.

Please name your logs in a way that describes the problem, for example: Crashedwhile_fighting_Dodo.log

HOW TO FIND SAVES

Your saves are located here:
C:\Users\%USERNAME%\AppData\Local\R5\Saved\SaveProfiles
Please close the game before archiving your saves!

If you are playing on a dedicated server:
β€’ Stop both the client and the dedicated server.
β€’ Find and archive your server logs and world save.

Dedicated server logs are located here:
R5\Saved\Logs

Dedicated server saves are located here:
R5\Saved\SaveProfiles

To get there, open Steam, find Windrose Dedicated Server in your library, right-click it, then go to Manage β†’ Browse local files (or go to the folder where your Windrose Dedicated Server is stored).

Please close the dedicated server before archiving your saves.

HOW TO FIND CRASH DUMPS

If crashes are involved, please share crash dumps:

Game client dumps (if play offline)
%LOCALAPPDATA%\Local\R5\Saved\Crashes
%LOCALAPPDATA%\Local\R5\.sentry-native

Server dumps (if you self-host from game client)
SteamLibrary\steamapps\common\Windrose\R5\Builds\WindowsServer\R5\.sentry-native
SteamLibrary\steamapps\common\Windrose\R5\Builds\WindowsServer\R5\Saved\Crashes

Dedicated server dumps
Windrose Dedicated Server\R5\.sentry-native
Windrose Dedicated Server\R5\Saved\Crashes

HOW TO FIND DXDIAG

Please also include your DxDiag report. This is your PC specifications in .txt format:

β€’ Press Win + R.
β€’ Type dxdiag and press Enter.
β€’ When the tool opens, click Save All Information.
β€’ Save the .txt file and attach it to your report.

Any additional screenshots and/or videos are HIGHLY appreciated!

high obsidian
earnest mirage
#

Thanks, we'll look into it.