All New Build- Lots of BSOD ax88x-pro Asus

Welcome aboard, @SalemCBR.

In your case, various different bugcheck codes are pointing to memory corruption.

Code:

BugCheck 1E, {ffffffffc0000005, fffff80139afa145, ffffffffffffffff, 0}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for clipsp.sys - 
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

Code:

5750 errors : !clipsp (fffff800b6f45f17-fffff800b6f7260b)

Code:

BugCheck 50, {ffffe001e1fcfb4c, 2, fffff800b6f57c4d, 2}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for clipsp.sys - 

Could not read faulting driver name
Probably caused by : memory_corruption

Followup:     memory_corruption
---------

Test your RAM modules for possible errors.

MemTest86+ - Test RAM

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Take a camera snap of the memtest86+ window before closing the program. Let us see it.
Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

Nice! It minimizes the biggest possibility.

A failing/buggy driver may pass bad info to the memory which is also a cause of memory corruption. As the next step, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

It blames Norton.

Code:

*** WARNING: Unable to verify timestamp for SYMEFASI64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFASI64.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff801ede48bef, ffffd000709db038, ffffd000709da850}

Probably caused by : SYMEFASI64.SYS ( SYMEFASI64+148bef )

Followup:     MachineOwner
---------

Can you Please uninstall (not disable) Norton Security at least for a test?
Disable Verifier, Uninstall Norton, run the computer normally with Windows Defender activated. See how it goes. Let us know.

Yes, Norton is a very frequent BSOD causer.

Still all different BSODs.

Code:

BugCheck 109, {a3a01f5a18c8b58d, b3b72be06b4a5e0a, fffff8021b5a8070, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup:     MachineOwner
---------

Code:

BugCheck 3B, {c0000005, fffff8016ae1e60c, ffffd001a1f65b90, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpLookupObjectName+46c )

Followup:     MachineOwner
---------

Code:

BugCheck 1E, {ffffffffc0000005, fffff8014567069c, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KiExecuteAllDpcs+26c )

Followup:     MachineOwner
---------

Please let Driver Verifier run one more time.