Windows 10 begins to restart repeatedly due to a repair process.

heatplayz
Junior Member

10-22-2016, 07:26 PM

heatplayz

10-22-2016, 07:26 PM #1

BlazedJew
Junior Member

10-22-2016, 08:05 PM

Use a Windows installer (Vista, 7, 8, 8.1 or 10) and select the repair my computer option.

BlazedJew

10-22-2016, 08:05 PM #2

Use a Windows installer (Vista, 7, 8, 8.1 or 10) and select the repair my computer option.

Ender_Craft47
Posting Freak

866

10-29-2016, 05:08 PM

I would start by removing the CMOS from the motherboard for 30 seconds, place it back, and observe the outcome. If it doesn’t resolve the issue, we can proceed further.

Ender_Craft47

10-29-2016, 05:08 PM #3

I would start by removing the CMOS from the motherboard for 30 seconds, place it back, and observe the outcome. If it doesn’t resolve the issue, we can proceed further.

Sunahh
Posting Freak

863

10-30-2016, 07:53 AM

I've already attempted a repair. It managed to start after receiving numerous app malfunction warnings. I planned to restart it multiple times to verify the solution. Now I'm stuck in a BSOD loop—progress is uncertain, but it's moving forward.

Sunahh

10-30-2016, 07:53 AM #4

Hidekih
Posting Freak

849

11-06-2016, 07:53 AM

CMOS was cleared for over a minute just to ensure safety, resulting in the current display. This has happened before—I'm currently experiencing issues loading my NVMe M.2 boot drive again.

Hidekih

11-06-2016, 07:53 AM #5

CMOS was cleared for over a minute just to ensure safety, resulting in the current display. This has happened before—I'm currently experiencing issues loading my NVMe M.2 boot drive again.

SuperClay101
Junior Member

11-09-2016, 01:05 AM

Update from @Tristerin and @Guiltyx: I can now manually boot from the drive in BIOS, but it crashes into a BSOD (see attached image). If I let it attempt to start on its own, it opens automatic repair and says it failed. It seems Danish, but I think the 'Stopcode'—CRITICAL PROCESS DIED—indicates something serious is wrong.

SuperClay101

11-09-2016, 01:05 AM #6

Reydam
Junior Member

11-09-2016, 04:09 AM

Consider taking all drives off the board except the boot drive. Then restart the computer and see what occurs.

Reydam

11-09-2016, 04:09 AM #7

Consider taking all drives off the board except the boot drive. Then restart the computer and see what occurs.

lookatmyskill2
Member

102

11-09-2016, 04:34 AM

Sorry for the slowdown! I attempted to delete other drives but still encountered BSOD during Windows startup. I’ve tried several solutions so far. Using the system recovery tool with sfc in cmd helped—no integrity issues reported, but remove function and quality updates didn’t work. Restoring from a previous state also failed. I ran memtest without success, as some warn it’s not very dependable. Right now, the only option that comes to mind is a clean install, since I can’t even boot into Windows anymore. It seems the Windows files are severely damaged or my system is completely broken.

lookatmyskill2

11-09-2016, 04:34 AM #8

Zam_GM
Member

158

11-13-2016, 05:43 PM

The command shows no Windows installs found, but it doesn’t necessarily mean the installation is completely broken. It could indicate missing files or a corrupt setup.

Zam_GM

11-13-2016, 05:43 PM #9

The command shows no Windows installs found, but it doesn’t necessarily mean the installation is completely broken. It could indicate missing files or a corrupt setup.