-
For $29/mo, we provide access to advanced level technicians who will answer your questions on any Macbook board related matter to the best of their knowledge promptly & walk you through how to solve your problem so you can deliver a working board to your customer.Subscribe Now
820-00138 have the same issues as 820-3662?
- Thread starter G.Beard
- Start date
Yes, also occurs with 2015 models (00138, 00426, 00163). Have confirmed it on multiple.
If we could somehow find a way to reliable make these things crash, it would be sooo helpful in trying to find a solution. I've got 5 in test cases that I've been trying to force to fail, and of course now that I need them to do so, they won't.
I don't have time to use each one for an hour or two and get them to crash, far too much work that needs to be done. If anyone can come up with a good way to force them to crash, let us know. So far the easiest way I've found is to run the boards hard, then put them to sleep overnight. About half the time they'll crash during sleep. I'm not 100% sure if it's the same issue, as Duke mentioned that if they crash during sleep, they technically may not be going into full sleep. No clue at this point.
If we could somehow find a way to reliable make these things crash, it would be sooo helpful in trying to find a solution. I've got 5 in test cases that I've been trying to force to fail, and of course now that I need them to do so, they won't.
I don't have time to use each one for an hour or two and get them to crash, far too much work that needs to be done. If anyone can come up with a good way to force them to crash, let us know. So far the easiest way I've found is to run the boards hard, then put them to sleep overnight. About half the time they'll crash during sleep. I'm not 100% sure if it's the same issue, as Duke mentioned that if they crash during sleep, they technically may not be going into full sleep. No clue at this point.
G.Beard
New member
Yes, also occurs with 2015 models (00138, 00426, 00163). Have confirmed it on multiple.
If we could somehow find a way to reliable make these things crash, it would be sooo helpful in trying to find a solution. I've got 5 in test cases that I've been trying to force to fail, and of course now that I need them to do so, they won't.
....Thanks.
The CPU Vcore design is identical besides 1 resistor that is not critical. My prediction is that 2015 models will also start getting the same issues as the 2014.
I have ordered some CPU FETs to see if that will make any difference. Pulling them from dead boards has not been a good idea to eliminate them as those could also have been flaky.
I have ordered some CPU FETs to see if that will make any difference. Pulling them from dead boards has not been a good idea to eliminate them as those could also have been flaky.
Hey Duke, I replaced the vcore power supplies with new ones as we discussed, and am having trouble making the units crash...which could be a good thing. I've replaced them on 3 boards so far and no issues, but again, I'm not sure how best to test them. Maybe just sell them and let the customers be the testers, lol.
I've had the 3 units running for 4 days now; I've tested them in spurts, but they've all passed my "sleep" test, where they don't crash overnight or during long sleep durations anymore. I might just go ahead and sell them and see if they come back...small price to pay to have someone test them in real-world settings.
I've had the 3 units running for 4 days now; I've tested them in spurts, but they've all passed my "sleep" test, where they don't crash overnight or during long sleep durations anymore. I might just go ahead and sell them and see if they come back...small price to pay to have someone test them in real-world settings.
Last edited: