appleaddictuser

Q: my Error Macbook Pro Very Slow Loading Bar, Kernel_task error, Trackpad Lagging

hy sorry my english bad..

 

I have searched google but could not find a solution..i use macbook pro late 2011 13inch 2,4ghz core i5 standard specification

why my macbook pro lagging trackpad, kernel task error and very slow loading bar sttartup but this problem does not apply in safe mode, in safe mode all normal working

steps have I done:

-change harddisk

-change sata harddisk

-change battery

-change trackpad and cable trackpad

-change OS 10.6 , 10.7 10.10 , 10.11

-change model identfier via

 

and problen not solved my macbook very very slow loading bar (It also occurred when I booted Through flashdisk and in setup mode in OSX ulities like a kernel task error very lagging trackpad) sometimes the boot sometimes can not boot and if i edit the model identifier that works but when booting from flash it for a long time

 

is there a solution that is more useful ? i very confused


thanksss


MacBook Pro, OS X El Capitan (10.11.5), null

Posted on Jul 2, 2016 11:06 AM

Close

Q: my Error Macbook Pro Very Slow Loading Bar, Kernel_task error, Trackpad Lagging

  • All replies
  • Helpful answers

  • by Esquared,

    Esquared Esquared Jul 2, 2016 11:08 AM in response to appleaddictuser
    Level 6 (8,410 points)
    Mac OS X
    Jul 2, 2016 11:08 AM in response to appleaddictuser

    If it doesn't happen in Safe Mode, it probably is a software issue. Can you post an Etrecheck report? http://etrecheck.com/

  • by Linc Davis,

    Linc Davis Linc Davis Jul 2, 2016 11:10 AM in response to appleaddictuser
    Level 10 (207,926 points)
    Applications
    Jul 2, 2016 11:10 AM in response to appleaddictuser

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

    Please launch the Console application in any one of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    In the Console window, select

              DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

    (not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

              View Show Log List

    from the menu bar.

    There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

    If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

    Please don’t post other kinds of diagnostic report.

    I know the report is long, maybe several hundred lines. Please post all of it anyway.

    When you post the report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

    If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

  • by appleaddictuser,

    appleaddictuser appleaddictuser Jul 2, 2016 8:55 PM in response to Esquared
    Level 1 (8 points)
    Notebooks
    Jul 2, 2016 8:55 PM in response to Esquared

    thanks for response.. this is my etrecheck

     

    EtreCheck version: 2.9.12 (265)

    Report generated 2016-07-02 20:35:39

    Download EtreCheck from https://etrecheck.com

    Runtime 20:02

    Performance: Poor

     

    Click the [Support] links for help with non-Apple products.

    Click the [Details] links for more information about that line.

     

    Problem: Computer is too slow

     

    Hardware Information:

        MacBook Pro (13-inch, Late 2011)

        [Technical Specifications] - [User Guide] - [Warranty & Service]

        MacBook Pro - model: MacBookPro8,1

        1 2.4 GHz Intel Core i5 CPU: 2-core

        4 GB RAM Upgradeable - [Instructions]

            BANK 0/DIMM0

                2 GB DDR3 1333 MHz ok

            BANK 1/DIMM0

                2 GB DDR3 1333 MHz ok

        Bluetooth: Old - Handoff/Airdrop2 not supported

        Wireless:  en1: 802.11 a/b/g/n

        Battery: Health = Normal - Cycle count = 933

     

    Video Information:

        Intel HD Graphics 3000

            Color LCD 1280 x 800

     

    System Software:

        OS X Yosemite 10.10.5 (14F27) - Time since boot: less than an hour

     

    Disk Information:

        APPLE HDD HTS545050A7E362 disk0 : (500.11 GB) (Rotational)

            EFI (disk0s1) <not mounted> : 210 MB

            Recovery HD (disk0s3) <not mounted>  [Recovery]: 650 MB

            Macintosh HD (disk1) / : 498.88 GB (486.47 GB free)

                Core Storage: disk0s2 499.25 GB Online

     

        MATSHITADVD-R   UJ-898   ()

     

    USB Information:

        Apple Computer, Inc. IR Receiver

        Apple Inc. FaceTime HD Camera (Built-in)

        Apple Inc. Apple Internal Keyboard / Trackpad

        Apple Inc. BRCM2070 Hub

            Apple Inc. Bluetooth USB Host Controller

     

    Thunderbolt Information:

        Apple Inc. thunderbolt_bus

     

    Gatekeeper:

        Mac App Store and identified developers

     

    System Launch Agents:

        [not loaded]    4 Apple tasks

        [loaded]    162 Apple tasks

        [running]    46 Apple tasks

     

    System Launch Daemons:

        [not loaded]    46 Apple tasks

        [loaded]    140 Apple tasks

        [running]    75 Apple tasks

     

     

    Other Apps:

        [loaded]    375 Apple tasks

        [running]    135 Apple tasks

     

    Internet Plug-ins:

        Default Browser: 600 - SDK 10.10 (2015-07-16)

        QuickTime Plugin: 7.7.3 (2015-07-22)

     

    3rd Party Preference Panes:

        None

     

    Time Machine:

        Time Machine not configured!

     

    Top Processes by CPU:

           374%    kernel_task

             3%    WindowServer

             2%    CoreServicesUIAgent

             1%    iconservicesd

             0%    QuickLookSatellite

     

    Top Processes by Memory:

        433 MB    kernel_task

        70 MB    mdworker(8)

        66 MB    mds_stores

        57 MB    WindowServer

        49 MB    Safari

     

    Virtual Memory Information:

        1.83 GB    Free RAM

        2.17 GB    Used RAM (1.00 GB Cached)

        0 B    Swap Used

     

    Diagnostics Information:

        Jul 2, 2016, 07:55:26 PM    Self test - passed

     

     

    whether there is an your feedback or an opinion?

  • by appleaddictuser,

    appleaddictuser appleaddictuser Jul 2, 2016 9:00 PM in response to Linc Davis
    Level 1 (8 points)
    Notebooks
    Jul 2, 2016 9:00 PM in response to Linc Davis

    hi! this is my report in paste bin

    http://pastebin.com/pNSQh63Q

     

    there is an your feedback or an opinion?

  • by Linc Davis,

    Linc Davis Linc Davis Jul 2, 2016 9:04 PM in response to appleaddictuser
    Level 10 (207,926 points)
    Applications
    Jul 2, 2016 9:04 PM in response to appleaddictuser

    1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

    The test works on OS X 10.8 ("Mountain Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

    Don't be put off by the complexity of these instructions. The procedure is easy to do right, but it's also easy to do wrong, so I've made the instructions very detailed. You do harder tasks with the computer all the time.

    2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

    3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

    You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

    In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.

    You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

    Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

    4. Here's a general summary of what you need to do, if you choose to proceed:

    ☞ Copy the text of a particular web page (not this one) to the Clipboard.

    ☞ Paste into the window of another application.

    ☞ Wait for the test to run. It usually takes a few minutes.

    ☞ Paste the results, which will have been copied automatically, back into a reply on this page.

    These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

    5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

    You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

    6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

    7. Load this linked web page (on the website "GitHub") in Safari. Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

    8. Launch the built-in Terminal application in any one of the following ways:

    ☞ Enter the first few letters of its name ("Terminal") into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

    9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

    If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

    If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

    10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

        Test started
            Part 1 of 4 done at: … sec
            …
            Part 4 of 4 done at: … sec
        The test results are on the Clipboard.
        Please close this window.

    The intervals between parts won't be exactly equal, but they give a rough indication of progress.

    Wait for the final message "Please close this window" to appear—again, usually within a few minutes. If you don't see that message within about 30 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something.

    In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

    11. When the test is complete, or if you stopped it manually, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

    At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

    If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

    12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

    If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

    13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

    14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

    15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

  • by appleaddictuser,

    appleaddictuser appleaddictuser Jul 2, 2016 9:18 PM in response to Linc Davis
    Level 1 (8 points)
    Notebooks
    Jul 2, 2016 9:18 PM in response to Linc Davis

    this my report again .. very thanks linc davis ..

    i hope my macbook got a solution

    http://pastebin.com/KWLWTRty

  • by Linc Davis,

    Linc Davis Linc Davis Jul 2, 2016 9:42 PM in response to appleaddictuser
    Level 10 (207,926 points)
    Applications
    Jul 2, 2016 9:42 PM in response to appleaddictuser

    The kernel is using excessive processor cycles. If "smcFanControl" is still installed, please remove it and see whether there's an improvement. Also see below:

    Reset the System Management Controller (SMC) on your Mac - Apple Support

  • by OGELTHORPE,

    OGELTHORPE OGELTHORPE Jul 3, 2016 3:39 AM in response to appleaddictuser
    Level 9 (52,147 points)
    Mac OS X
    Jul 3, 2016 3:39 AM in response to appleaddictuser

    Your MBP battery has seen much use so consider replacing it.

     

    More important is your HDD is suspect.  Boot into the recovery partition and open Disk Utility from the 4 option menu.  Run Disk Utility>First Aid>Repair.

     

    Ciao.

  • by appleaddictuser,

    appleaddictuser appleaddictuser Jul 3, 2016 2:10 PM in response to OGELTHORPE
    Level 1 (8 points)
    Notebooks
    Jul 3, 2016 2:10 PM in response to OGELTHORPE

    edited : my macbook error because while charging not lag, but its very unplug the MagSafe time lag .. impacting many cases like this in google but is this really damage logicboard?

     

     

    because I had to replace the battery but I have yet to replace dc board


    in apple test error 4SNS/1/40000001:VP0R-0.000 or 4SNS/1/40000001:YP0R-0.000 because I'm  forget "v" or "y"

  • by appleaddictuser,

    appleaddictuser appleaddictuser Jul 3, 2016 2:11 PM in response to Linc Davis
    Level 1 (8 points)
    Notebooks
    Jul 3, 2016 2:11 PM in response to Linc Davis

    edited : my macbook error because while charging not lag, but its very unplug the MagSafe time lag .. impacting many cases like this in google but is this really damage logicboard?

     

     

    because I had to replace the battery but I have yet to replace dc board


    in apple test error 4SNS/1/40000001:VP0R-0.000 or 4SNS/1/40000001:YP0R-0.000 because I'm  forget "v" or "y"

  • by Linc Davis,Solvedanswer

    Linc Davis Linc Davis Jul 3, 2016 9:09 PM in response to appleaddictuser
    Level 10 (207,926 points)
    Applications
    Jul 3, 2016 9:09 PM in response to appleaddictuser

    Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.

    Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

    If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

    Keep your confidential data secure during hardware repair.

    Apple recommends that you deauthorize a device in the iTunes Store before having it serviced.

    *An SSD doesn't need to be zeroed.

  • by OGELTHORPE,Helpful

    OGELTHORPE OGELTHORPE Jul 3, 2016 9:11 PM in response to appleaddictuser
    Level 9 (52,147 points)
    Mac OS X
    Jul 3, 2016 9:11 PM in response to appleaddictuser

    The Apple Hardware Test shows that there is a voltage problem with the power bus.  This will need to be resolved at an Apple store genius bar so make an appointment.   This does not mean that this is the only problem with your MBP but I an sure that the technicians will also look at the battery status and the HDD as well.  Good luck.

     

    Ciao.