Kernel panic no reason

It would at least appear your storage is fine for the time being, but the as you said Apple Diagnostics found an error with the multitasking memory of your computer. That has to be looked at by Apple. Still backup your data before bringing it in, as sometimes they will want to erase information on your drive to verify there is no other cause.

loaded kexts:

com.bitgapp.eqMac2Driver 2.0

What is that please? Do you need it? Did you check with its developer for updates? Same questions for Corel Painter.

If you don't know the answer to any of those questions, please write back for suggestions.

These kernel panics are odd then, Is your T2 chip login setup on your computer? If not, then my thinking is you may just have a storage issue with your computer.

Backup your data, and run http://www.binaryfruit.com/ DriveDX to determine the health of your drive. If it is 100% healthy, and the issue persists, reset the SMC, since that's reported as a problem. if the drive is not healthy bring it in to service after backing up your data.

If the issue persists after a reset of the SMC, try running the system diagnostics.Use Apple Diagnostics to test your Mac - Apple Support

DriveDX results or errors with Apple Diagnostics would be important information for Apple Support repair center to know about when you bring it in for service.

I think Memtest86 is showing one error, but I rarely read the summary screen. It does have a line item "# Tests Passed" which mentions "3/4 (75%)". I think this means one of the four test passes failed, but I also don't know how you ran the tests (default is to run all the tests four times or passes). Usually Memtest86 clearly shows any errors while the tests are actually running. Another indication of a memory failure is if Memtest86 freezes during the memory tests....usually that is more common in my experience. The last section is showing a single bit error which is more than enough to cause problems.

It is time to have this Mac repaired or replaced.

FYI, you can rotate pictures on your iPhone or iPad by using these instructions so they appear properly. I cannot read things sideways.

https://www.iphonelife.com/blog/5/tip-day-how-rotate-photo

If Apple Diagnostics reports a problem with memory, it definitely exists.

Memory failures do not manifest in anything except kernel panics, crashes or failure to boot. AD's most useful conclusion is to identify a specific failure, which it has. Contact Apple, here: Official Apple Support

Agreed, if the RAM module is reported bad it must be replaced.

Little known fact about RAM. Back in the 1980s computers got too complicated to 100% test the RAM modules.

To accurately determine if there is any issue with RAM, you would need to determine the on off switch circuits in combination by a factorial of the number of on/off circuits. A 128 bit on off switch has 128*127*126*125*124...*3*2*1 and all numbers in between. Even if the test took a millionth of a second it would take longer than the age of the universe to uncover the possibility of the pathways of circuits generating an error. That's 16 bytes! Now we have 16*10^9 bytes of RAM as commonplace. So if it tests bad, believe it. If it doesn't test bad, you don't yet know the cause of the error.

At this point unsigned software that is not longer on this machine become only a side issue.

The RAM Module (s) would be my top priority

Once that issue is addressed, the remainder can be dealt with at a later time

Perhaps the more learned colleagues on your question may help me recall this.

But at one time there used to an Apple Security Process built into macOS with something about " Steal My Mac " wherein Unsigned or Cracked Software was involved

Have been scratch my head to remember but it is not yet clear

As for the second issue abut RAM ( Memory ) Modules

More often than not the " Volume Mismatch Error " error may present

RAM Modules, especially if Third Party Modules are installed on this computer could be at play

Even if the machine a Soldered RAM Modules - when RAM Modules fail, more often than not it is without any warning at all

Volume hash mismatch, cannot reinstall MacOS

Monterey rev 12.4 - Hash mismatch

Please help - Terminal.app keeps crashing upon reopening - macoS Monterey version 12.4

Volume Hash mismatch

Strange Disk Space Issue

EDITED

Sounds like Filevault had trouble initializing

The unsigned software can be an ancillary problem. But the fact remains Apple's diagnostics is reporting back hardware issues.

Hardware issues can only be resolved by replacing the hardware.