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

I'm sorry, but I'm not sure I follow how this is related to the crashes we've been receiving. Were you receiving the same crash logs as the users from the rest of the thread?

Thanks

Yes, of course, thats how I found this thread.

I started looking at all because it were the only log entries regarding the crash.

And out of the obscurity of the logged messages.

Then it got worse, now its dead.

It's your GPU going haywire, thats what it is, I'd bet my mother in laws home on it.

OK to narrow it down - What type of GPUs have your machines got?

I have two MacBook Pros 8,2 with blown AMD 6750M.

Both won't boot any MacOS, not even the hardware test, unless I remove the AMD kexts.

Then they boot with crazy graphics and all kind of issues, no sleep, no brightness control, no gamma correction, must be some kind of legacy mode, but running on the AMDs.

It won't switch to the internal video, at least I didn't managed to make them.

Who'll take the blame and pay, AMD, Apple or the customer?

If you don't want to burry your machines and even don't want to fork out 650 € (thats the price in the EU) I'd consider a motherboard repair.

There are several services available on eBay. It's a GPU change, which isn't that much of a hassle if one has the right tools.

Most of the services with a good count offer a one year warranty and you'll get an up to date model of the GPU, which in this case is the 6770M.

It's about 150 € with shipping, I have one on the way.

I also have AMD graphics cards on my malfunctioning machine. Two AMD FirePro D500 graphics cards.

My MacBook Pro contains the Intel integrated graphics card and experiences no issues. However, I believe some have complained of this problem on their MacBook Airs, which do not offer AMD graphics cards either.

My MBP with this issue has an NVIDIA card. Yes, at least one person in this thread was using a MBA with no discrete graphics. I don't think it's specific to AMD cards.

Hm, maybe Apple found a way to burn any kind of GPU?

Not that nVidia had any issues, I think there are still some replacement programs running as well.

OS X 10.10.2 is officially out. As with the beta version, this issue is still not listed as fixed.

About the OS X Yosemite v10.10.2 Update - Apple Support

Just thought I'd add my voice. Bit of a mystery. "Quiet" crashes for me in that the machine stays up, but it happens three or four times a day now -- and 10.10.2 has not addressed the issue.

15" MacBook Pro 6,2 (Mid-2010)

OS X 10.10.2 (14C109)

Just a short me too notice:

bash-3.2# uname -a

Darwin straylight 14.1.0 Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64 x86_64

bash-3.2# cat CrashReporter/com.apple.networking.discoveryd.log

Jan 30 12:25:45.800890 straylight.local discoveryd_helper[166]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Jan 30 12:25:45.801255 straylight.local discoveryd_helper[166]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7ff643e00520: start (pid=48, <unknown> not root)

I've been having this same issue for several months, even before the release of Yosemite. I've tried everything from having Apple look at it to sending many (two or three a week for the entire month of October) disk images to Apple Support for engineers to look at. I think they may have gotten tired of trying to figure out what was wrong with my late 2012 iMac, because I wasn't contacted after my last call/message to Apple Support.

Below is a screen shot of the most recent crash report.

Problem still occurs with Yosemite 10.10.2:

Feb 3 10:57:30.927887 localhost discoveryd_helper[158]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Feb 3 10:57:30.928629 localhost discoveryd_helper[158]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fa072e00970: start (pid=51, <unknown> not root)

Bought my Macbook 15 inch retina in the early new year and I now have a genius appointment booked for the end of this week but the outlook doesn't look hopeful given the comments in this thread.

discoveryd_helper[150]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

That is what I'm getting and I also noticed crashes relating to Spotify although the trackpad and keyboard wouldn't work, the music still played. Its quite strange really and Apple's quality control is shocking. I cant work like this. I've been with Apple for 8 years now and have had more crashes in 1 month of use on this device than the last 2 Macbook's put together.

I'll be demanding either a brand new machine that works or a full refund. If they fail to issue either I'll be taking the matter through the courts because this is just ridiculous. These products are being released and they're not even fit for purpose. I have run hardware diagnostics and everything is fine according to those diagnostics tests. There is nothing more than I can do and when you have just parted with the best part of just under £2k for a laptop you expect it to ******* work.

Shocking quality since Steve Jobs died. Never has the quote that was used in the Jobs movie been more appropriate. If this type of crap continuously keeps being released people are going to get wise to it to Apple's detriment.

I have the same problem and log entries. Running 10.10.2 on a mid-2012 rMBP.

Feb 11 08:53:30.714037 Mac.local discoveryd_helper[169]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Feb 11 08:53:30.714484 Mac.local discoveryd_helper[169]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7ffa3c100110: start (pid=52, <unknown> not root)

As I have reported a while ago my crash problem disappeared after I disabled the unsupported version of Audio Hijack Pro which was set to run automatically on login.

For those of you who continue to experience these crashes, I would suggest reviewing what applications are running during the crashes. If you can afford it, try running the machine with Apple-only apps long enough to cover your typical crash period. Based on my experience with the Audio Hijack Pro, I have a hunch that the crash might be triggered by applications accessing external interfaces (maybe USB only) through a mechanism that changed in Yosemite.