Previous 1 2 Next 19 Replies Latest reply: Apr 28, 2013 1:51 PM by SwankPeRFection Go to original post
  • marcel23 Level 1 (0 points)

    You make a good point. Only issue I have is the apple store is not that close to me.
    Im convinced it's a software issue though, what else could cause this type of problem?
    Also, do you know if they suggest the issue is caused by something that is out of the 90 day warranty on the parts they replaced, if I have to pay for it or is it their problem that the issue isn't resolved? No matter what the cause it


    I will be going back in sometime this week hopefully.

  • marcel23 Level 1 (0 points)

    Here is a report after it crashing again!
    Hope someone can find something in this, I can make sense of these reports.



    Interval Since Last Panic Report:  56023 sec

    Panics Since Last Report:          1

    Anonymous UUID:                    7F0C089F-DBC6-BABE-7E87-941AA3508354

    Sat Apr 27 19:30:13 2013

    panic(cpu 6 caller 0xffffff80268b7e95): Kernel trap at 0xffffff7fa865f63a, type 14=page fault, registers:

    CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000002924a000, CR4: 0x00000000000606e0

    RAX: 0x0000000000000000, RBX: 0xffffff80336c8400, RCX: 0x0000000000000000, RDX: 0x0000000000000000

    RSP: 0xffffff80a592be50, RBP: 0xffffff80a592be50, RSI: 0x0000000000000000, RDI: 0xffffff80336c8400

    R8:  0xffffff80a592be70, R9:  0xffffff809a0465a8, R10: 0xffffffffffffff01, R11: 0x0000000000000000

    R12: 0x0000000000000000, R13: 0xffffff8033048400, R14: 0xffffff80336a4600, R15: 0xffffff7fa865f636

    RFL: 0x0000000000010246, RIP: 0xffffff7fa865f63a, CS:  0x0000000000000008, SS:  0x0000000000000010

    Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x6

    Backtrace (CPU 6), Frame : Return Address

    0xffffff80a592baf0 : 0xffffff802681d626

    0xffffff80a592bb60 : 0xffffff80268b7e95

    0xffffff80a592bd30 : 0xffffff80268cd4dd

    0xffffff80a592bd50 : 0xffffff7fa865f63a

    0xffffff80a592be50 : 0xffffff7fa86b37ed

    0xffffff80a592bea0 : 0xffffff7fa865ae04

    0xffffff80a592bec0 : 0xffffff7fa865a815

    0xffffff80a592bef0 : 0xffffff8026c467a8

    0xffffff80a592bf30 : 0xffffff8026c452aa

    0xffffff80a592bf80 : 0xffffff8026c453d9

    0xffffff80a592bfb0 : 0xffffff80268b2977

          Kernel Extensions in backtrace:

   [8CAD17E4-8359-3015-BCFC-F1964357CBFE ]@0xffffff7fa8654000->0xffffff7fa869efff

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6e66000

                dependency:[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa73cf000

                dependency:[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa738c000

   [1DDF899D-B472-36DF-A08D-365D3221F6CE]@0xf fffff7fa86aa000->0xffffff7fa8a60fff

                dependency:[8CAD17E4-8359-3015-BCFC-F1964357CBFE ]@0xffffff7fa8654000

                dependency:[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7fa6e66000

                dependency:[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7fa73cf000

                dependency:[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7fa738c000

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:


    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:     0x0000000026600000

    Kernel text base: 0xffffff8026800000

    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)

    System uptime in nanoseconds: 3622704105602

    last loaded kext at 31311211634: 1.9.5d0 (addr 0xffffff7fa832c000, size 36864)

    last unloaded kext at 236706969634:       5.2.5 (addr 0xffffff7fa7144000, size 65536)

    loaded kexts:  1.9.5d0        4.1.3f3      1.60   100.12.87    122       2.3.7fc4    3.0       8.1.0  1.0.0d1        3.5.10   8.1.0       2.3.7fc4   7.0.0     3.3.0  1.0.6        3.0.3d1       1.1.11   1.0.0        1.0.0      4.1.3f3        8.1.0       1.6.0        3.3.0    2.0.3d0      237.1     237.1      320.15     1.0.0d1 1.0.0d1     34      3.5.5     404      2.3.1    5.5.5      1.4.0       614.20.16    4.9.6    3.6.0b1  2.5.1   5.5.0  1.7       161.0.0       1.5       1.7      1.8    1.9    1.7      1.6     196.0.0       4.0.39   2   196.0.0  10.0.6     2.3.7fc4   1.8.9fc11    1.6 1.0       86.0.4       4.1.3f3     30.14        8.1.0       8.1.0  1.0.11d0   1.0.11d0 1.0.0 4.1.3f3     2.3.7fc4     2.3.7fc4 5.3.0d51   3.3.0   1.0.4   2.3.7        2.3.7       3.1.4d2    2.2.5    1.8.9        1.8.9 1.2.6     237.3  5.2.5       5.5.5      5.2.5  3.5.5       1.7      1.7.1       1.7.1       2.5.1   3.5.5    1.6.3     2.2.6 5.5.5   522.4        4.5.5 1.0.2b1      3.0    2.3.1     5.5.5        1.7     1.8.1   1.1      220.2       1.0.0d1  7     345 1.8  28.21      1.7     2.7.3    1.4        1.0

    Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2 GHz, 4 GB, SMC 1.69f3

    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB

    Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB

    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020

    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020

    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (

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

    Network Service: AirPort, AirPort, en1

    Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB

    Serial ATA Device: OPTIARC DVD RW AD-5970H

    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfa100000 / 3

    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0245, 0xfa120000 / 5

    USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4

    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 6

    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2

    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2

    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3

  • SwankPeRFection Level 4 (1,435 points)

    Look, you can try backing up all your data and then wiping the OS and reintalling just that and don't put anything back on it until you see if it crashes again or not.  That will tell you if it's 3rd party apps or personalized settings doing it.  But chances are good that it's probably hardware again.


    Sure, they can turn around and blame something else like memory or whatnot, but the bottom line is... it's their problem they misdiagnosed the initial problem or misrepaired the initial problem.  The thing is, you have to treat this as black and white (even though in the computer diagnosis world it's not that simple).  The fact is, ALL Apple techs misdiagnose stuff as "bad logic board".  It's such a routine diagnosis that I have no doubt it's the #1 replaced item in a Mac and Apple makes a ton of money off people out of warranty who pay those repair prices.


    The fact still remains that you took it in with these issues.  They misdiagnosed/misrepaired it, the issues continued.  Basically that to me means that you paid for nothing.  Nothing was fixed, so even if they say it's now something else, why should you have to pay for them to keep playing the guessing game.  That's the idea that you're going to want to plant in their heads.  They screwed up, problem continues, they have to fix it on their dime now.  It's really not that difficult, but it all depends on two factors... the person you'll be dealing with and the type of person that you are.  (i.e. will they take you seriously and be concerned enough to fix it your way to save themselves issues or keep putting you off)

  • marcel23 Level 1 (0 points)

    I agree with you completely. I'm just too use to fixing PCs myself all the time. This is my first mac i've had for two years and im not all that familiar with its issues. I'll be taking it back soon, again. Such an inconvenience.
    You've been great help, thanks for the direction.

  • SwankPeRFection Level 4 (1,435 points)

    You're welcome.  I know, I too wish Apple would do more to allow us the end users who work in the industry to do our own hardware repair with OEM hardware, but we can't even easily get our hands on replacement batteries, let alone reliable logic boards.  If Apple has anything to improve upon, it's this.  They need to take a note out of Dell's book and allow us to call in warranty fixes and offer to send either a tech/parts onsite (for both tower systems and laptops) or just parts.  Dell does this all the time and whenever I have something that fails that I show proper diagnostic proof that a part is bad, all I have to do is just ask for the part.  They sent that, I replace it and send back the old part.  Super simple for me, super simple for them (because now they don't have to pay anyone else for their labor) and I get my system fixed correctly and by someone who I trust (i.e. ME!).  It's so much soother of an interaction when a company doesn't make you run around to get things done.  I also hate how they won't even allow people in IT to take their certification tests and even then allow them to order parts for replacement.  You have to work for either an authorized repair center or a large campus who's paid them for self-support program.  That's BS!  Apple ***** in the support area if you ask me.  Even their phone support reps blow.  They're idiots and cannot fix anything and they aren't even aware of half the issues out there that arise.  A good example of this is when the new autopoweroff setting (i.e. hibernation) was introduced in November of 2012 and people start running into it.  I called in a week after the update was released about this new behavior and the nuances with it.  It took them 3 months even to get to the point where they understood the issues.  Then it took them another month or two to come out with an update that provided a slight change to the behavior to fix the changing state when unplugging from power (inherently negating the hibernation status they were entering).  That wasn't fixed until 10.8.3 came out a whole 4-5 months after the initial change.  It's amazing to me that it takes them that long to listen and understand the problems.  What's worse, it took a video for them to realize what I was trying to say when I was basically describing it just as it was in the video.  I tell you, they're not the brightest crayons in the box by any stretch of the imagination.

Previous 1 2 Next