DTC Code P06B8 Internal Control Module RAM error

[hybridbear]

Since Saturday our FFH has been turning on the check engine light every few times we start the car and the ScanGauge reads the code as P06B8. According to dtcdecode.com this code means: "Internal Control Module Non-Volatile Random Access Memory (NVRAM) Error". Here is a link to their definition of the code. Has anyone else had this error? Does anyone have any ideas what it means? I have a long list of items for the dealer next time we bring the car in and I have added this to the list.

 

Each time the code has appeared (three times so far) I have cleared it with the ScanGauge and then it has taken 10+ trips with no DTC before it appears again.

[murphy]

Does the code appear in the DTC screen in Engineering Test mode?

[GrySql]

Since Saturday our FFH has been turning on the check engine light every few times we start the car and the ScanGauge reads the code as P06B8. According to dtcdecode.com this code means: "Internal Control Module Non-Volatile Random Access Memory (NVRAM) Error". Here is a link to their definition of the code. Has anyone else had this error? Does anyone have any ideas what it means? I have a long list of items for the dealer next time we bring the car in and I have added this to the list.

 

Each time the code has appeared (three times so far) I have cleared it with the ScanGauge and then it has taken 10+ trips with no DTC before it appears again.

HB, if it appears again why not run a VHR, then from the Sync website print the VHR out so you can show the Dealer.

Printouts are reality to Dealers.

[GrySql]

Looks like a PCM problem. This is from a Mustang, but seems possible since we just had a PCM re-calibration.

 

Edited September 3, 2013 by GrySql

[murphy]

Are you certain the Scangauge is not interfering with communications on the buss?

 

I have a Davis Car Chip that monitors the car all of the time and stores the data. I download the data once a month. It plugs directly into the OBD II port. I can not run a Vehicle Health Report if it is plugged into the connector.

[hybridbear]

Does the code appear in the DTC screen in Engineering Test mode?

It does not.

[hybridbear]

Are you certain the Scangauge is not interfering with communications on the buss?

 

I have a Davis Car Chip that monitors the car all of the time and stores the data. I download the data once a month. It plugs directly into the OBD II port. I can not run a Vehicle Health Report if it is plugged into the connector.

I guess it could be. I don't know why or how it would be though.

[hybridbear]

HB, if it appears again why not run a VHR, then from the Sync website print the VHR out so you can show the Dealer.

Printouts are reality to Dealers.

Thanks for the reminder, I had completely forgotten about VHRs!

[acdii]

Thanks for the reminder, I had completely forgotten about VHRs!

I get occasional cross traffic failures and have a VHR stating so. which reminds me I need to print it out, car goes in Thursday for bumper repaint and trim fixing. Add it to the list along with the woowowowo noise.

[GrySql]

I guess it could be. I don't know why or how it would be though.

One way to know if the ScanGauge is the the culprit is whether the Error Code started AFTER you attached it.

Next time you get a error code, disconnect the ScanGauge and re-start, if the Code is still there, send a VHR before plugging the SG back in.

I don't recall acdii discussing those Codes when he was monitoring his 'BD' with his ScanGauge.

[hybridbear]

One way to know if the ScanGauge is the the culprit is whether the Error Code started AFTER you attached it.

Next time you get a error code, disconnect the ScanGauge and re-start, if the Code is still there, send a VHR before plugging the SG back in.

I don't recall acdii discussing those Codes when he was monitoring his 'BD' with his ScanGauge.

It started a few days after I attached it. Every time the error code has happened it has been when the car was turned off for a few seconds and then turned back on. The ScanGauge remains on for a few seconds after shut down. Now that you mention it and I think about it more, each time the check engine light has appeared we had turned the car off and then turned it back on while the ScanGauge was still awake. I will test this theory out and see...

Edited September 3, 2013 by hybridbear

[expresspotato]

This is a serious issue... I would get it checked out ASAP. If your ECU / PCM goes or malfunctions while you're driving you're probably just going to get into an accident.

[airbusguy]

hybridbear

I've had my scanguage attached for 6000 miles and have had no adverse effects or codes. It might be one of the updates. In the TSB for the PCM update and MFT update they were quite specific as to the order they were to occur. Have since tossed the bulletin but if you find it - all 22 pages- I believe it stated PCM and then MFT in that order, and then they came out with updates to which IDS number to use. Before I saw that bulletin, I had done the MFT first and have had no issues. Perhaps the dealer did it just like the bulletin and overwrote everything.

 

Rob W

Edited September 4, 2013 by airbusguy

[hybridbear]

hybridbear

I've had my scanguage attached for 6000 miles and have had no adverse effects or codes. It might be one of the updates. In the TSB for the PCM update and MFT update they were quite specific as to the order they were to occur. Have since tossed the bulletin but if you find it - all 22 pages- I believe it stated PCM and then MFT in that order, and then they came out with updates to which IDS number to use. Before I saw that bulletin, I had done the MFT first and have had no issues. Perhaps the dealer did it just like the bulletin and overwrote everything.

 

Rob W

We don't have MFT, just MyFord. We didn't spend the money for the center touch screen because of all the complaints about MFT. This is the only option that I now regret skipping.

[gemdc]

I can confirm that another thing (rather than anything) attached to the OBD port will prevent running a Vehicle Health Report. I downloaded the 3.6 version of MFT and installed it using a USB drive. When I came back to syncmyride.com to report the install, it always failed to upload the file from the USB on 3 of my computers. On chat, the Ford guy said to just run a VHR and it would serve to report the install. When I tried to run a VHR the MFT says "You must have over 200 miles on the odometer". I have 6800. Then I googled and found stuff about a Scanguage interferring. I have an Ultra Gauge. Unplugged it from the OBD port and VHR ran fine. Strange but true. However, I have not had a code show up on my gauge for anything as yet. I like the digital version of Instant MPG on the Ultra Gauge. Also the calibrated mpg is more accurate than the dash trip gauges. Hope we don't find a reason not to use these gauges.

[acdii]

I never had error codes when I had mine plugged in, but that was on that other car, havent had a need to plug it into this car, so cant say whether it is causing it or not, but from your description, I would suspect it. Try not to stop start the car like you say and see if it stops happening. More than likely you are getting a false reading due to the draw of the SG on the ODBII. The electronics are so sensitive to voltage levels now, that anything is possible.

[murphy]

I was unable to run a VHR on my 2010 Fusion Hybrid with the Davis Car Chip plugged into the OBD II port. My suspicion is that at the beginning of a VHR the car requests status from the buss and the Davis Car Chip answers causing the VHR to abort because it doesn't recognize the sender of the data.

 

My procedure became to remove the Car Chip after the last trip on the last day of the month so the months data could be transferred to my computer and the Car Chip's memory cleared. On the first day of the month I run a VHR and then install the Car Chip.

 

It took me a while to realize what the problem was because the car would just say a VHR couldn't be run at this time.

[hybridbear]

I confirmed this morning that the trigger is starting the car while the SGII is still awake. Sometimes we turn the car off only for a few seconds and then turn it back on. If the SGII display is still on it will cause this code. I will make sure to unplug the SGII or something in the future to avoid this.