Community Q&A

Where Wwise users help each other out!

Audiokinetic's Community Q&A is the forum where Wwise users ask and answer questions within the Wwise community. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

AkSoundEngine.dll caused an Access Violation (crashes Unity editor and runtime builds)?

0 votes
I am constantly getting the following error, which crashes both the Unity editor and the runtime player builds:

"AkSoundEngine.dll caused an Access Violation (0xc0000005)

in module AkSoundEngine.dll at 0033:d6ea50b4."


In the editor, I simply press play, click a menu button, start playing our game, and within 5-30 seconds it will crash the entire Unity editor.

In the runtime player, same thing: load up the game, click through the start menu, and at anytime after a level loads it will crash.


This problem was already present with previous versions of Wwise (2016.2) but seems to have gotten much worse and much more aggressive with the latest version (2017.1.1).


Does anyone have any idea what might be causing this crash, and how to fix it?

I would also love to hear more general advice on how to debug access violations that cause Unity to crash, if that's possible.
asked Sep 28, 2017 in General Discussion by Stephane B. (180 points)

1 Answer

0 votes

You can activate the Debug version of Wwise in the Unity Menu Assets->Wwise->Activate Plugin->Debug.  This will give you a more complete callstack when crashing.  Or simply send the crash dump (.dmp) to with your version information.
answered Oct 5, 2017 by Mathieu J. (Audiokinetic) (7,060 points)
Thanks for this answer, I hadn't thought of that. For everyone else out there: in the meantime, we actually fixed the issue by connecting to the Wwise profiler and noticing that our memory pool was getting filled up quick, so we increased the size of the Default Pool on the AkInitializer.