I've tried driver update trial and updated all old drivers but exact when the trial was ended my computer start lagging and in the next few minutes I've received message: "Critical Process Died" with blue screen. I've tried to reboot it's several time but the error doesn't disappeared - more my computer now I can't even log in. It's just crashed before it loaded with the same trouble. I didn't make any updates only driver update via Ccleaner (even windows 10 update). I've watch alot of videos, search alot of the same problem issues and it's resolving. I've tried to fix it via winodws tools /scannow chkdsk etc. but it didn't work, also I use restore point but it was when I've already updated my drivers - sure it didn't helped though.
So what I have now:
Computer literally blue screened right after trial ended with the error that mean that you have some trouble with the drivers. Coincidence? I don't think so.
Thank you so much for making my PC just rubbish. Now only I have left is to reinstall windows.
I can't even look what crashed my system via windows blue screen view because I can't load system properly it's crashed all the time.
My PC characteristics is i7-3770K, MSI z77a-g45 gaming, 16 GB DDR-3, ssd 240 GB, gigabyte windforce 1080 8GB.
Just for clarification, "Critical Process Died" more commonly indicates corrupted or damaged system/OS files, rather than drivers.
If updating the drivers had caused this to occur, then it would surely have occurred the next time you restarted the computer after updating the drivers, rather than at a later point (presumably close to two weeks later, given you mention it was after the trial ended?). Sounds more like a failed Windows Update or even a hard drive that's in the process of dying (especially since you mentioned it happening while Windows was running rather than after a restart).
Regardless of the cause, I found an extremely extensive guide in this discussion: https://answers.microsoft.com/en-us/windows/forum/all/unable-to-boot-critical-process-died/f9b53b40-d0b3-4661-9fde-4d02783faa50 - the first reply down, from Greg Carmack. From what you describe, I'm certain you've tried many of these steps, but I wanted to send it along in case you had not tried any of them, such as checking the hard drive for problems or his 'C' option of creating a new Admin account to try to work around files unique to your profile that might have been damaged (I've had to do that myself to correct a different error, in fact).