Having Issue with Kernel Panic

Dealing with Kernel Panics

Disconnect any third-party peripherals including any USB hubs. How to use safe mode on your Mac, Use safe mode to isolate issues with your Mac - Apple Support then boot the computer into Safe Mode: Use safe mode to isolate issues with your Mac - Apple Support and Playing Safe- what does Safe mode do? See Diagnosing problems- crash, freeze, panic, or spinning beach ball?, Don’t Panic! Understanding & Troubleshooting Kernel Panics in macOS, How to fix kernel panics after installing OS X updates | MacIssues, and If your Mac restarted because of a problem - Apple Support.

Kernel panics are indicative of possible hardware failure, so you should Check your Mac with hardware diagnostics or AHT. Kernel panic logs are found in: /Library/Logs/DiagnosticReports/ folder.

If you have no success figuring what is happening then you may need to examine the software you have running when the panics occur. Be sure it’s all current. If you must to resolve the problem erase the disk and reinstall macOS. Follow this outline to reset the computer to the factory-new state: Factory reset of your Mac - Apple Support.

Boot Into Safe Mode

1. If your Mac isn’t already shut down, then shut it down and wait at least 30 seconds before rebooting.
2. Immediately, at or before the chime, press and hold down the SHIFT key. 
3. Release the key after the Apple logo and progress bar appear.
4. Safe mode startup is much slower than normal startup, so be patient.
5. When the Login Screen appears enter your admin password. If you use automatic login, then this means you are in safe mode.

What you posted is not a kernel panic, it is a crash log for a single process, apsd, due to a NULL pointer dereference.

That generally indicates a program bug somewhere, so it never hurts to inform Apple Support of it directly:

Contact - Official Apple Support

Because it was just an application crash, it is unlikely your nvram commands had any effect on the situation.

If you do contact Apple Support, please tell them that apsd crashed, not that you had a kernel panic.

That report is meaningless outside of an Apple tech service. I don't know what it means. I wouldn't bother posting logs such as those because they are intended for engineers with debugging software and hardware.

FYI: These are user-only forums. This is not Apple Support.



<<just running chrome with memory clean in the background>>

Chrome-

is the most notorious resource hog in common usage on Macs today. You are not "just running Chrome" you have signed up for the resource-eating way of life that Chrome forces you to adopt.

You would be FAR better served by running a Browser that has been updated more recently, such as Firefox or Safari. These run faster with a far smaller resource load.

Memory clean-

I don't know what that is, but I do know that the makers of your Mac and its OS are not "holding out on you". Anything that could possibly make your Mac run faster and better has already been included as a part of MacOS.

This means that any third-party thing you ADD, has got to make your Mac run LESS well and be LESS stable. Remove that Dreck and NEVER re-Install it.

That alone could be the cause of your crashes.

<<error code 4MEM/9/40000000: 0xa5b36a98>>

4MEM is a definitely RAM MEMory error code. It is not at all ambiguous. You have defective RAM, so no wonder your Mac is crashing.

There is no point in debugging further until you RAM Memory problem is fixed.

Your MacBook Pro 2010 model with Dual Graphics (15 or 17 in) is limited to at most 8GB total across its two memory sockets.

The problem is the traces you have posted are from application crashes, not kernel panics, so it’s unclear that your RAM is responsible, though it was indeed bad and needed to be replaced.

If you could post a lot from your latest crash, I can take a peek and see if I can intuit anything in particular.

System model name: MacBookPro6,2 15-in 2010.

That model MacBook Pro had some problems with its Discrete GPU failing, and MacOS not noticing until there was a kernel panic condition like your reported "GPU panic". There was a recall, long since expired.

Some Users who are not using External displays or doing Editing have obtain some relief by applying a hobbyist hack that shuts down the Discrete GPU completely, and using just the Integrated Intel GPU. it still generally performs OK, but in some case, the computer can not be put to SLEEP, or it crashes.

We are discouraged from Volunteering such hacks unless you ask for them.

Read everything before you do anything. This is a collection of solutions, not a single procedure.

Install gfxCardStatus (https://gfx.io) and set it to "i" (integrated graphics only). It will allow your MBP to run on integrated graphics only, bypassing the discrete GPU which has the issues. This may allow your MBP to run normally, although it will have reduced graphics performance when permforming demanding graphics tasks. The alternative is replacing the logic board, which is not cost effective on a machine that old, unless gfx does not resolve the issue and you really want to keep this MBP.

There is an acknowledged bug in the current version of Cody Kreiger's Open-Source gfxcardstatus, and the developer has confessed he does not have time to fix it right now.

There is a fork off the main build by steveschow available that seems to fix that problem for current versions of MacOS such as ElCapitan and Sierra. He provides a finished .app for direct download -- you do not have to compile anything.

https://github.com/steveschow/gfxCardStatus/releases

Also note that if your Mac does not run long enough to allow gfxcardstatus to be added, this is not really practical.

In addition, Steve Schow writes that he has abandoned further development -- because there are better solutions available [for both the 2010 model and 2011 models].

2010 model:

I have discontinued use of gfxCardStatus to solve the MBP kernel panic problem as the issue is better solved on 2010 models with the nVidia GPU by the following hack:

https://github.com/julian-poidevin/MBPMid2010_GPUFix.

2011 model:

the use of ArchLinux bootable CD to gain access to and re-write the EFI on the drive, and permanently disable the discrete graphics chip. This page and scroll down past the list to the blog:

http://github.com/steveschow/gfxCardStatus

There are two similar procedure listed. I used the second from MacRumors as it seemed easier. I have made the Arch Linux bootable CD on another Mac, and tried this approach. I now have a perfectly-functioning MacBook Pro late 2011 15-in model with Discrete Graphics disabled. Runs just fine. But NO external display support any more.

--------

There is a completely different hack developed more recently. It requires only single-User mode to get started, then type a complicated string into NVRAM, then disable System Integrity Protection and run an additional little program (direct-download link provided there) to make the change semi-permanent.

http://dosdude1.com/gpudisable/

.or a similar procedure with a bit more manual work:

Power up and boot into Single User Recovery by holding

if you are on high sierra 10.13.6+ you might need to use Command + r instead

Command + r + s

Disable SIP (This takes a bit to complete so wait for it)

csrutil disable

Disable Discrete GPU on boot by running

nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

Enable verbose boot mode (This will show text everytime you boot up, shutdown or restart your mac)

nvram boot-args="-v"

Reboot

reboot

Boot into Single User-mode by holding

Command + s + r

It might look as if it hanged, but press enter and you should see the shell (root#)

Mount root partition writeable

/sbin/mount -uw /

Make a kext-backup directory

mkdir -p /System/Library/Extensions-off

Move ONLY ONE offending kext out of the way

mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/

Inform the system to update its kextcache:

touch /System/Library/Extensions/

Reboot

reboot

It will show a bunch of text in the screen (don't be alarmed, let it finish) and then it will restart again In second restart it will show text in the screen again and then it will show normal login screen Your computer now should work properly (dGPU off and iGPU on.

The povidien fix assumes that the problem is the Voltage is kept too low and the Discrete GPU needs to be kept on Warm standby instead of Cold standby until it is needed. So it increases the standby Voltage and uses a little more power at idle.

If this works for you, no features are lost except battery-only time is slightly reduced.

All others are more Draconian. Most disable the Discrete GPU entirely, but save all features except External Displays and ability to Sleep. They force the Integrated Intel GPU to do all the work, so heavy graphics like photo editing would be slower, but do-able.