Tech Support Guy banner

System restore causes BSOD

478 Views 4 Replies 2 Participants Last post by  Deleted member 1008442
G
2
Hi
I would appreciate your support.
I ran a system restore after turning off Kasperksy. The restore took very long and lead me to the next boot saying it failed due to something caused by kaspersky although it was off. After I shut down the computer, it went into a BSOD with the code Critical Process Died.
Now, it boots into that BSOD as a loop and I have no access to the desktop. everything I've tried in repair, advanced options is corrupt and won't work at all. Cmd does boot but the codes are not working. This is what restore looks like, this photo isn't mine, I got it online so C: is not referring to Me. My computer's system is D:. Here is also what I'm getting when DISM is typed. I am trying cmds that have worked before for me in similar situations but they won't work now. It is possible I could be typing the wrong code, please let me know. I am not that experienced with cmds.
I once did a very long DISM that fixed this exact situation on another pc. SFC /SCANNOW won't even run, even after directing it to D: instead of X:. Reset codes don't work either so far unless I'm doing it wrong. Windows reset itself doesn't work. the registry is damaged from the restore but I would appreciate any advice on a way to repair it without having to reformat the computer or to try something else at least. Thanks!
Computer Personal computer Font Display device Electronic device
Computer Personal computer Operating system Computer monitor Font
See less See more
Status
Not open for further replies.
1 - 5 of 5 Posts
You may not need to reformat the PC. At this point, your OS build is not likely to restore. I would suggest reinstalling Windows. It should detect there is an existing install and ask if you want to overwrite that. You should be able to install but save your data. Once the install is complete, the data will be available in the folder tree.
S87:
According to your images, your computer is running Version 1803 Build 17134 of Windows 10.
That's a very old version/build which was released in May 2018.
You should do a clean install of Windows 10 Version 20H2 Build 19042 and get a fresh start with your computer.
https://www.microsoft.com/en-us/software-download/windows10

-------------------------------------------------
G
S87:
According to your images, your computer is running Version 1803 Build 17134 of Windows 10.
That's a very old version/build which was released in May 2018.
You should do a clean install of Windows 10 Version 20H2 Build 19042 and get a fresh start with your computer.
https://www.microsoft.com/en-us/software-download/windows10

-------------------------------------------------
No worries, this is just a test computer with what you said, was a fresh install from an old disc but then I corrupted it the same way there's is from restore. The laptop with the problem Is experiencing the same critical process died after the restore, it's a 20H2 and is not with me. They get the same results. Just wondering if there was some other code to try. I would prefer not to reinstall the system at this time. Could I enable system protection throughout cmd?
G
You may not need to reformat the PC. At this point, your OS build is not likely to restore. I would suggest reinstalling Windows. It should detect there is an existing install and ask if you want to overwrite that. You should be able to install but save your data. Once the install is complete, the data will be available in the folder tree.
Based on my situation I prefer to try a few cmds before having to so is there any other cmd that comes to mind to try for a registry repair? I tried sfc /scannow and it won't work. Is there a way to enable system protection on cmd? the drive made many restore points for over a year. Seems like some corruption led to "enable system protection"
1 - 5 of 5 Posts
Status
Not open for further replies.
Top