# getNumdrivers failed return FMOD\_ERR\_INVALID\_PARAM

**URL:** <https://qa.fmod.com/t/getnumdrivers-failed-return-fmod-err-invalid-param/19489>\
**Category:** FMOD Engine\
**Tags:** cpp\
**Created:** [November 8, 2022, 6:14am UTC](https://qa.fmod.com/t/getnumdrivers-failed-return-fmod-err-invalid-param/19489 "2022-11-08T06:14:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [November 9, 2022, 12:07am UTC](https://qa.fmod.com/t/getnumdrivers-failed-return-fmod-err-invalid-param/19489/2 "2022-11-09T00:07:24Z")

</div>

Hi,

The `FMOD_ERR_INVALID_PARAM` could be thrown for a couple of reasons, would it be possible to get a full code snippet? Some causes could be, if the `*int` passed into the function is null or the `m_system` fails a validation test in the `getNumDrivers()` function. Initializing the debug system will also help resolve the issue, further explained under [FMOD API | Common](https://fmod.com/docs/2.02/api/core-api-common.html#debug_initialize). To use the debug system you will have to link the fmodL logging dll in your project preferences. Then before calling `System_Create` call `Debug_Initialize(FMOD_DEBUG_LEVEL_LOG)`. This will print out FMOD logs to the output console of your IDE.  
The FMOD\_OUTPUTTYPE will impact the number of drivers used by the system, in reference to calling getNumDrivers(). Using NOSOUND and logging the errors from FMOD is the best way for now.

---

_[View the full topic](https://qa.fmod.com/t/getnumdrivers-failed-return-fmod-err-invalid-param/19489)._