live-audio-transcription sample crashes on Windows / Surface Laptop Studio 2

[hansmbakker]

The live-audio-transcription sample sample crashes on my Surface Laptop Studio 2.

Device info:
Surface-model: Surface Laptop Studio 2 Model 2029 i7
SAM: 13.101.139
UEFI: 23.101.143
BIOS-version/-date: Microsoft Corporation 23.101.143 11/27/2025
Wi-Fi driver: 23.160.0.4
Edition: Windows 11 Pro
Operating system build: 26200.8655
Processor: 13th Gen Intel(R) Core(TM) i7-13800H
Installed RAM: 32 GB
Disk space: 97 GB free of 947 GB
GPU: Intel(R) Iris(R) Xe Graphics
NVIDIA GeForce RTX 4050 Laptop GPU
Screen resolution: 2400 x 1600

I have these EPs:

• CUDAExecutionProvider
• WebGpuExecutionProvider
• OpenVINOExecutionProvider
• NvTensorRTRTXExecutionProvider

There is a reproduction repository at https://github.com/[hansmbakker/bugrepro-foundrylocal-crash](https://github.com/hansmbakker/bugrepro-foundrylocal-crash).

There is no error message at all, but when running it in debug mode it crashes with error code 0xc0000409 which Google says is a stack buffer overrun / STATUS_FAIL_FAST_EXCEPTION.

The crash happens after the recorder starts streaming data to the model session.

PS X:\source\transcribe-sanitycheck> dotnet run                                                                          
===========================================================
   Foundry Local -- Live Audio Transcription Demo
===========================================================

Registering execution providers... ◴    Done.

Loading model nemotron-3.5-asr-streaming-0.6b-cuda-gpu:2...done.
       Session started

===========================================================
  LIVE TRANSCRIPTION ACTIVE
  Speak into your microphone.
  Transcription appears in real-time (cyan text).
  Press ENTER to stop recording.
===========================================================

PS X:\source\transcribe-sanitycheck>

[microsoft-github-policy-service]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[a1exwang]

Hi @hansmbakker, could you open issue on Foundry Local repo? They should have better knowledge for these kind of issues.

[hansmbakker]

Apologies, you're right, I mixed up the repos