Author Topic: BASS WASAPI crash  (Read 98 times)


  • Posts: 129
« on: 6 Jan '21 - 08:34 »
I have a user who occasionally get this issue usually after returning to the app after leaving his system idling for a few minutes or so. I dont have any idea how I can address this issue and was wondering if the information below is of any value in shedding light on what the cause might be?
It is configured to use wasapi exclusive using event mode

Faulting application name: MusicBee.exe, version: 3.4.7628.34032, time stamp: 0x5fb624f5
Faulting module name: basswasapi.dll, version:, time stamp: 0x5a0c633d
Exception code: 0xc0000005
Fault offset: 0x0000378c
Faulting process id: 0xe08
Faulting application start time: 0x01d6e3d777009fc5
Faulting application path: I:\0_MusicPlayers\MusicBee\MusicBee.exe
Faulting module path: I:\0_MusicPlayers\MusicBee\basswasapi.dll
Report Id: 55d83c30-7246-472d-8a90-e67112641102
Faulting package full name:
Faulting package-relative application ID:

Ian @ un4seen

  • Administrator
  • Posts: 23288
« Reply #1 on: 6 Jan '21 - 14:01 »
I notice you're currently using an old BASSWASAPI version (2.4.2). Please try upgrading to the latest version and see if the crash still happens then, and if it does then get a dump file. You/they can generate a dump file using the ProcDump tool. For example, run "procdump -e -ma -x . yourapp.exe". Then ZIP and upload the generated dump file to have a look at here:

Another way (perhaps easier for the user) to get a dump file is to apply this "localdumps-full" registry entry:

Windows will then generate a dump file in the "%LOCALAPPDATA%\CrashDumps" folder whenever a crash occurs. After they've got a dump file for your app's crash, they can use the "localdumps-off" registry file to disable the dump file generation.


  • Posts: 129
« Reply #2 on: 10 Jan '21 - 05:14 »
It looks like the latest basswasapi.dll does indeed fix the problem