05980: thegrid: MAME crashes with "FATALERROR: Extreme count" after the initial system test.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
05980	Crash/Freeze	Critical (emulator)	Always	Jul 5, 2015, 02:49	Jun 30, 2016, 08:19

Tester	F1ReB4LL	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Fixed	OS	Windows Vista/7/8 (64-bit)
Status [?]	Resolved			Driver	midway/midzeus.cpp
Version	0.163	Fixed in Version	0.175	Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	05980: thegrid: MAME crashes with "FATALERROR: Extreme count" after the initial system test.
Description	MAME crashes with "FATALERROR: Extreme count" after the initial system test.
Steps To Reproduce
Additional Information	format = 0120 00000000002281C0: 00000000014DEA71 (winmain_dump_stack()+0x0041) 0000000000228280: 00000000028CA029 (osd_break_into_debugger(char const)+0x0029) 00000000002282C0: 0000000002485D65 (emu_fatalerror::emu_fatalerror(char const, char)+0x0045) 0000000000228720: 0000000002485FE1 (fatalerror(char const, ...)+0x0041) 0000000000228820: 0000000000988D39 (midzeus2_state::zeus2_draw_model(unsigned int, unsigned short, int)+0x0319) 0000000000228930: 000000000098932D (midzeus2_state::zeus2_fifo_process(unsigned int const, int)+0x05ed) 00000000002289B0: 0000000000989EA2 (midzeus2_state::zeus2_w(address_space&, unsigned int, unsigned int, unsigned int)+0x01e2) 00000000002289F0: 00000000032EBBD2 (address_space_specific<unsigned int, (endianness_t)0, true>::write_dword(unsigned int, unsigned int)+0x00a2) 0000000000228A30: 0000000001A0F93E (tms3203x_device::sti_ind(unsigned int)+0x006e) 0000000000228AA0: 0000000001A2718E (tms3203x_device::execute_run()+0x01de) 0000000000228B40: 000000000247E001 (device_scheduler::timeslice()+0x04b1) 0000000000228BA0: 000000000248AE08 (running_machine::run(bool)+0x0188) 000000000022F690: 000000000247F55B (machine_manager::execute()+0x024b) 000000000022F840: 0000000002521F2B (cli_frontend::execute(int, char)+0x0d9b) 000000000022FDF0: 00000000014DDFE4 (utf8_main(int, char*)+0x0174) 000000000022FE50: 00000000028C8F7E (wmain+0x007e) 000000000022FF20: 00000000004013CA (__tmainCRTStartup+0x024a) 000000000022FF50: 00000000004014F8 (mainCRTStartup+0x0018) 000000000022FF80: 0000000076BF59CD (BaseThreadInitThunk+0x000d) 000000000022FFD0: 0000000076E2B981 (RtlUserThreadStart+0x0021) FATALERROR: Extreme count
Github Commit

Flags
Regression Version
Affected Sets / Systems	thegrid

Attached Files

No.11832 Robbbert Senior Tester Jul 5, 2015, 09:07	Confirmed. After checking the various systems, it says FACTORY SETTINGS RESTORED, and a countdown, but the test screen hasn't been erased. After the countdown is over, or any key pressed, the screen flickers rapidly until the reported crash occurs. Game is marked as not working, but it still shouldn't crash like this.
No.12864 B2K24 Senior Tester Jun 30, 2016, 06:39	Can anyone please confirm if this reported issue got fixed? This set doesn't crash on me using 0.175
No.12866 Osso Moderator Jun 30, 2016, 08:19 edited on: Jun 30, 2016, 08:19	Yes, it doesn't crash anymore. Very probably fixed by Ted Green.