Hinge faulty? / Harddisk speed on 2011 Macbook Pro
I've just (4 days ago) moved from a silver unibody 2008 macbook pro to a new 2011 macbook pro, I'm noticing differences and so far they're not really positive .
I like to work laying on the sofa with the base of the macbook resting vertically on my chest with the screen tilted back to make reading easy. Although this worked perfectly on the 2008 macbook the new one keeps closing itself! As I'm trying to work the screen constantly drifts back to about an 85 degree position (presumably due to its weight and the stiffness of the hinges).
To say this is annoying puts it mildly.
The forums seem full of posts about hinges and I'd be interested in opinions as to this being a fault or a feature before I travel to an apple store.
Also - is anyone else seeing an disk speed issues with a 2011 macbook? I've just restored from a time machine backup and the new macbook feels half the speed of the old one.
If I leave the base on the laptop horizontal (on a table or similar) then the display is self supporting in any position, it's only when the base is vertical that the problem occurs.
With the base vertical the display is also self supporting but not past about 85 degrees.
You guys are definitely sure that's a fault? I'd like to think it was, but the apple store is about 45 miles and its a long roundtrip
Thanks for the reply.
Re the disk I'm showing a five minute load average of 1.67 and although multiple applications are running its exactly the same apps as used to run on the 2008 machine without issue. CPU is sitting about 95% idle.
I've used disk utility to run a repair on the permissions and a verify of the disk but this doesn't seem to have helped.
The two thoughts that I had were 1) Was my old disk faster than 5200rpm? 2) Is there some process that must run following a time machine restore before speed comes back to usual?
Similar Messages
-
Early 2011 MacBook Pro- The thermal paste discussion.
It is my goal to clear up the questions and concerns Apple customers have been having regarding heat or fan related concerns with Early 2011 MacBook Pros. If your MacBook Pro was produced within the last few months the thermal issue has been resolved and it will likely not be in issue for you. If you are still wondering if your computer is effected or what the real issue is keep reading.
The MacBook Cools itself by 2 main methods: active and passive. The active cooling is via a fan that blows air through a heatsync and into a tube called a heat pipe which leads to the back of the computer where the hot air is discharged through a vent at the bottom of the screen behind the hinge. The fan lowers the air pressure inside the case causing outside air is drawn in the case, displacing the hot air inside and helping to cool the other components.
The computer uses passive cooling to remove the residual heat from the processor which comes mostly in the form of radiant heat. Passive cooling is also used to cool the other components of the computer (memory, disk drives, battery etc). Passive cooling works by conductive heat transfer ie. syncing to the case of the computer. Some of the heat then is radiated. Some of it is transferred from the outside of the case via convective cooling; the foot pads on the bottom cover are designed to raise it up just enough to allow air underneath for convection to occur. (Convection is the process in which hot air to rises and is displaced by cooler air.) The rest of the heat from the bottom cover is absorbed by whatever surface you have the computer on.
The processor will not sync to the case very much if the board is assembled properly however the other components of the computer will, requiring the case to be in open air to allow for passive cooling to take place.
If you have some sort of covering such as a plastic snap on case it will likely interfere with passive cooling in all of it's 3 of it forms, this will cause the computer to be abnormally hot. I recently saw someone in the Apple store with a MacBook Air experiencing abnormal heating due to a plastic snap case so this particular problem is not unique to MacBook Pros and it is not the cause of the issue being discussed here. I do not recommend the use or anything that covers the computer while it is running with the exception of something that covers the back of the display panel only. If you are worried about your computer getting damaged go and buy a laptop insurance policy from Worth Ave group. The insurance does not cover cosmetic damage or misplaced items but will cover accidental damage including spills. This insurance also covers theft, vandalism and natural disasters, is quite inexpensive and the claims process and deductible is similar to most phone insurance plans (which they also offer).
User induced overheating can also occur when the computer is placed on an improper surface such as a couch cushion, car seat, bed, pillow etc. Doing this can interfere with both passive and active cooling.
As I mentioned earlier In all likelihood if your computer was produced after May it is not affected. I personally have been in posession of 3 MacBook Pros, one produced before May which had the problem, one after which had no problems and one produced more recently that has mind blowing thermal performance way beyond all of my expectations.
So the question at this point is exactly what is the problem, how can it be diagnosed and how can it be rectified.
After extensive research and testing I have determined the issue to be related to improper application thermal paste. I involuntarily became involved in this pursuit as a result of the problems I was experiencing and I did not initially come at from an objective viewpoint but rather one of cautious skepticism. I had anticipated before purchasing my computer that there may be a thermal issue. This anticipaion came as a result of reading an article on ifixit.com about the disassembly of the brand new early 2011 MacBook Pro. When the technician performing the disassembly removed the main heat sync he expressed concern about how much much thermal paste was present, expressing that it seemed excessive. This lead the technician to question wether or not it would cause heating problems.
Proper application of thermal paste is critical to the functionality of the active cooling system and when applied improperly will not properly transfer the heat to the heat-sync which in turn gets cooled by the fan. Proper application of thermal paste insures the heat is removed from the case as efficiently as possible. Doing this both reduces the speed at which the fan needs to run in a lot of situations and prevents too much heat from the processor needing to be cooled by passive means. If is is not applied properly it will eventually lead to overheating of the case as well as the other components of the computer. This can cause damage firstly to the computer's battery and can also significantly shorten the life computer. (Or any other kind of electronic device for that matter.)
The problem can be diagnosed by testing the computer using a program called System Load or any other software that will put your computers proscessor use up to its maximum and keep it there indefinitely. Placing full load on your GPU at the same time during the test is also recommended. Keep in mind, if you are using your computer the fan will spin up if needed for additional cooling. You should expect the fan go up to its maximum speed during the test, it is not in of itself an indication of a negative result. Make sure to have the computer plugged in, fully charged and on a proper surface. A desk or other flat surface should be fine. Exceptions would include the top of a refrigerator since it has insulation just underneath the metal exterior or any surface that is heated by any means such as a dryer or other appliance.
(The temps to follow are in ºF)
Run the test for up to 1 hour. If the case of the computer breaks 93 degrees your unit is likely affected. Expect the unit to even possibly reach temps approaching and exceeding 100º, if this happens immediately abort the test. Also look for the processor temp shooting up to around 180 in the first 30 seconds and the fan spinning up right away. Typically on a properly functioning unit the temperature of the case will end up being somewhere in the neighborhood of 88-91º. If this test is preformed in a room with a normal ambient room temperature of about 68 degrees. Even after an hour the case of the computer should not be significantly hot, just warm to the touch. On a normally operating unit the fan will start to kick in within 90 seconds or so and may not reach full speed even after several minuets.
At one point the case of my computer actually reached 95º during normal web browsing.
This is a problem that I have had successfully corrected twice by reapplication of thermal paste. The first time was on a machine produced prior to may and the second was after a logic board was replaced at the repair depot. (I suspect the inventory turnover is lower for boards than whole computers resulting in a board from the initial production run being installed in my computer.)
If you forget everything I just wrote remember this. #1 if you are using your computer hard enough the fan will end up running at high speed at some point. #2 This problem is not in any way related to the design of the MacBook Pro, or its use/application. #3 This mostly not a problem of the CPU being too hot; these Sandy Bridge CPUs are rated for 212ºf and will routinely be in the neighborhood of 200º, this is hotter than other chips but well within design limits. #4 I have done everything in my power to make sure that this problem has been corrected and I have every logical and evidenced based reason to believe it has been resolved in machines produced after may. #5 This is not an Apple acknolidged issue. Technicians will tell you that there is no problem because these higher temps are normal and within operating limits and if they weren't the machine would shut itself off. (This is a bit extreme; just like a lot of other devices such as electronics, toaster ovens and space heaters with thermal overload protection this automatic shutoff is intended to occur when damage or risk of fire is imminent because the device is WAY outside of normal operating paramaters.) They will also not tell you when asked what these limits are, that they know what they are or in some cases that such figures they even exsist.
I stake my personal and professional reputation on the accuracy of my findings, it is my job as a private consultant to help my clients to resolve complicated and expensive issues just like this one.
Bottom line if you are having a problem and Apple won't fix it on warranty don't ditch your machine, just pay to have it done yourself. In most cases you can pay have it done at the Apple store. It will probably cost you less than 100.00, and it will not void your warranty as long as the work is done by Apple certified technician. It will be well worth it; after all in spite of this MacBook Pro's are hands down the best portable computers on the market, with an industry leading warranty and support to back it up. On it's worst day Apple's service and support is better than any computer/ consumer electronics company, even on its best day.
I hope this helps to clarify this issue! I also hope it will help anyone affected to resolve the problem instead of resorting to a refund and settling for something else.hello all
you can try this:
Go to system preferences > settings > built in display > see bottom of window.
check "show mirroring options in the menu bar when available". then click "airplay display" > and select your device.
That's what happened to my MBP - 15-inch, Late 2011 model. -
Late 2011 Macbook pro - Wont recognize 8gb memory
Hello Apple users,
so heres my problemo. I recently purchased this item . http://www.amazon.com/gp/product/B002YUF8ZG/ref=oh_details_o00_s00_i00?ie=UTF8&p sc=1 .
Corsair 8GB (2x 4GB) 1333mhz PC3-10666 204-pin DDR3 SODIMM Laptop Memory Kit CMSO8GX3M2A1333C9
For my 2011 Macbook Pro 13" 4gb. I Installed both sticks and turned it on, white/gray screen with apple logo shows up underneath it is a spinning white wheel and it spins for a bit then stops and nothing happens it just stays frozen like that. Now when I take one of 4gb sticks out and put a stock 2gb stick in, it loads and the computer turns on and recognizes that I have 6gb of memory. so im thinking okay maybe I have a faulty stick, but then I try the other 4gb with a stock 2gb and it works also.. so now im thinking okay maybe I DONT have a faulty stick.. so then whats the problem ?? I put both back in again in different slots and still not able to load. Am I not waiting long enough for it to fully load ? like does it take more than 5 mins to first start up? or is the speed on my macbook not capable of letting this load idk?
does anybody have the same problem and was able to solve it?
Any info will help, im about to start a new job and I need my macbook to be quick running multiple apps and having the extra storage helps.
thank you in advance!It appers to be the wrong memory type. Reliable sources for memory (gurarenteed compatible and warrantied for life with excellent service) are OWC (macsales.com) and Crucial.com.
They both report the spec is PC3-10600, not 10666.
http://www.crucial.com/store/mpartspecs.aspx?mtbpoid=39021F53A5CA7304
http://eshop.macsales.com/item/Other%20World%20Computing/1333DDR38S08/
Can you return it and then purchase from one of these sources? -
2011 Macbook Pro Overheating *VIDEO*
Well, I must say that I am really disappointed with the current 2011 Macbook pro lineup. This was my first Mac, I must say that I was really excited to finally own one. As I started using it, I noticed how hot the laptop was getting and how loud the fans were. While I was typing a simple E-mail, my palms were getting really hot and was a very uncomfortable feeling. I've been around friends who have own previous models and all have been very quiet and also fairly cool.
I started to get curious so I started reading the temps and it was a staggering 90c degrees! This was just while web browsing, having iTunes loaded and just doing normal day to day stuff. I immediately went online and did a Google search for "2011 Macbook Pro Overheating". I come to find out that it is a common problem. What was most disappointing to me was the fact that Apple is fully aware of this problem and has disabled Turbo Boost on the 13.3" Core i7 while running Bootcamp. So technically speaking, your better off buying the Core i5 model as it will run faster.
I decided to return the laptop, I feel it's deceiving to buy a product that really doesn't perform at it's full potential (It's like buying a Ferrari and only be able to go 60MPH). My batter life was also terrible, I was lucky if I got 3.5 hours under normal web browsing. I think this had a lot to do with the fact that the fan kept spinning at full speed every 2 minutes.
I hope this post doesn't come off as a flame, but rather constructive criticism on Apple's design to improve their products. I truly believe that Apple needs to redesign their Macbook Pro lineup to accept modern processors that run a lot hotter compared to when the Macbook Pro was first introduced. The fact that it has no ventilation in the bottom like every computer out there poses a huge problem with newer processors. I understand the aesthetics portion of the design, but I would much rather have a few small vent holes to keep the processor running cool and maintain a longer life for the hardware.
Lastly, before anyone say's that I got a "defective" one I want to say that this was my 2nd 2011 Macbook Pro as the first one was returned due to the same problems. Here is my video of my experience - http://www.youtube.com/watch?v=6_azMBStJnYI am having a similar problem. Bought MacBook Pro 17" 16 months ago and after about 9 months, routinely, daily, but no particular time I got a black screen suddenly.
(This is running Windows 7 all the time.)
So daily it has been doing this except for a 3 week visit to Europe ... weird. Yet while in Europe no change in usage. Software or hardware. Except that in US I have it plugged often into a bigger monitor. And sometimes have lid closed but not for the past month while being back.
Return to US and within 2 weeks, suddenly black screen of death anytime during the day, keyboard in use or not.
Called Apple finally yesterday ... they need to know if it happens under Apple IOS. No idea. So for 1 1/2 days ran Apple and did nothing! No black screen.
But what I have noticed is that when it does go black the bodyis HOT!!! Especially between the screen hinge and F keys to the left.
Today I did two more things ... installed gotomypc to see if when it goes black if the laptop is functional, just dead video. I will try to remote in when it goes "dead".
Also I put a load of coins on the laptop where it gets hot to absorb the heat and do they ever!
One thing ... the first time I ever saw this black screen symptom it RECOVERD after 3-4 seconds and gave off an error message like
“Display driver stopped responding and has recovered” error.
So based on researching this, it sounds like the video card needs replacing OR a driver update OR a bath in cold water? -
WIP: My adventures with 2011 MacBook Pro and Windows 8.1 including seconday HDD
So I've just lost about 3 days of my life trying to install Windows 8.1 (my preferred) operating system on a Late 2011 MacBook Pro.
I feel that I've learnt a lot and hopefully can share my experiences to speed a few of you along the process. This is my own experience please let me know if anything I have documented is not true and I will revise for completeness
What my initial goal was to have a dual HD set up with an SSD running both Mac OSX and Windows 8.1 (via Bootcamp) with a 2ndry HD in places of the optical (DVD) drive for shared storage.
I have tried all/some of the following:
Win 8.1 ISO from the MS site: http://windows.microsoft.com/en-GB/windows-8/create-reset-refresh-media
USB created using Rufus for Bios and EFI boot
DVD created using Windows 8.1 (can't remember how)
Yosemite USB created using: Create a bootable installer for OS X Mavericks or Yosemite - Apple Support
There are 2 main options when installing Windows:
Bios
EFI
Both have different pros and cons, which Im going to try and document here:
Bios
Full driver support via Bootcamp download
Slower (mainly boot time, not by much though)
Not quite as "native" as some may prefer
Limited number of partitions??
EFI
Fast
Native
Does not support video driver properly (no dual screen)
Audio does not work (says Failed to start device)
Here are some random facts I know
Windows DVD will only boot from optical drive when connected internally. If plugged in via external USB it stops at black screen with flashing cursor and doesnt progress
Using 5HT-2a's method on Redit (see below) and the EFI install, I get the Cx0000005 cannot find source media error and cannot install
Hacking the Bootcamp tool to create a Windows 8 ISO with all the drivers works (see link below) but when using it in EFI it crashes repeatedly during install so you never can complete the process (I think this is due to the video drivers) and therefore can't run Bootcamp assistant thus get proper trackpad support
Using lion10's method (below) for tweaking a standard Mac partitioned HD I was able to get past the cannot install Windows error ("windows cannot be installed to this disk. the selected disk is of the GPT partition style") and install Windows using EFI
Best guides/links I have found:
lion10's method:The ultimate way to install Windows 8.x in (U)EFI mode on Apple systems
5HT-2a's method: http://www.reddit.com/r/mac/comments/2fy3be/by_popular_demand_my_better_than_boo tcamp_guide/
skipsizemore's method: Can't install Windows 8 x64 on late 2013 MBP with1TB SSD
Bootcamp drivers 2 versions depending on Mac:
Older Macs: Boot Camp Support Software 5.1.5621
Newer Macs (most 2013+): Boot Camp Support Software 5.1.5640
Bootcamp Assistant Hack for USB creation on older Macs: http://forums.macrumors.com/showthread.php?t=1680652There is an additional parameter required if you are using Yosemite during code signing (-deep I think, but cant remember)What I ended up doing (so far)
I'm not 100% sure of the state of my disk when I got to where I ended up but I had previous completed the GDisk and DISKPART methods from 5HT-2a and lion10's methods. I was using a 128gb SSD
I then decided to start from the top (as I had previous installed Win 8.1 on the original HD using DVD)
So I ran the Yosemite installer (via USB) and used the partition tab in Disk Utility to repartition the disk into 2 partitions, 1 for OSX and 1 (ExFat/NTFS) for Windows
I then booted in Bios (Windows, not EFI) using the Windows 8.1 DVD using the DVD plugged in internally (wouldnt work using USB enclosure)
Installed Windows to the partition I created (probably the 4th one)
After Windows installed, ran the Bootcamp set up program
Reran Yosemite installer and installed Yosemite
Swapped out the optical drive for a larger HD (7200rpm) and formatted it with HFS+ -
2011 MacBook Pro, 64 bit i7 quad core, upgraded to Lion OSx, Bootcamp installed with Windows 7, wanting to install Windows 8 (don't ask), tried downloading/installing bootcamp 5.0.5033 (both on the mac/windows partitions (actually using a parallel to run Windows)), error message something similar to bootcamp doesn't support this Windows
So the question is am I doing something wrong? Should I just try and install windows 8 through my windows 7 partition and see if I can use the bootcamp 5.05033. Or do I solely have to use the bootcamp to install Windows 8? I'm not too familiar with bootcamp and how it runs.if you're using parallels and full bootcamp then you're making it 100% more troublesome for youself then it needs to be
bootcamp is running windows directly on the hardware this give full memory and cpu and 3d video game power
running windows in parallels is running a virtual machine where one can't run powerful games and the like but one can have it in a window and change fast between osx and windows
parallels as the only virutal machine (as far as I know) support not have the operating system as a file on the osx harddisk but can access a bootcamp parition as virtual machine but without the benefits bootcamps provides
it's a service parallels provide for those who want both to play games in normal bootcamp and sometimes use windows in a virutal machine
just install it like a normal virtual machine and you need not worry about bootcamp drivers and the likes
plus it would mean that the windows part would be a part of the timemachine bacup of osx
which it is not when it's in bootcamp -
Late 2011 MacBook Pro 15 - Slow and Freezes
Good Morning.
This is MBP is running slowly and freezes, particularly if watching video, but is sluggish even opening applications from finder.
The MBP was taken to a apple service provider with the complaint of very sluggish and a strange graphic issue (The graphics were garbled at times - there is a known issue with logic boards.) a picture of the graphics was provided.
The service provider stated that the HDD drive failed the SMART test but graphics passed his test. When questioned if he was comfortable that nothing was wrong with graphics based on picture he stated that he advised I take it to the apple store. Which I did. There the MBP passed both the graphics and HDD test. based on the photograph the no less than 3 geniuses agreed the logic board was bad, though it wasn't the "typical" failure. The genius bar was given the information about the apple service provider and slowness. All of that was entered into the comments.
The MBP was sent to apples repair depot where the logic board and magsafe board was replaced. and the MBP was returned with assurances that all was well.
Though the graphics issue has not reoccurred the speed is not any better and may be worse. (in excess of a minute fifteen boot, noticeable delay opening browsers or menus).
Additonal information:
When provided to the apple service provider (and presumably the apple store) the computer contained the original 4gb ram. and had never been opened. The ram showing on this report is crucial, contains the mac logo and was installed because the service provider said 4gb was low, so when the computer returned and was still slow it was tried - it seems to have made no difference).
The HDD failed to secure erase the freespace on HDD 3 times prior to repair with the message "could not create temp file" after running overnight.
I've reset PRAM and SMC and run trough various "why is my mac slow" guides to no avail.
The anti virus was also added post repair to look for any thing malicious.
Help please.
EtreCheck version: 2.2 (132)
Report generated 4/27/15, 10:28 AM
Download EtreCheck from http://etresoft.com/etrecheck
Click the [Click for support] links for help with non-Apple products.
Click the [Click for details] links for more information about that line.
Hardware Information: ℹ️
MacBook Pro (15-inch, Late 2011) (Technical Specifications)
MacBook Pro - model: MacBookPro8,2
1 2.4 GHz Intel Core i7 CPU: 4-core
16 GB RAM Upgradeable
BANK 0/DIMM0
8 GB DDR3 1333 MHz ok
BANK 1/DIMM0
8 GB DDR3 1333 MHz ok
Bluetooth: Old - Handoff/Airdrop2 not supported
Wireless: en1: 802.11 a/b/g/n
Battery: Health = Normal - Cycle count = 307 - SN = D862172005ZDGDMB3
Video Information: ℹ️
Intel HD Graphics 3000
Color LCD 1440 x 900
AMD Radeon HD 6770M - VRAM: 1024 MB
System Software: ℹ️
OS X 10.10.3 (14D136) - Time since boot: 0:23:32
Disk Information: ℹ️
APPLE HDD HTS547575A9E384 disk0 : (750.16 GB)
EFI (disk0s1) <not mounted> : 210 MB
Macintosh HD (disk0s2) / : 749.30 GB (610.87 GB free)
Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB
HL-DT-ST DVDRW GS31N
USB Information: ℹ️
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. BRCM2070 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. Apple Internal Keyboard / Trackpad
Apple Computer, Inc. IR Receiver
Thunderbolt Information: ℹ️
Apple Inc. thunderbolt_bus
Gatekeeper: ℹ️
Mac App Store and identified developers
Kernel Extensions: ℹ️
/Library/Extensions
[loaded] com.sophos.kext.sav (9.2.50 - SDK 10.8) [Click for support]
[loaded] com.sophos.nke.swi (9.2.50 - SDK 10.8) [Click for support]
Launch Agents: ℹ️
[running] com.sophos.uiserver.plist [Click for support]
Launch Daemons: ℹ️
[loaded] com.adobe.fpsaud.plist [Click for support]
[loaded] com.cloudpath.maccmd.plist [Click for support]
[loaded] com.microsoft.office.licensing.helper.plist [Click for support]
[running] com.sophos.common.servicemanager.plist [Click for support]
User Launch Agents: ℹ️
[loaded] com.adobe.ARM.[...].plist [Click for support]
User Login Items: ℹ️
iTunesHelper Application Hidden (/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)
AdobeResourceSynchronizer Application Hidden (/Applications/Adobe Reader.app/Contents/Support/AdobeResourceSynchronizer.app)
Internet Plug-ins: ℹ️
FlashPlayer-10.6: Version: 17.0.0.134 - SDK 10.6 [Click for support]
Default Browser: Version: 600 - SDK 10.10
AdobePDFViewerNPAPI: Version: 10.1.13 [Click for support]
CouponPrinter-FireFox_v2: Version: Version 1.1.9 - SDK 10.5 [Click for support]
AdobePDFViewer: Version: 10.1.13 [Click for support]
Flash Player: Version: 17.0.0.134 - SDK 10.6 Outdated! Update
QuickTime Plugin: Version: 7.7.3
SharePointBrowserPlugin: Version: 14.4.9 - SDK 10.6 [Click for support]
Silverlight: Version: 4.1.10329.0 [Click for support]
DirectorShockwave: Version: 11.6.5r635 [Click for support]
JavaAppletPlugin: Version: Unknown Check version
User internet Plug-ins: ℹ️
CitrixOnlineWebDeploymentPlugin: Version: 1.0.105 [Click for support]
3rd Party Preference Panes: ℹ️
Flash Player [Click for support]
Time Machine: ℹ️
Skip System Files: NO
Mobile backups: ON
Auto backup: YES
Volumes being backed up:
Macintosh HD: Disk size: 749.30 GB Disk used: 138.43 GB
Destinations:
Data [Network]
Total size: 2.00 TB
Total number of backups: 30
Oldest backup: 2015-03-12 17:13:32 +0000
Last backup: 2015-04-27 11:14:11 +0000
Size of backup disk: Adequate
Backup size 2.00 TB > (Disk used 138.43 GB X 3)
Top Processes by CPU: ℹ️
6% WindowServer
1% fontd
0% SophosUIServer
0% taskgated
0% InterCheck
Top Processes by Memory: ℹ️
819 MB com.apple.WebKit.WebContent(7)
785 MB kernel_task
180 MB SophosScanD
164 MB InterCheck
147 MB SophosAntiVirus
Virtual Memory Information: ℹ️
11.00 GB Free RAM
5.19 GB Used RAM
0 B Swap Used
Diagnostics Information: ℹ️
Apr 27, 2015, 10:02:50 AM Self test - passed
Apr 26, 2015, 08:15:18 AM /Library/Logs/DiagnosticReports/firefox_2015-04-26-081518_[redacted].cpu_resour ce.diag [Click for details]"This is not a retina 15" - though I just turned off the graphics switching to see if that made any difference."
That recall is not just for the Retina model:
From:
https://www.apple.com/support/macbookpro-videoissues/
Affected Models
MacBook Pro (15-inch Early 2011)
MacBook Pro (15-inch, Late 2011)
I'm aware of that recall it is the "known problem" I mentioned in the original post, however the linked story RE: Yosemite referenced retina MacBook Pros
There is an issue in retina MBPs and Yosemite:
http://www.macnn.com/articles/14/11/04/several.support.threads.discussing.issue. related.to.gpu.switching/
"Regardless of symptoms, the issue has been traced to switching to the discrete GPU from the integrated GPU.
Read more: http://www.macnn.com/articles/14/11/04/several.support.threads.discussing.issue. related.to.gpu.switching/#ixzz3YWcK80s9"
So I was not sure if this was discussing a separate issue, that is why I mentioned it was not a Retina.
"Does "disk warrior" report anything that the apple store test would not?"
The Apple Store would run the Apple System Diagnostic (ASD).
Re:
http://www.dannydullin.com/apple-service-diagnostic-asd-reference-list/
The trick when you take it to the Apple Store is to make your computer repeat the failure that you see. It actually would be a good idea to get it to fail just before your appointment. Don't shut it down just take it to them frozen.
Then you can hand the genius the MBP and say, "This is what happens."
Actually a suggestion of another senior member around here. I'd credit her if I could remember who it was.
They ran two test one was a video test and the other was a hard drive test "quick apple store" that said it "randomly checked disk" or something close to that.
I can only hope to get it to fail right before going. - only real problem is that considering the apple disclaimer about their responsibility for your data, there is absolutely no way they are getting it with our data on it. But if I can get it to fail I'll let them see it before wiping it... I mean the sluggishness is obvious so at least they can see that.
I do appreciate the ideas. There were a number of people there when I dropped it off the first time, one of them was on her third logic board. Another on the second. -
Late 2011 Macbook Pro iPhoto 9.2.2 Graphical Glitch
Please see the following video I have posted on youtube. The problem is happening on the late 2011 13"inch Macbook Pro with intel 3000 HD graphics. The problem is limited to iPhoto window. Is it a faulty GPU? or a Software problem?
https://www.youtube.com/watch?v=b9m1FD6MYs0&feature=youtu.be
Any feedback will be welcomed.
ThanksIf anyone has the same setup. Then I would love to know if you have the same problem. I have included the steps that recreate the problem. I have sent a bug report to Apple about this, but I am still not sure if this is a hardware issue or a software one.
I believe this glitch is specific to the Intel 3000 HD graphics card, as I am unable to replicate the problem on a Mid-2009 Macbook Pro or a Late 2009 iMac.
My Setup:
A) Late 2011 Macbook Pro 2.4Ghz with Intel 3000 HD graphics.
B) iPod touch 4th Gen 8GB, Original iPad 16GB, SDHC 4Gb Card
I have been able to replicate 3 times out of 5 this glitch by following these steps.
1) Connect your iPod touch or iPad or SDHC card to your Macbook Pro.
2) Wait for iPhoto to launch.
3)Once iPhoto is launched. Select iPhoto from the Menu bar and click EXIT iphoto.
4) Relaunch iPhoto since your iPod touch or iPad or SDHC card is still connected, iPhoto will show you device photos first. Deselect that by:-
5) Clicking on Photos option under Library and then hovering mouse over your Photos. The glitch should show up.
6) Quit iPhoto
7) Relaunch iPhoto
8) Deselect Device photos by clicking on Photos under Library
9) Hover mouse over Library Photos. The glitch should be still present. -
Late 2011 Macbook Pro green pixels on the screen where dark colors should appear.
I have a late 2011 Macbook Pro I bought it new with 4 gb of ram. About 4 months ago i purchased 8 gb of pny ram for this model and upgraded the ram. I followed all of the safety precautions and discharged my static electricity before upgrading. It increased the speed of my mac and helps with certain tasks. About 2-3 weeks i notices my mac froze and strange green black and pink bars appeared on the screen so i hold the power button to shut it down and it solves the problem this will happen about once a month but otherwise my mac works perfect. Now about a month ago I powered my mac on and low and behold The screen was covered in green pixels. I tried rebooting twice and it didn't do anything then i let it sleep for about 5 mins opened my mac and the green pixels were gone. Now my mac is still usable and everything works its just sometimes like once in a while ill get a few pixels and closing and opening my mac fixes it. I was curious if this was related to one another or is my mac just starting to die....
I have been getting green pixels/boxes the last while...
I have noticed it after waking the machine from sleep. Not 100% sure if that is the only time it happens. It goes away after a few seconds, typically.
Any idea what is going on? -
I know this question has been asked before. My problem is similar to what is mentioned here but I hope someone can explain the error log attached below and hopefully I'm able to find a DIY solution without much cost.
I'm using a early 2011 MBP with Yosemite installed. Not too long ago, I manually upgraded my hard disk to a OWC SSD.
Recently my MBP screen went into white blank screen AGAIN while I was working on a python script which crawls the web with about 10 threads. I used to run this same script without *much* problems before yosemite (ie: i encounter the same problem with Mavericks but not so frequent. I never install mountain Lion before so I can't comment on that. I came from Snow Leopard to Maverick and Yosemite). Other times, my MBP will go into the same white blank screen while doing other misc stuff and this usually doesn't involved me watching any HD video.
A couple of solutions that get my MBP up and running are:
1) I hard shutdown and bootup my MBP. After the apple logo it freezes at the white blank screen. While it stays in the white screen, I will unplug my power adapter and wait for my battery to drain out completely. Once the battery is completely drained out, I will plug in my power adapter and I'm definitely able to boot up my MBP without any problem the first time. I did the same and thus I'm able to post this question.
2) Bootup into safe mode and restart. It works once
3) I have also disabled dynamic switching of graphics card but that didn't work.
Below is my error report. I don't quite understand it. I hope someone explain to me?
Wed Nov 26 23:00:48 2014
*** Panic Report ***
Machine-check capabilities: 0x0000000000000c09
family: 6 model: 42 stepping: 7 microcode: 40
signature: 0x206a7
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
9 error-reporting banks
Processor 0: IA32_MCG_STATUS: 0x0000000000000004
IA32_MC3_STATUS(0x40d): 0xbe00000000800400
IA32_MC3_ADDR(0x40e): 0x00003f7fa25f70af
IA32_MC3_MISC(0x40f): 0x000000000003ffff
Processor 1: IA32_MCG_STATUS: 0x0000000000000005
IA32_MC3_STATUS(0x40d): 0xbe00000000800400
IA32_MC3_ADDR(0x40e): 0x00003f7fa25f70af
IA32_MC3_MISC(0x40f): 0x000000000003ffff
panic(cpu 0 caller 0xffffff802161f12a): "Machine Check at 0xffffff7fa25f70af, registers:\n" "CR0: 0x000000008001003b, CR2: 0x000000010bd43000, CR3: 0x0000000018e1e03e, CR4: 0x00000000000626e0\n" "RAX: 0x0000000000000000, RBX: 0x0000000000000040, RCX: 0xffffff814f6e042c, RDX: 0xffffff814f6e0340\n" "RSP: 0xffffff812ae23898, RBP: 0xffffff812ae238d0, RSI: 0x0000000000000004, RDI: 0xffffff812b337fd8\n" "R8: 0x0000000000000040, R9: 0x00000000ffffffff, R10: 0x0000000000000000, R11: 0xffffff812b337eec\n" "R12: 0x0000000000000012, R13: 0xffffff812b2d7fd8, R14: 0x0000000000000040, R15: 0xffffff812b2d7fec\n" "RFL: 0x0000000000010202, RIP: 0xffffff7fa25f70af, CS: 0x0000000000000008, SS: 0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2782.1.97/osfmk/i386/trap_native.c:168
Backtrace (CPU 0), Frame : Return Address
0xffffff81034d5cf0 : 0xffffff802153a811
0xffffff81034d5d70 : 0xffffff802161f12a
0xffffff81034d5ed0 : 0xffffff802163acef
0xffffff812ae238d0 : 0xffffff7fa25f91ec
0xffffff812ae23920 : 0xffffff7fa25fbd85
0xffffff812ae23940 : 0xffffff7fa25fc241
0xffffff812ae23990 : 0xffffff7fa22bd0bb
0xffffff812ae239d0 : 0xffffff7fa22bfcb4
0xffffff812ae23aa0 : 0xffffff7fa22c5190
0xffffff812ae23ac0 : 0xffffff7fa22c50dd
0xffffff812ae23ad0 : 0xffffff8021ad8008
0xffffff812ae23b30 : 0xffffff8021b01c92
0xffffff812ae23b60 : 0xffffff8021b02859
0xffffff812ae23bc0 : 0xffffff8021b00003
0xffffff812ae23d00 : 0xffffff80215ea517
0xffffff812ae23e10 : 0xffffff802153e91c
0xffffff812ae23e40 : 0xffffff80215235a3
0xffffff812ae23e90 : 0xffffff8021533e8d
0xffffff812ae23f10 : 0xffffff802160a142
0xffffff812ae23fb0 : 0xffffff802163ac66
Kernel Extensions in backtrace:
com.apple.iokit.IOHIDFamily(2.0)[917971EF-5947-3DF5-BB9F-D353D05C0484]@0xffffff7fa229b000->0xffffff7fa2310fff
dependency: com.apple.driver.AppleFDEKeyStore(28.30)[3BAA7FEE-7EF3-3A9A-A0B1-902A4AB7171F]@0xffffff7fa2290000
com.apple.iokit.IOGraphicsFamily(2.4.1)[6D99A3BE-D531-3780-880B-13F2FC894A4A]@0xffffff7fa25ef000->0xffffff7fa2629fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[766FC23F-452C-3B74-951C-598BB17BCF06]@0xffffff7fa1d24000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
14B25
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: 0x0000000021200000
Kernel text base: 0xffffff8021400000
__HIB text base: 0xffffff8021300000
System model name: MacBookPro8,2 (Mac-94245A3940C91C80)
System uptime in nanoseconds: 44905012498
last loaded kext at 7194739946: org.virtualbox.kext.VBoxNetAdp 4.3.12 (addr 0xffffff7fa4795000, size 28672)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp 4.3.12
org.virtualbox.kext.VBoxNetFlt 4.3.12
org.virtualbox.kext.VBoxUSB 4.3.12
org.virtualbox.kext.VBoxDrv 4.3.12
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AppleHDAHardwareConfigDriver 267.0
com.apple.driver.AGPM 100.14.37
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleHDA 267.0
com.apple.iokit.IOBluetoothSerialManager 4.3.1f2
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.ApplePolicyControl 3.7.21
com.apple.driver.AppleMikeyDriver 267.0
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.kext.AMDFramebuffer 1.2.8
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleIntelHD3000Graphics 10.0.0
com.apple.AMDRadeonX3000 1.2.8
com.apple.iokit.IOBluetoothUSBDFU 4.3.1f2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleIntelSNBGraphicsFB 10.0.0
com.apple.driver.AppleThunderboltIP 2.0.2
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.driver.AppleLPC 1.7.3
com.apple.kext.AMD6000Controller 1.2.8
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMuxControl 3.7.21
com.apple.driver.AppleBacklight 170.4.12
com.apple.driver.AppleMCCSControl 1.2.10
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 327.5
com.apple.driver.CoreStorageFsck 471
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.iokit.SCSITaskUserClient 3.7.0
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.5
com.apple.driver.AppleUSBHub 705.4.1
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.driver.AppleSDXC 1.6.5
com.apple.iokit.AppleBCM5701Ethernet 10.1.2b3
com.apple.driver.AirPort.Brcm4360 901.19.10
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleAHCIPort 3.0.7
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 267.0
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IOAudioFamily 200.6
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IOSerialFamily 11
com.apple.iokit.IOAcceleratorFamily2 156.4
com.apple.iokit.IOSurface 97
com.apple.driver.AppleThunderboltEDMSink 4.0.2
com.apple.driver.AppleThunderboltDPOutAdapter 4.0.6
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.iokit.IOBluetoothFamily 4.3.1f2
com.apple.driver.AppleHDAController 267.0
com.apple.iokit.IOHDAFamily 267.0
com.apple.kext.AMDSupport 1.2.8
com.apple.AppleGraphicsDeviceControl 3.7.21
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.8.0d49
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleGraphicsControl 3.7.21
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleUSBMultitouch 245.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.driver.CoreStorage 471
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.0
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.driver.AppleThunderboltDPInAdapter 4.0.6
com.apple.driver.AppleThunderboltDPAdapterFamily 4.0.6
com.apple.driver.AppleThunderboltPCIDownAdapter 2.0.2
com.apple.driver.AppleThunderboltNHI 3.1.7
com.apple.iokit.IOThunderboltFamily 4.2.1
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.0
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.iokit.IO80211Family 700.52
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOFireWireFamily 4.5.6
com.apple.iokit.IOAHCIFamily 2.7.0
com.apple.iokit.IOUSBFamily 705.4.14
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 389.1
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
com.apple.kec.pthread 1
Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 8 GB, SMC 1.69f4
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3030352E4130324C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 4.3.1f2 15015, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: OWC Mercury Electra 6G SSD, 240.06 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: IR Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1Hi all, I had many problems with the GPU of my Early 2011 MacBook Pro and the MLB was replaced three times so far. The first time was about a year ago and I went to an authorised retailer and not to an Apple Store. They first incorrectly diagnosed the problem and told me that they had to replace the hard drive. After that, they still did not really find the problem but said that the MLB had to be replaced, which I did given that my computer was only two years old and running fabulously. About a month later the problem reappeared and the MLB was replaced again, this time by using the 3-months guarantee of the MLB. The first time I had to pay. A few weeks ago I again had problems (the computer was very hot and fans were running at maximum speed most of the time although I was running only Mail and Preview). I'm, I took it directly to the Apple Store and after about five minutes of looking at it they decided to replace in the MLB for free. There is no official replacement program but I think Apple has now recognised the issue and they don't charge you anything if you had the issue before (they call this a repeat repair). So good luck if you haven't solved your problem yet. If the problem reappears there should be no problem.
-
OS 10.7.5 pinwheels Late 2011 Macbook Pro
I am using a late 2011 MacBook Pro and I am getting recurrent pinwheels no matter what I do. Even booting into safe mode, I get them but it usually takes a little while of normal use until they happen. At first I thought it was Chrome, but after I started using Safari the behavior continued. In the console, this sometimes happens right before the pinwheels start:
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
1/10/13 5:38:16.000 PM kernel: IOSurface: buffer allocation size is zeroI remove the istat widget and the excessive fan speeds ceased. However, the machine will still become unresponsive and begin pinwheeling after a random amount of time, never less than 10 minutes. I have run hardware tests and there does not appear to be anything wrong with the logic board or the RAM. I do have an SSD installed but over one-third of the drive is free space.
I have had the activity monitor open when this happens, but I cannot tell what process(es) are using the system resources because it becomes unresponsive too. I have tried updating to Mountain Lion, but I can't get it downloaded in full before the machine pinwheels again. I tried doing a Lion Internet Recovery, but I only got 10-15% done before it errored out and told me that it couldn't finish the download. After that, I could attempt to restart the installation, but then it did not see the SSD at all. I no longer have the original HDD to test the unit, but it appears that the SSD is the problem. I am looking for help in any other areas before I install a new piece of hardware. -
2011 Macbook Pro Hard Drive Upgrade?
Hi. I am looking at upgrading my 2011 Macbook Pro hard drive. I want to get a 7200 RPM hard drive. I have been looking on Newegg and doing some research, and from what I can tell, the 2011 Macbook Pro uses a 3.0GB/s interface. If I were to buy a hard drive that has a different interface, like a 6.0GB/s interface, would it be compatible? Does anyone know the sizing for an MBP hard drive?
Also, it doesn't matter who the manufactorer is right?
And finally, does anyone have any recommendations?But in my Honest opinion I don't think you'll really notice the difference between the 5400 and 7200 rpm unless your rendering large video files or transfering large amounts of data to an external or USB drive. But again you'll be limited on the speed of the external connections that your transferring too... If you really want to notice a difference, get the SSD with a Sata 3 or 6.0GBs connection speed. But the difference between a 5400 and 7200 rpm drive for normal tasks is almost negligable, you probably won't even notice the difference, but if you get the SSD you'll definately notice a difference in boot time, transfer speed, video rendering speed, copying speed of large files, etc...
-
I recently updated? to Lion from 10.6.8(snow leopard), and things seem to be running slower. Has anyone had similar problems? I have Feb 2011 Macbook pro 13" 2.3 Ghz.
As Shootist pointed out, the system uses more power.
However, initially it will reindex the hard drive for spotlight, which will slow things down temporarily.
It also must rebuild caches that eventually will speed things up.
If it has completed indexing the hard drive (no dot pulsing in the spyglass), then there might be something wrong.
Start by booting into the Recovery HD (a partition created with Lion that has Disk Utility and reinstallation options) by holding down cmd-r when you restart. You can let go when the gray screen appears.
When it boots, select Disk Utility and Repair the drive.
If that doesn't speed things up, try re-installing the OS from the same Recovery HD. It won't delete any of your files, but it has helped some people whose Macs ran slow after installing Lion.
Also, how much memory do you have? Lion needs RAM so maxing your Mac out might also help. -
New Sandisk SSD Plus on 2011 Macbook Pro is slow
Hello everyone,
Before I get into my issue here are some screen shots of system information.
I have recently installed a new Sandisk SSD on my early 2011 Macbook pro. After install of 0S and waited for finder to do its things I tested read and write speed using Black Magic Speed Test. My results are shown below.
ACTIVITY MONITOR
WHAT I HAVE ALREADY TRIED.
Used disk utility to verify disk and repair no issues found one problem found when repairing disk permissions but it was repaired.
Fresh install of OS 10.7
NAVRAM reset.
Verified disk was actually selected in systems preferences.
Im at a standstill I have ran out of ideas of what it could be. I cannot appear to find anyone else who did not resolve this issues by following one or more of the steps above.I searched that kernel process that is shown eating up my CPU and applied to following commands in Terminal.
Terminal method of fixing Kernel_Task RAM / CPU / Memory problem in Mac.
Use terminal in Mac to fix Kernel_Task RAM / CPU / Memory problem in Mac.
Command to check ModelIdentifier of your Mac:
system_profiler -detailLevel mini | grep "Model Identifier:"
Command to change directory to Resources:
cd /System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SM C_PlatformPlugin.kext/Contents/Resources/
Command to list the names of ModelIdentifier in Resources directory of your Mac:
ls
Command to move YourModelIdentifier.plist file to Users directory:
sudo mv YourModelIdentifier.plist /users
[Please Replace YourModelIdentifier.plist with Your Model Identifier.plist name. Like mine was MacBookPro8_2.plist. In My Case the command will be: sudo mv MacBookPro8_2.plist /users]
Video tutorial shown below.
http://teamdurga.wix.com/durga#!terminal-way-to-fix-kerneltask-problem/c7zd
rechecked system speed using Black Magic Speed Test
Thank you OGELTHORPE for the helpful hint on changing the vies on the Activity Monitor which allowed me to find the problem. -
Putting a SSD in the optical drive bay of a late 2011 MacBook Pro.
I want to put a large Solid State Drive in the optical drive bay of my late 2011 (Model ID 8,2, 2.4 GHZ quad i7, 8 Gigs RAM, SSD boot drive) using the carrier and drive from Other World Computing. The "About This Mac" box shows that the optical drive is 6G so I'm thinking that it should be OK putting a 6G drive in that bay, but OWC says that MacBook Pros have only a 3G optical drive capability. I know this was true on earlier models, but my bay says 6G. The 6 G SSD's are faster and have a longer warranty. I do pro audio work and want to record to the new drive with speed and reliability. Is there any way to prove that my MBPro will handle 6G? I was told by someone at OWC who looked up my my serial number that it would work, but another tech guy at OWC said they didn't recommend it. I'm thinking that they just issue a blanket "no" answer to cover themselves against people ordering a 6G drive for a machine that wouldn't handle it. Before I order a 6G drive is there a way I can know for sure if it will work?
Many thanks,
RobertIf the computer is correctly identified as 15-inch Late 2011 MacBook Pro, and not an Early 2011 build series,
according to MacTracker database (http://mactracker.ca download application) optical drive interface supports
the same spec as the hard disk drive...
Hard Drive Interface 6.0 Gbps Serial ATA (SATA)
Optical Drive Interface 6.0 Gbps Serial ATA (SATA)
So should there be an error in identification, that would make a difference. Some Early 2011 models may
have the 3.0 Gbps or 6.0Gbps data rate in the optical drive. All Late 2011 models should be 6.0 Gbps.
Good luck & happy computing!
Maybe you are looking for
-
Is it possible to create a variable in bex with the last work day?
Hi Gurus Is it possible to create a variable in bex with the last work day? Actually end-user every day open queries, - Put in selection date day - 1 or - put last Friday if the day is Monday or - put last Thursday if the day is Monday an
-
IChat gets choppy after 90 secs- Started after 10.4.10 update
I've tried all of the above fixes including changing the bandwith anywhere from none to LAN as well as various combinations of the Quicktime streaming speeds. Nothing has been going well. Things have been the same since going to 10.4.10. We have Comc
-
Mark a report as saved thru code in an add-in.
Is there a way to 'mark' a report within Crystal Report as saved? So if you close Crystal Reports the question 'Would you like to save the changes?' is suppressed as if the report is saved already. I want to do this 'to a report' from within an Add-I
-
I have all of my Aviation publications in .PDF format. I keep them on my android tablet (Samsung Tab S 8.4). With the adobe reader app for android, it allows you to bookmark pages (along with renaming the page you bookmarked). Also I have these p
-
after update of my iphone 3gs it is giving me error insert sim