D3 Not Launching -Stops responding after Play

I wouldn't be making my own topic if I thought I had an option but every "fix" listed in other threads isn't helping me any. I'm on my macbook right now so I don't have my profiler but D3 is running on my 2011 iMac (2.8GHz i7, 8GB of RAM, 6770m GPU) and was working fine from the Beta up until the latest patch (or the one before it, I got 2 at once)

The launcher opens fine but when I click play I get the skull, a black screen, and then the game stops responding and I have to force quit it. I don't have the debug file on me right now but I can say for certainty that the error appears right below the "Initializing sound subsystem" line which leads me to believe that the game for some reason can't find my sound drivers and therefore crashes.

and probably a lot more that I can't recall. There's nothing I can seem to do in order to fix this problem so I'm desperate at this point. I know my mac is capable of running it and every other game (WoW, Skyrim, Portal, TF2, etc) installed runs fine but D3 won't work.

If you want some debug files or profiler just ask and I'll try to get them up when I'm on my iMac. I'm willing to do just about anything at this point.

Nope, I made sure to check that, it isn't there. As a note as well I've now done another full re-install as a desperation move since I missed deleting a few things the first time around, no luck the problem still persists.

Alright, I don't really like to bump stuff but my support ticket has hit a standstill because he's determined it's an applecare problem (yet somehow the rest of my system works perfectly) and there's nothing more I can really tell him.

The problem may fix itself in 1.07 but I hardly feel like waiting around that long for an answer, if one even comes with it. I don't mean to complain but Diablo 3 has ran fine on my system ever since the beta and all of a sudden it doesn't open anymore, that's not my system, that's the game. For the last two months I've had a game I paid over $60 for that it just taking up harddrive space on a computer plenty powerful enough to run it. The way I see it this is not at all acceptable.

From your debug file, it seems a crash is being generated. Do you ever get a nice error code that says "Please type in what you were doing" to send to Blizzard? The report in the debug file doesn't explain much, but if a report Id is generated, I can look at the report there and it will show more specific details why it occurs.

I don't recall what usually pops up but I know there is something with a large empty box and a code under it that usually opens. I don't remember what it says but that's probably what you're talking about.

I dug up your crash report. The crash seems to be similar to the sonix web cam plug. All things match the same reports, but showing more OS related plugins. When you stated you reinstalled your OS, was it just a combo update install or full reinstall?

Here is a typical sonix webcam driver crash (I'm only showing the stack trace that is causing the crash):SIGABRT (Abort trap)

It was a combo update suggested by the support tech, I never did a full re-install as I didn't figure it would make a huge different. Do you believe that may be required or do you think I could simply delete those files and restart my computer, assuming they are corrupt they will just be re-created properly.

I don't know fore sure, as those files might be something in the frame work part of the OS. You may want to contact Apple just to be sure.

This was data from the last crash, so if you can get another crash error report, I can do a comparison, but at this point signs are pointing to the OS. Maybe Bluspacecow/Omegal can pop in and suggest something.

Alright, to see if it will help I got it to crash again (pretty easy at this point haha) and got this code:

33D7A110-20F3-4D2C-97D0-E3A49113D75A

If it looks like it's pointing to the same thing I can look into contacting apple and checking to see if it's something that will simply regenerate itself or if I should run a full re-install. If it points to something different then I guess we're a bit stuck haha.

Good news. Here is the feedback I got from the team after they read all the crash report IDs you provided today and yesterday:

After looking at his crashes. It appears the problem is when D3 initializes, it loads the system plugins and one of the plugins (DVCProHDAudio) is crashing during initialization. I think that plugin comes with Final Cut Pro. Can you please ask the user if he has Final Cut on his computer? If so, ask him if he has all the latest updates installed? Ask him if he is using the latest version of the DVCProHDAudio plugin. If he is willing can he uninstall Final Cut (make sure he runs the uninstaller and not just trash the app).

I couldn't find out where that plugin comes from. If he knows we can send an email to that company and try to figure out why it is crashing.

If he removes/Library/Audio/Plugin-Ins/HAL/DVCPROHDAudio.plugin then Diablo 3 will probably run. I don't recommend removing plugins unless he knows what he is doing because that plugin may be needed by another program.

That all sounds well and good, in fact I do have Final Cut installed on my computer. However I moved the file to my external drive (in case I need it later) and then deleted it. Unfortunately the problem sill persists. Here's the newest error code:

5E45023D-C3E2-4C17-BE10-0ADC2E58A3D1

In addition I did notice that the debug file has changed slightly. The error still occurs during the sound initializing but it's occurring further down then before. Here's the new debug file:

http://pastebin.com/HCkh8ig8

Hopefully the changes mean we're getting a little closer.

For the record, as far as I know, the plugin is just for reading audio signals from HVCPro HD cameras which would be Panasonics. I've never used one before and doubt I ever will so I'm not too worried about it. I kept it anyway though just in case. Also, it was tricky to find because your post implied it was in the user Library when, in fact, it was in the core one. Just letting you know.

The path should be point to the system Library (no ~). I apologize if there was any confusion. The path may have been different due to the format of the folders (this was simply a copy/paste from an email).

Looking at your new crash, it is still crashing when the FMOD initializes the system plugins. Just now it isn't referencing the DVCProHDAudio plug-in when it loads sound plugins (I'm trying to narrow down the new reference in the crash log). From what It see, FMOD loads, tries to load sound plugins, but nothing is being loaded. I'm having the team take a look at this updated crash.

Did you try the other suggestions they mentioned, such as making sure FCP was fully up to date or trying to do a full uninstall (not just trashing the app) to see if it fixes the issue.

I technically have two versions of FCP installed. I have Final Cut Pro X which is the brand new one. It isn't fully up to date because I almost never use it, I don't mind uninstalling this one because I hate it and never use it.

The other I have is Final Cut Pro 7, the older program. It is updated as far as possible since apple dropped support for the program. I'm not willing to uninstall this one, however. I have projects on the go that can get corrupted if I uninstall. FCP is required for me.

I will try uninstalling FCP X though and see if it helps while you look into it further.