Kernel panic after waking up from sleep mode

The original spec RAM for that model is: 204-pin PC3-12800 (1600 MHz) DDR3 SO-DIMM

The RAM in yours is: Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz,

While there is no guarantee of this being the issue, if you had the original RAM, it would be a good troubleshooting step. Macs are quite fussy about the quality and spec of the RAM used.

Could you please post the panic report?

I looked on Google and it looks like this problem can be caused by Bluetooth devices trying to wake up the computer. Go to Bluetooth in System Preferences, click Advanced in the bottom-right, and uncheck "Allow Bluetooth devices to wake this computer"

The two most common causes of kernel panics are faulty hardware and third-party kernel extensions.

The most common hardware cause is bad RAM.

You have installed some of the worst offenders of third-party kernel extensions, AV software. AV software provides absolutely no useful purpose on a Mac and always causes problems.

You've got BitDefender and AdGuard installed. Uninstall them using the developer's uninstall or instructions. You can't just drag them to the trash.

As noted, your RAM is not correct for your Mac. Crucial has a lookup function that finds the correct RAM for that Mac, so I'm not sure how you managed to buy the wrong type. You might check with them to see if they'll exchange it.

To isolate the probable cause of the panics, uninstall the third-party kernel extensions. There will be no need to reinstall the kexts if the panics do not subside as they are serving no purpose in the first place.

If you still have panics after uninstalling the kexts, then it is likely the RAM. Since that RAM is not spec'd for that Mac, and you do not have the original RAM to swap out, there is really nothing more you can do to test it unless you purchase the correct RAM.

You might try running Rember on it to see if it is actually faulty--if it is, Crucial will replace it, but probably still the wrong type.

Sorry, I missed the part about re-installing the old hard drive.

It could be something with the SSD. Normally, it is the Samsung SSDs that are reported as having issues.

Did you replace it yourself? Even if you had a repair shop install it, the ribbon cable could be not connected fully, causing random panics. MacBook Pro hard drives require a thermal sensor connection that many manufacturers do not have. Crucial makes good products, but I don't know whether their SSDs are fully compatible.

It may just need a firmware update--have you checked with crucial about the problem?

There is no definitive way to determine the cause of a panic. There are sometimes clues as to what it might be, like a Page Fault indicates a memory issue. Not necessarily RAM.

The only way to determine the cause short of taking it to Apple, is through trial and error-- uninstall third-party kexts, test/reseat/replace RAM. If you determine that all of those are not the cause, then it is some other hardware fault that only Apple can detect with more rigorous tests than Apple Diagnostics can provide.

There are very few causes of kernel panics and the most common is hardware and kernel extensions. In some weird, rare case it could be an Apple kext. There are a few other reasons that I can't recall.

One rare possibility is something odd in NVRAM, but you already reset that.

In your case, it may be some other hardware fault. The kernel extension in the backtrace, com.apple.kec.pthread, may indicate the subsystem where the fault occurred, but I don't know what that is.

Do you have access to the original, correct spec RAM for your computer? If so, reinstall it and check for improved performance.

You should take the system to an Apple Store or service technician. Repeated kernel panics like this indicate it's most likely a hardware problem as steadman wrote, RAM or something else.