I've got the same MBP here, same exact problem as these folks [post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer, G4 PowerBook Memory lawsuit: https://laz.paravis.net/apple_complaint. Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
=== Update (12/04/2016) ===
I seem to have spoken too soon about a fix! Typing this from my phone, since the laptop won't stay working long enough to finish a proper sentence.
So back to square one ... Going to get the right size pentalobe screwdriver and check for dust bunnies and reapply thermal compound to the CPU heatsink.
Big issue though, but at least we have a new symptom! When I put it to sleep earlier this morning, the fans stayed on indefinitely (until I hard-powered off). They just kept blowing and blowing - and it was COLD air, not even warm. So overheating seems to be a bit of a long shot at this point.
I'll update again after I have a chance to open it up.
Bummer!
I've got the same MBP here, same exact problem as these folks [post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer, G4 PowerBook Memory lawsuit: https://laz.paravis.net/apple_complaint. Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
=== Update (12/04/2016) ===
I seem to have spoken too soon about a fix! Typing this from my phone, since the laptop won't stay working long enough to finish a proper sentence.
So back to square one ... Going to get the right size pentalobe screwdriver and check for dust bunnies and reapply thermal compound to the CPU heatsink.
Big issue though, but at least we have a new symptom! When I put it to sleep earlier this morning, the fans stayed on indefinitely (until I hard-powered off). They just kept blowing and blowing - and it was COLD air, not even warm. So overheating seems to be a bit of a long shot at this point.
I'll update again after I have a chance to open it up.
Bummer!
I've got the same MBP here, same exact problem as these folks [post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer, G4 PowerBook Memory lawsuit: https://laz.paravis.net/apple_complaint. Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
+
+
=== Update (12/04/2016) ===
+
+
I seem to have spoken too soon about a fix! Typing this from my phone, since the laptop won't stay working long enough to finish a proper sentence.
+
+
So back to square one ... Going to get the right size pentalobe screwdriver and check for dust bunnies and reapply thermal compound to the CPU heatsink.
+
+
Big issue though, but at least we have a new symptom! When I put it to sleep earlier this morning, the fans stayed on indefinitely (until I hard-powered off). They just kept blowing and blowing - and it was COLD air, not even warm. So overheating seems to be a bit of a long shot at this point.
+
+
I'll update again after I have a chance to open it up.
I've got the same MBP here, same exact problem as these folks [post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer, G4 PowerBook Memory lawsuit: https://laz.paravis.net/apple_complaint. Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
I've got the same MBP here, same exact problem as these folks [post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
-
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer: {Powerbook Memory lawsuit|https://laz.paravis.net/apple_complaint]. Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
+
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer, G4 PowerBook Memory lawsuit: https://laz.paravis.net/apple_complaint. Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
I've got the same MBP here, same exact problem as these folks [post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
-
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer: https://laz.paravis.net/apple_complaint.... ... Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
+
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer: {Powerbook Memory lawsuit|https://laz.paravis.net/apple_complaint]. Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
I've got the same MBP here, same exact problem as these folks{[post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
+
I've got the same MBP here, same exact problem as these folks [post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer: https://laz.paravis.net/apple_complaint.... ... Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
I've got the same MBP here, same exact problem as these folks{https://www.ifixit.com/Answers/View/159057/MBP+turns+off+Randomly+Without+Warning|MacBook Pro 15" Unibody Mid 2009] Anyone been able to actually nail down the cause and permanently fix the issue?
+
I've got the same MBP here, same exact problem as these folks{[post|159057] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
-
Apple also says no problems at all. That's obviously not the case.
+
Apple also says no problems at all. That's obviously not the case.
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
=== Update (12/02/2016) ===
+
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer: https://laz.paravis.net/apple_complaint.... ... Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
What are your thoughts?
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
Thanks again for your reply, Dan. Have a wonderful weekend.
I've got the same MBP here, same exact problem ... Anyone been able to actually nail down the cause and permanently fix the issue?
+
I've got the same MBP here, same exact problem as these folks {https://www.ifixit.com/Answers/View/159057/MBP+turns+off+Randomly+Without+Warning|MacBook Pro 15" Unibody Mid 2009] Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
-
Apple also says no problems at all. That's obviously not the case.
+
Apple also says no problems at all. That's obviously not the case.
+
+
Unfortunately there's no diagnostic issues at all. We ran through everything mentioned above (except PRAM reset, see below), not one single anomaly. It's just, when the MBP decides "it's time to die", I can't keep it running for more than probably 2 minutes without it completely shutting off. Typing seems to facilitate the problem, but even when I am using the unit through an SSH session, it still exhibits serious system failures.
+
+
=== Update (12/02/2016) ===
+
As noted above, I had not reset the PRAM (only the SMC), so I did that this morning, and I am still waiting to see whether or not that is actually going to provide me with a solution. I only use the MBP when on site with clients. So I will know soon whether or not I have any success with this.
+
+
But it gets quite embarrassing in front of clients when I'm like, "Yea, sorry, my $2,000 MBP doesn't work for more than 45-60 seconds at a time. Please excuse me while I reboot. Also, for your recommendation regarding new workstations ... Probably, uh, I want to say Apple but I'm going to go with Dell."
+
+
(No, I would never go with Dell, especially if they want Apple. But I embarrass myself, my company, and my Apple products when they perform at an embarrassing level.)
+
+
With our MBP from late 2013 (manufactured in 2014), we never had this problem until upgrading to OS 10.10. And since 10.11, and 10.12, it has become progressively worse. At my most recent client meeting I had to hard shutdown my laptop 17 times, lost vital notes from client discussions each time, and this was all within a 75 minute period.
+
+
Please reference my previous interactions with Apple regarding an issue I didn't believe was the cause/problem of the consumer: https://laz.paravis.net/apple_complaint.... ... Apple has a tendency to blame consumers before they actually acknowledge a problem that was a result of their own engineering deficiencies. Maybe it's to see what they can get away with, or maybe it's that their quality control needs a bit of a refresh. But the bottom line ...
+
+
Three years old (my MBP is about 2.8 years old) is not a legitimate period of time for a consumer product to exhibit "normal wear and tear" and become completely unusable. That's just a joke -- barely outside of the hardware warranty ... And I take VERY good care of my hardware.
+
+
What are your thoughts?
+
+
I'm definitely going to update my post with my results after resetting PRAM, but to be honest, I don't expect that to be a fix. Anyhow, there are attorneys out there drooling from the mouth to sue Apple for the way they treat their customers. I love Apple, and always (probably always) will ... But I'm not one who appreciates getting blamed for their own engineering mistakes.
+
+
Sometimes, that extra $0.04 per unit for a bump in quality for a particular metal alloy is really the difference between a product success and product recall.
+
+
I love your analogy about the cars. It really is like that. But my poor little laptop is used so rarely, I couldn't see it even needing a tune-up. I'll get the thermal paste and sort that out, as well as the potential dust-bunnies and see how it goes. I ordered the proper screwdriver but they sent me one that was far too small instead of the right size.
+
+
Thanks again for your reply, Dan. Have a wonderful weekend.
I've got the same MBP here, same exact problem ... Anyone been able to actually nail down the cause and permanently fix the issue?
Or is this possibly something that Apple should '''legitimately''' be covering under a recall?
=== Update (12/02/2016) ===
I'm on my laptop right now trying to reply to this thread - and it's shutting down on me just the same.
Sometimes I can't get more than 45 seconds after it boots up before it shuts off again. It's quite embarrassing when I go on site to a client and I'm constantly saying "Hold on, gotta boot up again."
I have also reinstalled, reset SMC, done everything I can aside from tear it down and check for any issues ...
Apple also says no problems at all. That's obviously not the case.