Menu ▾ ▴

#1174 error 0x0c000005

5.0
closed
None
2 days ago
6 days ago
indah
No

Hai Marco,
i try to install beebeep 5.8.6 to win 7 or win 10, when installer success and 1 close/exit the app and run again 1 always get error 0xc000005, what happen?
and i try to install v. 4.0, it work fine
i missing something on my windows?
can you help me to solve my problem?

best regard,
Andi

Discussion

  • Marco Mastroddi

    Marco Mastroddi - 6 days ago

    Hi Andi,

    Thanks for your message. Error 0xc0000005 is an access violation, meaning the program crashes at startup. It is usually not caused by missing files in the Windows installation, so let's try to find out what is happening.

    A common cause is an antivirus removing or blocking some of the program's files after the first launch, so please try the following:

    1. Check your antivirus. Which one are you using? Please look in its quarantine or history for any file removed from the BeeBEEP folder (especially .dll files). Then try installing again with the antivirus temporarily disabled, or add the BeeBEEP folder to its exclusions.
    2. Check the running processes. After closing BeeBEEP, open Task Manager and make sure beebeep.exe is not still running. If it is, end it and try launching again.
    3. Reset the configuration. Rename the file beebeep.ini (in the BeeBEEP folder or in %APPDATA%\BeeBEEP) and start the program again.
    4. Try the portable version. Download the zip package and extract it to a folder where you have write permissions, for example C:\Temp\beebeep.

    If it still doesn't work, please send me the following:

    • A screenshot of the full error message.
    • Your Windows version and architecture (32 or 64 bit). You can find them by typing winver in the Start menu. Please also tell me whether it is a virtual machine.
    • The antivirus you are using.
    • The details of the crash from Event Viewer: go to Windows Logs → Application, find the "Application Error" entry for beebeep.exe, and send me the Faulting module name and the Exception code/offset.
    • The list of files in the BeeBEEP installation folder (open a command prompt in that folder and run dir /s /b > list.txt, then send me list.txt).

    If you are on Windows 7, please also make sure it has Service Pack 1 and the latest updates installed, and that the Microsoft Visual C++ Redistributable 2015-2019 is installed.

    With this information I should be able to understand what is going wrong.

     
  • Anonymous

    Anonymous - 4 days ago

    hai marco,

    1. i try using portable versin is still error
    2. i try rename beebeep.ini is still error
    3. in event viewer - Aplication nothing log, but i found it at System
    4. i not using antivirus
    5. my screen shoot, when i try at win 10
     
  • Marco Mastroddi

    Marco Mastroddi - 4 days ago

    Hi Andi,

    Thanks for the screenshots and the file list, they were very useful.

    What I found

    • Windows 10 22H2 is fully supported, so the problem is not your Windows version.
    • The error "The application was unable to start correctly (0xc0000005)" appears in the System log as an Application Popup (Event ID 26) and not in the Application log. This means BeeBEEP fails while Windows is loading its DLL files, before the program even starts. That is why there is no crash entry in the Application log.
    • Since the portable version fails too and v4.0 works, the cause is most likely one of the Visual C++ runtime DLLs in the BeeBEEP folder (msvcp140.dll, vcruntime140.dll, vccorlib140.dll), not your settings. Renaming beebeep.ini could not help, sorry for that suggestion.

    My main suspicion is that one of these DLLs in the BeeBEEP folder is older than the version the program needs, and it takes priority over the newer one installed in Windows. I cannot confirm it from the file list alone, so please try the steps below in this order.

    Step 1 – Check the DLL versions

    In C:\Program Files (x86)\BeeBEEP, right-click msvcp140.dll → Properties → Details, and tell me the "File version". Do the same for vcruntime140.dll. Please also tell me if you installed v5.8.6 over v4.0 in the same folder without uninstalling v4.0 first.

    Step 2 – Use the system runtime instead of the local one

    1. Download and install the latest Microsoft Visual C++ Redistributable 2015-2022, x86 (32-bit) from Microsoft: https://aka.ms/vs/17/release/vc_redist.x86.exe
    2. In the BeeBEEP folder, rename these files by adding .old at the end:
    3. msvcp140.dll
    4. vcruntime140.dll
    5. vccorlib140.dll
    6. Start BeeBEEP again.

    Step 3 – Clean reinstall (if Step 2 does not help)

    1. Uninstall BeeBEEP from Windows Settings.
    2. Delete the folder C:\Program Files (x86)\BeeBEEP completely.
    3. Install v5.8.6 again.

    Step 4 – If it still fails, find the file that causes it

    1. Download Process Monitor (Sysinternals): https://learn.microsoft.com/sysinternals/downloads/procmon
    2. Run it as Administrator, then add the filter Process Name is beebeep.exe and clear the log.
    3. Start BeeBEEP, wait for the error, then stop the capture.
    4. Go to the end of the list and send me a screenshot of the last 30 or so lines (or save the log with File → Save and attach it).

    Thank you for your patience, with these results I should be able to find the exact cause and fix it in the next release.

     
  • Anonymous

    Anonymous - 2 days ago

    Hi Marco,

    Thank you for your attention and suggestions. I have already tried everything you recommended, including a clean install, but unfortunately, nothing worked. In the end, I had to reinstall Windows, and that finally resolved the issue.

    Thank you again for your time and assistance.

     
  • Marco Mastroddi

    Marco Mastroddi - 2 days ago

    Hi Andi,
    I'm really sorry you had to go through reinstalling Windows—I can imagine what a hassle that must have been. There was likely some issue with a DLL or a corrupted system file somewhere in the old environment, even if it's hard to pinpoint exactly where things went wrong.

    However, I'm very glad to hear that you got it sorted out and that everything is working properly now.

    Thank you again for your patience, your testing, and the feedback! If you ever need anything else in the future, please feel free to reach out.

     

Anonymous
Anonymous

Add attachments
Cancel