STRIKE F1 STRIKE F2 ERROR

Ok everyone this is the most common error msg we deal with the dell account. With this error you must know how to troubleshoot properly to get the right part out. This is one error that can make break dispatch rates and repeat dispatch rates.

First, lets start from the beginning and you just got a call. Customer has the strike f1 strike f2 to continue error. Whats the first thing we do? The first thing that should be done is a cold boot to duplicate the error. Once you have done that and you get the error again then shut the system down and turn it back on and go into the bios. When your in the bios check and see what ide devices are not being shown. Then you will clear nvram and reset defaults. Sometimes doing this will solve issue. If this doesn’t solve issue then we must get the case open and disconnect all ide devices. One we do that we leave just the hdd pluged in because a lot of times strike f1 strike f2 comes from the cd rom being bad. Now after you done this then we must reboot go back in the bios and clear nvram again. Once you have done that and nothing has changed we must now determine it’s the controller or not. So now we are gonna shut down open the case and hook up the cd rom drive to the primary controller and insert a bootable cd rom in it. If the system boots from the cd rom then we know 2 things. 1. its not the controller. 2. Its not cd rom drive. Now if it doesn’t boot we must test the controller and drive again. This time we will hook the drive up to the secondary controller. If it doesn’t boot now we might have a problem with the cd rom drive. But lets be sure take the hdd and put it on the secondary controller and see if it boots to the OS. If it does the cd rom is the problem. If it doesn’t the controller is the problem. Now this applys also to the hdd also. Swap controllers with each drive by thereself and see what ya get. Troubleshooting strike f1 strike f2 is nothing but process of elimination with the drives and controllers. Hint – if you got a known good hdd then use it. A known good is a good way of determine which device is failing.