On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses slow performance, system freezing, or unexpected crashes caused by software issues, memory overload, connections, or environmental factors before assuming hardware failure.
Step-by-Step Troubleshooting
Ensure Patient Safety
- Confirm the system is not being used for active imaging.
- Move any patient requiring imaging to another functional system.
Check Power Stability
- Verify the system is plugged into a dedicated, grounded outlet.
- Inspect power cords for damage.
- Unstable power can cause freezing or crashes.
Close Unnecessary Applications / Reboot
- If safe, perform a controlled system reboot.
- Ensure no background tasks are overloading memory.
- Observe if performance improves after reboot.
Inspect Connections and Peripherals
- Disconnect any non-essential USB devices or network drives.
- Loose or faulty peripherals can cause software instability.
Check System Storage and Memory Usage
- Verify sufficient free disk space.
- If storage is nearly full, clear old studies or temporary files.
- Insufficient memory can lead to slowness or crashes.
Verify Network Connections
- Slow or unstable network connections can cause freezing during DICOM transfers or database access.
- Test network cable and switch port.
Check for Software Updates or Errors
- Review system logs for repeated error messages.
- Confirm the system firmware and software version are current per hospital IT or vendor guidance.
- Apply updates if available and approved by IT.
Observe for Environmental Factors
- Ensure the system is not overheating.
- Confirm adequate ventilation and that air vents are unobstructed.
Test with Minimal Configuration
- Remove non-critical probes or accessories.
- Boot the system with only essential devices connected to isolate potential conflicts.
If the Problem Persists
Common external and software causes have been ruled out.
Remove the system from service.
Label Out of Service.
Send for Philips service or internal bench evaluation.
Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Never troubleshoot software or reboot with a patient actively on the probe.
Always move patients to a functioning system first.
Document all steps and observations to assist vendor support.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"System intermittently freezes and crashes during routine imaging."
Cause
What was observed during troubleshooting.
Example:
"System memory near full and multiple background processes causing slow performance."
Resolution
What action was taken.
Example:
"Rebooted system, removed unnecessary applications, cleared temporary files, and monitored performance."
Helpful Details to Include (If Known)
- Power outlet tested and stable
- Cables and peripherals disconnected/swapped
- Software version checked
- System logs reviewed for errors
- Temperature and ventilation checked
- Observed behavior after reboot
Final Thought
Maintaining patient safety and documenting every step ensures logical troubleshooting and proper escalation. Slowness or crashes often originate from software or external factors, not immediately internal hardware. Following a structured approach minimizes downtime and helps support teams resolve issues efficiently.
That is successful troubleshooting.