# Unable to call FMOD\_System\_Create() without massive errors

**URL:** <https://qa.fmod.com/t/unable-to-call-fmod-system-create-without-massive-errors/22522>\
**Category:** FMOD Engine\
**Created:** [January 19, 2025, 5:41pm UTC](https://qa.fmod.com/t/unable-to-call-fmod-system-create-without-massive-errors/22522 "2025-01-19T17:41:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![julhe](https://avatars.discourse-cdn.com/v4/letter/j/e56c9b/32.png) [@julhe](https://qa.fmod.com/u/julhe)\
**Post date:** [January 19, 2025, 5:41pm UTC](https://qa.fmod.com/t/unable-to-call-fmod-system-create-without-massive-errors/22522/1 "2025-01-19T17:41:26Z")

</div>

Hey there!

I’m trying to get FMOD to work in my C (not C++) project under Windows 11 with both MSVC and Clang using SDL2 (if that matters). I barely do anything before calling FMOD, so I’m pretty puzzled on what is going on here.

I only call:

```auto
FMOD_System_Create(&system, FMOD_VERSION);

```

Just to be greeted with:

```auto
FMOD error: Error initializing output device.

```

Upon further digging with FMODs debug handlers, I came across this:

```auto
ERROR: FMOD_OS_Init()@C:\buildagent2\work\570ad728b1678096\core_api\platforms\win\src\fmod_os_misc.cpp:104║Frame=#0000000║Thread=0x2A1C║
ERROR: FMOD error: CoCreateInstance returned 0x80040154.

```

I figured this has something to do with OLE32, which is where my knowledge about the Windows API ends.😅 Because I have seen this in the examples, I also tried to call:

```auto
 CoInitializeEx(0, COINIT_APARTMENTTHREADED); 

```

But no luck.

Any ideas?

---

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [January 22, 2025, 4:53am UTC](https://qa.fmod.com/t/unable-to-call-fmod-system-create-without-massive-errors/22522/2 "2025-01-22T04:53:00Z")

</div>

Hi,

A couple of questions:

- What version of FMOD are you using?
- Does your device have functioning audio drivers and output devices? There have been issues in the past on OSes with reduced feature sets that remove audio functionality.
- Are there any other logs from FMOD present?

---

<div class="post-metadata">

**Author:** ![julhe](https://avatars.discourse-cdn.com/v4/letter/j/e56c9b/32.png) [@julhe](https://qa.fmod.com/u/julhe)\
**Post date:** [January 24, 2025, 6:34pm UTC](https://qa.fmod.com/t/unable-to-call-fmod-system-create-without-massive-errors/22522/3 "2025-01-24T18:34:16Z")

</div>

The error disappeared for some reason when I tried to make a reproduction case. The FMOD version was 2.02, there were no other messages besides the one stated, and I’ve confirmed already that audio was working with other applications while this error occurred.

---

<div class="post-metadata">

**Author:** ![Leah\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/leah_fmod/32/3685_2.png) [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)\
**Post date:** [January 28, 2025, 3:44am UTC](https://qa.fmod.com/t/unable-to-call-fmod-system-create-without-massive-errors/22522/5 "2025-01-28T03:44:45Z")

</div>

Happy to hear that the error is seemingly resolved. If you run into any more issues, feel free to let me know!