Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

30864

February 19th, 2018 19:00

XPS 8920, BIOS 1.0.14, Front I/O cable failure message

 

I upgraded the BIOS of my XPS 8920 from version 1.0.11 to version 1.0.14 last night (intermediate versions weren't offered in my country or were removed from Dell's website before I noticed them). After the upgrade, I started receiving the "Alert! Front I/O cable failure" message (code 2000-0716) on boot. I checked the cables, reseated all of them and tested the front panel devices, which are all working fine. The power LED is not blinking neither changed color. I run the diagnostics and no errors were found, which makes me suspect a bug in this BIOS version. Is anyone else having this same problem after this update?

3 Posts

February 21st, 2018 17:00

After updating my XPS 8920 to bios 1.0.14, I am now getting a similar error code at boot from Dell SupportAssist, "Power Button Cable failure".  Error Code: 2000-0716.  This was not an issue prior to the update.

-Abitman

4 Posts

February 21st, 2018 20:00

I have to say that I also have the same issue and error message after updating to  1.0.14 Bios today

XPS 8920, BIOS 1.0.14, Front I/O cable failure message  .  I reach out to Dell Support and it has been escalated to Level 3 whatever that is.  I get reboot then the message comes about the error, I press continue and the system keeps on working fine no issues.  The problem started after the BIOS.  What is amazing is that they do not allow you to go back in BIOS it is locked. Dell really drop the ball.  The technicians do what they are suppose to do, I know they spent 2 hours and no fix. So as long as I can work with my computer I am good.  I upgraded the SSD Drive a while ago, but I can see that people are having the issue whether they upgraded their SSD drive or not. Buddies yes seeing these many people here definitely tells me is a BIOS problem, DELL Fix it.

62 Posts

February 21st, 2018 20:00

Yes.  I think it is a bug in the update.  My ports all work and I did not receive this message in the past.

62 Posts

February 21st, 2018 21:00

There are some responses from Dell Support earlier in this thread confirming it as a bug.  See replies from "Justin C."

2 Posts

February 21st, 2018 23:00

ME too.  Come on Dell, fix your bug

8 Posts

February 22nd, 2018 03:00

Count me as another user with this same problem.  I called Tech Support yesterday after having upgraded to Bios 1.0.14.  I specifically asked if Tech Support had heard of other 8920's with this problem...they had not.  Then I sent them a link to these responses.  After running numerous SupportAssist tests, they are now telling me that I have to replace my motherboard because the update "corrupted" my motherboard.  This sounds a little extreme.  Can this be possible?

8 Posts

February 22nd, 2018 05:00

This is maddening!  I'm on with Dell Tech Support Chat again this morning.  All that I want to know is is it better to replace my motherboard for this issue or wait for a BIOS update?  I really hate to take such an extreme action like replacing a motherboard on a computer that is functioning perfectly other than the error screen at startup.  I not really all that familiar with BUIOS updates, can a new revised update correct this problem or is the motherboard replacement the only option?

February 22nd, 2018 05:00

I updated the BIOS yesterday. Since then I get the "power button cable failure" warning whenever I start the computer. The PC seems to operate normally after that.

February 22nd, 2018 06:00

Dell supports told me the same thing on 2 different incidents, they think it is my motherboard and tell me I need to send it in.  Both time is I found out is untrue, and the solutions for both time is simple.  One time I can not press f2/12 to go into the BIOS,  they think it is the motherboard they tell me I need to return it for repair.  Someone from this thread tell me how to resolve it.  It is a simple solution.  

If I were you I wait for the new BIOS update to fix the current issue with the version 1.0.14 and go from there.  

Dell XPS desktop support line is in Phillipines,   lost all my confident in them and their technical knowledge.  They follows troubleshooting procedures written down by others.  Their knowledge is not by experience but by documentation from others.

I think they have a stupid flow chart for troubleshooting when all else they went through that check list on what has documented and still don't know what is the problem then it must be the motherboard.

8 Posts

February 22nd, 2018 06:00

I tend to agree.  There are several hundred users on here that are experiencing a problem with 1.0.14.  Are they really suggesting that Dell replace all of these motherboards?  Seems like a sledge hammer approach when a tack driver would do.

21 Posts

February 22nd, 2018 07:00

Well if it really came to Dell replacing all of these motherboards under warranty they don't seem too bothered about it.

Why? Because despite all of the messages and reports to the firmware team, the 1.0.14 BIOS is still available as an urgent update for lots more unsuspecting users to download!!!

4 Operator

 • 

783 Posts

February 22nd, 2018 08:00

@Community,

While you're welcome to call Dell technical support and report this, there's not much need to do so.

Couple points I need to make:

-Dell engineering is now aware of the problem and is now working the case internally. No ETAs at this time.

-There's no need to replace the motherboard for this symptom as the firmware update in question does not cause firmware corruption and does not cause any detriment to systems

-I'm crafting internal messaging which is directed at Dell Technical support which includes all of the above points

5 Posts

February 22nd, 2018 09:00

I am having the same problem after updating the BIOS. Is there anyone who has updated the BIOS and had no problems?

8 Posts

February 22nd, 2018 11:00

Really appreciate your help and advice on this issue Justin.

February 22nd, 2018 14:00

Is "SOLVED" the correct status of this thread?  Perhaps a more appropriate status would be "PENDING" or "IN-PROGRESS"?

No Events found!

Top