Error 0xc000007b
Opened this issue · 8 comments
Hi, may I ask how this problem came about? Which operating system and architecture are used?
Windows 10, should be 22h2, x64
I just opened FFmpeg version and immediatly this error came (i have ffmpeg in PATH)
This error-code means STATUS_INVALID_IMAGE_FORMAT. Normally we get it if a 64-bit app tried to load a 32-bit DLL or tried to run on a 32-bit Windows.
Could you please check the Windows Events log? Sometimes Windows provides more information regarding which DLL made the app fail.
Do you get the same error when using FFmpeg? Are there more error messages?
idk in what tab those errors are located, the ffmpeg itself works perfectly (i personally use it for rendering midi into video in ump, zenith or qqs)
i found 2 errors in Windows logs -> System tab:
Log name: System
Source: Service Control Manager
Date: 10/14/2023 12:24:25
Event code: 7023
Task category: None
Level: Error
Keywords:Classic
User: N/A
Computer: Дима-ПК
Description:
The service "NVIDIA LocalSystem Container" terminated due to an error
The group command being executed returned a result that indicates an error.
and this one:
Log name: System
Source: Service Control Manager
Date: 10/14/2023 12:24:25
Event code: 7031
Task category: None
Level: Error
Keywords:Classic
User: N/A
Computer: Дима-ПК
Description:
The NVIDIA LocalSystem Container service terminated unexpectedly. This happened 3 times. The following corrective action will be taken after 10000 ms: Run the configured recovery program.
I tried to reproduce the error but failed. This error does not appear when I corrupt the DLL, use a 32-bit DLL, or use a wrong DLL. The compiler I used to compile it is mingw64 13.1.0. It may be different with the compiler in your environment, which I think is the reason of the error. Additionally, other sources indicate that this error may have many causes. 1 2 3 4
A better solution is that you can try to build it in your PC. You can learn how to build it from the README. Feel free to ask me any questions.
The error in Windows logs doesn't look like it has anything to do with it...