Windows stop error: Critical process has died

Information on what the environment is could help identify the issue.

Commonly if there is an Existence of an SBS or an Essential Version of windows server OS. This even will be seen on the SBS/Essential Server if it is not the Primary Domain Controller.

If you are using a HardDrive checkdisk?

Does the system reflect which Critical System Service is termed?
Event log access?
Is it anything like server/workstation service winlogon service?

Might not have stated it clearly/explicitly above, until you identify the service that is crushing, or is being terminated you will be running in circles trying to solve the issue.

Most sensible OSes have an OOM Killer process - Out of Memory Killer.

The OOM is responsible for killing off random processes, attempting to keep the OS running.

Windows has no OOM Killer, so processes thrash back + forth... in + out of swap space till random processes loose there mind + start dying... for a wide variety of reasons.

When processes... especially system processes die out of the blue, there are only a few causes.

1) System is low on memory.

2) System is hacked.

3) System updates missing, where some old bug triggers that's been fixed.

Starting Point Fixes: Install all updates + add enough memory system never swaps + cleanse machine of all Malware.

I will try the above solutions and post my results

So this is a reg win workstation running winPRO.
Checked event viewer and their seems to be alot of DCOM errors 1084.
PC boots into safe mode fine but thats about it. Checked dmp file see screenshot.

run sfc /scannow and dism /online /cleanup-image /checkhealth
Something is not right.
to complicate matter there are commonly several svchosts.exe that are running as service, determining which is needed.
hopefully the above will point you to a possible flaw/issue

Consider as a guesstimate
c:\windows\softwaredistribution
rename the download folder and see whether the svchost that is crashing is somehow related to the windows update one.

the other option, is to use a boot the system with boot loging enabled.
The other option is to get sysinternals process explorer and enable boot loging in the app. then reboot and see what it produces.
Does the error occur after a period of time the person works, or is it on boot/startup?

The error code happens on boot/startup
But I did already run the sfc and DISM tools and it cameback saying everything was fine but I will run it again

how much memory is in the system? consider running in debug mode, msconfig
check what server are started and see if you can disable some and test it out until you identify the time when it fails.

8GB of Ram. But I had tested earlier by disabling all services in msconfig and when I restarted the machine still got the windows stop error upon startup

The last resort is to use windows recovery tools and reset the system first using the option to keep users files then if that doesnt work a factory reset but I want to use all resources before using that option.

try reseting the network driver.
try booting into safe mode with network to see whether the network adapter might be the issue.

So I had uninstalled the network adapter and restarted the machine. I was able to boot into safe mode with networking fine even before doing that. I will say that the wireless network adapter does have a yellow exclamation along with some other devices in device manager. But I have tried uninstalling all the problematic devices and restarting they all still have the exclamation symbol I have also tried updating some drivers for them.