GE Healthcare CT Pace: troubleshooting and error codes
The ServiceForge knowledge base holds 79 documented symptoms for the GE Healthcare CT Pace, with 120 ranked causes, 89 diagnostic checks with test points and expected values, and 491 error codes. Each symptom below shows its causes and the first check; the rest is one connection away. Connect ServiceForge to your AI
Symptoms
XG system failure detected high voltage
XG FAIL LED (D1) is off, indicating one or more failures in the X-ray generator system
Ranked causes
- 1. Over KV condition (unknown)
- 2. Under KV condition (unknown)
- 3. Over MA condition (unknown)
- 4. Filament overcurrent detected (unknown)
- 5. Power supply failure (unknown)
- 6. X-ray tube overheat (unknown)
- 7. Rotor overcurrent (unknown)
- 8. Loose connector connection (unknown)
8 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry rotation initialization failure high voltage
Gantry does not rotate properly or stop at expected positions during power-on initialization
Ranked causes
- 1. Manual/System switch not in correct position (common)
- 2. Gantry not rotating in correct direction or getting stuck (occasional)
- 3. Azimuth position counter not initializing from G.PULSE (occasional)
- 4. Gantry azimuth position not in CCW rest area after initialization (occasional)
Check manual switch position on TGP
- Test point
- TGP manual switch
- Expected
- Switch in SYS or MNL position as required
2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Motor does not rotate caution
Gantry motor fails to spin when voltage command is present
Ranked causes
- 1. No voltage command to servo amp (common)
- 2. RSGO signal not present (common)
- 3. Fuse failure in servo amp (occasional)
- 4. Servo amp failure (rare)
Voltage command signal present
- Test point
- CN1, pins 3-4
- Expected
- 6 V / 1,000 rpm
- Tools
- Multimeter (DMM)
2 more checks with pass and fail actions, 4 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
System does not complete power-up sequence caution
LEDs on processor boards (FMP1, DMP, SMP) halt at a status code instead of progressing to 90H (system ready)
Ranked causes
- 1. Hardware test failure on FMP1, SMP, or DMP board (common)
- 2. DIP switch not configured correctly for P-On tests (common)
- 3. Hardware not installed or not in correct slot (occasional)
- 4. Hard disk or disk controller malfunction (occasional)
Observe LED status on processor boards during power-up
- Test point
- 8 LEDs on FMP1, SMP, DMP boards
- Expected
- LEDs should progress through sequence 01H, 11H-1CH (SMP test), 20H-28H (SMC test), 30H-39H (FPU tests), 40H-4DH (FPU tests), 50H-55H (FMP COM test), 60H (initial boot), 70H (wait OS), 80H (OS start), 8FH-90H (application load)
3 more checks with pass and fail actions, 5 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
14 adjacent channels with 42 channels periodic fail
Periodic band-shaped artifacts appear on image; bands may be localized or span entire image
Ranked causes
- 1. CAM CONT. Board failure (common)
- 2. Output Mux. switch of CAM Board failure (common)
- 3. ADC module failure (common)
Display Processor OVL board test error
LED displays hex status codes 20-2C during overlay board test phase
Ranked causes
- 1. OVL board defective (common)
- 2. CBRD board defective or not generating clock pulse (occasional)
- 3. Defective cable between FILE and DISP nest (occasional)
Verify OVL board test status
- Test point
- OVL Board
- Expected
- Hardware test passes
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
File Processor fails during system initialization
LED displays hex status code 80-83 during INIT routine; system stops with exception or error
Ranked causes
- 1. OS file corrupted or broken (common)
- 2. Memory board failure (common)
- 3. Memory allocation error (occasional)
Verify BOOT diskette availability
- Test point
- Boot drive
- Expected
- BOOT diskette can boot system
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry processor error condition
ERRA LED on TGP board lights, indicating RAM check error, ROM check error, or gantry azimuth initialize error in gantry processor system
Ranked causes
- 1. RAM check error (unknown)
- 2. ROM check error (unknown)
- 3. Gantry azimuth initialize error (unknown)
Scan Processor DMA access error
LED displays hex status codes 50-55; DMA access error or system bus access problem
Ranked causes
- 1. SMP board system bus access error (common)
- 2. Bus request level setting jumper misconfigured on SMP (occasional)
- 3. Daisy chain jumper misconfigured on FILE backplane (occasional)
Verify bus request level setting jumper
- Test point
- SMP Board jumper
- Expected
- Correct jumper position for system configuration
1 more check with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Scan Processor FCP communication error
LED displays hex status codes 32-38 during command write, status read or interrupt reception
Ranked causes
- 1. FCP2 board defective or board number select switch misconfigured (common)
- 2. SMP board defective interrupt receive function (occasional)
- 3. Defective cable between FILE and RECON nest (occasional)
Verify FCP2 board number select switch
- Test point
- FCP2 Board select switch
- Expected
- Switch set correctly for board configuration
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Scan Processor SMC board test error
LED displays hex status codes 20-28 during SMC board hardware test phase
Ranked causes
- 1. SMC board defective (common)
- 2. CBRD board defective or not generating clock pulse (occasional)
- 3. Defective cable between FILE and RECON nest (occasional)
Verify SMC board test status
- Test point
- SMC Board
- Expected
- Hardware test passes
3 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Single channel fail
Single detector channel or input capacitor fails, causing ring artifact or streak on image
Ranked causes
- 1. Single input capacitor failure (common)
- 2. Single detector channel failure (common)
- 3. Single channel data drop during conversion or transfer (occasional)
Measure distance from image center to streak using circle cursor
- Test point
- image center to streak
- Expected
- distance value to identify DAS channel from Ring Radius Chart
Table processor error condition
ERRB LED on TGP board lights, indicating RAM check error, ROM check error, or serial communication error in table processor system
Ranked causes
- 1. RAM check error (unknown)
- 2. ROM check error (unknown)
- 3. OCINTFC to table processor serial communication error (unknown)
Warm up error during initialization radiation
System performs warm-up routine (6 tube warm-up exposures plus 7th stationary scan for data collection). If collected raw data is insufficient or fails analysis, system generates 'WARM UP ERROR' message and halts.
Ranked causes
- 1. Insufficient raw data collected during 7th scan (common)
- 2. X-ray tube not functioning properly (occasional)
- 3. Detector malfunction or misalignment (occasional)
Verify 4 exposures at 120 kV 30 mA complete without error
- Test point
- System display and error log
- Expected
- No error message, exposures logged
3 more checks with pass and fail actions, 3 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Disk formatting required after controller failure or power loss
Hard disk needs formatting due to defective disk controller (FMP2) or sudden power shutdown; procedure also identifies disk-related troubles
Ranked causes
- 1. Defective disk controller (FMP2) (occasional)
- 2. Sudden power shutdown during operation (occasional)
Set Boot select switch S2 and S4 to ON position
- Test point
- Boot select SW on FMP1
- Expected
- Both S2 and S4 ON
9 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
File Processor fails to allocate memory area
LED displays hex status code 83; error during memory allocation phase of INIT
Ranked causes
- 1. Incorrect memory size specification (occasional)
- 2. OS file corrupted or broken (common)
Verify specified memory size
- Test point
- System configuration
- Expected
- Memory size matches system requirement
2 corrective actions and part numbers are in ServiceForge. Connect ServiceForge to your AI
Hard disk seek operation failure during power-up caution
FMP2 test halts indicating hard disk cannot seek to cylinders or read track 0
Ranked causes
- 1. Hard disk not ready, disconnected, or read/write head failure (common)
- 2. Hard disk controller (HDC) malfunction (occasional)
Verify hard disk ready status
- Test point
- HDC status register via FMP2
- Expected
- Disk ready signal asserted; LED status progresses through HD tests
3 more checks with pass and fail actions, 2 corrective actions, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Power-up self-test failure
System indicates power-up test failure via LED status code on processor board during startup sequence
Ranked causes
- 1. Hardware test phase error (common)
- 2. Boot-up phase error (occasional)
Observe LED status on FMP1, SMP, or DMP processor board
- Test point
- LED indicators on processor board
- Expected
- Green/normal condition (no error LED)
1 more check with pass and fail actions are in ServiceForge. Connect ServiceForge to your AI
Tube overheating or oil overpressure detected caution
OH LED on Power Cont board is lit, indicating tube thermal or pressure alarm
Ranked causes
- 1. Tube overtemperature (common)
- 2. Tube oil overpressure (occasional)
Check OH LED status on Power Cont board
- Test point
- OH LED
- Expected
- LED OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
14 adjacent channels fail
Band-shaped ring artifact appears on image across 14 contiguous channels
Ranked causes
- 1. Conditioning circuit failure (common)
168 channels fail
Complete CAM Board failure causing loss of all 168 channels from one board, ring artifact across entire detector
Ranked causes
- 1. CAM Board Bias Voltage failure (common)
7 adjacent channels fail
Band-shaped artifact spanning 7 contiguous channels in image
Ranked causes
- 1. CAM input Mux. chip failure (common)
AC mains power failure caution
ACLN LED on Power Cont board is lit, indicating AC power supply input has failed
Ranked causes
- 1. AC mains power loss or disconnection (occasional)
Verify ACLN LED status
- Test point
- ACLN LED
- Expected
- LED OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Calibration: System warm-up and calibration file correction radiation
Routine to warm up X-ray tube and update system calibration data by comparing current warm-up data with previous reference. Required after software load, generator calibration, detector replacement, or system recalibration.
Ranked causes
- 1. Calibration correction required (common)
Perform tube warm-up: 4 exposures at 120 kV 30 mA
- Test point
- X-ray tube operating parameters
- Expected
- Tube reaches operating temperature, exposures logged
5 more checks with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
CCW rest position check error during initialization high voltage
ERRA LED on when gantry does not stop at correct CCW rest position
Ranked causes
- 1. Position sensor error or gantry mechanical misalignment (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Communication sequence abnormal
LED 0 on OC INTFC (Slot #52) is not blinking or blinking abnormally
Ranked causes
- 1. Communication interface malfunction or module not responding (unknown)
Verify LED 0 blinking pattern on OC INTFC during normal operation
- Test point
- OC INTFC Slot #52, LED 0
- Expected
- Blinking continuously during communication
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Control circuit power supply failure caution
CTLPS LED on Power Cont board is lit, indicating control power supply fault
Ranked causes
- 1. Control power supply malfunction (occasional)
Verify CTLPS LED status
- Test point
- CTLPS LED
- Expected
- LED OFF
CRT display does not show proper response
System unresponsive on display output during File Processor system setup phase
Ranked causes
- 1. Program looping or CPU halt on File Processor (common)
Check HALT LED on FMP1 board
- Test point
- FMP1 Board HALT LED
- Expected
- LED is off
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Disk contains unregistered bad sectors after validation
During disk validation, bad sectors are detected that were not on the original media defect list and must be added to the Lock Out Table (LOT)
Ranked causes
- 1. Bad sectors developed after initial manufacturing (rare)
Check validation output for bad sector errors
- Test point
- Console display during validation phase
- Expected
- No errors or identified READ ERROR at specific PSN values
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display check pattern failure
Display or gantry panel switches do not show proper LED test patterns during initialization
Ranked causes
- 1. Display LED or panel switch malfunction (occasional)
Observe gantry display LED patterns during display check
- Test point
- Gantry display LEDs D1-D8 and panel switches
- Expected
- LEDs illuminate per pattern 0-11 and switches respond to manual input
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display Processor hardware test error
LED displays hex status codes 10-1C during DMP hardware test phase
Ranked causes
- 1. DMP board defective (common)
Verify DMP hardware test completion
- Test point
- DMP Board
- Expected
- Hardware test passes
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display Processor post-processing error after hardware test
LED displays hex status code 5C; error occurs during post-processing verification phase
Ranked causes
- 1. Intermittent hardware fault or test anomaly (rare)
Verify error repeatability
- Test point
- System startup sequence
- Expected
- Error does not reoccur on restart
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Display Processor shows no date/time entry display
CRT display fails to show date/time entry screen during Display Processor system setup
Ranked causes
- 1. Display Processor halt or chain line connection fault (common)
Check HALT LED on DMP board
- Test point
- DMP Board HALT LED
- Expected
- LED is off
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
DMP board not responding during power-up communication caution
LED status halts at 47H during DMP self-test indicating DMP command/response failure
Ranked causes
- 1. DMP board communication failure or not installed (common)
Verify DMP board presence in slot 25
- Test point
- Backplane slot 25
- Expected
- DMP board installed and seated properly
1 more check with pass and fail actions, 1 corrective action, and part numbers are in ServiceForge. Connect ServiceForge to your AI
Exposure excess time detected caution
T0 LED on Power Cont board is lit, indicating HV on time has exceeded 30 seconds
Ranked causes
- 1. High voltage on time exceeds 30 seconds (unknown)
Monitor T0 LED during HV operation
- Test point
- T0 LED
- Expected
- LED OFF during normal exposures
Filament circuit active at high current high voltage
FIL LED on Power Cont board is lit, indicating main HV P/S contact ON and filament current exceeds 2 Amps
Ranked causes
- 1. Filament current elevated above 2 Amps (unknown)
Measure filament circuit current
- Test point
- Filament power circuit
- Expected
- less than 2 Amps
Filament overcurrent detected high voltage
FIL OC LED on Power Cont board is lit, indicating filament circuit overcurrent
Ranked causes
- 1. Filament circuit overcurrent (occasional)
Monitor FIL OC LED during operation
- Test point
- FIL OC LED
- Expected
- LED OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Filament power supply running high voltage
FIL RUN LED on Power Cont board indicates filament supply is actively operating
Ranked causes
- 1. Filament supply circuit active (common)
Verify FIL RUN LED status
- Test point
- FIL RUN LED
- Expected
- LED ON when filament active
File Processor bus error during memory clearing
LED displays hex status code 81; system stops with bus error exception during INIT
Ranked causes
- 1. Memory board defective or bus connection failed (common)
Check error information at memory address
- Test point
- A00H
- Expected
- Bus error exception data present
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
File Processor contradiction detected in software
LED displays hex status code 82; software inconsistency detected during INIT routine
Ranked causes
- 1. OS file corrupted or read error occurred (common)
Verify BOOT diskette and disk initialization
- Test point
- Boot drive and disk
- Expected
- BOOT diskette available; disk successfully initialized
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
FMP1 internal RAM error during power-up caution
LED status halts at 13H during FMP1 power-up self-test indicating RAM failure
Ranked causes
- 1. 512 k static RAM failure or addressing error (occasional)
Observe LED status during FMP1 RAM test
- Test point
- LEDs on FMP1 board
- Expected
- Progress from 12H (Bus Error Check) to 14H (PTM Operation Check); if halts at 13H, RAM failure
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
FMP1 ROM checksum error during power-up caution
LED status halts at 11H during FMP1 power-up self-test indicating ROM error
Ranked causes
- 1. 128 kW EPROM checksum mismatch or corrupted ROM (rare)
Observe LED status during FMP1 test
- Test point
- LEDs on FMP1 board
- Expected
- Progress from 01H to 11H without halting; if halts at 11H, ROM error indicated
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
G.PULSE not detected during CCW rotation high voltage
ERRA LED on when G.PULSE signal not detected during rotation to CCW rest position
Ranked causes
- 1. G.PULSE sensor malfunction or cable disconnection (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry did not reach home position within timeout high voltage
ERRA LED on when gantry does not reach 0 degrees home position within 10 seconds
Ranked causes
- 1. Motor speed too slow or home position sensor malfunction (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry limit position or cable check switch error high voltage
ERRA and GLIMT LEDs on during gantry initialization
Ranked causes
- 1. Limit position switch malfunction or cable error (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry not rotating during initialization high voltage
ERRA LED on but gantry remains stationary
Ranked causes
- 1. Motor stalled or drive circuit failure (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry over speed condition during initialization high voltage
ERRA LED on during rotation indicating excessive speed
Ranked causes
- 1. Motor speed control circuit malfunction (occasional)
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry Processor RAM check failure
LEDs show ERRA, LOOPA, REQA and MNLA all ON during power-on or reset
Ranked causes
- 1. Gantry Processor internal RAM or external RAM failure (rare)
Observe LED status during power-on self-test
- Test point
- ERRA, LOOPA, REQA, MNLA LEDs
- Expected
- LOOPA LED blinking indicates RAM check passed; all four LEDs on indicates failure
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Gantry Processor ROM check failure
LEDs show ERRA, REQA and MNLA ON during power-on or reset after RAM test passes
Ranked causes
- 1. Gantry Processor ROM sum check failure (rare)
Observe LED status during ROM sum check phase
- Test point
- ERRA, REQA, MNLA LEDs
- Expected
- LOOPA LED blinking indicates ROM check passed; three LEDs on indicates failure
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
High voltage fuse F1 or F2 open high voltage
FUSE LED on Power Cont board is lit, indicating one of the main HV fuses has failed
Ranked causes
- 1. Fuse F1 or F2 open circuit (occasional)
Verify FUSE LED status
- Test point
- FUSE LED
- Expected
- LED OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
High voltage generator running normally high voltage
HV RUN LED on Power Cont board indicates high voltage generator is operating at specified parameters
Ranked causes
- 1. HV generator circuit active (common)
Check HV RUN LED status
- Test point
- HV RUN LED
- Expected
- LED ON during HV operation
High voltage output enabled high voltage
HV ON LED on Power Cont board is lit, indicating high voltage is actively generated
Ranked causes
- 1. HV output active (common)
Verify HV ON LED status
- Test point
- HV ON LED
- Expected
- LED ON during X-ray operation
High Voltage Power Supply failure indicated high voltage
HVPS LED on Power Cont board is lit, indicating HV power supply malfunction
Ranked causes
- 1. HVPS circuit malfunction (unknown)
Verify HVPS LED status on Power Cont board
- Test point
- HVPS LED
- Expected
- LED OFF
HV generator inverter module overtemperature caution
TEMP LED on Power Cont board is lit, indicating inverter module thermal fault
Ranked causes
- 1. Inverter module temperature exceeds limit (occasional)
Monitor TEMP LED during operation
- Test point
- TEMP LED
- Expected
- LED OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
HV generator overcurrent detected high voltage
OC LED on Power Cont board is lit, indicating high voltage circuit overcurrent condition
Ranked causes
- 1. Overcurrent in HV circuit (occasional)
Verify OC LED status
- Test point
- OC LED
- Expected
- LED OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
HV generator overvoltage detected high voltage
OV LED on Power Cont board is lit, indicating high voltage output exceeds safe limits
Ranked causes
- 1. HV output voltage exceeds specification (rare)
Verify OV LED status
- Test point
- OV LED
- Expected
- LED OFF
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
Input voltage low
Gantry servo amp 7-segment LED displays V.E indicating input voltage below 85% of normal voltage
Ranked causes
- 1. Input voltage below 85% of normal voltage (unknown)
Microprocessor signal present
µP LED on Power Cont board is lit, indicating signal from microprocessor on FIL CUR CONT ASSY
Ranked causes
- 1. Microprocessor communication active (common)
Motor overspeed detected
Gantry servo amp 7-segment LED displays S.E indicating motor overspeed at 120% of maximum speed
Ranked causes
- 1. Motor running at 120% of maximum speed (unknown)
RAM check error at power-on
LED 3 on OC INTFC (Slot #52) is lit during power-up self-test
Ranked causes
- 1. RAM memory failure or corruption (unknown)
Observe LED 3 on OC INTFC module during power-on
- Test point
- OC INTFC Slot #52, LED 3
- Expected
- Extinguished (normally off); lit indicates RAM check error
1 corrective action and part numbers are in ServiceForge. Connect ServiceForge to your AI
More symptoms
- Read microprocessor error message on FIL CUR CONT
- ROM checksum error at power-on
- Rotor speed at selected operation speed
- Scan Processor abnormal OS or memory corruption
- Scan Processor hardware test error
- Servo alarm during gantry initialization
- Servo amp circuit breaker tripped
- Servo amp commutation error
- Servo amp dynamic brake function failed
- Servo amp over current
- Servo amp over load
- Servo amp over temperature
- SMP board not responding during power-up communication
- System boot fails with program looping or halt
- System in manual mode
- Table Processor RAM check failure
- Table Processor ROM check failure
- X-ray generator aborted by overcurrent
- X-ray generator power on
19 more symptoms with ranked causes and checks are in ServiceForge. Connect ServiceForge to your AI
Error codes
| Code | Meaning | Trigger | Severity |
|---|---|---|---|
01 | Hardware Test program missing from ROM | During power-on self-test initialization | error |
08010003 | NONEXISTENT TARGET TASK | OS attempts to operate on task that does not exist | critical |
08010005 | SEGMENT TABLE FULL | Operating system segment table reaches maximum capacity | critical |
08010006 | DUPLICATE SEGMENT NAME | OS detects duplicate segment name in memory allocation table | critical |
08010008 | INSUFFICIENT MEMORY | Operating system cannot allocate requested memory | critical |
0801000A | NON–DORMANT TARGET TASK | OS attempted operation on task that is not in dormant state | error |
0801000B | LOGICAL ADDRESS CONFLICT | Logical address mapping has conflicting or invalid entries | critical |
08020003 | NONEXISTENT TARGET TASK | Operation references task that does not exist in system | critical |
08020007 | NONEXISTENT SEGMENT NAME | Reference to segment name that does not exist in system | error |
0802000A | NON–DORMANT TARGET TASK | Operation requires dormant task but task is active | error |
08040005 | SEGMENT TABLE FULL | Segment table capacity exceeded | critical |
08040006 | DUPLICATE SEGMENT NAME | Duplicate segment name found during allocation | critical |
08040007 | NONEXISTENT SEGMENT NAME | Requested segment name not found | error |
0804000B | LOGICAL ADDRESS CONFLICT | Address mapping contains conflicting entries | critical |
08060003 | SOURCE TASK NOT FOUND | Inter-task message or operation specifies source task that does not exist | error |
08060007 | DESTINATION TASK NOT FOUND | Inter-task message specifies destination task that does not exist | error |
08060009 | USER TO SYSTEM TASK NOT ALLOWED | User task attempts forbidden operation on system task | error |
0806000B | ADDRESSES DIFFERENT EVEN/ODD BOUNDARY | Memory addresses are not aligned to even/odd boundary as required | error |
08090003 | TARGET TASK NOT FOUND | Operation targets task that does not exist | error |
080B0006 | DUPLICATE TASK NAME | Two tasks have the same name during creation | critical |
080B0008 | INSUFFICIENT MEMORY | Cannot allocate memory for task creation | critical |
080D0003 | TASK DOES NOT EXIST | Task reference points to non-existent task | error |
080D000A | TASK NOT DORMANT | Operation on task that is not in dormant state | error |
080D0023 | TASK DOES NOT EXIST | Task lookup fails because task not found | error |
08100003 | TARGET TASK DOES NOT EXIST | Termination target task not found | error |
08100006 | TARGET TASK ALREADY IN TERMINATION | Task termination attempted but task already terminating | warning |
08100009 | USER TASK CAN NOT TERMINATE SYSTEM TASK OR SELF | User privilege task attempts to terminate system task or itself | error |
08100023 | TARGET TASK DOES NOT EXIST | Task termination references non-existent task | error |
08170003 | TARGET TASK DOES NOT EXIST | Task suspension target not found | error |
0817000A | TASK IS TERMINATING | Task suspension attempted on task that is terminating | warning |
08170023 | TARGET TASK DOES NOT EXIST | Task suspension references invalid task | error |
08190003 | TARGET TASK DOES NOT EXIST | Task stop operation targets non-existent task | error |
08190006 | TARGET TASK ALREADY STOPPED | Task stop attempted but task already stopped | warning |
08190009 | USER TASK CAN NOT STOP SYSTEM TASK | User task attempts to stop system task | error |
08190023 | TARGET TASK DOES NOT EXIST | Stop command references task not found | error |
083A0001 | UNDEFINED XI/O | Undefined extended I/O operation code encountered | error |
083A0002 | UNIMPLEMENTED I/O | I/O operation is not implemented in current system configuration | error |
083A0003 | TASK NOT–EXISTED | I/O operation references task that does not exist | error |
083A0008 | UNDEFINED I/O | OS-level input/output operation on undefined resource | error |
083A0009 | MULTIPLE ASSIGN | Attempt to assign same resource to multiple tasks | error |
083AFF81 | CLOSE ERROR | Failure to close device or file properly | error |
083AFF82 | ALLOCATE ERROR | Failure to allocate system resources | error |
08UUYYZZ | Trap 1 ERROR | FPU Trap 1 exception occurred | error |
1000000C | INSUFFICIENT SYSTEM SPACE | Disk or memory capacity exceeded | error |
10000020 | CFMS CPU TIME OUT | CFMS CPU operation exceeded time limit | error |
10000021 | CFMS CPU FAIL | CFMS CPU failure detected | critical |
10000022 | CFMS LU SPACE FULL | CFMS logical unit storage space exceeded | error |
10000082 | INVALID FUNCTION | Unrecognized or unsupported function called | error |
10000083 | INVALID LOGICAL UNIT | Reference to non-existent logical device unit | error |
10000084 | INVALID DATA BUFFER | Invalid memory buffer address or size | error |
10000085 | INVALID RANDOM RECORD | Attempt to access non-existent record in random access file | error |
10000086 | INVALID PARAM BLOCK ADDRESS | Parameter block pointer is invalid | error |
10000087 | PROTECT CODE ERROR | Violation of file or data protection settings | warning |
10000088 | INVALID BLOCK LENGTH | Magnetic tape block size invalid | error |
10000091 | TAPE MIS–MATCH (800/1600 BPI) | Tape density mismatch | error |
10000092 | FILE NOT FOUND (MT) | Requested file not found on tape | warning |
10000093 | REJECTED BY MT | Tape drive rejected operation | error |
10000094 | DATA SHORT 0 (MT BLOCK READ) | Tape block read returned incomplete data | error |
10000095 | LOST DATA 0 | Data loss during tape operation | critical |
10000096 | ERROR CORRECTED (MT WRITE) | Error detected and corrected during tape write | warning |
10000097 | I/O ERROR (MT DIRECTIVE) | I/O error in tape directive command | error |
10000098 | I/O ERROR (MT PACKET) | I/O error in tape packet operation | error |
10000099 | INCONSISTENCY OF WRITING TYPE (MT) | Tape write format inconsistency detected | error |
1000009A | FILE MARK ERROR (MT) | Tape file mark error detected | error |
100000A0 | INVALID COMMAND | Invalid optical disk command | error |
100000A1 | PBN NOT FOUND | Physical block number not found on disk | error |
100000A2 | UNWRITTEN (READ) | Attempt to read unwritten sector | warning |
100000A3 | DELETED (READ) | Attempt to read deleted sector | warning |
100000A4 | OVER WRITE (WRITE) | Attempt to write to already allocated sector | warning |
100000A5 | ALTERNATE TRACK FULL (WRITE) | Alternate track space exhausted | error |
100000A7 | DON'T SEARCH UNWRITTEN | Search operation encountered unwritten sector | warning |
100000A8 | BUS ERROR | I/O bus communication error | error |
100000A9 | BUS TIME OUT | I/O bus operation timeout | error |
100000AA | DVC TIME OUT | Device operation timeout | error |
100000AB | GPIB COMMUNICATION ERROR | GPIB interface communication failure | error |
100000AC | DISK PARMANENT ERROR (READ) | Permanent disk error on read operation | critical |
100000AD | DISK PARMANENT ERROR (WRITE) | Permanent disk error on write operation | critical |
100000AE | DRIVE ERROR | Disk drive hardware error | error |
100000AF | ODC ERROR | Optical disk controller error | error |
100000C1 | BUFFER OVERFLOW | Data exceeds buffer capacity | error |
100000C2 | END OF FILE | Attempt to read past end of file | info |
100000C3 | END OF VOLUME | Attempt to write past end of storage volume | error |
100000C4 | INVALID OR EMPTY FAB | File access block (FAB) is invalid or uninitialized | error |
100000C5 | INVALID TRANSFER FOR DEVICE | Unsupported data transfer operation for device type | error |
100000C6 | BREAK CONDITION | I/O operation interrupted | warning |
100000C7 | INTERNAL IO ERROR | Internal I/O subsystem failure | error |
100000C8 | FAB/DATA BLOCK CONFLICT | File access block and data block mismatch | error |
100000C9 | RECORD DOES NOT EXIST | Attempt to access non-existent record | warning |
100000CA | RECORD ALREADY EXISTS | Attempt to create duplicate record | warning |
100000CB | RECORD OVERFLOW/TOO MANY RECORDS IN DATA BLOCK | Data block capacity exceeded | error |
100000CC | KEY ERROR, FAB KEY CONFLICT | Key field conflict or duplicate key | error |
100000CD | DISK SPACE FULL | No available disk space for operation | error |
100000D1 | UNRECOVERABLE DEVICE ERROR | Hardware device failure during operation | critical |
100000D2 | DATA COMPARE ERROR | Read data does not match written data | error |
100000D3 | SECTOR PROTECT ERROR | Attempt to write to protected sector | warning |
100000E1 | DEVICE NOT READY | Device is offline or not responding | error |
100000E2 | DEVICE BUSY | Device is busy with another operation | warning |
100000E3 | DATA CRC ERROR | Cyclic redundancy check fails on read | error |
100000E4 | WRITE PROTECTED DEVICE | Attempt to write to write-protected device | warning |
100000E5 | DELETED DATA MARK DETECTED | Read operation encounters deleted data marker | warning |
100000E6 | TIMEOUT | Device operation did not complete within time limit | error |
100000E7 | INVALID SECTOR ADDRESS | Sector address is out of range or invalid | error |
100000E8 | CHECKSUM ERROR | Data checksum validation fails | error |
100000E9 | DISK RESTORE ERROR | Disk recovery or restore operation fails | error |
100000EA | DATA OVERRUN | Data received faster than device can process | error |
100000EB | DEVICE STATUS CHANGED | Device status changed during operation | warning |
100000EC | TRACK/SECTOR ID NOT FOUND | Disk controller cannot find track or sector ID | error |
100000ED | ADDRESS MARK CRC ERROR | Address mark CRC validation fails | error |
100000EF | BAD SECTOR | Disk sector marked as bad or unreadable | error |
100000F1 | CHANNEL BUSY | I/O channel is busy with another operation | warning |
100000F2 | CHANNEL DMA ERROR | Direct memory access channel error | error |
100000F3 | CHANNEL UNRECOVERABLE CHANNEL ERROR | Channel suffered unrecoverable error | critical |
100000F4 | CONTROLLER ERROR | Device controller malfunction | error |
100000F5 | DEVICE CONFIGURATION ERROR | Device not properly configured | error |
100000F6 | DMA BUS ERROR | DMA bus addressing error | error |
100000F7 | DMA MAPPING ERROR | DMA address mapping fails | error |
100000F8 | DMA CONTROLLER ERROR | DMA controller malfunction | error |
10–1C | Scan Processor main data memory error | Error during hardware test of FPU main data memory on SMP local bus | error |
10–1C (Display) | Display Processor main data memory error | Error during hardware test of FPU main data memory on DMP local bus | error |
10UUYYZZ | Trap 2 ERROR | FPU Trap 2 exception occurred | error |
11-1B | Error during FMP1 Board test | Hardware Test phase testing FMP1 Board | error |
18000002 | INVALID COMMAND | FHS received invalid command | error |
18000003 | INVALID LOGICAL UNIT | FHS reference to non-existent logical unit | error |
18000004 | INVALID OR NONEXISTENT VOLUME | FHS volume not found or invalid | error |
18000005 | DUPLICATE FILE NAME | Attempt to create file with existing name | warning |
18000006 | FILE DESCRIPTOR ERROR | File descriptor is invalid or corrupted | error |
18000007 | PROTECT CODE ERROR | File protection violation | warning |
18000008 | RECORD LENGTH ERROR | Record length exceeds maximum or is invalid | error |
18000009 | SHARED SEGMENT ERROR | Error in shared memory segment access | error |
1800000A | INSUFFICIENT DIRECTORY SPACE | Directory storage full | error |
1800000B | ACCESS PERMISSION ERROR | User lacks access permission | warning |
1800000C | INSUFFICIENT SYSTEM SPACE | Overall system storage space exceeded | error |
1800000D | ASSIGNMENT ERROR | Resource assignment error in FHS | error |
1800000E | INVALID DEVICE DEVICE TYPE | Device type not recognized | error |
1800000F | BUFFER OVERFLOW | FHS buffer capacity exceeded | error |
18000010 | INVALID TASK NAME | Task name not recognized | error |
18000011 | INVALID BUFFER ADDRESS | Buffer memory address is invalid | error |
18000012 | INVALID FILE TYPE | File type not recognized or unsupported | error |
18000013 | INTERNAL FHS ERROR | Internal FHS subsystem error | error |
18000014 | INVALID PARAM BLOCK ADDRESS | Parameter block address invalid in FHS | error |
18000015 | DATA BLOCK LENGTH ERROR | Data block length exceeds limit | error |
18000016 | SIZE ERROR | Data size exceeds limit | error |
18000017 | NONEXISTENT FILE NAME | Referenced file does not exist | warning |
18000019 | KEY LENGTH ERROR | Key field length is invalid | error |
1800001A | FAB LENGTH ERROR | File access block length exceeds limit | error |
1800001B | DEFAULT VOLUME NOT DEFINED | System default volume not configured | warning |
1800001C | INVALID STATE FOR COMMAND | Command invalid for current system state | warning |
1800001D | USER NOT OWNER OR ADMINISTRATOR | User lacks authority for operation | warning |
18000020 | CFMS CPU TIME OUT | CFMS CPU timeout in FHS operation | error |
18000021 | CFMS CPU FAIL | CFMS CPU failure detected in FHS | critical |
18000022 | CFMS LU SPACE FULL | CFMS logical unit storage full in FHS | error |
180000CD | DISK SPACE FULL | FHS disk space exhausted | error |
180000D1 | UNRECOVERABLE DEVICE ERROR | FHS device hardware failure | critical |
180000D2 | DATA COMPARE ERROR | FHS data integrity check fails | error |
180000D3 | SECTOR PROTECT ERROR | FHS sector protection violation | warning |
180000E1 | DEVICE NOT READY | FHS device offline or unresponsive | error |
180000E2 | DEVICE BUSY | FHS device busy with another operation | warning |
180000E3 | DATA CRC ERROR | FHS data CRC validation fails | error |
180000E4 | WRITE PROTECTED DEVICE | FHS write protected media | warning |
180000E5 | DELETED DATA MARK DETECTED | FHS encounters deleted data marker | warning |
180000E6 | TIMEOUT | FHS operation timeout | error |
180000E7 | INVALID SECTOR ADDRESS | FHS sector address out of range | error |
180000E8 | CHECKSUM ERROR | FHS checksum validation fails | error |
180000E9 | DISK RESTORE ERROR | FHS disk restore operation fails | error |
180000EA | DATA OVERRUN | FHS data transfer rate exceeded | error |
180000EB | DEVICE STATUS CHANGED | FHS device status change during operation | warning |
180000EC | TRACK/SECTOR ID NOT FOUND | FHS disk track/sector ID not found | error |
180000ED | ADDRESS MARK CRC ERROR | FHS address mark CRC fails | error |
180000EE | SEEK ERROR | FHS disk seek operation fails | error |
180000EF | BAD SECTOR | FHS bad sector detected | error |
180000F1 | CHANNEL BUSY | FHS I/O channel busy | warning |
180000F2 | CHANNEL DMA ERROR | FHS DMA channel error | error |
180000F3 | UNRECOVERABLE CHANNEL ERROR | FHS channel unrecoverable error | critical |
180000F4 | CONTROLLER ERROR | FHS controller malfunction | error |
180000F5 | DEVICE CONFIGURATION ERROR | FHS device not properly configured | error |
180000F6 | DMA BUS ERROR | FHS DMA bus error | error |
180000F7 | DMA MAPPING ERROR | FHS DMA address mapping fails | error |
180000F8 | DMA CONTROLLER ERROR | FHS DMA controller malfunction | error |
18UUYYZZ | Trap 3 ERROR | FPU Trap 3 exception occurred | error |
20000001 | UNDEFINED DIRECTIVE | Undefined load file directive | error |
20000012 | OUT OF SEGMENT AREA | Load address exceeds segment limits | error |
20000013 | FILE IS NOT A LOAD FILE | File format not recognized as load file | error |
20–28 | Scan Processor SMC board hardware test error | Error during SMC board hardware test | error |
20–2C (Display) | Display Processor OVL board test error | Error during OVL board hardware test | error |
21-11 | Error during MRX Board test | Hardware Test phase testing MRX Board | error |
28YY0001 | Directive No. remains undecided | DMA directive number not determined | error |
28YY0002 | Invalid Parameter Block Address | DMA parameter block address invalid | error |
28YY0003 | Invalid direction Code | DMA direction code invalid | error |
28YY0004 | Invalid memory address | DMA memory address out of range | critical |
28YY0005 | Invalid Data Size | DMA data size invalid or out of range | error |
28YY0006 | Invalid CPU number | DMA CPU number not recognized | error |
28YY0080 | Channel Busy | DMA channel in use | warning |
28YY0081 | Configuration Error | DMA configuration is invalid | critical |
28YY0082 | Operation Timing Error | DMA operation timing constraint violated | error |
28YY0084 | Address Error | DMA address error detected | critical |
28YY0085 | Address Error | DMA address boundary error | critical |
28YY0086 | Address Error | DMA address range error | critical |
28YY0087 | Address Error | DMA memory address error | critical |
28YY0088 | Bus Error | DMA bus error detected | critical |
28YY0089 | Bus Error | DMA system bus error | critical |
28YY008A | Bus Error | DMA I/O bus error | critical |
28YY008B | Bus Error | DMA memory bus error | critical |
28YY008C | Count Error | DMA count value error | error |
28YY008D | Count Error | DMA transfer count error | error |
28YY008E | Count Error | DMA packet count error | error |
28YY008F | Count Error | DMA sequence count error | error |
28YY0090 | External Compulsory Stop | DMA external halt signal received | info |
28YY0091 | Software Compulsory Stop | DMA software halt signal sent | info |
28YY00A0 | Time Out | DMA operation exceeds time limit | error |
2D–2E (Display) | Display Processor IFB2 board test error | Error during IFB2 board hardware test | error |
30–31 | Scan Processor FCP3 test error | Error during FCP3 board hardware test on SMP local bus | error |
30–31, 39 (Display) | Display Processor local bus memory test error | Error during FPU main data memory test on DMP local bus | error |
31-39 | Error during FMP2 Board test | Hardware Test phase testing FMP2 Board | error |
32–38 | Scan Processor FCP command/status communication error | Error during command write, status read or interrupt between FPU and SMP | error |
32–38 (Display) | Display Processor FCP communication error | Error during command write, status read or interrupt between FPU and DMP | error |
40–41, 49 | Scan Processor FCP3 address signal error | Error in FCP3 board test or local bus address signal | error |
41-43 | Communication error between FMP and SMP | Hardware Test phase when testing FMP-SMP communication | error |
42–48 | Scan Processor FCP command/status error variant | Error during command write, status read or interrupt between FPU and SMP | error |
45-4F | Communication error between FMP and DMP | Hardware Test phase when testing FMP-DMP communication | error |
48YY0001 | Directive No. Error | Image data unpack directive invalid | error |
48YY0002 | Odd parameter Address | Image unpack parameter address is odd | error |
48YY0003 | Unpack Task is Busy | Image unpack task still processing | warning |
48YY0004 | Unpack Task is not Busy | Image unpack task unexpectedly idle | warning |
48YY0010 | Odd Information Block Address | Image info block address is misaligned | error |
48YY0011 | Invalid parameter | Image unpack parameter invalid | error |
48YY0020 | Not Same Task | Different task completed unpack than requested | error |
4A–4B | Scan Processor DBU board test error | Error during DBU board hardware test | error |
50 | Directive No. Error | Invalid directive number sent to display system | error |
500000F0 | Image Type is not Supported | Display system does not support image type | error |
500000F1 | Display Task is Busy | Image display task currently processing | warning |
500000F2 | Invalid file Name | Image file name invalid or file not found | error |
500080YY | Task abort | Image display task aborted | error |
50–55 | Scan Processor DMA access error | DMA access error or system bus access channel fault | error |
50–55 (Display) | Display Processor system bus access error | DMA access error or system bus access channel fault | error |
51 | Odd Parameter Address | Parameter address is odd rather than even | error |
53 | Invalid Request | Request to display system is invalid or malformed | error |
5314**30 | TARGET CPU HALT | Specified CPU halted unexpectedly | critical |
5314**31 | TARGET CPU NONEXISTENT | Reference to non-existent CPU | error |
5323**30 | TARGET CPU HALT | Specified CPU halted unexpectedly | critical |
5323**31 | TARGET CPU NONEXISTENT | Reference to non-existent CPU | error |
56 | Invalid Parameter (W/L Control) | Invalid window/level control parameter received | warning |
57 | Invalid Parameter (Frame Setting) | Invalid frame setting parameter | warning |
58 | Invalid Parameter (Frame Data) | Invalid frame data received | error |
59 | Invalid Parameter (W/L) | Invalid window/level parameter | warning |
5A | Invalid Parameter (Identify) | Invalid identification parameter | warning |
5C | Invalid Parameter (Image Display) | Invalid image display parameter | error |
5C (Display) | Display Processor post-processing error | Error occurs during post-processing after hardware test | warning |
5D | Invalid Parameter (Image Data Read) | Invalid image data read parameter | error |
5E | Invalid Parameter (Paging) | Invalid paging parameter | warning |
5F | Invalid Parameter (Interrupted Display Processing) | Invalid parameter during interrupted display operation | warning |
60 | Invalid Parameter (Interrupted FPU Processing) | Invalid parameter during interrupted FPU operation | error |
60 | Abnormal termination during boot before vector set | Boot-up (IBOOT) phase before CPU vector initialization | critical |
60 | Scan Processor ROM or interrupt error | Abnormal exception during SMP ROM boot before vector set | error |
60 (Display) | Display Processor ROM or interrupt error | Abnormal exception during DMP ROM boot before vector set | error |
62 | Hard Disk or Floppy Disk error during boot | Boot-up (IBOOT) phase when accessing disk drive | critical |
63 | Information sector 0 of disk not proper | Boot-up (IBOOT) phase when reading disk | critical |
64 | Exception during FMP1 ROM execution (not Bus/Address Error) | Boot-up (IBOOT) phase during ROM execution | critical |
65 | Bus or Address Error during FMP1 execution | Boot-up (IBOOT) phase during ROM execution | critical |
68 | Time Out (Image Display) | Image display operation exceeds time limit | error |
69 | Time Out (Graphic Cursor) | Graphic cursor operation exceeds time limit | warning |
6A | Time Out (W/L Processing) | Window/level processing operation exceeds time limit | warning |
6B | Time Out (Interrupted Display Processing) | Interrupted display processing exceeds time limit | warning |
6C | Time Out (Interrupted FPU Processing) | Interrupted FPU processing exceeds time limit | error |
6F | Graphic Sequence Error | Graphical operation sequence error detected | error |
70 | Exception during IPLT (Initial Program Load Test) execution | OS File Loading phase during boot loader execution | error |
70 | Directive No. Error | Invalid directive for PLNCTL task | error |
70 | Scan Processor OS loading error | Exception during IPLT run for OS loading | error |
70 (Display) | Display Processor OS loading error | Exception during IPLT run for OS loading | error |
71 | Odd Parameter Address | Odd parameter address for PLNCTL | error |
72 | Device No. Error | Invalid device number | error |
72 | OS file not found on specified disk | OS File Loading phase searching for OS file | error |
73 | Invalid Request | Invalid request to PLNCTL | error |
73 | Scan Processor OS loading timeout | OS for FMP has not started or loading timeout | error |
73 (Display) | Display Processor OS loading timeout | OS for FMP has not started or loading timeout | error |
74 | Hard Disk or Floppy Disk error during OS loading | OS File Loading phase when accessing disk drive | critical |
76 | Invalid Parameter (Erase Processing) | Invalid erase operation parameter | warning |
77 | Invalid Parameter (Graphic DMA) | Invalid DMA parameter for graphics | error |
78 | Invalid Parameter (Screen Save) | Invalid screen save parameter | warning |
79 | Invalid Parameter (Overlay Display) | Invalid overlay display parameter | warning |
7A | Invalid Parameter (Graphic Cursor) | Invalid graphic cursor parameter | warning |
7C | Invalid Parameter (LED/Buzzer) | Invalid LED or buzzer control parameter | unknown |
80 | Time Out (Erase Processing) | Erase operation exceeds time limit | error |
80 | File Processor initialization exception | Exception during INIT routine execution | error |
8010 | BUS ERROR | Processor bus error | critical |
8011 | ADDRESS ERROR | Invalid memory address access | critical |
8012 | ILLEGAL INSTRUCTION | CPU encountered undefined instruction | critical |
8013 | ZERO DIVIDE | Division by zero attempted | error |
8014 | CHK INSTRUCTION | CHK instruction condition violated | error |
8015 | TRAPV INSTRUCTION | TRAPV instruction trap condition | error |
8016 | PRIVILEGE VIOLATION | Privilege instruction executed in user mode | critical |
8017 | UNIMPLEMENTED INSTRUCTION ('1010') | CPU encountered unimplemented 1010 instruction | critical |
8018 | UNIMPLEMENTED INSTRUCTION ('1011') | CPU encountered unimplemented 1011 instruction | critical |
80 (Display) | Display Processor initialization exception | Exception during INIT routine execution on DMP | error |
80 (Scan) | Scan Processor initialization exception | Exception during INIT routine execution on SMP | error |
81 | File Processor bus error during memory clear | Bus error exception during memory clearing in INIT | error |
81 | Time Out (Graphic DMA) | DMA transfer for graphics exceeds time limit | error |
81 (Display) | Display Processor bus error during memory clear | Bus error exception during memory clearing in INIT | error |
81 (Scan) | Scan Processor bus error during memory clear | Bus error exception during memory clearing in INIT | error |
82 | File Processor software inconsistency detected | Contradiction found in software during INIT routine | error |
82 | Time Out (Screen Save–overlay) | Screen save with overlay exceeds time limit | warning |
82 (Display) | Display Processor software inconsistency | Software inconsistency detected during INIT routine | error |
82 (Scan) | Scan Processor software inconsistency | Software inconsistency detected during INIT routine | error |
83 | File Processor memory allocation error | Error during memory area allocation in INIT | error |
83 | Time Out (Screen Save–Image) | Screen save for image exceeds time limit | warning |
83 (Display) | Display Processor memory allocation error | Error during memory area allocation | error |
83 (Scan) | Scan Processor memory allocation error | Error during memory area allocation | error |
84 | Scan Processor terminal display port timeout | Timeout on DMP terminal display port during initialization | error |
84 | Time Out (Graphic Cursor) | Graphic cursor update exceeds time limit | warning |
84 (Display) | Display Processor terminal display port timeout | Timeout on DMP terminal display port during initialization | error |
8E | ACRTC Command Error | CRT controller command execution fails | critical |
8F | Graphic Sequence Error | Graphics command sequence error | error |
90 | Directive No. Error | Invalid directive for KBDRY task | error |
90 | File Processor program loop or CPU halt | Program enters infinite loop or CPU halts | error |
90000001 | PINT (FPU → CPU Interrupt) | FPU signals interrupt to CPU | info |
90000002 | RESET | FPU reset completed | info |
90000003 | INVALID PARAMETER | Invalid parameter sent to FPU | warning |
90000004 | TIME OUT | FPU operation exceeds time limit | error |
90000005 | BUSY (FPU RUNNING) | FPU currently executing operation | warning |
90000006 | BUSY (FPU INITIALIZING) | FPU initialization in progress | info |
90000007 | ILLEGAL (Error Occurred in FPU) | FPU internal error detected | critical |
9000000B | INTERRUPT OVER (Interrupt Buffer Overflow) | FPU interrupt buffer exceeded capacity | error |
90 (Display) | Display Processor program loop or halt | Program enters infinite loop or CPU halts | error |
90 (Scan) | Scan Processor program loop or halt | Program enters infinite loop or CPU halts | error |
91 | Invalid Parameter Block Address | Invalid keyboard parameter block address | error |
92 | Invalid Parameter | Invalid keyboard parameter | warning |
93 | Invalid Request | Invalid keyboard request | warning |
94 | Can't requested Command | Keyboard cannot execute requested command | warning |
95 | Invalid No. of Characters | Keyboard command has invalid character count | warning |
98 | Key Board not allocated | Keyboard device not properly allocated | error |
99 | Channel Busy | Keyboard channel is busy | warning |
9A | Response Time Out | Keyboard response exceeds time limit | error |
9C | Hardware Error | Keyboard hardware malfunction detected | critical |
9D | Hardware Error | Keyboard hardware malfunction | critical |
9E | Hardware Error | Keyboard hardware error | critical |
9F | Hardware Error | Keyboard hardware error | critical |
A0000001 | I. D No. Error | Raw data ID number error | error |
A0000002 | Not Valid | Raw data validity check fails | error |
A0000003 | Transfer Byte Error | Raw data byte count mismatch | error |
A0000004 | Sub Code Error | Raw data sub-code error | error |
A0000005 | Size Error | Raw data size mismatch | error |
A0000006 | Can not Reserve | Raw data cannot be reserved/allocated | error |
A0 (Display) | Display Processor abnormal memory | Abnormal memory condition during application task | error |
A0 (Scan) | Scan Processor abnormal memory | Abnormal memory condition during application task | error |
A1 | Invalid Parameter | Invalid parameter for User/Prime Display function | warning |
A1 (Display) | Display Processor task start failure | Abnormal termination due to memory layout or task configuration error | error |
A1 (Scan) | Scan Processor task start failure | Abnormal termination due to memory layout or task configuration error | error |
A2 | Not Defined Area | Display area not defined in configuration | error |
A3 | Duplicate Define | Display area defined more than once | error |
A4 | Value Not Defined | Required display value not defined | error |
A5 | Invalid Area Position | Display area position is invalid | warning |
A6 | Invalid Area Size | Display area size is invalid | warning |
AA | DCB Graphic Flag Double Assigned | DCB graphics flag assigned to multiple areas | error |
B7 | Read Event Flag Error | Event flag read operation fails | error |
B8 | Event Status Error | Event status is invalid or corrupted | error |
B9 | Event Busy Error | Event system busy or blocked | warning |
BA | Not Enable Mag. Character Error | Magnetic character support not enabled | warning |
BB | Cancel Flag Error | Cancel flag operation fails | warning |
BC | Over Split Over Error | Over-split condition detected | error |
BD | Not Split Device Error | Device split configuration missing | error |
BE | Over Line Error | Over-line condition detected | error |
BF | Invalid Parameter Error | Invalid parameter in WTTY system | warning |
C0 | Write FIFO Empty Time Out Error | Write FIFO remains empty beyond timeout | warning |
C1 | Write FIFO Ready Time Out Error | Write FIFO not ready within timeout | error |
C2 | Read FIFO Ready Time Out Error | Read FIFO not ready within timeout | error |
C3 | Read FIFO Empty Time Out Error | Read FIFO becomes empty before timeout expected | warning |
C5 | Command End Time Out Error | Command execution does not complete in time | error |
C8 | Command Error | Command execution fails | error |
C.E. | Communication Error | Digital signal path between servo amp and motor is degraded or broken | critical |
CF | ACRTC NOT READY | Display CRT controller not ready | critical |
D0 (Display) | Display Processor bus error exception | Bus error from accessing absent address or invalid instruction | error |
D0 (Scan) | Scan Processor bus error exception | Bus error from accessing absent address or invalid instruction | error |
D1 | Configuration Error | System configuration is invalid | critical |
D1 (Display) | Display Processor address error exception | Word reference to odd number address | error |
D1 (Scan) | Scan Processor address error exception | Word reference to odd number address | error |
D2 | Operation Timing Error | Operation timing constraint violated | error |
D2~D8 (Display) | Display Processor instruction/memory corruption error | Incorrect instruction or corrupted memory detected | error |
D2~D8 (Scan) | Scan Processor instruction/memory corruption error | Incorrect instruction or corrupted memory detected | error |
D4 | Address Error | Memory address error detected | critical |
D8 | Bus Error | System bus error detected | critical |
DC | Count Error | Counter or count value error | error |
E0 | Abort | Operation aborted by user or system | warning |
E0 (Display) | Display Processor task abort error | Abnormal termination of OS-related task | error |
E0 (Scan) | Scan Processor task abort error | Abnormal termination of OS-related task | error |
E1 | Software Abort | Software-initiated operation abort | warning |
E8 | DMAC Ready Time Out Error | DMA controller not ready within timeout | critical |
EF (Display) | Display Processor abnormal OS | Abnormal OS detected during application task | error |
EF (Scan) | Scan Processor abnormal OS | Abnormal OS detected during application task | error |
ER-001 | System Error | Error of Directive/System Subroutine | error |
ER-002 | Undefined Event Received | Failure in Event Data communication message | warning |
ER-003 | Abnormal Termination Detected | Task terminated abnormally | error |
ER-004 | Task Termination | EDSP detected task termination | info |
ER-099 | TREND Task Error | Error during message registration to disk | error |
ER-100 | Aperture Error | Aperture positioning or command error | error |
ER-101 | Axial Scan Error | Axial scan command or execution error | error |
ER-102 | Gantry Error | Gantry positioning or rotation error | error |
ER-103 | Stationary Scan Error | Stationary scan command or execution failure | error |
ER-104 | Manual Gantry Error | Manual gantry operation failure | error |
ER-105 | Gantry Communication Error | Communication failure between TGP and Scan Processor | error |
ER-106 | Tilt Error | Tilt request out of range | warning |
ER-107 | Scout Scan Error | Scout scan execution failure | error |
ER-109 | Cradle Mode Error | Cradle mode operation failure | error |
ER-111 | Table Electrical Communication Error | Communication failure with table electronics | error |
ER-115 | TGE Response Timeout | TGE subsystem fails to respond in time | error |
ER-116 | XG Response Timeout | X-ray generator fails to respond in time | error |
ER-117 | XG Fail | X-ray generator failure | critical |
ER-118 | SCNCTL Sequence Error | Scan control sequence error | error |
ER-131 | Comm. Receive Buffer Over | Communication receive buffer overflow | warning |
ER-132 | Comm. Transmit Buffer Over | Communication transmit buffer overflow | warning |
ER-133 | Comm. Write Reg. Ans. Timeout | No answer to register write command | error |
ER-135 | PNLCTL Sequence Error | Panel control sequence error | error |
ER-140 | Anode Temperature Over | Tube anode temperature exceeds limit | warning |
ER-141 | Case Temperature Over | Tube case temperature exceeds limit | warning |
ER-151 | Scan Timeout | Scan data collection did not complete | error |
ER–152 | Warm up Error | During system warm-up, reference channel mean value, high frequency component, rate, or standard deviation out of specification | error |
ER–153 | Initialize Air Data Error | During air calibration initialization, data validation fails | error |
ER–160 | Event Sequence Error | Incorrect sequence of update, OK/NO decision, or soft key events due to off-line end demand or manual soft key operation | warning |
ER–201 | Recon Timeout | Image reconstruction does not complete within specified time limit | error |
ER–202 | Invalid Parameter | Parameter conversion error between Operator interface and CPU during reconstruction | critical |
ER–400 | Duplicate Study ID Deleted | Multiple STUDY IDs found in STUDY POINTER area during data consistency check | warning |
ER–401 | No Study Inf. ID Deleted | STUDY POINTER exists but corresponding STUDY INF. record not found | warning |
ER–402 | Illegal Study Eye Catcher | STUDY INF. header signature (eye catcher) does not match expected value | warning |
ER–403 | Illegal Study ID Deleted | STUDY ID in chained STUDY INF. differs from STUDY POINTER's STUDY ID | warning |
ER–404 | Study in Old Area Deleted | STUDY POINTER references new STUDY INF. in old memory area during area reorg | warning |
ER–405 | Old Study Inf. Study Deleted | STUDY POINTER references old STUDY INF. in new memory area | warning |
ER–406 | Same Area Inf. Study Deleted | Duplicate STUDY POINTER found with same memory area reference in STUDY INF. | warning |
ER–407 | No Buffer for Image Inf. | IMGINF buffer space not allocated or not found when attempting to read | error |
ER–408 | Image Inf. Size Over | IMGINF data exceeds allocated buffer size when reading from storage | error |
ER–409 | Illegal Image Inf Eye Catcher | IMGINF header signature (eye catcher) does not match expected value | warning |
ER–410 | Illegal Study No Image Deleted | STUDY NO. in STUDY INF. does not match STUDY NO. in IMAGE INF. | warning |
ER–411 | Duplicate Image Inf Deleted | Duplicate IMAGE IDs found in IMGINF | warning |
ER–412 | No Image Data Image Inf Deleted | IMAGE DATA not found in storage but IMAGE INF. record exists | warning |
ER–413 | Illegal Study ID Image Deleted | STUDY ID in IMGPTR differs from STUDY ID in IMGINF. | warning |
ER–414 | Illegal Study ID Image Deleted | IMAGE ID in IMGPTR differs from IMAGE ID in IMGINF. | warning |
ER–415 | Same Area Image Inf. Deleted | IMAGE DATA and IMGINF use same memory area (should be separate) | warning |
ER–416 | Image Data Area Size Over | Required IMAGE DATA storage exceeds available area | error |
ER–417 | Duplicate Image Pointer Deleted | Duplicate IMGINF found using same memory area as existing IMGINF | warning |
ER–418 | Image Pointer Area Size Over | Required IMAGE POINTER area exceeds available allocation | error |
ER–419 | Same Area Image Inf Deleted | IMGINF uses same area as another IMGINF during consistency check | warning |
ER–420 | Image Inf Area Size Over | Required IMGINF area exceeds available allocation | error |
ER–421 | No Image Inf Study Inf Deleted | STDINF exists but has no associated IMGINF records | warning |
ER–422 | Study Inf Area Size Over | Required STDINF area exceeds available allocation | error |
ER–430 | Event Code Error | IMAGE FILE MANAGEMENT PROCESSOR receives illegal or undefined event code | error |
ER–431 | Event Sequence Error | IMAGE FILE MANAGEMENT receives event at illegal timing or sequence state | error |
ER–432 | Logical Error | Logic error detected in IMAGE FILE MANAGEMENT processor state | error |
ER–433 | Image Already Stored | Attempt to store image that is already in storage (MT or FD) | warning |
ER–434 | Image Already Exist | Attempt to retrieve image that already exists in destination | warning |
ER–435 | Image Not Found | Image not found in disk or device during store or retrieve operation | error |
ER–436 | Image in Scan Study, No Load | Attempt to retrieve image whose STUDY# matches currently scanning STUDY# | warning |
ER–437 | OD Study Incorrect, No Store | During OD store, only STUDY INF. OR only IMAGE INF. exists, not both | error |
ER–440 | OD Study Inf. Nothing | IMAGE INF. file exists in OD but corresponding STUDY record not found | error |
ER–441 | OD Image Inf. Nothing | STUDY record exists in OD but IMAGE INF. file for that study not found | error |
ER–442 | OD Study Inf. Incorrect | Number of images in STUDY INF. does not match number in IMAGE INF. file | error |
ER–443 | OD Study Inf. Nothing Deleted | IMAGE INF. file exists but corresponding STUDY not found in OD | warning |
ER–500 | Inhalator not Ready | Inhalator device does not respond with ready status within specified timeout after xenon transmission command | error |
ERROR XXXXXXXX | System error occurred during Support Display operation | Software detects internal error condition | error |
F0 | Time Out Error | General operation timeout | error |
F1 | Can't Display During Horizontal Blanking | Display attempted during horizontal blanking interval | warning |
F2 | Can't Refresh DRAM During Horizontal Blanking | DRAM refresh attempted during horizontal blanking | error |
F.E. | Circuit Breaker Off or tripped | AC input breaker has opened due to overcurrent or fault | critical |
FF | Invalid Parameter Error | Invalid parameter in Basic graphics | warning |
FILE NOTHING | Named file does not exist | User enters name of nonexistent file | warning |
INVALID CURSOR | Cursor is not properly positioned or out of range | ROI function selected before cursor positioned or cursor placed outside valid range | warning |
INVALID ENTRY | User provided unacceptable data entry | Invalid parameter entered at Support Display menu | warning |
INVALID ENTRY | User input was not recognized or valid | Wrong menu selection or invalid parameter entry | warning |
INVALID FILE | File format is incorrect | User enters file name with wrong format | warning |
MS–000 | Abort Button on | User presses Abort button on control panel | info |
MS–001 | Start Timeout | Scan does not start within specified time after start command issued | warning |
MS–002 | Insert KEY–FD | Maintenance program requires key floppy disk but it is not inserted | warning |
MS–003 | X–Ray Over Range Detect | DAS (Data Acquisition System) data exceeds maximum acceptable range | error |
MS–004 | FPU Busy | Floating Point Unit processor is busy with previous calculation when new command issued | warning |
MS–005 | Tube Warm up End | X-ray tube warm-up procedure completes successfully | info |
MS–006 | Tube Warm up Canceled | X-ray tube warm-up procedure is canceled by user or system | info |
MS–007 | Reconstruction's Queue Full | Priority reconstruction request queue reaches maximum capacity | warning |
MS–008 | Recon Completion | Image reconstruction completes successfully (shown in non-Auto Display mode) | info |
MS–009 | Calibration End | Calibration program completes successfully | info |
MS–010 | Calibration Canceled | Calibration routine is canceled by user or system | info |
MS–011 | Warm up Scan Set Timeout | Scan setup for warm-up does not complete within specified time | warning |
MS–060 | Display Busy | Requested program cannot run because display is in use by another process | warning |
MS–070 | Image Data Full (Delete & Reset) | Reconstructed image data cannot be stored because disk is full | error |
MS–071 | Image inf. Full in Study | Reconstruction cannot proceed because IMGINF. for the study is full | error |
MS–072 | Next Scan Preparation Time Out | In Dynamic Scan mode, scan does not complete within specified delay time | warning |
MS–099 | On Dynamic Scan | Another function is running during a Dynamic Scan operation | info |
O.C. | Over Current alarm | Motor winding short, lead grounded, transistor shorted, or control circuit fault | critical |
O.H. | Over Heat alarm | Servo amp temperature exceeds safe operating limit | critical |
O.L. | Over Load alarm | Excessive load on motor during rotation | critical |
P.E. | Dynamic Brake Function Fail | Dynamic brake resistor open or input voltage too high | critical |
RANGE ERROR | Entered parameters exceed specified range | User inputs MIN or MAX values outside allowed bounds | warning |
S.E. | Speed Error or feedback mismatch | Actual motor speed does not match commanded speed | critical |
SYSTEM ERROR XXXXXXXX | Unspecified system error with error code appended | Internal software or hardware fault during maintenance operation | critical |
V.E. | Voltage Error or Power Fail | Input AC voltage drops below safe minimum or control power rails out of range | critical |
WARM UP ERROR | Warm-up routine failed to collect sufficient raw data or data analysis failed | Raw data collected during 7th stationary scan (120 kV 30 mA, 10 mm slice, 8 sec apex) is insufficient or fails quality check during analysis phase | error |
Likely causes and actions for each code are in ServiceForge. Connect ServiceForge to your AI
Community
0 fixes logged by technicians through their AI, with outcomes, for this model.
ServiceForge knowledge base record. Field-unverified unless technicians confirmed it. A teaching summary of the record, not a service manual. Export 2026-10-14.