Jump to content

Blue screen and service rear vision system

Radchad
 Share

Recommended Posts

Radchad Enthusiast

Radchad

Posted
Posted

Some morning while backing out of my garage and the temps are cooler here in Michigan I get the blue screen of deaths and service vision system screen.  Do I need a software update or is it a connection issue ?

anyone else have this problem? 

Thanks 

 

IMG_3809.JPG

bowtie2007 Enthusiast

bowtie2007

Posted
Posted

I brought my truck in for this problem a few weeks ago. They did all the latest updates that applied to my truck including one to supposedly fix the camera issues. Since that update, I've got the blue screen twice... so it did not fix it.

On the plus side, i haven't had the acknowledgments pop up ever other day!

Sent from my SM-G892A using Tapatalk

vegasbob Enthusiast

vegasbob

Posted
Posted

6600 Miles..mine just turned blue today and my screen still has the occasional climate control off screen... That is 3 electronic bugs ...We should get an extended warranty of 6 months to allow for our troubleshooting GM's bugs!

 

Jmonty Enthusiast

Jmonty

Posted
Posted

Mine showed up a few times but after the last update hasn't reappeared 

  • 2 weeks later...
JayTrailBoss Enthusiast

JayTrailBoss

Posted
Posted
On 5/23/2019 at 5:50 PM, Radchad said:

Some morning while backing out of my garage and the temps are cooler here in Michigan I get the blue screen of deaths and service vision system screen.  Do I need a software update or is it a connection issue ?

anyone else have this problem? 

Thanks 

 

IMG_3809.JPG

https://www.gm-trucks.com/forums/topic/223462-2019-silverado-backup-camera-problems/

 

Please file a complaint with GM and NHTSA, this seems like an ongoing issue with their backup cameras. Mine is constantly doing this, so frustrating. I also notified the attorney general's office since GM gave me a generic response. When someone gets hurt or killed they might respond with oh this is the first we've heard of it wow...frustrating!

steve841 Enthusiast

steve841

Posted
Posted (edited)

Back when the reverse cams first started appearing many years ago, you'd put it in reverse, be all the way backed out before the image would appear.  This must be the updated version.

Edited by steve841
  • 8 months later...
DenaliDave Enthusiast

DenaliDave

Posted
Posted

My 2019 Sierra Denali experienced the same issue. Dealer replaced the camera module, hasn’t happened since. This was before all the updates for brake issues.


Sent from my iPhone using Tapatalk

Steve Martin Enthusiast

Steve Martin

Posted
Posted
43 minutes ago, DenaliDave said:

My 2019 Sierra Denali experienced the same issue. Dealer replaced the camera module, hasn’t happened since. This was before all the updates for brake issues.


Sent from my iPhone using Tapatalk

Can you describe the camera module?  Any idea where it's located, etc?  I don't plan on working on it.  I'll leave that to my dealer, but I wanted to give them some information to go off of.  Just in case they don't call it the camera module or something.  Is that what was listed as a description on your invoice?  Thank you for this info.  Dealer replaced my rear camera in the tailgate before and did not fix.  I suspect the camera module is a piece of hardware that boots up and connects to the entertainment system somehow.  I've heard of something like this under a seat or something.  Just trying to gather some info and detail when I tak it in next week.

DenaliDave Enthusiast

DenaliDave

Posted
Posted

Dealership stated it’s a module behind the rear seats. If I can find the invoice I’ll post a pic of the repair info.


Sent from my iPhone using Tapatalk

Steve Martin Enthusiast

Steve Martin

Posted
Posted (edited)

Thank you for that info.  Took mine in yesterday and dealer reproduced issue, not hard to do...  Tried the service bulletin, 19-NA-076, but still reproduced,  Sent me home  saying they will replace the control module and have ordered it.  I assume same module you got replaced.  I checked the part number 84624987 and got only a couple of hits on Google which only confirms it's a genuine GM part...  Anyway, will see if this finally fixes the issue.  It sounds like they contacted GM after the service bulletin didn't take care of it and this was the recommendation.  Patiently waiting.

 

Edit, after checking my invoice shows they ordered a different module part number, 84691752, module 9.680 with no (N) like yours.  Wonder the difference.  I have the technology package with surround cameras.

Edited by Steve Martin
additional
  • 10 months later...
Nathan Hayes New Member

Nathan Hayes

Posted
Posted

Searched a ton of forums with this issue and I’ve seen One post that tied all my problems together and thought this would help. Bought my 2016 Sierra 3500 duramax used with 90k miles.  Off the lot I had the blue screen of death. Along with my trailer brake cutting in and out when pulling. Changed out the camera and still nothing. Went over all the fuses at least 3 times and still nothing, until I pulled the fuse for my trailer brake ( under hood) and noticed a very small patch of white corrosion forming?.  I eventually lost my backup lights sometime later.  Searched some posts and another guy with the same problem mentioned he changed out his main fuse block under the hood and it fixed the camera.  I order a new fuse block and for the first time I got my backup camera back and my backup lights are now working. Hope this helps

  • 6 months later...
Ron Vickney New Member

Ron Vickney

Posted
Posted
On 1/26/2021 at 2:21 PM, Nathan Hayes said:

Searched a ton of forums with this issue and I’ve seen One post that tied all my problems together and thought this would help. Bought my 2016 Sierra 3500 duramax used with 90k miles.  Off the lot I had the blue screen of death. Along with my trailer brake cutting in and out when pulling. Changed out the camera and still nothing. Went over all the fuses at least 3 times and still nothing, until I pulled the fuse for my trailer brake ( under hood) and noticed a very small patch of white corrosion forming?.  I eventually lost my backup lights sometime later.  Searched some posts and another guy with the same problem mentioned he changed out his main fuse block under the hood and it fixed the camera.  I order a new fuse block and for the first time I got my backup camera back and my backup lights are now working. Hope this helps

 

 

Hey do you know what fuse number that was under the hood please?

 

 

Ron Vickney New Member

Ron Vickney

Posted
Posted

I'm having the same issue on my 2018 Sierra once I put in reverse I get the blue screen so the dealership replace the rear camera and I'm still having that problem does anybody recommend another level I should tackle or has anyone had their HMI replaced?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   4 Members, 0 Anonymous, 1,640 Guests (See full list)

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...