Mame64 .177 - Win 10 - crashes on launch/exit, strange audio error

[bmuse]

Hi all,

When I launch mame64.exe by double-clicking, it hangs on a black screen until Windows says the program has stopped working and will be closed. I am able to launch it via Command Line Admin, but when returning to the home menu or trying to exit, it also hangs on a black screen.

The console window shows a number of audio errors -- XAudio2, CreateSourceVoice.

I installed MAME .177 from the executable, fresh install.

It seems to work through the frontend (Maximus Arcade).

Does anyone have any insight?

Thanks very much!
B

[OverLander]

Hello,

I'm new here ....

Did you get anywhere with this bmuse ?

I am having the same kind of issue with Mame0180 64bit on Win 10 / 64bit

I can install and run it for a while but on returning to the pc a few hours later or after reboot I get the same
black screen as bmuse described.

hangs on a black screen until Windows says the program has stopped working and will be closed

The only way to get Mame to work again is to re install Win 10  after a full disk format
If I re install Win 10 from the desktop then Mame will still not load up.

I am rebuilding my upright cab and have new hardware and will be using mGalaxy...

I have ditched my old hardware due to a dead Motherboard and I was running XP no problems.
Now I have new hardware running Win10 and Problems !

Any help or advice on this would be very appreciated ....

[bmuse]

Hey OverLander,

I'm trying a complete fresh install of .177, starting from the .exe and redoing everything including media. I'll definitely post back with any results.

On a semi-related note from another thread, I'm having some audio issues with .177 and may downgrade to my previous .149 -- but will be trying the new install of .177 first.

Doing a Google search on that xAudio error message returns a lot of matches, but on many different programs/Win versions/systems. I'm hoping someone has encountered it, or recognizes it from coding, or something.

B

[Tafoid]

Your best bet is to not use xaudio2 as your sound provider, but use dsound.
Check your mame.ini for:
sound and change the value to "dsound"
or.. if using command-line, use "-sound dsound"

Hopefully that helps!

[bmuse]

Awesome, thank you!  I will definitely do that. Wouldn't have known that was an option.

[OverLander]

I can now run Mame64 from CMD prompt as Admin ...

But it wont run from WIn10 GUI

When I do run Mame64 this way, it cant see the Roms in Rom folder ( I have to point it to the Rom directory )

Below is the output text from CMD Promt..... ( Without starting a rom )

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Windows\system32>C:\Users\Arcade\Desktop\Mame\mame64
m_xAudio2->CreateMasteringVoice( &temp_master_voice, format.nChannels, sample_rate()) failed with error 0x80070490
create_voices(format) failed with error 0x80070490

C:\Windows\system32>

Here is the event log from Event Viewer when Mame64 is run from GUI....

This is obviously telling me that there is a faulting process but I need help translating the code ...

Faulting application name: mame64.exe, version: 0.180.0.0, time stamp: 0x058402e0
Faulting module name: mame64.exe, version: 0.180.0.0, time stamp: 0x058402e0
Exception code: 0xc0000005
Fault offset: 0x000000000165d779
Faulting process ID: 0xe5c
Faulting application start time: 0x01d250a1b062e202
Faulting application path: C:\Users\Arcade\Desktop\Mame\mame64.exe
Faulting module path: C:\Users\Arcade\Desktop\Mame\mame64.exe
Report ID: 6ba6ec8b-cfb5-4c33-8ecc-c4231efb0412
Faulting package full name:
Faulting package-relative application ID:

Anyone ?

Cheers

J

[atxvfx]

I am having the same problem... I can run mame fine from a command line, but from windows explorer it crashes every time.  Windows 10 pro 64bit

[Malarrya2]

I was looking for an answer to this issue and think I may have stumbled upon it myself. I was setting up a computer away from its usual location for use with LaunchBox and MAME either would not load, would crash, or would hang with a black screen. Once I plugged in headphones/speakers, everything ran fine. Hyperspin used to have a similar problem to this. Hope this helps someone.