I figured it out with an IT friend. Computer specs are plenty good, it was working on another computer of mine that has worse specs. It ended up being a file in system32 that got changed because of a Microsoft visual C++ file that got updated called "ucmhc.dll". Was able to do some backdoor stuff to get a previous version installed and now it works beautifully. Hopfully this doesn't happen again in the future.

A couple of months ago I came into my office and had to do a restart on my computer after working on a mastercam file. After the restart I reopened the same file and went to regenerate some toolpaths (fairly large ones) and mastercam would crash essentially and pop up with the message "Mastercam 2022 has stopped working". Talked to a buddy and he recommended a system restore back to a known good date. So I did that and it fixed my issues and thought I'd never have to deal with it again. Well a couple of days later the same thing happened and had to do a system restore again. It fixed my issue and I've just been having to restore the computer to the known good point after a restart for about a month now. Its just been a Band-Aid, I know I would have to deal with this later on down the road. Well, somehow I've lost my known good restore point and have no way to go back to the known good point where mastercam will regenerate with no issues. I decided to upgrade to 2023 thinking that would fix my issue and it did not unfortunately it does the same exact thing 2022 does. I can do a verify and mastercam has no issues with that, its only when I go to actually regenerate bigger toolpaths. It seems to do regular 2d toolpaths fine I assume because they're simpler to regenerate. I thought it might have been my file was corrupted so I opened the same file on another computer of mine that has mastercam and it regenerates perfectly fine with no issues so I know my file isn't corrupted. Ive also went and tried to regenerate a completely different part that has 3d toolpaths and it crashes when I do those as well. So something inside the config, registry, etc is bugged and I don't know how to narrow it down. Was hoping someone else has had this issue and has a fix. I've attached some screenshots to help with reference. Computer is a pretty decent computer also: i5-10600k 4.10 GHz 16gb ram DDR4 2666MHz GeForce GTX1660Ti Samsung 1tb SSD