Windows runtime terminating in an unusual way

[eagles051387]

every time i try to open the lmms its stop and tells me (thisapplication has requested the runtime to terminate it in and unusual way ) and than closes the program some one help me please i look on youtube and cant find a video for my problem only video on how to use it

[musikBear]

Please ad your OS ver. and wheater you use the new lmms 1.0 -if not what ver. do you use?

[eagles051387]

This came over from an SF bug feel free to close it if its invalid.

On Wed, Mar 26, 2014 at 12:04 PM, musikBear notifications@github.comwrote:

Please ad your OS ver. and wheater you use the new lmms 1.0 -if not what
ver. do you use?

Reply to this email directly or view it on GitHubhttps://github.com//issues/512#issuecomment-38671117
.

Jonathan Aquilina

[tresf]

It might be valid, but probably best to mark as won't fix for now since this is hard to reproduce and too difficult to determine where the bug actually lies (Windows or LMMS).

I had this issue too. Windows 7 32-bit, LMMS 0.4.15 x86, x64, LMMS 1.0.0 x86, x64. The cause in my case was a bug or misconfiguration with the Conexant Audio Driver supplied from the factory from Toshiba on a Satellite S5200 laptop.

Microsoft Visual C++ Runtime Library
This application has requested the Runtime to terminate in an unusual way. Please contact the applications support team...
Details: libportaudio-2.dll

Duplicate issues:
https://lmms.io/forum/viewtopic.php?f=7&t=392
https://lmms.io/forum/viewtopic.php?f=7&t=286

I would recommend:

1. Open Device Manager
2. Expand Sound and Game controllers
3. Locate your sound card, Right Click, Remove Device
4. Click the Checkbox that says "Remove driver software for this device"
5. Reboot
6. Windows should automatically search for a sound driver. This will take a few minutes.
7. Windows should install a sound driver from Windows updates. Once finished, reboot if needed.
8. If Windows could not located a sound driver, visit the manufacturer website and manually download a sound driver for your computer, install the sound driver manually, reboot if needed.
9. Try LMMS again.

I would suspect there is an avoidable bug where LMMS is trying to access features of the sound driver that aren't available. This will continue to happen, so we need to provide a way to our Windows users to provide us logs so perhaps we can understand exactly why this is happening.

[Sti2nd]

#451

[kifujin]

I posted on the sf.net bug as that was what came up in google for me when searching for the issue https://sourceforge.net/p/lmms/bugs/550/ I was asked to link from here.

I've tried the solution suggested by tresf, removing and installing updated sound drivers. But it didn't change anything with LMMS (although I do have a shiny new interface for my sound card settings now...)

The screenshots are from the win64 build, but identical errors came up with the win32 build. I also have Razer's virtual surround sound drivers installed, but I got identical results after disabling them.

I have jack running (using portaudio_x86.dll) as well, but it seems to have no effect on the issue.

edit: I just tried using the win32 build with the portaudio dll from portaudiosharp, and it works! I'd still like to get the win64 version working as well, though...

[tresf]

Thanks for posting this. When you say you have updated sound drivers are they from the manufacturer or Windows update? In the case of my fix, we needed the Windows update drivers (which I understand are inferior to the manufacturers supplied ones).

To install the Windows update drivers, Windows Update Driver Searching needed to be enabled, and the original driver had to be removed and uninstalled using the "Remove device driver" checkbox in the confirmation dialog upon removal from Device Manager as per the instructions I offered above.

Can you post some details about your hardware? Hardware details may shed some light down the road on why certain people are experiencing this whereas other people are not experiencing this.

You may also want to rename your %USERPROFILE%/.lmmsrc.xml in between trials.

Last, this is fairly obvious but any virus scanning you can do on the PC to ensure the DLLs aren't infected would be of benefit as well.

-Tres

[kifujin]

After rebooting with the drivers uninstalled (following the instructions above, including the checkbox), some generic audio drivers were installed by windows. I tested at that point, and it still wasn't working. I then went to the Realtek site and got the latest Realtek drivers installed, rebooted again, and it's still not working. I haven't been downloading any .dll files from random places (at least not for sound, I've also been trying to get a prodikeys keyboard working on win7 x64, which has gone nowhere...).

Thanks for the location of the config file, I wasn't able to find anything other than the directory before.

I'll be able to test again later and post hardware specs, after sleeping perhaps. I'm also idling in the IRC channel if that would help.

[jeremy-hoke]

This worked for me:

1. Download "PortAudio.dll" from https://code.google.com/p/portaudiosharp/ and rename it to "libportaudio-2.dll"
2. Browse to "C:\Program Files (x86)\LMMS" and replace the existing "libportaudio-2.dll" with the one you just renamed.

[tresf]

This is part of our known issues section available with the release notes starting with version 1.1. Closing.

[BeaQueen]

I tried all the solutions shared on this post and LMMS (version 1.1.3) is still not running on my computer {Windows 10 64bits}.
[Intel i7-6700K 4.GHz, 16RAM GB, Sound card Approx APPPCI71 PCI 7.1]

[musikBear]

error

[tresf]

@BeaQueen This thread is for a general crash when LMMS is closed down fully normally with a click in the red-x, or the file context-menu.

No it's not, it's identical to her problem.

That is different, and does not belong here

It's OK here. Although it's a known issue, it's a quite severe one and @BeaQueen has at least posted to the topic versus creating a new/duplicate.

@BeaQueen have you tried to reinstall your sound card drivers? I've have a computer start working simply by uninstalling the sound card driver and getting a new driver from Windows. In other cases the opposite has helped.

You may also want to move your %USERPROFILE%/.lmmsrc.xml file to see if you can force a fallback on to SDL. Alternatively you can try to copy a config file from another computer with DummyAudio selected and see if that will help it load.

@musikBear is correct in the sense that you'll get more end-user help on the forums. Most of the devs don't run Windows at all, and those that do, can't reproduce the problem, making this bug very difficult to debug from a development perspective, leaving the forums a better home for discussion.

[musikBear]

Why dig in the DB to recreate my mistake. I realized i was on the wrong track emediately and removed the comment?
@BeaQueen If you already has tried as you wrote

I tried all the solutions shared on this post

Then the driver thing is also old news.
One way to get a working LMMS could perhaps be to try the 32x windows version, or perhaps this
https://lmms.io/forum/viewtopic.php?t=392&start=10#p15566
Is what you need?

[BeaQueen]

Well, I'll tell you what happened.
First, I uninstalled all my sound card drivers, LMMS worked but it didn have any sound.
I installed all my sound card drivers, my headphones and my speakers didn't work but LMMS worked.
I configurated all the drivers software, LMMS stopped working again with the Runtime Error again but all my sound stuff was working again.
I downloaded Bitwig and replaced the portaudio for libportaudio. Error 0xc000007b ocurred. I tried it in different ways and nothing worked. I surrender
Thank you all for the info

[Umcaruje]

@BeaQueen could you post your .lmmsrc.xml (its located in your user folder)

You can use a service like https://gist.github.com/ or http://pastebin.com/

[BenMcLean]

Seeing as how this is a serious bug (crash on launch!) that is affecting lots of people making the software completely unusable on current gen systems, why does this issue say closed? Is there an open version anywhere I should be following?

I want to switch to using more free software for my music production and maybe eventually migrate to Linux completely, but I'm stuck using commercial DAW for now because of this.

[tresf]

Seeing as how this is a serious bug (crash on launch!) that is affecting lots of people making the software completely unusable on current gen systems, why does this issue say closed? Is there an open version anywhere I should be following?

The issue was resolved here: #512 (comment)

You're absolutely correct, this is still a bug, but it's not necessarily one we can easily fix. The portaudiosharp library is no longer maintained; built with .NET (Mono) and needs review to see if it's actually GPL2 compliant. Whether this bug is open or closed, we keep this crash as part of our known issues; it's not forgotten.

The underlying problem is most likely an upstream bug with the portaudio library itself and proper resolution should be made with the portaudio team. Since we don't have any active Windows developers, this won't change for a while.

I want to switch to using more free software for my music production and maybe eventually migrate to Linux completely, but I'm stuck using commercial DAW for now because of this.

This won't happen on Linux and I strongly encourage you to try the aforementioned workaround. Note, this doesn't happen on all computers, only some. I believe the issue to be caused by specific device drivers as I've successfully fixed the crash by downgrading and/or upgrading sound card device drivers, which should be attempted in your troubleshooting as well.

Although many developers sympathize with these struggles, we're all here as volunteers and the project is in desperate need of help with debugging this and many other problems.

[musikBear]

@BenMcLean Could you post soundcard and driver information. All information regarding this issue, could eventually be useful.

[BenMcLean]

@musikBear I have RealTek High Definition Audio in my ASUS Q551LN-BBI706 laptop.

If you want me to copy-paste detailed info then let me know what tool to use to get you that info. Anything I can do to get this issue fixed for anyone whom it is still affecting.

But good news: the latest beta seems to work for me! :D

[kifujin]

It's been a while, but I think I eventually found a DLL in system32 that it
was loading instead of the one in the directory for some reason, so I got
the 64 bit version working by uninstalling the thing that was providing
that.

My memory may be flaky, but I think that's what happened...

On Nov 21, 2016 08:34, "Benjamin McLean" notifications@github.com wrote:

I have RealTek High Definition Audio in my ASUS Q551LN-BBI706 laptop.

If you want me to copy-paste detailed info then let me know what tool to
use to get you that info. Anything I can do to get this issue fixed.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#512 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAr81afwsl880VYckPDTCQmJB7l9Sv2ks5rAcgZgaJpZM4Bs7KF
.

[tresf]

It's been a while, but I think I eventually found a DLL in system32 that it was loading instead of the one in the directory for some reason, so I got the 64 bit version working by uninstalling the thing that was providing that.

That's what I've experienced as well. This usually comes down to a driver. (Not excusing the crash) In the one time I've experienced this it was resolved by using Device Manager to remove the sound card using the "Remove driver software" checkbox. Once the driver was reinstalled through Windows update, the problem was resolved.

This technique hasn't work for all people though. There's most certainly a bug with the backend we use however we lack the proper Windows environment to reproduce and then to debug.

[kifujin]

No, I think it was actually a Qt dll.

On Nov 21, 2016 10:09, "Tres Finocchiaro" notifications@github.com wrote:

It's been a while, but I think I eventually found a DLL in system32 that it
was loading instead of the one in the directory for some reason, so I got
the 64 bit version working by uninstalling the thing that was providing
that.

That's what I've experienced as well. This usually comes down to a
drivers. That doesn't excuse the crash, but in the one time I've
experienced this it was resolved by using Device Manager to remove the
sound card using the "Remove driver software" checkbox. Once the driver was
reinstalled through Windows update, the problem was resolved.

This technique hasn't work for all people though. There's most certainly a
bug with the backend we use however we lack the proper Windows environment
to reproduce and then to debug.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#512 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAr8yc7Wmfv10Bi0lOP5-mSGij0xiEeks5rAd5JgaJpZM4Bs7KF
.

[tresf]

No, I think it was actually a Qt dll.

That would certainly cause a crash too. Usually the startup messages mention libportaudio-2.dll, which is sound driver related.