Usually it is a HDD error in an arcade environment. Those things run pretty hot and it is often the first thing that goes in modern cabinets like that.
!analyze -v :110: Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION The CRITICAL_OBJECT_TERMINATION bug check has a value of 0x000000F4. This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. Source: http://msdn.microsoft.com/en-us/library/ms797140.aspx Parameter 1 = 3, so it is a process rather than a thread. The NT session manager SMSS starts vital processes like CSRSS and WINLOGON and waits for them to terminate. If the wait ever completes, SMSS triggers this kind of fault. I've seen a few of these errors, but never on XP (they are easy to trigger under NT4, but I never managed to get them on newer systems ;-)). Fur further diagnostics, one would need a memory dump of the system.
Pretty sure it was caused by a lack of quarters being inserted into it. It felt lonely and neglected and committed software suicide.