Desperate for help | Automatic Repair Loop

[WaitDontSh00t]

I'm really hoping somebody can help me out. I'm typing this from my phone as of now. As of recently, out of the blue..I booted up my PC and it wanted to scan and repair my disk? I skipped it and booted into windows. Weird..? It wanted me to run a check disk still, so I had to restart my PC and it ran.

 

Well, it attempted to automatic repair, but failed. System restore also fails. I can't boot into windows at all now, not even safe mode. I'm immediately greeted with it checking the disc, diagnosing, automatic repairs and then stuck at the Windows 10 recovery screen.

 

I tried researching but I have found nothing useful to my situation. I can't access my PC at all and this is just randomly happening out of the blue.
My specs:.

6700k

Asus Maximus VIII Hero Alpha

Corsair Dominator Platinum 16GB

Dual980Tis

CorsairRM1000i

Samsung850 Evo 500GB (Windows, apps and games installed here)

WesternDigital Black 1TB and 2TB

Samsung850 Evo 1TB

Samsung 960 M.2. 1TB

 

I have no clue what's happening, I've tried everything I could think of. Even trying to run a sfc scan in command prompt via recovery screen wouldn't work.

Are you guys able to help me out? Hopefully I provided enough info. Many thanks in advance

[voiha]

Did a little reading and from what I understand most of the time a clean install of Windows is best.

Can you run in safe mode from the recovery screen ? What happen next ?

[Radium_Angel]

56 minutes ago, WaitDontSh00t said:

I booted up my PC and it wanted to scan and repair my disk? I skipped it

That was a poor decision. Your drive was mostly likely going bad and Windows/the BIOS picked up on this and wanted to try to repair.

Since you skipped it, it tried to boot and you see the end result.

 

My guess is you have enough bad sectors in your windows directory that it cannot repair and therefore won't boot...

You need to check the health of your drive 1st.

[WaitDontSh00t]

12 hours ago, voiha said:

Did a little reading and from what I understand most of the time a clean install of Windows is best.

Can you run in safe mode from the recovery screen ? What happen next ?

I can't boot to safe mode. If I do select to boot from that in the recovery screen, the PC resets, but goes back into the checking disk, diagnosing, automatic repair and back into recovery screen. 

 

If I absolutely need to reinstall Windows, would I be able to do it to a different drive and hopefully save my data in the current one?

11 hours ago, Radium_Angel said:

That was a poor decision. Your drive was mostly likely going bad and Windows/the BIOS picked up on this and wanted to try to repair.

Since you skipped it, it tried to boot and you see the end result.

 

My guess is you have enough bad sectors in your windows directory that it cannot repair and therefore won't boot...

You need to check the health of your drive 1st.

Yes, I ended up skipping the first time (and it booted into windows and asked me to run it there again). Though next restart I let it complete. I tried running chkdsk again via the command prompt in recovery screen, but it didn't say anything about bad sectors. I'm not too sure what to do now.

I find it hard to believe my drive would be going bad. It's just hard to think that out of the blue, especially when it's not that old.

[WaitDontSh00t]

UPDATE: I found a boot critical file corrupt.  

 

G:\EFI\MICROSOFT\boot\resources\custom\bootres.dll is corrupt.  

 

Repair action: File repair. 

 

Result: Failed. Error code = 0x4005. 

 

Time taken = 515 Ms. 

 

This was in my SrtTrail file apparently. It seems to be the only thing "wrong" in it.  

I'm not sure what any of this means or how to fix it though!

[Radium_Angel]

1 hour ago, WaitDontSh00t said:

I can't boot to safe mode. If I do select to boot from that in the recovery screen, the PC resets, but goes back into the checking disk, diagnosing, automatic repair and back into recovery screen. 

 

If I absolutely need to reinstall Windows, would I be able to do it to a different drive and hopefully save my data in the current one?

Yes, I ended up skipping the first time (and it booted into windows and asked me to run it there again). Though next restart I let it complete. I tried running chkdsk again via the command prompt in recovery screen, but it didn't say anything about bad sectors. I'm not too sure what to do now.

I find it hard to believe my drive would be going bad. It's just hard to think that out of the blue, especially when it's not that old.

I have seen 2 hour drives go south. Defects can, and do, happen.

Find a bootable USB/ISO/DVD of hard drive checking tools (start wit the manufacturer of your hard drive) and run their tests, and see what they say.

If they pass, then a bad drive isn't the issue (which would be a good thing)

Report back please

[WaitDontSh00t]

Just now, Radium_Angel said:

I have seen 2 hour drives go south. Defects can, and do, happen.

Find a bootable USB/ISO/DVD of hard drive checking tools (start wit the manufacturer of your hard drive) and run their tests, and see what they say.

If they pass, then a bad drive isn't the issue (which would be a good thing)

Report back please

We may have posted at the same time so you may have not seen the message I just posted. Though look at what I posted above your post. I believe this may be the issue? I'm not sure what it means, but it's the only thing I found wrong via command prompt and in the file location.

[Radium_Angel]

3 minutes ago, WaitDontSh00t said:

We may have posted at the same time so you may have not seen the message I just posted. Though look at what I posted above your post. I believe this may be the issue? I'm not sure what it means, but it's the only thing I found wrong via command prompt and in the file location.

We must have.

Sadly I'm not certain how to fix that. *some* DLLs are interchangeable and you could pull one off another system or even download from the 'net, but you'd have to research this, as I cannot confirm this would work.

[WaitDontSh00t]

5 minutes ago, Radium_Angel said:

We must have.

Sadly I'm not certain how to fix that. *some* DLLs are interchangeable and you could pull one off another system or even download from the 'net, but you'd have to research this, as I cannot confirm this would work.

Thank you for trying. I appreciate it.

Even if I could, I feel like it wouldn't work since I can't access anything except the recovery screen. Hopefully a bit of luck will pass my way soon.

[WaitDontSh00t]

Another update...So I ended up installing a fresh copy of windows to another SSD in the system. Of course none of my previous apps are working, though the drive where windows was installed seems fine and everything is on there still.

 

Is there anything I can do to try and repair that windows now that I'm actually able to boot? I'm not sure what to do with that drive now with all my programs and apps. Of course everything was reset, so it's a pain to get everything working to back how it was. 

 

So if I could repair the other copy of windows where it originally was that would be great. Does anybody know anything about that?

[ZacoAttaco]

I'd mess with the BIOS boot options, sometimes the BCD or boot configuration data can get confused and you end up having to boot off different drives. If you want to fix it then you're on the right path, it's not easy to just fix the BCD because Windows was probably originally installed in that way. This happened to a relatives computer, they just live with it now and just boot from a different drive in BIOS but it's actually to the correct drive with Windows on it.

 

So try messing with BIOS boot settings and see if that helps.