MacBook Pro Retina Fan Issues

peppie55 wrote:

Just spoken a senior advisor at apple care, he will keep me personally in touch about this problem. He also said this problem is not a known problem, I hope this is going to be fixed soon, because it's very annoying...

This is what you people SHOULD BE DOING.

There is a lot of whining here and it makes me that much happier that I no longer work in AppleCare with all the "OH EM GEE Guys… Spent soo much money and the fanz revz soooo hard… bLBAHBLAHBLAH complain complain complain"

It's fan revving is annoying… and REALLY that's about all. I'm UNEMPLOYED at the moment yet, mustered up some money because I NEEDED a computer and have the same problem as ALL of you guys… fans are revvin hard for no reason. Complaning and complaining in here WILL NOT RESOLVE THIS ISSUE. I personally could care less that the fans rev, it doesn't bother me as I know it can be FIXED via a EFI or SMC update

Everyone should use Peppie's case number as our aid when we call in and report the issue.

DO NOT LET the "Advisor" tell you to reset the PRAM as that has absolutley NOTHING to do with the fan issue. If the advisor recommends you to reset the PRAM, then nicely ask to please be escalated to a Senior Advisor.

Share Peppie's case number with the Senior Advisor (my former position). Ask to have a written escalation to engineering. The ONLY thing that would resolve this issue is an SMC reset - http://support.apple.com/kb/ht3964 —— if you've already done that and issue persist then great … tell them that. The more people report this, the faster we'll get a resolution.

THATS THE WAY IT WORKS… when they see the same kind of issue being reported, then they investigate it.

Sorry for the rant but my email keeps getting hit with all the replies from this and people's whinning is MORE ANNOYING thanthe fan situation we all have

Can reproduce on the floor model in front of genius (for appointment). Will keep you informed.

I gave the number preppie mentioned earlier. Everyone should use that case number in correspondence with apple.

You are annoying

What ssd is in that macbook? Because I pointed the senior advisor at the wrong sandisk ssd's

My case number is 419723106

I'm still waiting for the call of Apple. Hopeffully I will hear from them today.

My case number 419669449

I've called them twice - nothing good.

eshirinkin wrote:

My case number 419669449

I've called them twice - nothing good.

Did you end up speaking to a senior advisor?

Here is our collection of case numbers:

416742374

419723106

419669449

I'll be adding mine later today

Unfortunatly no, I didn't speak with senior advisor.

Hi Oyinko2,

Got a call from Apple Executive Relations. They talked to the engineering and confirmed that they are investigating the issue.

Regards'

A bunch of messages disappeared here (strange?), but i talked with the genius bar a few hours and have an engineering code R86219445

It was the same sandisk ssd that we all saw. This macbook clearly said "early 2013" too

FWIW, have this too on my wife's new rMBP (10,1 - ME665LL/A)

16GB RAM, 512GB SSD, i7, NVIDIA 650M 1GB.

Will see if an SMC/software update has any impact before going nuts on it.

I have been watching this thread for a few days now. I have an early 2013 rMBP - 2.4,16,256 model. The fans do spin up seemingly randomly and definitely with lossless audio. Since it has been bugging me, I contacted apple tonight and explained the issue and mentioned the forum - which they claim to not be able to pay attention to due to rumours etc...! Anyway they are replacing the computer. After reading this and other threads, I seriously doubt this will help. It is pretty annoying as this one is already a replacement for one that had a logic board fault (graphics controller fault), although that one did also have the same fan issue (2012 spec rMBP 2.3,16,256, february build.

The case number is 420291377 btw...

the 14 day return policy warrants going nuts. I've got a bit more than a week left but others are on their last days.

Is there anywhere we can look for updates with this code?