AtWhatMileage
Software · 12 owner reports

Software fault or failed update on the 2013 Chevrolet Volt

Only 7 reports for this mode came with an odometer reading, which is too few for percentiles to mean anything. The page is here because someone linked to it; treat the figures as anecdotes, and see the full report for this year instead.

Reports of this failure 12
With an odometer reading 7
Reports per 1,000 built 1.4 per 1,000
Filed below 36,000 miles 0%
Mention a crash, fire or injury 0
Typical repair $0–$600
What it means when it happens Moderate
Rank among this year's problems 7th

When software fault or failed update gets reported

There are 12 reports of software fault or failed update on the 2013 Chevrolet Volt, 7 with a mileage attached. That is too few to place the failure on the odometer with any confidence.

A part like this is normally expected to survive 30,000 miles. It is the 7th most-reported problem on this model year.

The whole distribution

Percentiles of the 7 odometer readings owners gave.
10th25thMedian 75th90th
— — 66,000 miles — —

Read the 10th percentile as “one report in ten arrived this early”. Exact figures are shown in this table because it is the table of record; everywhere else on the site they are rounded to the precision the sample can carry.

What a percentile can and cannot tell you here

These five numbers describe the readings owners gave, in order. The median is the middle one: half the reports arrived below it. The 10th and 90th are the edges of the bulk of the distribution, and the distance between them is the part worth reading. A tight spread — say 70,000 to 95,000 miles — points at something that wears out on a schedule, and the schedule is knowable. A wide one, 20,000 to 190,000, points at a fault that hits some cars and never troubles others, which means the mileage on the listing in front of you tells you very little about your odds.

What these figures are not is a survival curve. Every reading here comes from a car whose owner filed a complaint, so the sample contains only failures: it cannot say what share of the fleet made it past 150,000 miles untouched, because those owners had nothing to report. Nor is the mileage the moment of failure — it is the odometer reading as recalled at the time of filing, which may be weeks later and is sometimes rounded to the nearest ten thousand by the person typing it.

Percentiles are shown at all only once 8 readings exist for the vehicle and mode. Below that the middle of a handful of numbers is noise wearing a decimal point, so the figures are withheld rather than dressed up.

What happens, and what it costs

Putting it right typically runs $0–$600 at an independent US shop. That range is an editorial estimate held in this site's failure-mode catalogue, not a figure from NHTSA, and it is a repair cost rather than a diagnosis cost.

The same failure on other years

The same failure is reported on 3 model years of this car. It shows up earliest on the 2013, at a median of 65,000 miles, and latest on the 2012 at 100,000 miles.

By volume the 2013 is the worst of them, which makes this a problem of this specific year rather than of the model as a whole.

If one year stands out to the left, that is the year to avoid; if the whole line sits at a similar mileage, this is wear rather than a defect in one production run.

Median
  1. 2011 Chevrolet Volt software fault or failed update 101k
  2. 2012 Chevrolet Volt software fault or failed update 101k
  3. 2013 (this one) 66k
  4. 2014 Chevrolet Volt software fault or failed update 27k
  5. 2015 Chevrolet Volt software fault or failed update 96k
  6. 2017 Chevrolet Volt software fault or failed update
    no odometer readings given
    —
  7. 2019 Chevrolet Volt software fault or failed update
    no odometer readings given
    —

Tick median reported mileage Solid middle half of reports Faint 10th to 90th percentile Colour how bad the failure is when it happens

What owners wrote

Verbatim from NHTSA complaint narratives, trimmed for length. The mileage is the one the owner gave.

I've brought my 2013 chevy volt to the dealership 4 times because it dies suddenly while driving. It has put my family in danger multiple times. One of the "fixes" was a software update that ended up as a recall because it causes the engine to die suddenly (it's recall #n172130460, which came out two days before my latest incident, but I didn't receive the recall notice in the mail until 7/28/18...6 weeks after my last incident). The most recent time the car died (6/16/18), I was on a mountain highway and I was lucky enough to not get hit as I pulled the car to the side. There was no signage there except for the "caution bear xing" sign. After towing my car to the nearest dealership (in carson city, nv, an 8 hour ordeal), I had expenses for lodging and transportation (including lyft to south lake tahoe to rent a car because no rental car offices open on sunday in carson city, then flying to reno and taking a lyft to carson city to pick up the car because chevy refused to ship the car to me even though I said that I was afraid and didn't trust the car in the mountains). Chevy customer service and concierge services refused to…

66,000 miles NHTSA complaint 1487114 filed 2018-07-30

I've brought my 2013 chevy volt to the dealership 4 times because it dies suddenly while driving. It has put my family in danger multiple times. One of the "fixes" was a software update that ended up as a recall because it causes the engine to die suddenly (it's recall #n172130460, which came out two days before my latest incident, but I didn't receive the recall notice in the mail until 7/28/18...6 weeks after my last incident). The most recent time the car died (6/16/18), I was on a mountain highway and I was lucky enough to not get hit as I pulled the car to the side. There was no signage there except for the "caution bear xing" sign. After towing my car to the nearest dealership (in carson city, nv, an 8 hour ordeal), I had expenses for lodging and transportation (including lyft to south lake tahoe to rent a car because no rental car offices open on sunday in carson city, then flying to reno and taking a lyft to carson city to pick up the car because chevy refused to ship the car to me even though I said that I was afraid and didn't trust the car in the mountains). Chevy customer service and concierge services refused to…

66,000 miles NHTSA complaint 1487115 filed 2018-07-30

I've brought my 2013 chevy volt to the dealership 4 times because it dies suddenly while driving. It has put my family in danger multiple times. One of the "fixes" was a software update that ended up as a recall because it causes the engine to die suddenly (it's recall #n172130460, which came out two days before my latest incident, but I didn't receive the recall notice in the mail until 7/28/18...6 weeks after my last incident). The most recent time the car died (6/16/18), I was on a mountain highway and I was lucky enough to not get hit as I pulled the car to the side. There was no signage there except for the "caution bear xing" sign. After towing my car to the nearest dealership (in carson city, nv, an 8 hour ordeal), I had expenses for lodging and transportation (including lyft to south lake tahoe to rent a car because no rental car offices open on sunday in carson city, then flying to reno and taking a lyft to carson city to pick up the car because chevy refused to ship the car to me even though I said that I was afraid and didn't trust the car in the mountains). Chevy customer service and concierge services refused to…

66,000 miles NHTSA complaint 1487116 filed 2018-07-30

Also reported on the 2013 Chevrolet Volt

Other electrical problem

38 reports median 67k

Other fuel system problem

34 reports median 67k

Other engine problem

25 reports median 57k

Other body or interior problem

25 reports median 69k

Other powertrain problem

17 reports median 54k

How far this goes

This page is kept out of search results because 12 reports is not enough to publish percentiles from. It stays reachable because somebody looking at this exact car would rather see the reports than be told there are none.

Complaints are voluntary, so 12 is a floor and not a count of affected cars. Mileages are typed in by owners and cluster on round numbers. And the mode itself is assigned by software reading the complaint text, which is reliable in bulk and fallible one report at a time.

Questions this page answers

At what mileage does software fault or failed update happen on the 2013 Chevrolet Volt?

Across 7 owner reports that included an odometer reading, half were filed by 65,000 miles. A quarter were filed before — and a quarter after —. These are the mileages owners reported when they complained, not a prediction for any individual car.

How common is software fault or failed update on the 2013 Chevrolet Volt?

12 reports have been filed with NHTSA, about 1.4 per 1,000 vehicles. Complaints are voluntary, so this is a floor rather than a count of affected cars.

What this is and is not. These are the mileages at which owners chose to complain to a federal agency, which is not the same as the mileage at which the part fails on every car. It skews toward failures that happened outside warranty, cost real money, or frightened someone. It is still the only public dataset that carries failure mileage at all, and the shape of a few hundred readings is informative even when a single one is not. Methodology · JSON · this failure on other cars

Source Owner complaints and recall records published by the US National Highway Traffic Safety Administration, model years 1996–2027 Figures rebuilt Published by AtWhatMileage How every figure is computed