Previous 1 47 48 49 50 51 Next 752 Replies Latest reply: Jul 20, 2015 3:43 PM by Rembert Oldenboom Go to original post Branched to a new discussion.
  • Grant Bennet-Alder Level 9 (55,325 points)

    That certainly looks like a graphics failure.


    Can you get access to an Apple Store instead of the AASP you used before? They sometimes give the Genius Bar guys more room to make judgement calls about when repairs are appropriate. If you can, take copies of those Kernel panic reports.


    Apple Authorized Service Providers (AASP) have to follow tighter guidelines to make sure they are not just inventing repairs to enrich themselves.

  • Peter Lorraine Level 1 (15 points)

    I managed to get approval from my credit card extended warrantee to cover the repair.  Just hope replacing the logic board fixes this.  Cost isn't so much an issue now as getting a reliable fix.  Grant - thanks for taking the time to help here.



  • caseysue Level 1 (0 points)

    After over a year dealing with this kernel panic problem, I have finally narrowed it down to temperature. As long as I use my computer when it's cool (meaning has been turned off for a while, I have no problem. The minute it gets warmed up, bye bye video screen, CRASH!


    I went to Best Buy and bought myself a Samaung Chromebook for $179, and a Toshiba laptop with a 17" screen for $350 (both included two years Geek Squad service). I LOVE the chromebook by the way.


    I use my MacBook Pro for my important detail work, and I save all of my files in the 500 GB of Google Drive I got free with my Chromebook purchase. So, everything's in the cloud as well as backed up on a couple hard drives. When I need to Skype or use the internet, I use the Toshiba. When I need to edit my files, I use Google Docs on the the Chromebook and save everything back to Google Drive.


    I use my Mac for PowerPoint and Dreamweaver, and other Mac apps that I'm used to. Once those are PDFs, to the cloud they go. In the mean time, I'm learning PC and Chromebook, and find little need for the Mac anymore.


    Too bad. I've used Mac since 1985, exclusively.

  • jjjohnson Level 1 (0 points)

    This will be the last Apple product I buy, the qualiy just isn't there anymore, I remember  buying Apple products in the 80's and 90's and they would last for 10-15 years without any issues. That was always the reason why you bought Apple, because "they use top quality hardware".  That all has changed I have a mid 2010 Mac Book Pro and it has had nothing but quality issues.  Every Apple product I have bought in the last 8 years has had issues, from my iMac, to my Mac Mini and now my Mac Book pro. I took my Mac Book Pro in today and in big red letters after running the video test it said "Test FAILED, replace MBL".


    I used my computer for coding and until recently haven't used any graphics intensive stuff so the "extended warrenty" ran out in April and I only found this issue happening maybe 2 months ago after I began using it for more than coding (using google street view to look at houses to buy).  The person at the genius bar explained that they couldn't replace the logic board because it was passed the 3 year date.  They wanted 527$ to replace the motherboard on a 3 1/2 year old computer which I paid 2700$ for.  To date I have experienced all these problems with this computer:


    Yellowing around the screen edges



    Intermittent sleeping



    Video card kernel panics


  • Peter Lorraine Level 1 (15 points)

    As an update on the mid 2012 MBP Retina which had been having GPU panics -

    we had the logic/gpu board replaced at a cost of $600 or so including labor on Monday.  Over the past weekend the system was panicking every few minutes, HDMI output was off and on, and boots occasionally failed.  The system would occassionally settle down for an hour or two.  Since the replacement, these problems have not recurred.  One day is a small interval but this is the longest stretch without a panic in the last month.  I'm optimistic we've caught this.


    I spoke with the authorized service shop that did the repair, they said they have seen very few MBP retinas in for service and none with this issue.  I'm not sure how common the problem is but this was a first for them. 


    As an interesting note, the repair was 600 including labor.  They said the core exchange fee on the board was 700 - so the repair would have been 1300 without turning in the old logic board.  For a bad spill or broken board, the old board cannot be returned.  Also, my credit card had extended the warrantee by another year so I'm covered on this repair.  Next time, I will definitely purchase apple care.



  • Grant Bennet-Alder Level 9 (55,325 points)



    If yours is a MacBook Pro 6,2, the Video card kernel panics are likely related to the TS4088 issue. If you have documented complaints on record with AppleCare, you should either call them or re-visit the store and press your case for this being a pre-exiting warranty issue that was never fixed properly.


    No one gets penalized for authorizing the repair, they just need to be convinced they should spend Apple's money outside of the standard guidelines. Apple wants you to be a happy customer.

  • FrenchToast Level 3 (645 points)

    I don't know if my contribution to come is going your way or not, but I own a 2006, 1.83GHz MacBook Pro, one of the very first rigged with an Intel chip, and aside from a faulty SuperDrive AppleCare replaced without blinking and a logic board that got replaced by them a few months later (that was sometime in '08), it's still working just fine.


    Granted, I recently swapped the original 80Gb hard drive for a 128Gb SSD (boy, did THAT change my life!), but I'm still stuck with a grand max of 2Gb of RAM, and I can still do pretty much everything with that MBP, even run Windows 8.1 in VirtualBox.


    My two cents. Oh, and a Happy New Year to all you techies and geeks!

  • ryan202 Level 1 (0 points)

    Thanks Peter Lorraine for mentioning the credit card extended warranty. I have the EXACT same issues as you and am out of the base 1 year warranty (I never had any issues with my last several MBPs). I have the same work order cost $600 with the logic board and labour and tax that I received from the apple store. I called Visa and they're sending me all the forms I need to fill in for the claim.. thanks again!

  • Peter Lorraine Level 1 (15 points)

    We've gone a week since having the logic/gpu board replaced with no panics under heavy usage.  Hopefully this is resolved.

  • meloman Level 1 (0 points)

    better late than never... or maybe not...


    anyway, same problems as everyone here. Same model year 15" MBP w/ the Nvidia GT330m dGPU (or MBP 6,2). I only recently found out about this in the last couple of months though when I started using FCP X and Motion 5 again. I can't get any work done since these programs would inevitably trigger a KP without fail. But, I do remember a time when I was able to work on these programs just fine. No crashes or anything. I don't know what changed or if my dGPU is getting too old. Just kidding. Computers don't age. Or do they?


    Anyway, I took my MBP to the Apple Store a few weeks ago and it failed the Video Systems Test. The Apple Genuis then quoted me a price to have the logic board replaced. But, since I couldn't afford it, I walked out of the store with my this bad news and a bad feeling in the pit of my tummy. Since then, I've tried everything I could do. I did a clean install of Mavericks. Same thing! I went back to Mountain Lion! Same thing!!!


    And, then I went back to Snow Leopard and it was more stable. I say more stable because I did have one crash 45 minutes into playing COD: Modern Warfare, which is a very intense, graphically-oriented, 3D-driven, FPS game that would surely make any dGPU stretch its legs. anyway, I had the same usual symptom of the video screen going blank, backlit keys fully lit, the sound of audio in constant loop and even tho the computer was still on, it was unresponsive. A hard reboot was the only solution, in which it then presented me the NVRM KP Crash error report thing people here have been posting about. Anyway, after reporting the crash to Apple, I then fired up COD:MW again to see if I could replicate the crash and I played maybe 30 minutes more of gameplay before giving up not because it crash, but because I just wanted to stop playing the game.



    I have been running snow leopard for 4 days now and it is vastly different experience than Mountain Lion or Mavericks.


    Other apps I've tested and used by making projects solely for the purpose of recreating the crash are Final Cut Express 4, Soundtrack 1.5 and Garageband '11. Of course, I can't test FCP X or even Motion 5 in Snow Leopard b/c they aren't compatible. But, the aforemention programs were stable and didn't cause my computer to crash.


    The problem is that running Snow Leopard is not a real solution for me, even if it's a superficial fix and/or real fix, I don't care since most of the apps I use aren't even compatible with it.


    I also can't afford anything right now to send my logic board to be replaced since I already miss that window by a mile and a few moons.


    I just feel like Apple needs to fix this via Software patch, easiest for everyone, or Hardware fix by offering or stretching that window farther to include people like me who are late to our computer-logic-board funeral.


    Thank You!

  • Grant Bennet-Alder Level 9 (55,325 points)

    RE: Mitigation for Failed VST test


    If your Mac has been tested and failed the VST Test, it has not broken down from hard use or anything else, but has a Latent Defect that was there from its manufacture.


    Reverting to 10.6.8 works because each version of Mac OS X  uses the graphics chip a little differently. This is also the reason the problem gets worse with age -- as users upgrade their Mac OS X, it beats on the graphics chip harder and causes the Latent Defect to show up more and more.


    On another thread on this subject, several users have suggested two different novel approaches for MacBook Pro 6,2 2010 that have failed the VST test and been refused free repair from Apple:


    • One is to have a re-balling service work on the graphics chip on your motherboard, and once the graphics chip is removed, replace it with a new part before re-soldering. This can cost around US$200 complete.


    • another is to make a setting change in  "/System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphi cs.framework/Resources/" and change a setting in the "Configurtion.plist" file to force all graphics writes to main store. IF your Mac has FAILED the VST Test, this seems to improve stability.


    Screen Shot 2014-04-26 at 12.12.19 PM.png


    GPU Panic - OSX 10.9 Mavericks - Macbook PRO 6,2



  • bikegreeny Level 1 (0 points)

    My 17" Mid-2010 MBP's logic board (with NVIDIA GPU) was replaced for $free in 2012 after a considerable effort proving this was a hardware fault that software could not sidestep to get around. It's been running OK ever since switching happlily between on-board Intel and NVIDIA GPUs depending on the app.


    Now a complete segway: My Dell Inspiron 9400 had a NVIDIA GeForce 7800 problem. Actually 3 cards in all had been used over time. Then I stumbled on the root cause and a solution. It turns out that NVIDIA had a GPU solder problem whereby thermal stress caused some joints to become intermittent or open over time. Made sense, the more thermal stress, the sooner the card failed.


    While investigating a bizarre solution, I found NVIDIA's class action settlement at but unfortunately it's too late for both individuals and affected computer manufacturers to take action now.


    Nevertheless, the bizarre solution was to bake the graphics card for 10 minutes at 195C (remove heat sinks and plastics then stand it up on screws with al-foil under it). Those intermittent connections were made OK again by the "plasticity" of the hot solder remaking the bond. Guess what, it works! Make sure that you use a good heat sink compound like Arctic Silver 5 when you put it back together.


    While I haven't had this confirmed by Apple Technicians here in Australia, my hypothesis is that this same bizarre graphics card baking solution will work just fine with MBP NVIDIA graphics cards as well.


    Apparently, the replacement Logic Boards are all "reconditioned" in the sense that offending connections have been resoldered with the proper solder that does not suffer from thermal stress fractures.


    Good luck all as the likelyhood of Apple still coming to the $free replacement logic board party is growing more remote by each month that passes. What can you lose by trying yourself, provided you have the skill to both assemble and dissassemble your beloved MBP?

  • Grant Bennet-Alder Level 9 (55,325 points)

    Yes, BUT...


    The problem with a certain batch of MacBook Pro 6,2 is NOT caused by bad solder, it is caused by a Latent Defect in the Graphics chip. If your MacBook Pro 6,2 has failed the VST test, it will NOT be made right by baking or commercial re-balling -- unless the graphics chip with the Latent Defect is replaced as part of the Repair.


    Baking may be an option for Owners of MacBook Pro 6,2 that PASSED the VST test, or other models of MacBook Pro that are behaving badly. If your MacBook Pro is already so bad you cannot use it, you have nothing to lose by baking it, and the price is right.

  • PJCamacho Level 1 (0 points)

    I have a similar issue as well.  I noticed this computer started doing that early on while the original warranty still covered it.  Now that my 2010 MBP i7 is out of warranty, I am stuck with the same problem again.  Here's one of my error reports:


    Anonymous UUID:       249D127D-5FDE-E780-2820-71F6B3D89EEB


    Mon Aug 25 07:51:24 2014


    *** Panic Report ***

    panic(cpu 2 caller 0xffffff7f8956ef63): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff8122c4d000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.7.19/src/Apple MuxControl/kext/GPUPanic.cpp:127

    Backtrace (CPU 2), Frame : Return Address

    0xffffff81119ab0f0 : 0xffffff800693b731

    0xffffff81119ab170 : 0xffffff7f8956ef63

    0xffffff81119ab250 : 0xffffff7f874d2b9f

    0xffffff81119ab310 : 0xffffff7f8759c18e

    0xffffff81119ab350 : 0xffffff7f8759c1fe

    0xffffff81119ab3c0 : 0xffffff7f8781b056

    0xffffff81119ab4f0 : 0xffffff7f875bf82d

    0xffffff81119ab510 : 0xffffff7f874d95f1

    0xffffff81119ab5c0 : 0xffffff7f874d70fc

    0xffffff81119ab7c0 : 0xffffff7f874d807a

    0xffffff81119ab8a0 : 0xffffff7f88b4c446

    0xffffff81119ab8e0 : 0xffffff7f88b5bdff

    0xffffff81119ab900 : 0xffffff7f88b8a493

    0xffffff81119ab930 : 0xffffff7f88b8a4ed

    0xffffff81119ab970 : 0xffffff7f88b61a1f

    0xffffff81119ab9c0 : 0xffffff7f88b2c027

    0xffffff81119aba60 : 0xffffff7f88b27da1

    0xffffff81119aba90 : 0xffffff7f88b25873

    0xffffff81119abad0 : 0xffffff8006f009ac

    0xffffff81119abb60 : 0xffffff8006f02ad3

    0xffffff81119abbc0 : 0xffffff8006f00363

    0xffffff81119abd00 : 0xffffff80069eae07

    0xffffff81119abe10 : 0xffffff800693f83c

    0xffffff81119abe40 : 0xffffff80069244e3

    0xffffff81119abe90 : 0xffffff8006934dcd

    0xffffff81119abf10 : 0xffffff8006a0aa62

    0xffffff81119abfb0 : 0xffffff8006a3b2f6

          Kernel Extensions in backtrace:

   [E18BB1A8-0FF4-3698-86F6-4DB9445DB7E2]@ 0xffffff7f89560000->0xffffff7f89573fff

                dependency:[35039829-9A90-3553-858A-79F8340E2 C2C]@0xffffff7f89558000

                dependency:[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xfffff f7f873b9000

                dependency:[021B9DF9-5931-3092-A611-47A1937BD3B4]@0xffffff 7f87124000

                dependency:[4557FEB1-E413-32E2-807E-DF6578DB647B]@0 xffffff7f8742b000

                dependency:[3D90F02A-E911-3551-9D6C-9939B4F5F9 4C]@0xffffff7f8955b000

   [796AE430-39FB-3255-8161-D52AFA28 EE2B]@0xffffff7f87482000->0xffffff7f876ebfff

                dependency:[021B9DF9-5931-3092-A611-47A1937BD3B4]@0xffffff 7f87124000

                dependency:[D4EFFD3C-9A10-383F-927E-9B9C81B705B0]@0xff ffff7f87472000

                dependency:[4557FEB1-E413-32E2-807E-DF6578DB647B]@0 xffffff7f8742b000

   [7FE40648-F15F-3E18-91E2-FDDDF4C DA355]@0xffffff7f876f6000->0xffffff7f8799ffff

                dependency:[796AE430-39FB-3255-8161-D52AFA 28EE2B]@0xffffff7f87482000

                dependency:[021B9DF9-5931-3092-A611-47A1937BD3B4]@0xffffff 7f87124000

   [D96AC2DB-2D20-3B56-BA08-82599CDC693A]@0xffffff7f88 b09000->0xffffff7f88bd6fff

                dependency:[021B9DF9-5931-3092-A611-47A1937BD3B4]@0xffffff 7f87124000

                dependency:[D4EFFD3C-9A10-383F-927E-9B9C81B705B0]@0xff ffff7f87472000

                dependency:[4557FEB1-E413-32E2-807E-DF6578DB647B]@0 xffffff7f8742b000

                dependency:[796AE430-39FB-3255-8161-D52AFA 28EE2B]@0xffffff7f87482000


    BSD process name corresponding to current thread: WindowServer


    Mac OS version:



    Kernel version:

    Darwin Kernel Version 14.0.0: Sat Aug  9 00:14:02 PDT 2014; root:xnu-2782.1.80~2/RELEASE_X86_64

    Kernel UUID: 0ECBDCDE-E469-3B8D-A6B8-E8B807F55FD5

    Kernel slide:     0x0000000006600000

    Kernel text base: 0xffffff8006800000

    __HIB  text base: 0xffffff8006700000

    System model name: MacBookPro6,2 (Mac-F22586C8)


    System uptime in nanoseconds: 1015267250836

    last loaded kext at 257349236979:     3.0.0 (addr 0xffffff7f89662000, size 385024)

    last unloaded kext at 244876024928:     656.4.1 (addr 0xffffff7f87cef000, size 65536)

    loaded kexts:     3.0.0     1.4     1.70     1.9.5d0     100.14.32     3.0     4.3.0b13     1     124     265.99     3.6.1     10.0.0     10.0.0     1.7.1     1.0.0     10.0.0     265.99     1.2.10     4.3.0b13     2.0.4d1     1.0.1     7.0.0     1     1     3.7.19     1.0.0     3.0.4d1     240.2     240.2     327.5     3.5.0     1.0.0d1     1.0.0d1     35     3.7.0     404     2.6.5     800.20.24     10.1.2b3     705.4.1     5.5.1     3.0.7     705.4.4     161.0.0     2.0     3.1     1.8     2.1     3.1     1.7     218.0.0     161     3     8     218.0.0     4.3.0b13     3.7.19     1.0     11     10.0.0     10.0.0     2.2.6     1.0.0     265.99     1.15     200.5     1.2.0     4.3.0b13     97     4.3.0b13     1.0.13d1     1.1.0     2.4.1     3.7.19     5.8.0d47     705.4.0     265.99     2.4.1     265.99     1.0.12d1     3.1.9     245.1     705.4.0     3.7.0     3.7.0     468     705.4.0     705.4.9     3.7.0     1.7     1.7.1     1.7.1     2.6.1     3.7.0     1.0.3b3     700.40     1.0.1b8     3.2     4.5.5     2.7.0     707.4.10     2.0     2.0     2.0.0     1.1     300.0     1.0.0d1     2     1.0.5     1.0     389     2.0     31     28.30     3.1     2.9     1.4     1.0     1     1

  • dcallagh521 Level 1 (0 points)

    Hey Grant, as I see you're doing a wonderful job of helping everyone out, is there any chance you could take a look at what I have? I've been going at it all day, and (hopefully) diagnosed it's something related to this thread. When I open up a few apps and get the CPU running faster, that's when the screen shuts off. I just can't seem to spot out anything you've highlighted here, and others have elsewhere. (note: I downloaded Avast Mac Security after this began happening. This may or may not have been a good idea, but I wouldn't think it'd be the cause.)


    Fingers crossed... Apologies for probably not commenting correctly on a thread like a rookie, and thanks in advance!



    Anonymous UUID:      7ECF5524-E585-8F9D-4EA2-19816775E33A



    Fri Jan 16 13:57:41 2015



    *** Panic Report ***

    panic(cpu 0 caller 0xffffff7f88052f63): "GPU Panic: [<None>] 5 0 a0 d9 9 8 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x104000000 0xffffff81167b3000 0x0e7150a2, D0, P2/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.7.21/src/Apple MuxControl/kext/GPUPanic.cpp:127

    Backtrace (CPU 0), Frame : Return Address

    0xffffff81132f32d0 : 0xffffff800553a811

    0xffffff81132f3350 : 0xffffff7f88052f63

    0xffffff81132f3430 : 0xffffff7f86099d28

    0xffffff81132f34f0 : 0xffffff7f861641b6

    0xffffff81132f3530 : 0xffffff7f86164226

    0xffffff81132f35a0 : 0xffffff7f8639b656

    0xffffff81132f3610 : 0xffffff7f86186db1

    0xffffff81132f3630 : 0xffffff7f860a07e1

    0xffffff81132f36e0 : 0xffffff7f8609e2ec

    0xffffff81132f38e0 : 0xffffff7f8609fc3b

    0xffffff81132f39b0 : 0xffffff7f8768ee2b

    0xffffff81132f3a80 : 0xffffff7f8760022c

    0xffffff81132f3ab0 : 0xffffff7f875fec0a

    0xffffff81132f3b30 : 0xffffff8005b01c92

    0xffffff81132f3b60 : 0xffffff8005b02859

    0xffffff81132f3bc0 : 0xffffff8005b00003

    0xffffff81132f3d00 : 0xffffff80055ea517

    0xffffff81132f3e10 : 0xffffff800553e91c

    0xffffff81132f3e40 : 0xffffff80055235a3

    0xffffff81132f3e90 : 0xffffff8005533e8d

    0xffffff81132f3f10 : 0xffffff800560a142

    0xffffff81132f3fb0 : 0xffffff800563ac66

          Kernel Extensions in backtrace:

  [32B7E2DE-1F9D-3555-B687-7A76A62B81D2]@ 0xffffff7f88044000->0xffffff7f88057fff

                dependency:[62689710-EEA7-307A-AC83-B8F25DA88 A6A]@0xffffff7f8803c000

                dependency:[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xfffff f7f869c2000

                dependency:[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f85d24000

                dependency:[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f85fec000

                dependency:[0183904C-6A16-32C4-9405-EEFD7F820B 02]@0xffffff7f8803f000

  [20DDCE61-E3EC-3CC1-8B79-170CEF2B603 A]@0xffffff7f875ec000->0xffffff7f87658fff

                dependency:[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f85d24000

                dependency:[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f85fec000

  [53CC0E05-7382-336C-8239-AE884D6CA71A]@ 0xffffff7f86049000->0xffffff7f862befff

                dependency:[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f85d24000

                dependency:[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f86033000

                dependency:[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f85fec000

                dependency:[4700601D-3FEB-3B86-B2BA-8D71AF84D1 C4]@0xffffff7f86043000

  [DC43029D-568A-3B7C-976B-E922C17F5143 ]@0xffffff7f862ca000->0xffffff7f86477fff

                dependency:[53CC0E05-7382-336C-8239-AE884D6CA71A ]@0xffffff7f86049000

                dependency:[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f85d24000

  [26D2EC64-4AF8-32C8-BF74-5B1E80772FAA]@0xffffff7f8766700 0->0xffffff7f876fcfff

                dependency:[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff 7f85d24000

                dependency:[F4738C55-B507-3627-A9CA-3D29A5230A03]@0xff ffff7f86033000

                dependency:[53CC0E05-7382-336C-8239-AE884D6CA71A ]@0xffffff7f86049000

                dependency:[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0 xffffff7f85fec000

                dependency:[20DDCE61-E3EC-3CC1-8B79-170CEF2B603 A]@0xffffff7f875ec000



    BSD process name corresponding to current thread: WindowServer



    Mac OS version:




    Kernel version:

    Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64

    Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61

    Kernel slide:    0x0000000005200000

    Kernel text base: 0xffffff8005400000

    __HIB  text base: 0xffffff8005300000

    System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)



    System uptime in nanoseconds: 1088360149511

    last loaded kext at 13586519182: com.avast.AvastFileShield 2.1.0 (addr 0xffffff7f88154000, size 40960)

    last unloaded kext at 131205673723: 1.0.3b3 (addr 0xffffff7f86a44000, size 28672)

    loaded kexts:

    com.avast.AvastFileShield 2.1.0         ----- Installed afterwards

    com.avast.PacketForwarder 2.0 1.70 1.9.5d0 2.1.0d1 100.14.37 1.0.0 3.0 4.3.1f2 124 1 267.0 267.0 3.6.1 10.0.0 1.0.1 10.0.0 7.0.0 1 1.2.10 2.0.4d1 4.3.1f2 1.7.3 10.0.0 1 3.7.21 1.0.0 2.0.2 240.2 240.2 1.0.0d1 1.0.0d1 35 404 705.4.1 2.6.5 1.6.5 901.19.10 3.0.7 705.4.14 705.4.14 161.0.0 3.1 2.0 1.8 2.1 3.1 1.7 218.0.0 161 3 8 218.0.0 1.0 11 267.0 1.15 200.6 1.2.0 10.0.0 10.0.0 97 1.0.0 1.0.13d1 267.0 267.0 4.3.1f2 4.3.1f2 1.0.12d1 705.4.0 3.1.9 156.4 3.7.21 1.1.0 2.4.1 3.7.21 2.4.1 5.8.0d49 3.7.0 245.2 705.4.0 705.4.0 705.4.9 4.0.6 4.0.6 2.0.2 471 3.1.7 4.2.1 700.52 1.0.1b8 3.2 2.7.0 705.4.14 2.0 2.0 2.0.0 1.1 300.0 1.0.0d1 2 1.0.5 1.0 389.1 2.0 31 28.30 3.1 2.9 1.4 1.0 1 1

    Model: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.3 GHz, 8 GB, SMC 2.3f36

    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB

    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020

    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020

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

    Bluetooth: Version 4.3.1f2 15015, 3 services, 19 devices, 1 incoming serial ports

    Network Service: Wi-Fi, AirPort, en0

    Serial ATA Device: APPLE SSD SD256E, 251 GB

    USB Device: Hub

    USB Device: FaceTime HD Camera (Built-in)

    USB Device: Hub

    USB Device: Hub

    USB Device: Apple Internal Keyboard / Trackpad

    USB Device: BRCM20702 Hub

    USB Device: Bluetooth USB Host Controller

    Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4