crash log - happens regularly

Accidental generation of a wrong address through compiler code is vanishingly unlikely, and if it occurred, would cause a memory protection fault.

With the whole raft of protections including sandboxing protecting segments of memory Not accessible to user software, a software issue is almost impossible.

You have a hardware error. Proving that in detail appears impossible in your organization, so you should demand a different device and leave it to IT to find and fix the one you have at the moment.

Your postings on this thread are good step into making your case to the IT department, if they are on the ball.

"No fault found' says that under the enormously constrained conditions, in the exceptionally brief amount of time allotted, using the limited tests available, no faults were found.

It is NOT the same as "All is Well"

--------

it is common when testing for RAM memory problems to run the test ONLY (not the test inside running MacOS) non-stop for Days on end.

if you want to dig, there is MemTest 86 test software that can be made into a stand-alone bootable USB-stick. Be sure to allow booting from alternate devices before you attempt to boot from anything other than the built-in boot drive.

...or make an appointment at an Apple-owned store for a free evaluation and service diagnostic.

NB>> Be sure you have a backup of all your files before you go in for service. if the mainboard is replaced, your drive and its files will NOT be returned to you.

Have you tried to run the diagnostic? Gross issues may show up there, which makes the repair process easier.

Intel Mac or Apple silicon?