MacBook Air fans spinning while sleeping

[zfgxdfgdfg]

Hi!

I got a MacBook Air about two weeks ago (Apple refurbished Early 2015 1.6 GHz i5 with 8GB RAM and 256 SSD), and it's been good to me so far.

However, I've noticed lately that sometimes I can hear the fans going nuts when it's asleep and charging. I know that suggests that Power Nap has something to do with it, but according to this page…

Power Nap is silent

During Power Nap, your Mac plays no system sounds, including the Play Sound or Send Message feature of Find My Mac. If your Mac uses flash storage (excluding Fusion Drive), you hear no fan. When Power Nap is turned on, your computer may be warm to the touch even if it's sleeping. If it exceeds a predefined temperature, Power Nap operations are suspended so that your Mac does not overheat. When your Mac wakes up, it’s ready to go.

…the fans shouldn't come on during Power Nap (italics mine).

I checked the Console, as as best as I can tell, the two offending entries seem to be these…

10/9/15 12:30:10.085 AM navd[405]: NSURLSession/NSURLConnection HTTP load failed (kCFStreamErrorDomainSSL, 100005)
10/9/15 12:30:10.087 AM navd[405]: PBRequester failed with Error Error Domain=NSURLErrorDomain Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made." UserInfo={NSURLErrorFailingURLPeerTrustErrorKey=<SecTrust 0x7f836346b950 [0x7fff7b9aa890]>, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFStreamErrorDomainKey=3, _kCFStreamErrorCodeKey=100005, NSErrorPeerCertificateChainKey=(
    "<SecCertificate 0x7f836376afe0 [0x7fff7b9aa890]>",
    "<SecCertificate 0x7f8363755640 [0x7fff7b9aa890]>",
    "<SecCertificate 0x7f8363713b40 [0x7fff7b9aa890]>"
), NSUnderlyingError=0x7f836345e830 {Error Domain=kCFErrorDomainCFNetwork Code=-1200 "An SSL error has occurred and a secure connection to the server cannot be made." UserInfo={NSErrorFailingURLStringKey=https://gsp10-ssl.apple.com/use, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, _kCFNetworkCFStreamSSLErrorOriginalValue=100005, kCFStreamPropertySSLPeerCertificates=(
    "<SecCertificate 0x7f836376afe0 [0x7fff7b9aa890]>",
    "<SecCertificate 0x7f8363755640 [0x7fff7b9aa890]>",
    "<SecCertificate 0x7f8363713b40 [0x7fff7b9aa890]>"
), _kCFStreamPropertySSLClientCertificateState=0, kCFStreamPropertySSLPeerTrust=<SecTrust 0x7f836346b950 [0x7fff7b9aa890]>, NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made., _kCFStreamErrorDomainKey=3, NSErrorFailingURLKey=https://gsp10-ssl.apple.com/use, _kCFStreamErrorCodeKey=100005}}, NSLocalizedDescription=An SSL error has occurred and a secure connection to the server cannot be made., NSErrorFailingURLKey=https://gsp10-ssl.apple.com/use, NSErrorFailingURLStringKey=https://gsp10-ssl.apple.com/use, NSErrorClientCertificateStateKey=0}

…although I can't say for sure. These two entries appear to be repeated exactly every 15 minutes in the latest sleep session. Last night's sleep, however, doesn't seem to have them (and I don't remember hearing the fans last night). It's inconsistent, I suppose.

I've also tried resetting my SMC, but no dice.

I know this isn't supposed to happen. Is there anything I can do, or is this faulty hardware and something I should bring in to the Apple Store?

Thanks!

(Also, I'm running all the latest software updates, etc.)

 

[frankdogg]

I see you did the SMC reset, but did you also try doing a PRAM reset as well? just trying to help you cover all the bases.

 

[zfgxdfgdfg]

I see you did the SMC reset, but did you also try doing a PRAM reset as well? just trying to help you cover all the bases.

I'm not positive the SMC reset was successfully done before actually. I just did an SMC reset, did a Safe Boot, and reset NVRAM right now. Now I suppose we play the waiting game, and see what happens. I'll report back!

 

[zfgxdfgdfg]

Welp, those didn't take. Seems like a longshot, but I've also had removing the sleepimage suggested. I'll give it a shot and report back. Odds aren't seeming in my favor though.