Yosemite random Crash - discoveryd_helper[147]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Confirm the same problem, freeze&reboot every week (

10.10.1, 13" pro mid 2012

Jan 13 20:57:03.842053 localhost discoveryd_helper[149]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Jan 13 20:57:03.842667 localhost discoveryd_helper[149]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7f922a409ab0: start (pid=51, <unknown> not root)

Same Issue: Mac Book pro - Yosemite 10.10.1 (14B25):

Jan 12 09:19:34.128279 MacBook.local discoveryd_helper[157]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Jan 12 09:19:34.128742 MacBook.local discoveryd_helper[157]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fe7d8600610: start (pid=52, <unknown> not root)

Another one: MacBook Air

Jan 15 11:21:07.387995 MacBook-Air.local discoveryd_helper[151]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Jan 15 11:21:07.388617 MacBook-Air.local discoveryd_helper[151]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fa570600460: start (pid=51, <unknown> not root)

Since disabling Bluetooth, I haven't had this error/crash in more than a week. I can't be 100% sure that Bluetooth was the cause, because disabling Bluetooth has also forced me to use the laptop open rather than in clamshell mode (with external keyboard, mouse, trackpad and monitor). I have since connected to the external monitor, but not to the Bluetooth peripherals. Another possibility is that it's related to heat and an automatic shutdown triggered by internal temperature, as I assume that using the laptop in clamshell mode was resulting in higher temperatures. Finally, I have also installed the latest beta version of OS X. But I'm convinced that one of these 3 things is the cause:

1. Bluetooth (or specific Bluetooth devices)

2. Temperature (especially when using the laptop in clamshell mode with an external screen, perhaps triggered by heavy processor or graphics card use)

3. OS X (if the bug was fixed by the latest Beta version)

Option 4 would be none of these if it's just a coincidence that my computer has been 100% stable since disabling Bluetooth and using the laptop 'open'. Time will tell.

I did originally use gfxCardStatus to disable the discrete graphics card, but connecting to the external monitor forced me to use the NVIDIA card. However, this did not result in a crash, so I'm now convinced that the NVIDIA card is not the culprit for this specific "discoveryd_helper" bug (other than perhaps being partly responsible for high temperatures). Also, I notice that the last person to post this bug (Werner Noebauer) is using a Macbook Air with no NVIDIA card, and is having the exact same problem.

So my suggestion is to disable Bluetooth and avoid clamshell mode, and see what happens. If that doesn't work, try to enrol in the AppleSeed program and install the latest beta version of OS X. I'll post again if I have a crash, which would invalidate all of these theories.

The causes could be seemingly different for everyone. For you, it seems to be Bluetooth. For me, it seems to be media related (flash, iTunes, etc ...). For others it might be different, or the same.

My theory is that disabling these features just neglects to call the line of code that triggers that crash. Another feature could potentially cause it too.

As I said in my previous post, I have received far less crashes neglecting to use media related apps/plugins. However, I've still come into work in the mornings and have found that my MacPro had crashed over night.

Again, still do not have this issue on my Macbook Pro (Late 2012).

Please Apple. Fix this issue. It's a huge setback for some of us.

I have found the following posts MacRumors forums: http://forums.macrumors.com/showthread.php?t=1824040

The author narrowed it down to a RAM issue. In my case (MacMini), I noticed the problem after I upgraded my RAM with 3rd party DIMMs. But I cannot definitely be sure that crashes were not happening before the RAM upgrade.

The apparent randomness is perplexing, along with the strangeness of the console message itself (which I've yet to see a good explanation for, or even an interpretation)...using Flash, iTunes etc. seemed to have no impact in my case. Your theory could be the best explanation I've heard so far, i.e. that the initial trigger could be different for everyone but ultimately related to a particular line of code which is common (in OS X). If I've found my trigger, I suppose I should just be happy with that.

Are you running the latest beta of OS X? The other possibility is that Apple has finally fixed this, as my Macbook becoming stable again also coincided with installing the beta of 10.10.2.

I'm not running the beta version. I will try it and report back.

I can confirm that this issue still exists in OS X Yosemite beta 10.10.2

Jan 15 10:58:28.829695 oph-ryan45-r10.ad.uab.edu discoveryd_helper[148]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Jan 15 10:58:28.829972 oph-ryan45-r10.ad.uab.edu discoveryd_helper[148]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fdf335005c0: start (pid=51, <unknown> not root)

I have read all the posts in this thread.

I have the same issue here. 2013 MacBook Pro 15" (second 15" MacBook Pro as first one was stolen). After upgrade of OS to 10.10 only 3 weeks ago I had 5 crashes in 8 days at random times with bluetooth on and off, flash active and not, and no Time Machine turned on as I do this manually given the lack of scheduling capability. I blocked the unexplainable ff and IP accesses going on and being brought to my attention to Norton and have not had a crash since. Maybe the trigger point for my computer, maybe the root cause of the crashing, only Apple can know. What I know is that it is less perplexing than we may think. As an IT executive and professional with over 27 years experience (and someone who has had every job in IT), this only happens with bad code and poor attention to quality assurance.

It is crappy programing and poor quality control within Apple! And it has been getting worse not better.

Since 2011 the software & product releases have had more and more bugs to the point where the systems are now crashing repeatedly inlcuding iPhones and iPads (albeit the iPads seem the most stable). As the leadership tries to tie their products together with similar OS services the poor programming in the base OS kernel will propagate throughout their product portfolio. So, instead of having tougher QA requirements, they release, to great fan fair, a new OS with more bugs than any OS in recent history and far more than any I know of since they switched from the PowerPC to Intel chip based machines (RISC vs. CISC) in 2006. In fact, I am still running a PowerPC G5 with OS 10 that is far more stable and FASTER than my newer MacPro (G5 like) and even newer MacBook Pro. Funny how the older machine is faster and more stable but has less processing power and less memory. Could it be better code?

Does anyone remember what happened the last time Apple decided to financially manage the company and not pay attention to the customer and to quality? 1985 - 1995 was the decade Apple would like to forget.

Like it or not, if we don't study history we are doomed to repeat it. Has Tim Cook studied Apple's history? Given what I have seen, I would guess not. Maybe he should call John Sculley and ask his advice as a former Apple CEO. Contrary to Sculley's perception, he was the beginning of the down fall at Apple even when he was CEO and saw revenue increase 10 fold. Like Cook, Sculley was not the leader that drove that revenue increase it was Jobs' leadership or as we say in executive meetings, it was the "long tail" of revenue. Stated another way, it just took a while for the lack of customer focus and lack of quality control to catch up with the company. Consumers switch technology over a long period of time but they also have longer memories that most CEOs give them credit for. I will start my switch away from Apple products with my personal cell phone. Apple won me back with the iPod in 2002 (which is no longer available because of the iPhone) so it is a bit poetic. Also, Apple is forcing me to do an upgrade anyway as their software becomes more buggy on my iPhone 4 (and slower too) and there is no way on earth I am spending another $400-$750 for a new iPhone (anyone remember Moore's Law?). Android devices work well enough for me so Google wins this cell phone customer. Next will be my home servers followed by my laptops and iPads. It may take a few years but Apple has lost me, again.

I am too old to wait another 20 years for them to see the mistake and maybe fix it.

It's hard to say accurately how many users this has been afflicting. I can understand how this problem could go unnoticed initially.

Given that this thread keeps climbing in views, it's hard to believe that Apple hasn't recognized the issue. I cannot listen to music or view anything media related. Granted, this is my work machine, so I'm not watching videos to begin with and I have my iPod for music. But for someone who might have this issue on their personal laptop, I can understand how upsetting this could be. I hope a possible fix comes soon; this issue is quite serious IMO.

The first post of this issue was in November and sadly no fix even in beta 10.10.2 .

Hey Old-School, I've been in the business since 1987 - from the datacenter up to the desktop.

Funny you mention Sculley here. I thought about these days just recently, while looking at APPLE and what they are doing.

I've even been to the Expo in SF when he was CEO, but missed his keynote. It was a sad event anyway, regarding the products and the outlook.

I had to work on a Mac in the office which looked worse than a Compaq (and was, he took care of that).

I only had this crash once, but it tripped me somehow and I went looking.

I would have sorted it out under lost and found, but this particular log entry just blew me.

What does it mean?

I've been on many consoles in my life, any kind, but this is by far the most strange log entry I ever saw.

P.S.

I suspect Google's keystone crap to be the cause...

I wouldn't blame it on APPLE solely, if it's not gonna be explained.

But, I plan to run some threads on some conspiracy forums about this, it has everything it takes to go viral.

I've got this problem too. iMac Retina 5K, 10.10.1. Crashes have been becoming more and more frequent.

It seems like my problem is resolved, my mac mini is up and running for more that 3 days without a crash.

This happened after I stopped using Audio Hijack Pro [AHP] (ver 2.11.4). My system was set up to start AHP at login. A few days ago I realized that my version of AHP did not seem to be officially supported for 10.9 or above. On a hunch I turned it off, and the system has been stable since then.

Note: Since I was not doing any recording with Audio Hijack, I started using LineIn --again by Rouge Amoeba, but free-- when I need to use the USB turntable. So far no problems.

Good luck with that. In the meantime my MacBook Pro just died.

I have another case with a customer's MacBook, same story.

Turned out to be of those models which burn out their GPU.

See this story here

http://www.macworld.co.uk/news/mac/widespread-2011-macbook-pro-failures-continue -petition-3497935/

Its sad. Poor design, thats the cause of it and Apple won't take the responsibility.