Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

0 points

Damsel in Distress Again.

Yesterday I updated whatever the system software update was and ever since, my MacBook Pro Mid- 2009 will shut down/crash due to a "problem" only after the machine goes to sleep for I"m guessing 10 minutes, maybe less. All I know is that I come back and when I either move the mouse or press a key to wake the machine, I have that gray screen with the message. I've included the crash report and if someone here would be so kind to give me a clue to what or where I might start to remedy the problem, I would be forever grateful. Okay..maybe not forever, but this week anyway. 🙂 I am saavy enough with the inner workings to fix most of the 26 macs in my lab, but this one is beyond my knowledge base. Thank you in advance.

Dawn

Interval Since Last Panic Report: 11931 sec

Panics Since Last Report: 3

Anonymous UUID: 4D20B80C-72BE-5224-3433-831E0CB0B6B0

Wed Mar 20 12:31:59 2013

panic(cpu 1 caller 0xffffff8008ab7e95): Kernel trap at 0xffffff7f8941ee49, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x0000000000000040, CR3: 0x000000000b734000, CR4: 0x0000000000000660

RAX: 0x0000000000000000, RBX: 0x0000000000000001, RCX: 0x0000000000000000, RDX: 0x0000000000000900

RSP: 0xffffff808186b910, RBP: 0xffffff808186b9b0, RSI: 0x0000000000000000, RDI: 0xffffff806d4e1000

R8: 0xffffff808186b354, R9: 0xffffff808186b514, R10: 0x0000000100000600, R11: 0xffffff808186b190

R12: 0x0000000000000000, R13: 0xffffff808186bcf8, R14: 0xffffff806d4e1000, R15: 0x00000000ffffff00

RFL: 0x0000000000010282, RIP: 0xffffff7f8941ee49, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0x0000000000000040, Error code: 0x0000000000000000, Fault CPU: 0x1

Backtrace (CPU 1), Frame : Return Address

0xffffff808186b5b0 : 0xffffff8008a1d626

0xffffff808186b620 : 0xffffff8008ab7e95

0xffffff808186b7f0 : 0xffffff8008acd4dd

0xffffff808186b810 : 0xffffff7f8941ee49

0xffffff808186b9b0 : 0xffffff7f894137f7

0xffffff808186bbf0 : 0xffffff7f891bd387

0xffffff808186bc60 : 0xffffff7f891a957b

0xffffff808186bcd0 : 0xffffff7f891ac1b8

0xffffff808186bd40 : 0xffffff7f891ac343

0xffffff808186bdb0 : 0xffffff7f891abdb4

0xffffff808186be10 : 0xffffff7f89172c78

0xffffff808186be50 : 0xffffff7f89171f63

0xffffff808186be80 : 0xffffff7f8917131e

0xffffff808186bef0 : 0xffffff8008e467a8

0xffffff808186bf30 : 0xffffff8008e452aa

0xffffff808186bf80 : 0xffffff8008e453d9

0xffffff808186bfb0 : 0xffffff8008ab2977

Kernel Extensions in backtrace:

com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f89164000->0xffffff7f8919bfff

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8905a000

com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f891a7000->0xffffff7f891b8fff

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f89164000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8905a000

com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f891bb 000->0xffffff7f894c8fff

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f8905a000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f891a7000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f89164000

BSD process name corresponding to current thread: kernel_task

Mac OS version:

12D78

Kernel version:

Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64

Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6

Kernel slide: 0x0000000008800000

Kernel text base: 0xffffff8008a00000

System model name: MacBookPro5,5 (Mac-F2268AC8)

System uptime in nanoseconds: 4146224333684

last loaded kext at 80172189897: com.apple.filesystems.smbfs 1.8 (addr 0xffffff7f8900d000, size 229376)

last unloaded kext at 130035876012: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f8abc7000, size 8192)

loaded kexts:

com.apple.filesystems.smbfs 1.8

com.apple.driver.AppleBluetoothMultitouch 75.19

com.apple.iokit.IOBluetoothSerialManager 4.1.3f3

com.apple.driver.AudioAUUC 1.60

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AGPM 100.12.87

com.apple.driver.AppleUpstreamUserClient 3.5.10

com.apple.GeForce 8.1.0

com.apple.driver.AppleHDA 2.3.7fc4

com.apple.filesystems.autofs 3.0

com.apple.driver.AppleMikeyHIDDriver 122

com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.1.3f3

com.apple.driver.AppleSMCLMU 2.0.3d0

com.apple.driver.AppleMikeyDriver 2.3.7fc4

com.apple.iokit.IOUserEthernet 1.0.0d1

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.ApplePolicyControl 3.3.0

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleLPC 1.6.0

com.apple.driver.AppleBacklight 170.2.5

com.apple.driver.AppleMCCSControl 1.1.11

com.apple.driver.SMCMotionSensor 3.0.3d1

com.apple.driver.AppleUSBTCButtons 237.1

com.apple.driver.AppleUSBTCKeyboard 237.1

com.apple.driver.AppleIRController 320.15

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.BootCache 34

com.apple.driver.AppleUSBCardReader 3.1.7

com.apple.iokit.SCSITaskUserClient 3.5.5

com.apple.driver.XsanFilter 404

com.apple.iokit.IOAHCIBlockStorage 2.3.1

com.apple.driver.AirPort.Brcm4331 614.20.16

com.apple.driver.AppleFWOHCI 4.9.6

com.apple.driver.AppleAHCIPort 2.5.1

com.apple.driver.AppleUSBHub 5.5.5

com.apple.nvenet 2.0.19

com.apple.driver.AppleUSBEHCI 5.5.0

com.apple.driver.AppleUSBOHCI 5.2.5

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleEFINVRAM 1.7

com.apple.driver.AppleRTC 1.5

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleACPIButtons 1.7

com.apple.driver.AppleSMBIOS 1.9

com.apple.driver.AppleACPIEC 1.7

com.apple.driver.AppleAPIC 1.6

com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0

com.apple.nke.applicationfirewall 4.0.39

com.apple.security.quarantine 2

com.apple.driver.AppleIntelCPUPowerManagement 196.0.0

com.apple.driver.IOBluetoothHIDDriver 4.1.3f3

com.apple.driver.AppleMultitouchDriver 235.29

com.apple.iokit.IOSerialFamily 10.0.6

com.apple.nvidia.nv50hal 8.1.0

com.apple.NVDAResman 8.1.0

com.apple.driver.DspFuncLib 2.3.7fc4

com.apple.iokit.IOAudioFamily 1.8.9fc11

com.apple.kext.OSvKernDSPLib 1.6

com.apple.kext.triggers 1.0

com.apple.iokit.IOFireWireIP 2.2.5

com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.1.3f3

com.apple.driver.AppleHDAController 2.3.7fc4

com.apple.iokit.IOHDAFamily 2.3.7fc4

com.apple.iokit.IOSurface 86.0.4

com.apple.iokit.IOBluetoothFamily 4.1.3f3

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.AppleSMBusPCI 1.0.11d0

com.apple.driver.IOPlatformPluginFamily 5.3.0d51

com.apple.driver.AppleGraphicsControl 3.3.0

com.apple.driver.AppleBacklightExpert 1.0.4

com.apple.iokit.IONDRVSupport 2.3.7

com.apple.driver.AppleSMBusController 1.0.11d0

com.apple.iokit.IOGraphicsFamily 2.3.7

com.apple.driver.AppleSMC 3.1.4d2

com.apple.driver.AppleUSBMultitouch 237.3

com.apple.iokit.IOUSBHIDDriver 5.2.5

com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.5

com.apple.iokit.IOUSBMassStorageClass 3.5.1

com.apple.driver.AppleUSBMergeNub 5.5.5

com.apple.driver.AppleUSBComposite 5.2.5

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.5

com.apple.iokit.IOBDStorageFamily 1.7

com.apple.iokit.IODVDStorageFamily 1.7.1

com.apple.iokit.IOCDStorageFamily 1.7.1

com.apple.iokit.IOAHCISerialATAPI 2.5.1

com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.5

com.apple.iokit.IO80211Family 522.4

com.apple.iokit.IOFireWireFamily 4.5.5

com.apple.iokit.IOAHCIFamily 2.3.1

com.apple.iokit.IOUSBUserClient 5.5.5

com.apple.iokit.IONetworkingFamily 3.0

com.apple.driver.NVSMU 2.2.9

com.apple.iokit.IOUSBFamily 5.5.5

com.apple.driver.AppleEFIRuntime 1.7

com.apple.iokit.IOHIDFamily 1.8.1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 220.2

com.apple.kext.AppleMatch 1.0.0d1

com.apple.security.TMSafetyNet 7

com.apple.driver.DiskImages 345

com.apple.iokit.IOStorageFamily 1.8

com.apple.driver.AppleKeyStore 28.21

com.apple.driver.AppleACPIPlatform 1.7

com.apple.iokit.IOPCIFamily 2.7.3

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.corecrypto 1.0

Model: MacBookPro5,5, BootROM MBP55.00AC.B03, 2 processors, Intel Core 2 Duo, 2.53 GHz, 4 GB, SMC 1.47f2

Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x31364A53463235363634485A2D3147314631

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.16)

Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports

Network Service: AirPort, AirPort, en1

Serial ATA Device: FUJITSU MJA2250BH FFS G1, 250.06 GB

Serial ATA Device: HL-DT-ST DVDRW GS23N

USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24400000 / 2

USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26500000 / 2

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0x04600000 / 3

USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x04500000 / 2

USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06100000 / 2

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06110000 / 3

iMac, OS X Mountain Lion (10.8.1)

Posted on Mar 20, 2013 10:53 AM

20 replies

missrossbach Author

Level 1

0 points

Apr 7, 2013 8:28 AM in response to SwankPeRFection

Well, certainly I do apologize for not being methodical enough but as I stated before, I know enough just to be dangerous. Translation: I am not a tech guru, nor can I read the system log and know what it says. My methods trying to fix this blasted thing because partially it was my lifeblood as an art teacher in a high school. I've transferred my files, but regardless...enough said.

The smartboard is an older model (I'm guessing 9-10 years) made by Smart Technologies. I don't have the connector in front of me (not at work) but it is a USB to 15 pin made by apple. I couldn't read the numbers on the connector and I will try and update that later. I may have a second one I can replace. I do move the machine from one room to another room which means disconnecting the machine from the smartboard to a freestanding projector. I leave the USB connection in the machine generally speaking and connect/disconnect the 15 pin end.

I don't have a copy of Windows to load in Bootcamp and at this point, it's either time for it to go to the Apple boys or let my tech guy deal with it.

I will try replacing the connector and if that doesn't do it, it's beyond my knowledge base then.

I thank everyone who has contributed to helping me solve the problem.

Apr 7, 2013 8:54 AM in response to SwankPeRFection

I disagree with the interpretation that this is related to SMB issues.

The backtrace show that the panic occurred deep in the system -- but in routines called by graphics extensions.

Backtrace (CPU 0), Frame : Return Address

0xffffff807d59b5b0 : 0xffffff8004c1d626

0xffffff807d59b620 : 0xffffff8004cb7e95

0xffffff807d59b7f0 : 0xffffff8004ccd4dd

0xffffff807d59b810 : 0xffffff7f855abe49

0xffffff807d59b9b0 : 0xffffff7f855a07f7

0xffffff807d59bbf0 : 0xffffff7f8534a387

0xffffff807d59bc60 : 0xffffff7f8533657b

0xffffff807d59bcd0 : 0xffffff7f853391b8

0xffffff807d59bd40 : 0xffffff7f85339343

0xffffff807d59bdb0 : 0xffffff7f85338db4

0xffffff807d59be10 : 0xffffff7f852ffc78

0xffffff807d59be50 : 0xffffff7f852fef63

0xffffff807d59be80 : 0xffffff7f852fe31e

0xffffff807d59bef0 : 0xffffff80050467a8

0xffffff807d59bf30 : 0xffffff80050452aa

0xffffff807d59bf80 : 0xffffff80050453d9

0xffffff807d59bfb0 : 0xffffff8004cb2977

Kernel Extensions in backtrace:

com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f852f1000->0xffffff7f85328fff

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f852a3000

com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f85334000->0xffffff7f85345fff

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f852f1000

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f852a3000

com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f85348 000->0xffffff7f85655fff

dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f852a3000

dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f85334000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f852f1000

BSD process name corresponding to current thread: kernel_task

The order of listing of loaded/unloaded extensions generally does not correlate with the cause of the problem.

I agree with Linc Davis that this is likely to be a Hardware (specifically a graphics Hardware) issue.

You should take your MacBook in for service, and if it no longer under warranty, the bill will be large.

Apr 7, 2013 9:42 AM in response to missrossbach

missrossbach wrote:

Well, certainly I do apologize for not being methodical enough but as I stated before, I know enough just to be dangerous. Translation: I am not a tech guru, nor can I read the system log and know what it says. My methods trying to fix this blasted thing because partially it was my lifeblood as an art teacher in a high school. I've transferred my files, but regardless...enough said.

The smartboard is an older model (I'm guessing 9-10 years) made by Smart Technologies. I don't have the connector in front of me (not at work) but it is a USB to 15 pin made by apple. I couldn't read the numbers on the connector and I will try and update that later. I may have a second one I can replace. I do move the machine from one room to another room which means disconnecting the machine from the smartboard to a freestanding projector. I leave the USB connection in the machine generally speaking and connect/disconnect the 15 pin end.

I don't have a copy of Windows to load in Bootcamp and at this point, it's either time for it to go to the Apple boys or let my tech guy deal with it.

I will try replacing the connector and if that doesn't do it, it's beyond my knowledge base then.

I thank everyone who has contributed to helping me solve the problem.

There's no such thing as USB to 15 pin. Are you sure your cable isn't a MiniDisplay one? Even so, if this smartboard is used for showing what's on the screen of your laptop, then make it a habit of turning off that display selection within OSX and then unplugging the adapter from your laptop. OSX does not do well (they've improved it, but it still doesn't handle stuff well enough) when you unplug in-use hardware from it. It doesn't know how to properly handle the safe unloading of the module while also transfering all the work back to whatever else natively replaces that. Since it's a display type setup, it shouldn't be causing you this issue, but the fact that it only started to happen after you updated to 10.8.3 makes me think it IS NOT a hardware issue. This is software stuff and no different than what happens to me when I unplug my serial connection without first closing out of the programs using it.

Yes, you might not have had to do it in the past, but if Apple overlooked something in 10.8.3 and this is an OS bug (which you'll probably need to report on the Feedback pages), you may have to change your process of connecting/disconnecting the smartboard. If that is now truly the only thing that's causing this crash, then you have your answer. The system is on or was last on (maybe it's sleeping when you disconnect it) pushing data to this smartboard and when you just yank the connection out, it doesn't know how to handle the change. When that happens, the OS crashes. It's pretty simple and there's nothing magical about what's going on. Figure out another way to disconnect from that board. Perhaps something along the lines of set you display back to just your LCD screen on the laptop effectively turning off the mirroing on the smartboard and then unplug cables. Start by making that display change and then unplug the 15 pin from the dongle on your laptop (like you have been all this time). See if this is doesn't cause a crash. If it does, then change it to unplugging the dongle from your laptop first and then that from the 15 pin cable. The trick is figuring out a way to SAFELY unplug that external display from your system without causing this crash.

As a side note, if and that's a big IF, you ever had to load any drivers or anything for this smartboard to work properly, then you need to go and try and get the newest drivers for it. I looked on SmartTech's website and they definitely do have drivers and software for their stuff, but I don't know if they had this 9-10 years ago for the model you specifically have or if it can be treated as a simple external display. Either way, check into that as well. But, and most importantly, if there is software on your Mac that somehow controls this board, QUIT that app(s) before you unplug the device. That can also be added to your list of things to try.

Good luck and let us know what happens please.

missrossbach Author

Level 1

0 points

Apr 7, 2013 9:52 AM in response to SwankPeRFection

You're correct on the dongle (truth be told, I thought that was a slang)...it is not a USB connection. I was incorrect.

And I have been sending the reports in every time. I'll attempt some of this later in the week.

Apr 7, 2013 10:03 AM in response to missrossbach

No, you missed what I meant by reporting it. The crash reports won't tell Apple much and they'll probably write it off as a normal crash with some kind of graphics hardware glitch like others on here have done.

You need to work on finding out a way to keep the crash from happening now that we know it's somehow related to the smartboard connection. Maybe try a normal external monitor hooked up to your dongle and see if disconnecting it the same way you do the smartboard causes the same crash. If it does, then you know it's just a glitch with external display connections... heck, maybe it's specific to that model dongle you have, who knows. If it ends up being specific to the smartboard then, you need to figure out if there is a safe way to disconnect it and once you have all your findings put together, go to Apple - Feedback and report it there under the MacBook Pro section. Be specific with model numbers of the smartboard, the model number of the dongle you're using, OSX version, procedure you're doing to disconnect and cause the crash as well as the other procedure you come up with disconnecting without causing a crash and the full crash report (copy/paste it). That is what Apple will need to do their job and correct the issue. You gotta spoon feed those folks quite a bit.

Damsel in Distress Again.