Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06903 Crash/Freeze Critical (emulator) Always 9 days ago 9 days ago
Tester Gryzor1363 View Status Public Platform MAME (Unofficial Binary)
Assigned To Resolution Unable to reproduce OS Windows Vista/7/8 (64-bit)
Status [?] Closed Driver neogeo.cpp
Version 0.195 Fixed in Version Build 64-bit
Summary 06903: neogeo [ncombat and clones]: Ninja Combat crashes MAME upon loading attempt
Description Even though audit is marked as "passed", game crashes MAME when trying to load it, at which point the emulator crashes, and windows displays a generic critical shutdown "program has stopped working" pop-up.

Loading does not make it to the "OK" screen.
Steps To Reproduce Attempt to load game in MAME. Emulator should crash almost instantly upon loading roms. Issue reproduced with the two existing versions of the rom (NGH-009 and NGM-009).
Additional Information Issue experienced via MAMEUI64 0.195, for both auditing step and loading attempts.
Identical behaviour observed via MAMEUI64 0.194 and 0.193.
Regression Version
Affected Sets / Systems neogeo [ncombat and clones]
Attached Files
There are no relationsihp linked to this issue.
User avatar
9 days ago
I'm going to assume you may have outdated cheat files, incomplete romset or MAMEUI is not running neogeo properly for whatever reason.
Just a reminder that no bugs should be reported unless there is some minimal testing with the Official releases (from in a clean install.

You can try to run -verbose to see if anything isn't initializing correctly - you can also try a fresh install to see if maybe you have some corrupted .cfg, .ini, or nvram/memcard file(s).

That said, I cannot duplicate locally with official MAME either with current Git sources or any version of MAME I tested (went back to 0.190)
User avatar
9 days ago
Unable to reproduce on my end as well.
User avatar
9 days ago
edited on: 9 days ago
Tested with MAMEUI64 0.195, works fine.

You might have an old cheat enabled somewhere.

MAMEUI64 automatically makes a verbose.log and a winui.log that might provide a clue.