|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
|
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PR
Perhaps this was a to long title. But this should explain what happens when i try to start Pro Tools on my Macbook Pro. I have resently installed Pro Tools 9 on my iMac with Mac OS 10.7.1. I t works fine. But when i tried to do the same on Mac Book Pro it crashes. With the message provided in the title.
Any idé on what the problem might be. I can work but want to be mobile Thanks for any help!
__________________
http://www.pehjaproduktion.se when it makes a difference Macbook Pro 2.26 GHz intel Core Duo. OS 10.10.5 /Mbox Pro/Focusriteclarett 8Pre / iMac 3.06 GHz Intel Core 2 Duo OS 10.10.5/ PT 12 ( Mac Pro 3,5Ghz 6 core OS X 10.10.5 |
#2
|
||||
|
||||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
How old is the MBP? Have you checked the RAM?
Could be an app that is causing conflicts. Check to see if there are different apps in the computers. You need to give a list of your system. MBP OS version, RAM, drives, stuff like that. Please see: http://duc.avid.com/showthread.php?t=300050
__________________
Park The Transfer Lab at Video Park Analog tape to Pro Tools transfers, 1/4"-2" http://www.videopark.com MacPro 6 core 3.33 GHz, OS 10.12.1, 8 GB RAM, PT12.6.1, Focusrite Saffire Pro 40, PreSonus DigiMax, MC Control V3.5, dual displays, Neumann U-47, Tab V76 mic pre, RCA 44BX and 77DX, MacBook Pro 9,1, 2.3 Mhz, i7, CBS Labs Audimax and Volumax. Ampex 440B half-track and four-track, 351 tube full-track mono, MM-1100 16-track. |
#3
|
|||
|
|||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
Quote:
Macbook Pro 2.26 GHz intel Core Duo. OS 10.7.1 Saffire 6 USB iMac 24" 3.06 GHz Intel Core 2 Duo OS 10.7.1 The systems are identical apart from that one is a few years older. That is, the older computer works fine and the newer does not. This has nothing to do with RAM. The RAM is 4GB on both machines. The programs are identical. What I have installed on the iMac i have installed on the MacBook Pro. This must have something to do with computer model ? or?
__________________
http://www.pehjaproduktion.se when it makes a difference Macbook Pro 2.26 GHz intel Core Duo. OS 10.10.5 /Mbox Pro/Focusriteclarett 8Pre / iMac 3.06 GHz Intel Core 2 Duo OS 10.10.5/ PT 12 ( Mac Pro 3,5Ghz 6 core OS X 10.10.5 |
#4
|
|||
|
|||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
Quote:
How did you install Lion? Clean install or upgrade from SL? |
#5
|
|||
|
|||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
Upgrade on both Macs
__________________
http://www.pehjaproduktion.se when it makes a difference Macbook Pro 2.26 GHz intel Core Duo. OS 10.10.5 /Mbox Pro/Focusriteclarett 8Pre / iMac 3.06 GHz Intel Core 2 Duo OS 10.10.5/ PT 12 ( Mac Pro 3,5Ghz 6 core OS X 10.10.5 |
#6
|
||||
|
||||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
Been having the same issue after clean install over clean Lion.
It seems to occur after I have upgraded to 10.7.1. Process: Pro Tools [408] Path: /Applications/Digidesign/*/Pro Tools.app/Contents/MacOS/Pro Tools Identifier: com.digidesign.ProTools Version: 9.0.5 (9.0.5f52) Code Type: X86 (Native) Parent Process: launchd [145] Date/Time: 2011-08-27 23:50:48.157 +0300 OS Version: Mac OS X 10.7.1 (11B26) Report Version: 9 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000 VM Regions Near 0: --> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Digidesign/*/Pro Tools.app/Contents/MacOS/Pro Tools __TEXT 0000000000001000-000000000019d000 [ 1648K] rwx/rwx SM=COW /Applications/Digidesign/*/Pro Tools.app/Contents/MacOS/Pro Tools Application Specific Information: objc[408]: garbage collection is OFF Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.CoreFoundation 0x933628f1 CFStringGetLength + 17 1 com.apple.CoreFoundation 0x9337ac62 CFStringCompare + 18 2 com.digidesign.framework.DAE 0x040a71db FicHostPlugInRunnerInit + 153934 3 com.digidesign.framework.DAE 0x040a77d0 FicHostPlugInRunnerInit + 155459 4 com.digidesign.framework.DAE 0x03f4bed5 FicMain + 49541 5 com.digidesign.framework.DAE 0x03f64524 FicRegisterDirectMIDIClient + 80026 6 com.digidesign.framework.DAE 0x03fe4664 FWAudioCallback + 138910 7 com.digidesign.framework.DAE 0x03fe5ce9 FWAudioCallback + 144675 8 com.digidesign.framework.DAE 0x04028e71 FWAudioCallback + 419499 9 com.digidesign.framework.DAE 0x03f985ed FicReportExternalEvent + 7420 10 com.digidesign.framework.DAE 0x03f3fda0 FicMain + 80 11 com.digidesign.framework.DAE 0x03f3fb5e InitFic + 166 12 com.digidesign.framework.ProTools 0x01092432 MFortressHWBPEntryPoint_exit_mfort6317_ + 7411414 13 com.digidesign.framework.ProTools 0x010933a4 MFortressHWBPEntryPoint_exit_mfort6317_ + 7415368 14 com.digidesign.framework.ProTools 0x01d27916 MFortressHWBPEntryPoint_exit_mfort6317_ + 20605882 15 com.digidesign.framework.DFW 0x031925bd TCommandHandler::PerformCommand(TCommand*) + 251 16 com.digidesign.framework.DFW 0x03192b83 TCommand::Process() + 31 17 com.digidesign.framework.DFW 0x0318ab1a TApplication::ProcessEvent(TEvent*) + 26 18 com.digidesign.framework.DFW 0x0318ad74 TApplication::WakeUp() + 64 19 com.digidesign.framework.DFW 0x0329ca6f TApplication::GetApplicationVersionComponents(Cmn_ PolyVector<long, false>*) + 5659 20 com.apple.HIToolbox 0x9b5f4e54 _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36 21 com.apple.HIToolbox 0x9b47082b _ZL23DispatchEventToHandlersP14EventTargetRecP14Op aqueEventRefP14HandlerCallRec + 1602 22 com.apple.HIToolbox 0x9b46fca8 _ZL30SendEventToEventTargetInternalP14OpaqueEventR efP20OpaqueEventTargetRefP14HandlerCallRec + 482 23 com.apple.HIToolbox 0x9b46fac0 SendEventToEventTargetWithOptions + 75 24 com.apple.HIToolbox 0x9b48571e _ZL29ToolboxEventDispatcherHandlerP25OpaqueEventHa ndlerCallRefP14OpaqueEventRefPv + 3152 25 com.apple.HIToolbox 0x9b470ce6 _ZL23DispatchEventToHandlersP14EventTargetRecP14Op aqueEventRefP14HandlerCallRec + 2813 26 com.apple.HIToolbox 0x9b46fca8 _ZL30SendEventToEventTargetInternalP14OpaqueEventR efP20OpaqueEventTargetRefP14HandlerCallRec + 482 27 com.apple.HIToolbox 0x9b484ac9 SendEventToEventTarget + 76 28 com.apple.HIToolbox 0x9b5f4ca0 ToolboxEventDispatcher + 82 29 com.apple.HIToolbox 0x9b5f4dcf RunApplicationEventLoop + 236 30 com.digidesign.framework.DFW 0x032a3141 DFW_EventLoop::RunApplicationEventLoop() + 11 31 com.digidesign.framework.DFW 0x0318a73b TApplication::Run() + 45 32 com.digidesign.framework.ProTools 0x01ee8c0a LaunchProTools + 2365 33 com.digidesign.ProTools 0x0000f4a3 0x1000 + 58531 34 com.digidesign.ProTools 0x0000e4cb 0x1000 + 54475 35 com.digidesign.ProTools 0x0000e3f9 0x1000 + 54265
__________________
iMAC 27" i7, DIGI003 + ADA8000, PT9, Waves and Sonnox, ReelTape, DIY large Analog Modular Synthesizer, MKS-70, Matrix-6R, DIY sequencers, MP5, Tannoy Precision-8D. |
#7
|
|||
|
|||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
So then use 10.7.0 until AVID qualifies v10.7.1.
__________________
Jonathan S. Abrams, CEA, CEV, CBNT Apple Certified - Technical Coordinator (v10.5), Support Professional (v10.6 through v10.10) |
#8
|
||||
|
||||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
Using beta software with an unqualified software version might be the place to start.
__________________
Park The Transfer Lab at Video Park Analog tape to Pro Tools transfers, 1/4"-2" http://www.videopark.com MacPro 6 core 3.33 GHz, OS 10.12.1, 8 GB RAM, PT12.6.1, Focusrite Saffire Pro 40, PreSonus DigiMax, MC Control V3.5, dual displays, Neumann U-47, Tab V76 mic pre, RCA 44BX and 77DX, MacBook Pro 9,1, 2.3 Mhz, i7, CBS Labs Audimax and Volumax. Ampex 440B half-track and four-track, 351 tube full-track mono, MM-1100 16-track. |
#9
|
|||
|
|||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
With me it was the presence of Flux and Izotope plugins. After a call to Tech Support, removed those. Now everything is fine.
It is my understanding that both companies are working on a fix and expect to have it out very soon. Mac OS 10.6.8 HD|Native Rob |
#10
|
|||
|
|||
Re: Crashed Thread: 0 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KER
I believe that Apple does not officially support Lion on the Core Duo, Core 2 Duo yes, Core Duo, no. If it really is a "Core" not a "Core 2", that might point to a cause for your error message.
Good luck. Kevin
__________________
Gigabyte GA-P35-DS4; Q9650; Win 7-64; Saffire Pro 40; PT 12 / MacBook Pro C2D 2.66; 10.10.3; PT 11.3.1 |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PR | dorothy | macOS | 12 | 12-07-2013 10:19 PM |
Exc_bad_access (sigbus) | basslik | macOS | 17 | 12-03-2013 08:04 AM |
"floating point exception" in thread "mainthread", at address 0x0 | simmo.d.cooper | macOS | 10 | 03-09-2013 10:34 PM |
Fatal Exception | Badsimaritan | Digidesign Hardware & Software | 0 | 11-07-2002 08:48 PM |
Fatal exception OE | tkob24 | Digidesign Hardware & Software | 0 | 02-16-2002 02:51 AM |