foster_cabinet
Posts: 1
Joined: Thu Apr 27, 2017 9:53 am

MAME technical problem crash on launch with -video d3d

Thu Apr 27, 2017 10:20 pm

Here is a paste bin of the stack trace after I try and run mame64.exe : https://pastebin.com/BKPHeAnc

I've tried deleting .ini, contents of nvram and cfg. Didn' change.

Using latest mame release (mame0185b_64bit). Tested older versions and same problems. MAME was working fine before.

Other DX9 games on my PC run fine.

I'm not sure what triggered this, the only thing I did different was try to run MAME with rlauncher which I haven't used for awhile.

This is the command line it attempted to execute: "U:\Emulation\MAME\mame64.exe" 1941 -rompath "U:\Emulation\MAME\roms;U:\Emulation\MAME\roms" -nowindow -nohlsl_enable -nogl_glsl -video d3d -artwork_crop -nouse_bezels -use_overlays -use_backdrops -nouse_cpanels -nouse_marquees -nofilter -skip_gameinfo

After that I attempted to run MAME by itself when I seen the stack trace error. And then like I said I tested my older versions of MAME and seen none of them were running anymore. Visited irc chat and discovered it was related to d3d. However my DX9 games on steam are running without issue.

Would like to use d3d as according to the docs it's the best graphics api to use with MAME on Windows.

Stack Trace:

Code: Select all

U:\Emulation\MAME>mame64.exe -video d3d ----------------------------------------------------- Exception at EIP=00007ffb07a4fd0c (register_frame_ctor+0x1d6aa2c): ACCESS VIOLATION While attempting to write memory at 0000000000000000 ----------------------------------------------------- RAX=0000000000000000 RBX=000000000a4574d0 RCX=0000000013e48c60 RDX=000000000fbb20b0 RSI=0000000000000001 RDI=0000000013e3ffa0 RBP=000000000a4577c0 RSP=000000000a457428 R8=000000000a457970 R9=0000000000000000 R10=0000000013e49a7c R11=0000000000000246 R12=0000000000000001 R13=000000000fbb20b0 R14=000000000a457970 R15=0000000000000000 ----------------------------------------------------- Stack crawl: 000000000a457420: 00007ffb07a4fd0c (Direct3DCreate9Ex+0xe82c) 000000000a457460: 00007ffb07a5167f (Direct3DCreate9Ex+0x1019f) 000000000a4576b0: 00007ffb07a676a6 (Direct3DCreate9Ex+0x261c6) 000000000a4578c0: 00007ffb07a6cb68 (Direct3DCreate9Ex+0x2b688) 000000000a457ae0: 00007ffb07a6a81e (Direct3DCreate9Ex+0x2933e) 000000000a457b50: 0000000001b7a404 (renderer_d3d9::device_create(HWND__*)+0x0154) 000000000a457be0: 0000000001b7ab82 (renderer_d3d9::create()+0x00e2) 000000000a457ce0: 0000000001b41464 (win_window_info::complete_create()+0x0324) 000000000a457fe0: 0000000001b420e7 (win_window_info::create(running_machine&, int, std::shared_ptr<osd_monitor_info>, osd_window_config const*)+0x09b7) 000000000a458050: 0000000001b3ddd8 (windows_osd_interface::video_init()+0x0088) 000000000a458160: 0000000001b351e5 (osd_common_t::init_subsystems()+0x1585) 000000000a458490: 0000000001b2d4c8 (windows_osd_interface::init(running_machine&)+0x01e8) 000000000a458590: 00000000031e6791 (running_machine::start()+0x0351) 000000000a458690: 00000000031e84a1 (running_machine::run(bool)+0x01b1) 000000000a45f440: 0000000001bd8cca (mame_machine_manager::execute()+0x00ea) 000000000a45f540: 0000000001c36a25 (cli_frontend::start_execution(mame_machine_manager*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x01d5) 000000000a45f6b0: 0000000001c36c15 (cli_frontend::execute(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x0045) 000000000a45f710: 0000000001bd6f3a (emulator_info::start_frontend(emu_options&, osd_interface&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x002a) 000000000a45fdb0: 0000000001b2d0a2 (utf8_main(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x0122) 000000000a45fe50: 000000000375f609 (wmain+0x0169) 000000000a45ff20: 0000000000401410 (__tmainCRTStartup+0x0260) 000000000a45ff50: 000000000040153b (mainCRTStartup+0x001b) 000000000a45ff80: 00007ffb2ac82774 (BaseThreadInitThunk+0x0014) 000000000a45ffd0: 00007ffb2cf70d61 (RtlUserThreadStart+0x0021)

mhoes
Posts: 22
Joined: Wed Oct 26, 2016 12:26 pm

Re: MAME technical problem crash on launch with -video d3d

Tue May 02, 2017 7:11 pm

For what it's worth: I cannot reproduce this issue with Mame 0.185 on Windows 10 Home x64.

But since you state that (older versions of) Mame were working fine before but not anymore, I suspect something may be wrong with your system/setup. The only thing I can think of that might give some insight into what it might be, is running 'dxdiag'.

Also, you explicitly state DirectX version 9, which makes me wonder what Windows version you are running: Windows XP ?

Return to “MAME Discussion”

Who is online

Users browsing this forum: No registered users and 3 guests