IBM System x3650 M4 BD Type 5466 Installation And Service Manual page 155

v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
v See Chapter 5, "Parts listing," on page 153 to check if a component is a consumable, structural, or FRU part.
v If an action step is preceded by "(Trained technician only)," that step must be performed only by a trained
technician.
Symptom
The screen is blank.
The monitor works when you
turn on the server, but the
screen goes blank when you
start some application
programs.
Action
1. If the server is attached to a KVM switch, bypass the KVM switch to eliminate
it as a possible cause of the problem: connect the monitor cable directly to the
correct connector on the rear of the server.
2. Make sure that:
v The server is turned on. If there is no power to the server, see "Power
problems" on page 143.
v The monitor cables are connected correctly.
v The monitor is turned on and the brightness and contrast controls are
adjusted correctly.
3. Make sure that the correct server is controlling the monitor, if applicable.
4. Make sure that damaged server firmware is not affecting the video; see
"Updating the firmware" on page 87.
5. Observe the checkpoint LEDs on the system board; if the codes are changing,
go to step 6.
6. Replace the following components one at a time, in the order shown, restarting
the server each time:
a. Monitor
b. Video adapter (if one is installed)
c. (Trained technician only) System board.
7. See "Solving undetermined problems" on page 148.
1. Make sure that:
v The application program is not setting a display mode that is higher than
the capability of the monitor.
v You installed the necessary device drivers for the application.
2. Run video diagnostics (see "Running the DSA Preboot diagnostic programs"
on page 129).
v If the server passes the video diagnostics, the video is good; see "Solving
undetermined problems" on page 148.
v (Trained technician only) If the server fails the video diagnostics, replace the
system board.
Chapter 4. Troubleshooting
139