If your Rocksmith+ closes to the desktop a few seconds after you connect a Helix Stadium over ASIO on Windows, you are not alone and it is not your PC. I spent the last few months on it with Line 6 support (ticket open since July) and finally found the cause.
**What is happening**
The Stadium ASIO driver (version 0.0.3.15, also 0.0.3.13) crashes on its own audio thread whenever a program opens *only input channels*. Rocksmith+ does exactly that when it connects the guitar: 8 inputs, no outputs. DAWs always open outputs too, which is why Ableton and Reaper work fine with the same driver on the same PC. The game's crash handler swallows the error, so you get no message, just the desktop.
I reproduced it outside the game with a small test program, decoded the exact faulting instruction, and sent Line 6 the details and dumps. Until they ship a fix, there is a workaround.
**The workaround: CrashBarrier**
A small open-source (MIT) proxy driver that sits between the game and the Line 6 driver. When a program asks for inputs only, it quietly adds one silent output channel so the driver does not fall over. Everything else passes straight through. With it installed the game connects, calibrates and plays over ASIO.
Install, about five minutes:
Download `CrashBarrier-0.1.0-x64.zip` from https://github.com/NotMyself/crash-barrier/releases
Unzip to a permanent folder, e.g. `C:\Program Files\CrashBarrier`
Open PowerShell 7 **as administrator** in that folder and run `Unblock-File .\*.ps1` then `.\install.ps1 -Stealth`
Launch the game, keep "ASIO Stadium" selected.
`.\uninstall.ps1` puts everything back.
**Before you install, read this**
- It is unofficial. Not from Ubisoft, not from Line 6. Ubisoft support cannot help with it.
- It needs admin rights and changes one registry value so "ASIO Stadium" points at the proxy. Uninstall restores it exactly. The Line 6 files are never touched.
- The DLL is not code-signed. The source is public and the GitHub Actions build is reproducible if you would rather build it yourself.
- Tested on one PC so far: Windows 11, Stadium XL, driver 0.0.3.15. A future Line 6 driver may change things; the README has a one-line check.
- It keeps a log in `%LOCALAPPDATA%\CrashBarrier`. If it does not work for you, open an issue on the repo with that log and I will look.
If you have a Stadium and this fixes it for you, or does not, please say so here. Right now the sample size is me.