crwdns2936637:0crwdne2936637:0 crwdns2853008:0crwdne2853008:0 crwdns2861143:0crwdne2861143:0

2.2 GHz (Turbo Boost up to 3.4 GHz), 2.5 GHz (Turbo Boost up to 3.7 GHz), or 2.8 GHz (Turbo Boost up to 4.0 GHz) quad-core Intel Core i7 processor with 6 MB shared L3 cache.

crwdns2934591:0774crwdne2934591:0 crwdns2934593:0crwdne2934593:0

crwdns2933897:0crwdne2933897:0

MacBook Pro a1398 mid 2015 restarts under gpu load

Hey everyone.

Super excited to be joining the community.

I've recently brought a macbook pro 15" mid 2015 without the dedicated gpu (820-00138).

It was a mess when I bought it and the battery was swollen to its limit. So I disassembled everything, cleaned the PCB carefully and removed the battery. It now turns on with the charger and I was able to easily install windows.

All seemed ok until I decided to do some stress testing. The issue starts when I try to do anything gpu related. As soon as I start a gpu benchmark, the system restarts and I'm back to where I started. CPU benchmark didn't replicate the issue.

Is it possible that the issue is related to battery not being in the system yet? I want to make sure before ordering one.

PS: I played 4k videos on YouTube and didn't notice the same issue.

PS II: I bought the item to start repairing as a hobby, and have no issues working on the motherboard as I have some basic equipment to work on it and try my luck.

Any help would be appreciated.

Cheers.

crwdns2934089:0crwdne2934089:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2853045:0crwdne2853045:0 crwdns2853046:0crwdne2853046:0
crwdns2889612:0crwdne2889612:0 0
crwdns2942205:01crwdne2942205:0

As I suspected, no difference on MacOS. Still restarts on gpu stress test.

I've read about the 3 cpu MOSFETs that usually cause crash and shut down/restart the device which is a common issue with this model. but the way I understood it, they are a result of cpu idle mode not gpu under load.

Could they be related and these 3 MOSFETs are the issues here as well?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2933313:01crwdne2933313:0

crwdns2934221:0crwdne2934221:0
crwdns2931211:0crwdne2931211:0 crwdns2931215:0crwdne2931215:0 crwdns2934225:0crwdne2934225:0
crwdns2934057:0crwdne2934057:0

crwdns2933897:0crwdne2933897:0

Give this a try as it is a known bug:

1) reboot with CMD+R pressed.

2) open Terminal

3) sudo csrutil disable

4) reboot in normal mode

5) sudo mv /System/Library/Extensions/AppleThunderboltNHI.kext

/System/Library/Extensions/AppleThunderboltNHI.kext.BAK

6) reboot with CMD+R pressed

7) csrutil enable

8) reboot and forget about problem

crwdns2934105:0crwdne2934105:0

crwdns2853045:0crwdne2853045:0 crwdns2853046:0crwdne2853046:0
crwdns2889612:0crwdne2889612:0 1

crwdns2944067:04crwdne2944067:0:

Thanks for your suggestion. I wouldn't think this helps or even doable as I'm using Windows 10 on the device. Am I wrong?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

do you not have a mac system installed?

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

No but I will install it just to make sure. Since I have Windows, I don't think my problem is a MacOS driver issue anyways as the code I believe is suggesting.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

conveniently, I can't even install El Capitan for the reason explained here:

https://apple.stackexchange.com/question...

I'm going to stick with Windows anyways. Hope to get more suggestions from the community.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

Naweed crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 1

crwdns2936753:07crwdne2936753:0 4

crwdns2936753:030crwdne2936753:0 6

crwdns2942667:0crwdne2942667:0 133