Windows 10 - Automatic Repair - boots in 2nd cycle

[sew333]

Hello. I am sorry if i am disturbing with my topic, but i want to know where was the issue in problem. My motherboard is Asus Sabertooth Z97 Mark2.

So my UEFI settings are default, i not changing anything despite of boot priority. Windows 10 was installed due to MBR partition format, so i guess through automacially legacy.Yeah i dont change anything in UEFI still. Primary boot was P1 SSD SAMSUNG EVO 250 GB and all was working fine and properly booting.
Problem started after i change ( switch ) in my UEFI, boot priority from :"UEFI USB KINGSTON" to again "P1 SSD SAMSUNG EVO 250 GB ( MBR partition )".


When starting Windows 10 boot loader starts by "preparing automatic repair" and diagnosing pc. Then after this i get screen with Your pc did not start correctly or Automatic Repair couldnt repair your pc . And when i click restart then Windows 10 boot fine. So i am needing 2 boots to boot properly to windows. He must reboots twice and then get's through. Event viewer showing that system was not closed properly.

So i need help. Where is the issue, hardware, software/bios issue?

Maybe something with UEFI and boot of my SSD which is MBR? Or that doesnt matter?

RAM tested 19 hours in memtest - 0 errors, HD TUNE 0 errors. So i think ram and SDD is fine. Also what is your opinion?

Cpu is 4790k, rams 2x8gb DDR3 Kingston Hyperx 1600mhz.

 

[EarthDog]

You have many MANY answers at other forums already...Did nothing in any of these 8 other threads solve your issue?

http://www.bleepingcomputer.com/forums/t/606757/windows-10-automatic-repair-boots-in-2nd-cycle/
http://www.windows10forums.com/threads/windows-10-automatic-repair-boots-in-2nd-cycle.7781/
http://forums.bit-tech.net/showthread.php?t=300266
http://www.overclock.net/t/1593345/windows-10-automatic-repair-boots-in-2nd-cycle
https://forums.overclockers.co.uk/showthread.php?t=18720822
http://pricespy.co.nz/forum/index.php?showtopic=4094
http://www.rage3d.com/board/showthread.php?t=34026716
http://www.techpowerup.com/forums/threads/windows-10-automatic-repair-boots-in-2nd-cycle.220592/
http://www.techpowerup.com/forums/t...-loop-and-applications-not-responding.219960/


Anyway, not sure if any of the others threads you posted in said this (which is part of the reason why cross-posting in different forums isn't a great idea - Please read this link why you SHOULD NOT be cross-posting threads: http://www.excelguru.ca/content.php?184), but have you tried keeping ONLY the boot drive in the boot sequence and see if that resolves it?

 

[sew333]

Primary boot was P1 SSD SAMSUNG EVO 250 GB and all was working fine and properly booting even after installation of Windows 10.
Problem started after i change ( switch ) in my UEFI, boot priority from :"UEFI USB KINGSTON" to again "P1 SSD SAMSUNG EVO 250 GB ( MBR partition )". And then Automatic Repair showing during 1 boot. On screen with Automatic Repair cant repair your pc i clicking restart and then Windows boot fine. He must reboots twice and then get's through. Event viewer showing that system was not closed properly.

 

[EarthDog]

Repeating what was already in the first post is not helpful at all. Please answer my questions...

1. Did any of the other 7+ threads not resolve this issue already?
2. Did you try leaving ONLY the P1 SSD SAMSUNG EVO 250GB as the boot order?

 

[sew333]

Sorry i cant understand.What you mean ? "2. Did you try leaving ONLY the P1 SSD SAMSUNG EVO 250GB as the boot order?"

Here is a bios screen ( i have always the same boot devices in order ).




Where P1:Samsung is first in priority then i have that Automatic Repair.

 

[EarthDog]

1. This was not resolved with the other 7+ threads... correct?

2. I mean take everything else out of the boot order leaving only the P1: Samsung SSD as a boot option.

 

[sew333]

"2. I mean take everything else out of the boot order leaving only the P1: Samsung SSD as a boot option." How can i do that? Is this possible to leave only SSD in boot priority table?

 

[EarthDog]

Yes. That is what I have told you to do.

I don't have your board so I cannot hold your hand through it. It would be in the ADVANCED version of the BIOS (hit F7) and in the Boot section... just 'disable' the other options leaving only the SSD.


So, wait a minute.... after looking at one of the threads, this appears to be resolved???

So i formatted disk , install again Windows 10 , now Windows booting fine without automatic repair. But i tried to reproduce issue by running memtest86 again. So i run test for 5 hours, stop test and booted Windows 10. This time it booted fine without automatic repair. So i guess its fine. But i want to know why it happened earlier?

http://www.techpowerup.com/forums/t...ion-memory-faulty-or-not.220203/#post-3420101


Is this still an actual issue or are you looking for why it happened (which really, NOBODY is going to be able to answer)???

 

[sew333]

Yes dear Earthdog.i am looking for why it happened.

So i formatted disk this time to GPT , install again Windows 10 , now Windows booting from Windows Boot Manager fine without automatic repair.
Tried switching few times between UEFI USB KINGSTON to P1:Samsung Evo 250 GB BOOT MANAGER and no automatic repair.
But i want to know why it happened earlier just before format? That was still hardware issue? Thx for opinion. Somebody said that can be caused by bad ram. Like i said after format is ok. But i want to know why it happened before format. What caused this ,software ,hardware?

 

[EarthDog]

No idea...and nobody will know.

If the other 8 forums couldn't/didn't want to find out, we likely won't. We could speculate until we are blue in the face about the issue, but, chances are we will not find out the answer if the others didn't over the past month.

What a waste of time this thread has been.... again. You need to be more clear in your posts that the problem was RESOLVED and we were actually looking for the source of the issue.

 

[sew333]

But there is a chance that was not caused by hardware?

 

[EarthDog]

There is a chance of hardware or software that may have caused it... no clue.