# Requesting fmod.pdb debug symbols for crash tracking

**URL:** <https://qa.fmod.com/t/requesting-fmod-pdb-debug-symbols-for-crash-tracking/19488>\
**Category:** FMOD Engine\
**Tags:** cpp\
**Created:** [November 8, 2022, 6:01am UTC](https://qa.fmod.com/t/requesting-fmod-pdb-debug-symbols-for-crash-tracking/19488 "2022-11-08T06:01:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neople](https://avatars.discourse-cdn.com/v4/letter/n/f9ae1b/32.png) [@Neople](https://qa.fmod.com/u/Neople)\
**Post date:** [November 8, 2022, 6:01am UTC](https://qa.fmod.com/t/requesting-fmod-pdb-debug-symbols-for-crash-tracking/19488/1 "2022-11-08T06:01:41Z")

</div>

Using : FMOD Engine Core Api 2.02.09  
OS : Windows 10

It only occurs on a specific user’s PC.  
Unfortunately, the audio device information was not confirmed.

Crash occurs intermittently after about an hour of use.  
When I analyzed the crash dump, an exception occurred (0xC0000005) in fmod.dll.  
Here is bit part of crash callstack. (disassembly)

00007FF9CE60A519 mov eax,dword ptr [rdx+1Ch]  
00007FF9CE60A51C lea ecx,[rax+rax]  
00007FF9CE60A51F mov eax,dword ptr [rdx+14h]  
00007FF9CE60A522 add eax,eax  
00007FF9CE60A524 vmovdqu ymm0,ymmword ptr [rbx+rax\*2]

It’s so hard to analysis crash dump. currently not possible.  
Requesting fmod.pdb file for crash tracking.

---

<div class="post-metadata">

**Author:** ![morgan\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/morgan_fmod/32/1766_2.png) [@morgan\_fmod](https://qa.fmod.com/u/morgan_fmod)\
**Post date:** [November 9, 2022, 2:41am UTC](https://qa.fmod.com/t/requesting-fmod-pdb-debug-symbols-for-crash-tracking/19488/2 "2022-11-09T02:41:31Z")

</div>

Hello, and welcome to the FMOD Q&A Forums!

I have uploaded the debug symbols for FMOD Engine 2.02.09 to the Uploads section of your [fmod.com](http://fmod.com) [profile page](https://fmod.com/profile#uploads).

Kind regards,  
Morgan