Mame .178 runtime error crash on Windows 10

[maks]

Upgraded to Mame 0.178 for the controller remap fix but mame just won't start on my Win10 machine. Its working fine on my win7 and win8.1 PCs. Other mame version such as 168, 170, and 177 worked fine on win10. I tried re-installing Directx9 and my nvidia graphic drivers. No luck so far. Any ideas on what else to try?

When i launch a game i get a error window that says.. "Visual C++ Runtime Error: The application has requested the runtime to terminate it in an unusual way."

Here is what my CMD prompt says.

D:\Desktop\Mame 0.178>mame64.exe -v
Video: Monitor 65537 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
Physical width 1920, height 1080
Direct3D: Initialize
Direct3D: Configuring adapter #0 = NVIDIA GeForce GTX 670
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 1920x1080
Direct3D: Initialize HLSL
terminate called after throwing an instance of 'emu_fatalerror'
  what():  std::exception

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

[lilshawn]

http://www.microsoft.com/en-us/download/details.aspx?id=35

run as admin and see if it fixes it.


also try removing kb3081424 if it is installed. I think there is an issue with it overwriting some directx files with new ones screwing up dx9.

[maks]

Thanks for the reply. I have 'directx_Jun2010_redist' installed so when I attempted to install dx9c I get an error message saying i already have a newer or equivalent version installed.

I did not have kb3081424 installed. I do have KB3176935, ...36, ...37 installed.

Whats strange is that I installed a version of 178 tverona compiled in his stable controller thread (LINK) and that build worked fine for me. HLSL settings were not enabled in that build even though my mame.ini had "hlsl_enable 1". I rolled back to the regular 178 release and disabled hlsl but im still getting the crash.

[cyberfix]

Whats strange is that I installed a version of 178 tverona compiled in his stable controller thread (LINK) and that build worked fine for me. HLSL settings were not enabled in that build even though my mame.ini had "hlsl_enable 1". I rolled back to the regular 178 release and disabled hlsl but im still getting the crash.

I have the same error with the same results.   Nothing I have tried has been able to get MAME, MAME64, MAMED or MAMEUI64 to work.    If I launch a game in MAMEUI64, it will crash the frontend, but the game will work in a window until I close the error.   I tried the build mentioned above and sure enough, it works with no issues for me.    I thought it must have been something added in build .178 that broke things and probably dealing with the new monitorprovider OSD stuff or controller code, but that is speculation.   I tried build .177 and had no issues either.    I am hoping that since build .179 will have the controller code from the linked build above that it might fix this for those of us with this weird issue.

I am running on Windows 10 64 bit with AMD Radeon HD 5670 graphics card and installed all the DirectX items.

Update:  I have tried compiling my own versions with MAME Compiler 64 v2.0.176 for MAMEUI64.   I tried many different combinations and settings with no success.  I tried a 32 bit build and that did not work either.   Is it possible to get a posting of the differences between the tverona version and standard MAME64 source?