On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
CT scanner startup, console boot, application launch, or software loading failures caused by power, network, peripheral, or system issues.
Step-by-Step Troubleshooting
1. Ensure Patient Safety
Confirm no patient is on the table or actively being scanned before troubleshooting.
Action:
- Stop any attempted exam.
- Remove the patient from the scanner room if clinically appropriate.
- Notify CT staff that the scanner is not available for use.
- Use another scanner if imaging is urgent.
Expected outcome: Patient care continues safely without relying on an unstable CT system.
2. Verify the Reported Boot or Software Failure
Confirm what part of the system is failing.
Action:
- Ask CT staff what they observed.
- Determine whether the issue affects the operator console, gantry, acquisition system, reconstruction system, or all components.
- Note any displayed error messages, frozen screens, failed application launches, or startup loops.
- Check whether the failure occurs during power-up, login, exam launch, scanning, or image reconstruction.
Expected outcome: The failure point is clearly identified before additional troubleshooting begins.
3. Check for Active Patient or Exam Data Concerns
Before restarting or power cycling, confirm whether any patient exam data may be unsaved or mid-transfer.
Action:
- Ask CT staff if an exam was in progress.
- Check whether images were acquired but not sent to PACS.
- Confirm whether the system is frozen during reconstruction, transfer, or exam closure.
- Do not force shutdown if data recovery may still be possible unless patient or equipment safety requires it.
Expected outcome: Potential patient data loss is considered before rebooting.
4. Check Main System Power
Boot failures may be caused by incomplete or unstable power to the CT system.
Action:
- Verify the CT system, console, monitors, gantry, and computer cabinets are powered.
- Check for tripped breakers, emergency power-off activation, UPS alarms, or power distribution faults.
- Confirm the room has normal facility power.
- Look for abnormal power indicators on console equipment or system cabinets.
Expected outcome: External power problems are identified or ruled out.
If restoring proper power resolves the issue, confirm normal boot and stop troubleshooting.
5. Check the Emergency Stop and System Interlock Status
A pressed emergency stop or active interlock may prevent full system startup.
Action:
- Inspect all accessible emergency stop buttons.
- Confirm none are pressed or latched.
- Check scanner room door/interlock status if applicable.
- Ask CT staff whether an emergency stop was used recently.
Expected outcome: The scanner is not being held in an inhibited state by an external safety control.
If resetting an active emergency stop allows the system to boot normally, document the finding and stop.
6. Inspect Console Workstation Power and Peripherals
A console issue may appear as a CT system software failure.
Action:
- Verify the workstation is powered on.
- Check monitor power, video cables, keyboard, mouse, and network connections.
- Confirm all required console monitors are displaying properly.
- Look for frozen screens, blank displays, or failed operating system startup.
Expected outcome: A simple workstation, display, or peripheral issue is ruled out before assuming CT software failure.
7. Check Network and Data Connections
Some CT systems may fail to fully launch applications or complete startup if required network paths are unavailable.
Action:
- Inspect visible network cables at the console and equipment cabinet.
- Confirm cables are fully seated and not damaged.
- Check for disconnected wall data ports or patch cables.
- Ask staff whether PACS, worklist, or hospital network issues are occurring elsewhere.
Expected outcome: Network-related startup or application loading issues are considered.
If reconnecting a loose network cable resolves the startup issue, verify normal operation and stop.
8. Perform a Controlled Software Restart
If the console is responsive enough, use the normal shutdown or restart process.
Action:
- Close the CT application using the standard system workflow if possible.
- Restart the application or workstation through normal software controls.
- Avoid unplugging equipment or forcing shutdown unless the system is completely unresponsive.
- Observe whether the CT software launches normally after restart.
Expected outcome: Temporary software lockups clear without unnecessary hard power cycling.
If the system boots and software loads normally, perform basic operational checks and stop.
9. Perform a Full Controlled System Reboot
If a software restart does not resolve the issue, perform a controlled system reboot according to site policy.
Action:
- Notify CT staff before rebooting.
- Follow the normal Philips system shutdown and startup sequence used at the facility.
- Allow the system enough time to fully power down and restart.
- Observe startup messages, application launch, gantry communication, and reconstruction system status.
Expected outcome: Temporary communication or software initialization faults may clear after a complete controlled reboot.
If the system returns to normal operation, document the reboot and final status.
10. Check for Repeated Boot Loops or Recurring Software Errors
Recurring failure after restart suggests a deeper system issue.
Action:
- Observe whether the same failure repeats.
- Note exact error messages, codes, timestamps, and startup stage.
- Record whether the console OS loads but the CT application fails, or whether the workstation itself fails to boot.
- Check for unusual sounds, cabinet alarms, overheating, or warning indicators.
Expected outcome: Escalation information is captured accurately for repair support.
11. Check Environmental Conditions Around System Electronics
Overheating or poor airflow can cause software instability or failed startup.
Action:
- Inspect console and equipment cabinet ventilation.
- Confirm air vents are not blocked.
- Check for excessive heat around the console, reconstruction hardware, or equipment cabinets.
- Listen for abnormal fan noise or missing fan operation.
- Report room HVAC problems if the CT equipment room is unusually warm.
Expected outcome: External environmental causes are ruled out before assuming internal computer or software failure.
12. Confirm System Status After Recovery
If the system boots successfully, verify basic readiness before returning it to service.
Action:
- Confirm the CT application opens normally.
- Verify gantry and table communication.
- Confirm no active system errors remain.
- Confirm worklist, image reconstruction, and image send functions are available if appropriate.
- Ask CT staff to perform normal startup checks or required QA before clinical use.
Expected outcome: The scanner is not returned to service based only on a successful boot screen.
If the Problem Persists
If the Philips Brilliance Series CT scanner still will not boot, repeatedly freezes, fails to launch software, loses communication between console and scanner components, or displays recurring system errors, common external causes have been ruled out.
The device should be:
- Removed from service
- Labeled Out of Service
- Escalated for Philips service, imaging specialist support, or bench-level evaluation of the affected console, reconstruction, acquisition, power, or communication components
Do not continue repeated restarts without a clear reason. Repeated forced shutdowns may increase the risk of data corruption or delayed recovery. Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Do not troubleshoot CT boot or software failures with a patient on the table unless immediate safety requires action. Move the patient off the scanner first, use another imaging pathway if needed, and only continue troubleshooting when the room and equipment are safe.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"CT staff reported the Philips Brilliance CT scanner would not complete startup and the CT application failed to launch."
Cause
What was observed during troubleshooting.
Example:
"Verified console power was present, network connections were seated, emergency stop was not active, and the system continued to freeze during software startup after controlled reboot."
Resolution
What action was taken.
Example:
"Removed scanner from service, labeled Out of Service, documented recurring startup failure, and escalated to imaging service/Philips support for further evaluation."
Helpful Details to Include (If Known)
- Alarm behavior or exact error message
- Whether the console, gantry, or full system failed to boot
- Exact error message or startup screen where failure occurred
- Whether patient data or image transfer was in progress
- Whether facility power and UPS status were normal
- Whether emergency stop or door interlock was active
- Whether network cables were checked or reseated
- Whether the system froze, rebooted, or stayed blank
- Accessories swapped or console peripherals checked
- Power behavior and indicator lights on console, gantry, cabinets, or UPS
- Environmental factors such as unusual fan noise, heat, odor, or cabinet alarms
- Whether controlled reboot changed the behavior
- Final device status and escalation path
Final Thought
System boot and software failures on a CT scanner should be handled carefully and logically. Start with patient safety, then check power, emergency stops, console hardware, network connections, and environmental conditions before escalating. Good documentation helps service teams identify whether the problem is software, communication, power, workstation, or internal system hardware related.
That is successful troubleshooting.