11. Error Conditions

11.1.1    Player Terminal must be capable of immediately detecting, displaying, recording in a Game error log and communicating to the Backend System, if technically possible, the conditions listed in 11.1.2.

11.1.2  The Player Terminal and all peripherals must be disabled under the following conditions, and may only be enabled after the condition has been resolved:

1. RAM error (RAM defective or Critical Game Data corrupted);
2. Critical Game Software errors, in cases such as:
   
   1. Defective Software Storage Media (SSM);
   2. Hash failure;
   3. Player Terminal application crash; and
   4. Communication errors, e.g. loss of communication with the Backend System;
3. Buffer full;
4. Ticket Reader error (the individual column dispensing Tickets may be disabled instead the entire Player Terminal);
5. Ticket dispensing jam (the individual column dispensing Tickets may be disabled instead the entire Player Terminal);
6. Ticket runaway (more than expected number of Tickets dispensed);
7. Bill Validator jam;
8. Printer mechanism paper jam;
9. Printer cassette out of paper, if there is no alternate means for the Player Terminal to make the payment;
10. Low RAM battery (this condition may be cleared by an attendant as an interim measure until the battery is replaced); and
11. Bill Validator CRC error.

11.1.3  If the Player Terminal is powered down while in an error condition listed in section 11.1.2, then upon restoring power, the error message shall still be displayed and the terminal shall remain disabled, unless power down is used as part of the error reset procedure, or if on power up the terminal checks for the error condition and detects that the error is no longer in existence.

11.1.4  The Player Terminal must, at minimum, upon completion of the current Game inform the player if there is a loss of communication with the Associated Equipment internal to the Play- er Terminal. This message must be visible to the player at all times and may only be removed after the condition has been resolved.

11.1.5  The integrity of Critical Game Data stored in Critical Memory must be continuously moni- tored for corruption by methodology that enables failure detection, backup and recovery of Critical Game Data.
 
11.1.6  In cases when a Player Terminal is disabled by the Backend System, or communication is lost with Associated Equipment, or any other unplayable error condition, the Game must com- plete current Play, print a Voucher for outstanding credits if able, and display an explanatory message. Optionally, the Game may lockup in hand-pay mode without printing the Voucher, and must not exit from this mode until it has been reset by the use of a reset key or other methods approved by the Registrar. The player must be alerted by a conspicuous display viewable from the front of the Player Terminal that alerts the player to see an attendant to receive full payment.