Software Problems of Buick Rainier

A person ran two stop signs and entered vehicle path. The two vehicles hit head on and this vehicle made impact at 40 mph after it decelerated from 43 mph. The two vehicle hit head on with near perfect even impact, based upon third party visual description of the front end of the vehicles damage. The vehicle decelerated at a max sdm recorded velocity change rate of -14. 07 (mph) and a algorithm enabled to maximum sdm recorded velocity change of 127. 5 msec. Driver of the vehicle hit the steering wheel with head knocking the person out. Airbags did not deploy. Onstar was not notified that there was an accident. Computer shows the seatbelt was worn by driver. When the onstar was manually activated by the driver when he came too, the gps showed the vehicle further north up the road causing incorrect police division being called. Vehicle was going up hill when the accident occurred. Other vehicle was going downhill. The other vehicle was a Subaru. Vehicle computer data was retrieved by a bosch crash data retrieval tool using version 8. 0 software. I have a copy of this data. Gm reports that the computer was correct not to deploy airbags and not call for help using onstar. The vehicle had a software modification due to a fault with the fan speed calibration setting off a warning light. We had complained that things were never correct after this modification of the software and took the vehicle to two different dealerships complaining that computers were doing strange things after this firmware modification. Vehicle VIN: 5gaet13p442277676.

See all problems of the 2004 Buick Rainier 🔎.

A person ran two stop signs and entered vehicle path. The two vehicles hit head on and this vehicle made impact at 40 mph after it decelerated from 43 mph. The two vehicle hit head on with near perfect even impact, based upon third party visual description of the front end of the vehicles damage. The vehicle decelerated at a max sdm recorded velocity change rate of -14. 07 (mph) and a algorithm enabled to maximum sdm recorded velocity change of 127. 5 msec. Driver of the vehicle hit the steering wheel with head knocking the person out. Airbags did not deploy. Onstar was not notified that there was an accident. Computer shows the seatbelt was worn by driver. When the onstar was manually activated by the driver when he came too, the gps showed the vehicle further north up the road causing incorrect police division being called. Vehicle was going up hill when the accident occurred. Other vehicle was going downhill. The other vehicle was a Subaru. Vehicle computer data was retrieved by a bosch crash data retrieval tool using version 8. 0 software. I have a copy of this data. Gm reports that the computer was correct not to deploy airbags and not call for help using onstar. The vehicle had a software modification due to a fault with the fan speed calibration setting off a warning light. We had complained that things were never correct after this modification of the software and took the vehicle to two different dealerships complaining that computers were doing strange things after this firmware modification. Vehicle VIN: [xxx] information redacted pursuant to the freedom of information act (foia), 5 u. S. C. 552(b)(6).

The lower instrument panel display, that shows the odometer, fuel mileage etc, does not always come on. I have had the display show up prior to starting, while in "run" but not started and then not come on after starting. Most of the time it will come on the next time I start the vehicle after letting it sit for a minute or two. . Even more recently the fuel gauge did not go up to full after adding fuel, the needle bounced on full and then when I placed the vehicle into drive it went back to empty, then thirty seconds later it went back to full. Fortunately at that point the display was working and the range immediately went to zero, leaving me with no information on the fuel. The fuel gauge has also dropped to empty unexpectedly while driving. The problems are irritating and intermittent at this point, and chasing it down is next to impossible. I would also like to note that when the fuel gauge did its dance from e to f to e to f that the check engine light also came on. Unfortunately I am not able to get my obdii scanner to work on the car yet, to determine the problem, that may have to do with I have older software. The engine light is now off so I may never figure out what went wrong.

See all problems of the 2005 Buick Rainier 🔎.