Windows 8 is stuck in an automatic repair loop

Anonymous
2012-10-26T21:04:03+00:00

My windows 8 get in a automatic repair loop and it couldn't repair it. And than it says log file d:\windows\system32\logfiles\srt\srttrail.txt

What to do?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2012-10-29T14:14:32+00:00

do a selective boot up with bios

get cmd to open and check

bootrec /fixMBR

bootrec /Fixboot

bootrec /rebuildBCD

and also

chkdsk /r c:

chkdsk /r d:

chkdsk /r e:

chkdsk /r f:

then let repair go thowe again and should be stoped

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2014-12-31T16:33:06+00:00

Hello Coonut,

Thank you for your reply,

I would suggest you to login to any other computer and create a Windows 8 installation disk. Using that disk you can perform the troubleshooting methods given below.

Refer the link to create the installation disk:

How to create installation media for a PC refresh or reset:

http://windows.microsoft.com/en-us/windows-8/create-reset-refresh-media

Hope the information helps.

Please reply with the results, in order to help you fix the issue.

Wish u a Happy New Year!

Thank you

Was this answer helpful?

70+ people found this answer helpful.
0 comments No comments

280 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-05-30T23:10:24+00:00

     

    (please keep in mind that this might not be the same issue that produced the same problem)

     

    I was having that problem from the time I tried to install. (it kept restarting). when I finally did get it to install it was becouse I put anouther video card in. ( I degraded from nvidia 450gts to 250gts ) there seemed to be a problem with card and the drivers from windows/nvidia. I finally got it to install and then tried to install the newer card (I know this card isn't new but it is within my budget). It then went into a crash/reboot loop and after that it went into a "repair" loop. I finally put the 250's back in and it booted.

     

    On mine I found out after trying a few programs that the sli wasn't being recognised in windows 8 even with the updated drivers (although the older card was being recognised. I also found out that any driver after the 286 (nvidia) was causing the system to crash (I hadn't updated my drivers in a while. So I had no idea that there was a flaw either in the card or the drivers or the system)

     

    so to sum up:

    I can work in windows 8 without the dreaded repair loop (that I get with the newer card) but I had to sacrifice the sli tech. to do it. And, to me, that was just unexceptable

     

    Windows 8 is great on visual effects and I'm sure it's a great system. However I actually just went back to windows 7 untill the issue is fixxed.

     

    On that note: Would some one please tell me when this issue is fixxed?

     

    thanks.

    Your post help me to realize my problem, described many times in this thread, was also a hardware issue, but also, (I think in combination with Windows 8 two latest updates of this date)..  In my case, (hardware), was apparently bad memory.  How do I know?  If one let the reboot go on long enough, at least on an HP, it will show several different memory related errors.  Clue, ok?  I had previously replaced stock memory modules to go from 4GB to 16GB.  It worked for a while.  Why?  I do not know, unless the memory did in fact certainly go caput.  So, I took the 16GB out, and restored the original.  No more reboot loop.  It stayed in repair mode for seveal minutes then gave me several options to choose from to help me repair.  I chose first to back up all the files I desired, to an external disk.  If I cannot find windows 8 willing to restore itself after this, then I will try Win 7.  To get back to the memory chips issues I bought Corsair, because in the old days this was premium memory chips.  Not any more.  Probably "bin" ram now, from Taiwan or shipped back to Taiwan from Frye's ;)  To be sure the memory was indeed bad  I put it in my Toshiba, P845-S4200 laptop, with Win7.  Win7 started freaking out immediately, though it would run, but with different errors every time.  I took it out after about the 4th self started reboot, because I didn't want it to destroy that laptop too.  Put back in the original memory in it, and every thing is fine with that machine now.  My recommendation?  Keep complaining to Microsoft.  Take your computer back on warranty, demand that those upgraded from Windows7 to 8, like at Best Buy, remove all traces of the old OS.  The previous laptop mentioned at the beginning of use,, prompted me several times telling me it had an old operating system on it that was taking up huge amounts of disk space.  It said notthing about how to get rid of it, but when I looked for Windows.old files, there we're none to be FOUND.  Figure that out.  All the technology we have today, and Microsoft still cannot put out a self repairing OS.  Isn't that unusual?  NO, it's not, not for the economy and keeping other folks busy.  While emptying the pockets of consumers.  Ought to be against the law.  They know it, we know it.  DO not touch any hardware on a machine running Windows 8.  Why do you think they are pushing so hard to get out the next OS in such a hurry?  Don't touch it either, until at least 2 years after it's been released and much research.  

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-05-23T20:08:37+00:00

    Thx dude !

    help me a lot !

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-05-12T00:11:29+00:00

    HOLY JESUS CHRIST THANK YOU JESUS AND THE LORD!!!! JUSTINKOSTIC GOD BLESS YOU LET THE GODS BLESS YOU , YOU FIXED MY PROBLEM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    bootrec /fixMBR

    bootrec /Fixboot

    bootrec /rebuildBCD

    and also

    chkdsk /r c:

    chkdsk /r d:

    chkdsk /r e:

    chkdsk /r f:

    Was this answer helpful?

    0 comments No comments