[Solved] BSOD Loop

[fortycal16]

Last night when my wife and I logged off for the night her computer was working fine, this morning we get up and her computer is booted into advanced repair options and will not boot into windows.

 

Ive already ran System restore, startup repair, and a few “universal” command lines like sfc.

 

We recently installed windows 10 fresh into a refurbished Corsair 240gb drive.

 

The only codes that I’m getting are 0x0 and “Critical_Service_Failed”

 

When I check the SrtTrail.txt log it says root cause is “Registry is corrupt”

 

Im unsure of what to do to correct the corrupt registry from either advanced repair options or CMD any help would be greatly appreciated.

[Fasauceome]

If you've still got the install disk, try to run a repair install.

[fortycal16]

3 minutes ago, fasauceome said:

If you've still got the install disk, try to run a repair install.

I will give that a shot, still I’m confused as to what would’ve caused the corruption.

[Fasauceome]

5 minutes ago, fortycal16 said:

I will give that a shot, still I’m confused as to what would’ve caused the corruption.

it just happens randomly i guess. happens to me sometimes too, I hate it.

[fortycal16]

Just now, fasauceome said:

it just happens randomly i guess. happens to me sometimes too, I hate it.

The repair install failed mid way, it looks like the only option left would be a format and reinstall. Only problem is I’d like to find out what caused the problem rather than just delete it because it may happen again.

[homeap5]

1 hour ago, fortycal16 said:

The repair install failed mid way, it looks like the only option left would be a format and reinstall. Only problem is I’d like to find out what caused the problem rather than just delete it because it may happen again.

That is good way of thinking. It may happens due to hardware failure. Normally, if everything works fine, it never happens (at least I didn't notice it on any computer I've used, but found that problem on some computers with faulty disk or ram).

 

I can only recommend you what is good to do in the future. First - buy another SSD, even small one. Then clone or image/restore your working system to that SSD. Now you have two operating systems and you can made images of your working system using second one (it's always better option than imaging system that is in use). More - you can always boot into copy of your OS if something bad happens to your main system. It's much more convinient if you have fully operating system to search what is wrong on second drive (or made virus scan or any other actions you want). Of course that requires some experience but it's a good start.

 

What is strange in your case is that your system cannot repair itself, especially if your computer was shut down without problem. Since Win uses hiberboot instead of full shutdown, it may be, as I said, problem with SSD or ram. So best method is to made fresh install of Windows but using second SSD. And disable that fastboot as soon as possible.

[fortycal16]

12 minutes ago, homeap5 said:

That is good way of thinking. It may happens due to hardware failure. Normally, if everything works fine, it never happens (at least I didn't notice it on any computer I've used, but found that problem on some computers with faulty disk or ram).

 

I can only recommend you what is good to do in the future. First - buy another SSD, even small one. Then clone or image/restore your working system to that SSD. Now you have two operating systems and you can made images of your working system using second one (it's always better option than imaging system that is in use). More - you can always boot into copy of your OS if something bad happens to your main system. It's much more convinient if you have fully operating system to search what is wrong on second drive (or made virus scan or any other actions you want). Of course that requires some experience but it's a good start.

 

What is strange in your case is that your system cannot repair itself, especially if your computer was shut down without problem. Since Win uses hiberboot instead of full shutdown, it may be, as I said, problem with SSD or ram. So best method is to made fresh install of Windows but using second SSD. And disable that fastboot as soon as possible.

Fast boot is already disabled, I’ve hooked the drive up to my laptop and I’ve been going through the file system checking everything installed including drivers and making sure system 32 is intact. The only problem I’m still having is windows still refuses to run SFC on this drive. I’m seriously considering that it could be hardware failure luckily it doesn’t have any major files saved on it since she has 4TB on her hard disk she uses for anything big or important. 

 

Im going to see what I can do, worst case senario is to send the SSD back to Newegg cause we’ve only had it for a week. I guess you get what you pay for when it comes to this stuff 

[fortycal16]

I ended up having no choice but to format the drive, a windows update corrupted the registry to the point it was beyond recovery. This was partly my fault for not installing all the updates prior to installing apps to her pc there were some conflicting drivers and files. So I wiped the drive and did a fresh install this time installing EVERY SINGLE UPDATE prior to migrating data back over to the drive. Now we are safe and stable for now, I am buying her a brand new 480gb SSD to put in rather than the 240gb mostly cause the refurbished unit is dodgy. I want to thank all that gave input to this thread.