Try these quick steps to recover your computer from a POST or startup issue.
Not required
If so, there are several basic questions to ask so you can troubleshoot the issue further.
If you have ruled out the other issues, then we are left with troubleshooting a No POST issue. The first thing to do is to confirm the status of the machine and what it is reporting to you. You can get a list of the No POST LED and Beep codes here:
Diagnostic and Battery Indicators for Notebooks (If you require information about Desktops, see Understanding Beep Codes on a Dell Desktop personal computer.)
Does it remain lit, does it flash or does it power off after coming on for a time?
All Dell Latitude systems are supplied with diagnostic LEDs that can advise at which point during POST the system has encountered a problem.
There are several beep codes possible with a No POST issue, these can advise at which point during POST the system found a fault as with the Diagnostics LEDs.
If the system has gone far enough through POST, you may get an on-screen error about keyboards, hard drive, Video, and such.
Ensure that there are no peripherals plugged to the notebook and that it is out of the Docking Station. If there was anything plugged up, disconnect them and check the POST again. Is the issue the same on either the battery or the AC Adapter fitted individually with the system off the Dock?
If the LEDs come on and then the system powers off before you can see or hear a code, then hold down both the <Fn> key and the Power Button simultaneously to start the machine up. If you hold them down together, the machine should cycle through so you can get any codes or beeps. If you let go of the key and the power button, it should try to boot to the onboard diagnostics. The Pre-boot System Assessment (PSA) is accessed by pressing the F12 key at the Dell logo screen, and selecting Diagnostics from the menu.
If you received a particular error code showing a particular type of issue, it can speed up the troubleshooting considerably by narrowing down your focus. If for example you got a memory error code, this would allow you to skip straight to troubleshooting the memory in the unit. If it was a Video error, again you go to troubleshooting the video. The easiest way to troubleshoot your fault further is by two procedures Removal and Substitution.
This means to remove the affected part and seeing if it changes what is reported by the notebook on startup. Keeping with the example above. If you remove the memory, does the error change to report no memory detected? If you reseat it does the fault come back?
This means either moving the part to another slot or replacing the part with a part from a similar model to see if the issue is repeated or resolved.
By removing possibly faulty parts and replacing with either known good working parts or by checking them in other ports, we can narrow down whether the issue is with the part or where it connects to your system. You can report this troubleshooting to your local Technical Support, and it should speed up a resolution for you.
If you are not getting a No POST code and the diagnostics are not running, then we have to fall back to general troubleshooting to isolate the fault. Try removing as many parts from the system as possible and power the machine on with those parts removed (such as Hard Drive, CD/DVD Drive, Memory, WiFi card, 3G card, Bluetooth card, and any additional parts added to the unit such as removable media and flash memory.)
This troubleshooting should hopefully achieve at least 1 of 2 things, it should either get you back up and running or it should narrow the fault down far enough, that it can help your Technical Support resolve the problem as quickly as possible and cut down on the chances of any secondary faults.
Here are some recommended articles related to this topic that might be of interest to you.