Find your guide

Independent port guide.

Troubleshooting · Savage Wind

Savage Wind GTX 1050 Crash: NVIDIA GTX 10 Startup Help

Error message
address-write-invalid-0

Run the two commands in Command Prompt first. Use this when a Pascal card turns the game window black and closes it after Play.

On this page

Changing how the game sends frames to the screen helped two players get past this crash.

Run the Startup Workaround

NVIDIAWindowsPascalWorkaround
  1. Open a new Command Prompt in the Savage Wind folder containing savagewind.exe.

  2. Run both commands in that same window:

    bat
    set SAVAGEWIND_VK_PRESENT_THREAD=0
    
    bat
    savagewind.exe
    
  3. If Configuration appears, press Play and check whether the game starts. Keep the failing log if it still closes.

Successful workaround reports

Automatic selection is planned for Alpha 4.

If it still crashes

NVIDIAWindowsPascalOpen
  1. Press Win+R, type cmd and press Enter to open Command Prompt; the set commands use this shell, while PowerShell uses different environment-variable syntax.

  2. Change to the folder containing savagewind.exe, replacing the example path with your installation:

    bat
    cd /d "D:\Savage Wind"
    
  3. Enable both diagnostic options in that same window:

    bat
    set SAVAGEWIND_VK_DEVLOST_TRACE=2
    
    bat
    set SAVAGEWIND_SYNC_SUBMIT=1
    
  4. Start the game from that window:

    bat
    savagewind.exe
    
  5. If Configuration appears, press Play and wait for the crash; keep the new savagewind.log in the Savage Wind folder, including the last GPU operations before device loss.

  6. Close this Command Prompt after collecting the log, then use your usual shortcut. Tracing slows the run, and these options apply to programs started from that window.

Affected hardware and report conditions
  • Original reports: GTX 1050 and 1050 Ti on Alpha 2, with driver examples 582.66 and 582.78. Alpha 3 hotfix reports include GTX 1050 Mobile, desktop GTX 1050 and desktop GTX 1080 Ti. These cards use the Pascal generation.
  • Configuration may work normally, but the game fails before the title screen; some reports show a Windows error dialog. Directly starting savagewind.exe can also trigger it.
  • Desktop reports extended the investigation beyond the earlier Optimus laptop theory. The logs show the graphics card writing to address zero in its first frames, followed by a Vulkan device-lost failure. The Windows hotfix already enables Vulkan maintenance5 on NVIDIA, and these crashes continued. An older test disabling GPU access to mapped game memory also left the invalid write.
  • The MX130 report in issue 55 was initially grouped here; later analysis separated its extremely slow frames and Windows GPU reset from the Pascal memory-write fault. Match the GTX diagnostic to Pascal hardware and this startup symptom.
  • An Alpha 2 text report records FATAL: sr failed: -4 (runtime/nvn/vulkan/exec.c:302).
  • The maintainer requested the last GPU operations to identify the responsible draw and gave no release version for a fix. Published changes are on Updates.

Send the Failing Trace

Attach the log to issue 36. For an AMD or Intel launcher that is black before Play, use the black-window guide.

  • Exact Savage Wind version, GPU model, NVIDIA driver and Windows version.
  • Whether the crash happens before or after Play, and whether the presentation-thread workaround helped.
  • Whether you ran both trace commands in Command Prompt, and whether the log contains the last GPU operations.
Project / system Log location
Savage Wind / Windows
savagewind.log
in the Savage Wind folder.

What's Next