My 2013 Mac Pro keeps restarting.

Single error detection means your computer stores a parity bit with each word. If ANY single bit in the entire word has flipped, that 'single-bit error' can be detected. Checking Hardware works by 'adding up' the number of binary one-bits turned on in a word, and making sure the check bit is set so that, for example, there is always an ODD number of bits in every word. This is Odd Parity. It is helpful, but limited.

Parity can be also be computed on subgroups of bits. Groupings are chosen very methodically. Then, in addition to overall parity telling you some error occurred, you can figure out which bit is in error. Hardware can be called into action to correct the wrong bit and make it right almost instantly.

The number of additional check bits required depends on the width of the data word. For the 64-bit words in your Mac Pro an additional eight bits is enough to store the additional check bits needed, but a lot of support Hardware must be added in the processor to make it work. at this wring, only Intel Xeon processor implement Error Correcting Code (ECC) memory.

As a side effect, you can also now detect -- but NOT correct -- when a double-bit/uncorrectable error occurs. double-bit errors cause your Mac to halt with a kernel panic, machine check, detected by multiple processors. This prevents this memory error from poisoning your data.

--------

When the hardware detects a single-bit error-correction event, status bits are set that can allow the number and location of those errors to be tabulated.

The Power-On Self Test runs for only a few seconds. If, in those few seconds, ANY error-correction events have occurred in that short time, the module that incurred those events is marked "absent". Its memory will not be used. The system is told the slot is "empty".

The modules marked absent are no longer operating without errors. They are NOT GOOD ENOUGH to be trusted with your precious data. They are BAD.

Most users feel compelled to remove and re-seat such modules. This simply puts off the inevitable -- Those modules need to be removed from your Mac. If you want the same amount of memory you had before, NEW modules must replace the ones found BAD.

RAM errors:

Macs like yours use Error-Correcting Code RAM. When it is found to to have ANY errors at Startup, it is 'not good enough' and the slots are declared "empty". This does NOT happen while your Mac is running. If uncorrectable RAM errors occur while running you get a distinctive Kernel Panic, machine check, detected by multiple processors.

User Tip: Mac Pro and Error Correcting Co… - Apple Community

.

Security updates disabled - Security updates are disabled. This computer is at risk of malware infection.

Apple security disabled - Apple security software is disabled. This computer is at risk of malware infection.

Security:

Gatekeeper: App Store and identified developers

System Integrity Protection: Enabled

Security Updates: Disabled

do this: >> Re-enable these protections at your earliest opportunity.

>> Remove these as soon as possible, and NEVER re-install them:

Antivirus software: CleanMyMac

System Extensions:

[Running] com.sophos.endpoint.scanextension - version 10.3.1 (Sophos - 2022-02-23)

Application: /Applications/Sophos/Sophos Scan.app - version 10.3.1 (Not found!)

Description: Scanning Services

[Running] networkextension - version 10.3.1 (Sophos - 2022-02-23)

Application: /Applications/Sophos/Sophos Network Extension.app - version 10.3.1 (Not found!)

Your third-party utilities have left out some of your drives atet should be getting TRIM, but are not. Your use of TRIM is all mucked up. You have TWO third-party TRIM enablers installed when MacOS I can provide this feature natively since 10.10 El Capitan.

Iin Terminal:

sudo trimforce enable

then read the disclaimer, agree to the terms, and enter the items demanded to restart and enable the feature for ALL drives.

The Power-On Self Test has no way of knowing whether you have re-arranged modules or anything. it just tests what is installed. This means that those BAD modules may sometimes test good.

If another error occurs in the same module, that could be a double-bit uncorrectable error, and your Mac will halt with a kernel panic, machine check.

Is it Bad or is it really bad, or is it really really really bad?

I dunno, but if you don't want it to halt with a kernel panic, best practice would be to replace the module that failed the test, and the sooner the better.

You have an awful lot of Utilities left over from the days when modest-sized drives cost US$1000, and after a data disaster the prize was the DRIVE.

Nowadays we know the prize is Your data, and you should get rid of:

disk warrior

drive genius

and invest in enough locally attached drives to do local backups.

Backblaze is NOT a replacement for backups -- it takes too long (up to three days at broadband speeds) to restore from the web, among other things.

Your Mac is a candidate fro starting over, and only installing ONE add-on a day, unless you delete an older add-on.

When removing Apps, CleanMyMac just guesses at similar file names in typical places. It has been known to attempt to remove active parts of MacOS. It is now, and has always been, junk.

You can run Disk [Directory] Utility from time-to-time, and take a look at SMART status with driveDx you already have installed.

Did you understand about TRIM? I can explain more if you need more suggestions.

Did you understand why your RAM memory is disappearing? I can explain more about that as well.