nebulasleuth
Posts: 2
Joined: Thu Sep 29, 2016 9:11 pm

Mame v0.178 crashes for me. Any one else having this?

Just upgraded from 177 to 178 and a getting a crash as below. Anyone else getting this? I have tried both x86 and x64 versions...

Code: Select all

D:\mame178>mame -v Video: Monitor 65537 = "\\.\DISPLAY1" (primary) Direct3D: Using Direct3D 9 Physical width 1440, height 900 Direct3D: Initialize Direct3D: Configuring adapter #0 = NVIDIA GeForce GTS 450 Direct3D: Using dynamic textures Direct3D: YUV format = RGB Direct3D: Max texture size = 16384x16384 Direct3D: Device created at 1440x900 Direct3D: Initialize HLSL RawInput: APIs detected RawInput: APIs detected RawInput: APIs detected Sound: XAudio2 created initial buffers. total size: 46080, count 10, size each 4608 Sound: XAudio2 initialized. 62 ms. Input: Adding Kbd #0: HID Keyboard Device (device id: \\?\HID#VID_413C&PID_2501&MI_00#8&1b01048&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Kbd #1: HID Keyboard Device (device id: \\?\HID#VID_04F3&PID_0801&MI_00#8&14c99b29&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#8&16eaa1d3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #1: HID-compliant mouse (device id: \\?\HID#VID_04F3&PID_0801&MI_01&Col01#8&27f9b767&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #2: HID-compliant mouse (device id: \\?\HID#VID_1241&PID_1111#7&23b34a47&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#8&16eaa1d3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #1: HID-compliant mouse (device id: \\?\HID#VID_04F3&PID_0801&MI_01&Col01#8&27f9b767&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #2: HID-compliant mouse (device id: \\?\HID#VID_1241&PID_1111#7&23b34a47&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Joy #0: ATRAK Device #1 (device id: ATRAK Device #1) Input: Adding Joy #1: ATRAK Device #2 (device id: ATRAK Device #2) Input: Adding Joy #2: 4-axis, 4-button joystick (device id: 4-axis, 4-button joystick ) ----------------------------------------------------- Exception at EIP=0172f070 (output_win32::send_id_string(HWND__*, long)+0x0020): ACCESS VIOLATION While attempting to read memory at 00000030 ----------------------------------------------------- EAX=00000000 EBX=00000000 ECX=0aea36a0 EDX=00000000 ESI=0000c1aa EDI=0aea36a0 EBP=08e6bd64 ESP=08e6bd1c ----------------------------------------------------- Stack crawl: 08e6bd64: 0172f070 (output_win32::send_id_string(HWND__*, long)+0x0020) 08e6bda4: 0172f20f (output_window_proc(HWND__*, unsigned int, unsigned int, long)@16+0x00af) 08e6bdd0: 74d9d273 (SetManipulationInputTarget+0x0053) 08e6beb8: 74d7e84a (DispatchMessageW+0x08fa) 08e6bf18: 74d7e480 (DispatchMessageW+0x0530) 08e6bf58: 74d88ad9 (MsgWaitForMultipleObjectsEx+0x0309) 08e6bfc0: 770dfef6 (KiUserCallbackDispatcher+0x0036) 08e6bff8: 74d86a3d (PeekMessageW+0x014d) 08e6c078: 01734f42 (winwindow_process_events(running_machine&, int, bool)+0x0072) 08e6c0a8: 0173371b (windows_osd_interface::update(bool)+0x009b) 08e6c108: 02c40586 (video_manager::frame_update(bool)+0x00a6) 08e6c148: 017f0ae5 (mame_ui_manager::set_startup_text(char const*, bool)+0x0085) 08e6c198: 017bbb60 (mame_machine_manager::create_ui(running_machine&)+0x00c0) 08e6c208: 02bdc216 (running_machine::start()+0x0bc6) 08e6c278: 02bdc455 (running_machine::run(bool)+0x0135) 08e6f8f8: 017bdf44 (mame_machine_manager::execute()+0x0184) 08e6fbd8: 0181f100 (cli_frontend::execute(int, char**)+0x0fc0) 08e6fc08: 017bc1d4 (emulator_info::start_frontend(emu_options&, osd_interface&, int, char**)+0x0034) 08e6fe38: 01723ea8 (utf8_main(int, char**)+0x0128) 08e6feb8: 02fc8071 (wmain+0x0161) 08e6ff80: 004013f0 (__tmainCRTStartup+0x0280) 08e6ff94: 76ce62c4 (BaseThreadInitThunk+0x0024) 08e6ffdc: 770d0609 (RtlSubscribeWnfStateChangeNotification+0x0439) 08e700a8: 770d05d4 (RtlSubscribeWnfStateChangeNotification+0x0404)

User avatar
Tafoid
Posts: 295
Joined: Thu Nov 06, 2014 12:50 pm
Location: USA
Contact: Website

Re: Mame v0.178 crashes for me. Any one else having this?

nebulasleuth wrote:Just upgraded from 177 to 178 and a getting a crash as below. Anyone else getting this? I have tried both x86 and x64 versions...

Code: Select all

D:\mame178>mame -v Video: Monitor 65537 = "\\.\DISPLAY1" (primary) Direct3D: Using Direct3D 9 Physical width 1440, height 900 Direct3D: Initialize Direct3D: Configuring adapter #0 = NVIDIA GeForce GTS 450 Direct3D: Using dynamic textures Direct3D: YUV format = RGB Direct3D: Max texture size = 16384x16384 Direct3D: Device created at 1440x900 Direct3D: Initialize HLSL RawInput: APIs detected RawInput: APIs detected RawInput: APIs detected Sound: XAudio2 created initial buffers. total size: 46080, count 10, size each 4608 Sound: XAudio2 initialized. 62 ms. Input: Adding Kbd #0: HID Keyboard Device (device id: \\?\HID#VID_413C&PID_2501&MI_00#8&1b01048&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Kbd #1: HID Keyboard Device (device id: \\?\HID#VID_04F3&PID_0801&MI_00#8&14c99b29&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#8&16eaa1d3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #1: HID-compliant mouse (device id: \\?\HID#VID_04F3&PID_0801&MI_01&Col01#8&27f9b767&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #2: HID-compliant mouse (device id: \\?\HID#VID_1241&PID_1111#7&23b34a47&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#8&16eaa1d3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #1: HID-compliant mouse (device id: \\?\HID#VID_04F3&PID_0801&MI_01&Col01#8&27f9b767&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #2: HID-compliant mouse (device id: \\?\HID#VID_1241&PID_1111#7&23b34a47&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #3: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1602&MI_02#8&389ab7f3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #4: HID-compliant mouse (device id: \\?\HID#VID_D209&PID_1601&MI_02#8&253a70e3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Joy #0: ATRAK Device #1 (device id: ATRAK Device #1) Input: Adding Joy #1: ATRAK Device #2 (device id: ATRAK Device #2) Input: Adding Joy #2: 4-axis, 4-button joystick (device id: 4-axis, 4-button joystick ) ----------------------------------------------------- Exception at EIP=0172f070 (output_win32::send_id_string(HWND__*, long)+0x0020): ACCESS VIOLATION While attempting to read memory at 00000030 ----------------------------------------------------- EAX=00000000 EBX=00000000 ECX=0aea36a0 EDX=00000000 ESI=0000c1aa EDI=0aea36a0 EBP=08e6bd64 ESP=08e6bd1c ----------------------------------------------------- Stack crawl: 08e6bd64: 0172f070 (output_win32::send_id_string(HWND__*, long)+0x0020) 08e6bda4: 0172f20f (output_window_proc(HWND__*, unsigned int, unsigned int, long)@16+0x00af) 08e6bdd0: 74d9d273 (SetManipulationInputTarget+0x0053) 08e6beb8: 74d7e84a (DispatchMessageW+0x08fa) 08e6bf18: 74d7e480 (DispatchMessageW+0x0530) 08e6bf58: 74d88ad9 (MsgWaitForMultipleObjectsEx+0x0309) 08e6bfc0: 770dfef6 (KiUserCallbackDispatcher+0x0036) 08e6bff8: 74d86a3d (PeekMessageW+0x014d) 08e6c078: 01734f42 (winwindow_process_events(running_machine&, int, bool)+0x0072) 08e6c0a8: 0173371b (windows_osd_interface::update(bool)+0x009b) 08e6c108: 02c40586 (video_manager::frame_update(bool)+0x00a6) 08e6c148: 017f0ae5 (mame_ui_manager::set_startup_text(char const*, bool)+0x0085) 08e6c198: 017bbb60 (mame_machine_manager::create_ui(running_machine&)+0x00c0) 08e6c208: 02bdc216 (running_machine::start()+0x0bc6) 08e6c278: 02bdc455 (running_machine::run(bool)+0x0135) 08e6f8f8: 017bdf44 (mame_machine_manager::execute()+0x0184) 08e6fbd8: 0181f100 (cli_frontend::execute(int, char**)+0x0fc0) 08e6fc08: 017bc1d4 (emulator_info::start_frontend(emu_options&, osd_interface&, int, char**)+0x0034) 08e6fe38: 01723ea8 (utf8_main(int, char**)+0x0128) 08e6feb8: 02fc8071 (wmain+0x0161) 08e6ff80: 004013f0 (__tmainCRTStartup+0x0280) 08e6ff94: 76ce62c4 (BaseThreadInitThunk+0x0024) 08e6ffdc: 770d0609 (RtlSubscribeWnfStateChangeNotification+0x0439) 08e700a8: 770d05d4 (RtlSubscribeWnfStateChangeNotification+0x0404)
Can you unplug your joystick(s) and see which one is causing the function which appears to be reading your HID string to malfunction? I'd assume things will work if we can determine that. It also looks like you may be on Windows 10? As I thought I read somewhere.. there IS or WAS a bug very recently causing multiple ID's for the same controller which may also be causing an issue here as well.

There was an external commit that dealt directly with this located here: https://github.com/mamedev/mame/pull/1405

nebulasleuth
Posts: 2
Joined: Thu Sep 29, 2016 9:11 pm

Re: Mame v0.178 crashes for me. Any one else having this?

Yes it is Windows 10.
I unplugged everything except the Keyboard and mouse and tried again. Pretty much the same thing.

Code: Select all

D:\mame178>mame -v Video: Monitor 65537 = "\\.\DISPLAY1" (primary) Direct3D: Using Direct3D 9 Physical width 1680, height 1050 Direct3D: Initialize Direct3D: Configuring adapter #0 = NVIDIA GeForce GTS 450 Direct3D: Using dynamic textures Direct3D: YUV format = RGB Direct3D: Max texture size = 16384x16384 Direct3D: Device created at 1680x1050 Direct3D: Initialize HLSL RawInput: APIs detected RawInput: APIs detected RawInput: APIs detected Sound: XAudio2 created initial buffers. total size: 46080, count 10, size each 4608 Sound: XAudio2 initialized. 31 ms. Input: Adding Kbd #0: HID Keyboard Device (device id: \\?\HID#VID_413C&PID_2501&MI_00#8&1b01048&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Mouse #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#8&16eaa1d3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) Input: Adding Gun #0: HID-compliant mouse (device id: \\?\HID#VID_413C&PID_2501&MI_02#8&16eaa1d3&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}) ----------------------------------------------------- Exception at EIP=0172f070 (output_win32::send_id_string(HWND__*, long)+0x0020): ACCESS VIOLATION While attempting to read memory at 00000030 ----------------------------------------------------- EAX=00000000 EBX=00000000 ECX=0ade3518 EDX=00000000 ESI=0000c1b3 EDI=0ade3518 EBP=08e6bd64 ESP=08e6bd1c ----------------------------------------------------- Stack crawl: 08e6bd64: 0172f070 (output_win32::send_id_string(HWND__*, long)+0x0020) 08e6bda4: 0172f20f (output_window_proc(HWND__*, unsigned int, unsigned int, long)@16+0x00af) 08e6bdd0: 747dd273 (SetManipulationInputTarget+0x0053) 08e6beb8: 747be84a (DispatchMessageW+0x08fa) 08e6bf18: 747be480 (DispatchMessageW+0x0530) 08e6bf58: 747c8ad9 (MsgWaitForMultipleObjectsEx+0x0309) 08e6bfc0: 77d3fef6 (KiUserCallbackDispatcher+0x0036) 08e6bff8: 747c6a3d (PeekMessageW+0x014d) 08e6c078: 01734f42 (winwindow_process_events(running_machine&, int, bool)+0x0072) 08e6c0a8: 0173371b (windows_osd_interface::update(bool)+0x009b) 08e6c108: 02c40586 (video_manager::frame_update(bool)+0x00a6) 08e6c148: 017f0ae5 (mame_ui_manager::set_startup_text(char const*, bool)+0x0085) 08e6c198: 017bbb60 (mame_machine_manager::create_ui(running_machine&)+0x00c0) 08e6c208: 02bdc216 (running_machine::start()+0x0bc6) 08e6c278: 02bdc455 (running_machine::run(bool)+0x0135) 08e6f8f8: 017bdf44 (mame_machine_manager::execute()+0x0184) 08e6fbd8: 0181f100 (cli_frontend::execute(int, char**)+0x0fc0) 08e6fc08: 017bc1d4 (emulator_info::start_frontend(emu_options&, osd_interface&, int, char**)+0x0034) 08e6fe38: 01723ea8 (utf8_main(int, char**)+0x0128) 08e6feb8: 02fc8071 (wmain+0x0161) 08e6ff80: 004013f0 (__tmainCRTStartup+0x0280) 08e6ff94: 77c062c4 (BaseThreadInitThunk+0x0024) 08e6ffdc: 77d30609 (RtlSubscribeWnfStateChangeNotification+0x0439) 08e700a8: 77d305d4 (RtlSubscribeWnfStateChangeNotification+0x0404) 00000000: 03028040 (device_t* device_creator<cgb_lcd_device>(machine_config const&, char const*, device_t*, unsigned int)+0x0090)

Return to “MAME Discussion”