Solved Win 7 keeps restarting after fresh instalation

[ryanek011]

Hi,
I wanted to format HDD and install fresh copy of Win7 to make the notebook a bit faster again. The format and installation of OS went well until the last automatic restart where the desktop screen appears with ASUS logo but just for a few seconds.Then the notebook restart itself again and stays in this restarting loop forever.
I formatted partition marked as System where the original copy of Win7 was installed.I store data on partition marked as Logical that was not formatted.Also there is RECOVERY partition marked as Primary and it is 25GB of total size with 9GB of free space.. Does the RECOVERY partition have anything to do with the restart loop or is there any chance to use it for recovering the system? Should not be the partition with fresh copy of Windows marked as Primary?

Thank you

 

[gregrocker]

You should be following http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164 to assure you get and keep a perfect install. If what you've already done varies much from those steps then I'd do it over.

Always back up all files and delete all partitions during the booted http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html using the Drive Options in Steps 7 and 8, then create your partitions as desired, format, and install to the first large partition (ignoring the small boot partition created).

If you can't back up your data which is extremely risky since a HD can die at any minute, then at least delete all other partitions and create new to try to refresh the partition table.

If these fail then you'll need to follow the steps for Overcoming Windows 7 Installation Failures - Windows 7 Help Forums.

 

[Kaktussoft]

Which partition is marked ACTIVE?
Can you boot to http://www.sevenforums.com/tutorials/666-advanced-boot-options.html ? And select "Disable Automatic Restart on System Failure" there? Then you see why it crashes on next boot! Of course I want to know what errorcode on carsh.

 

[ryanek011]

Thank for quick responses. I have to try some of your advices. I'll let you know the result.
@gregrocker Deleting 2 partitions out of three (System and Recovery) and making just one of them both as System primary partition was my first idea.The only reason for not doing so was that the partition marked as Recovery may be theoretically used for recovery of the original OS.But I am not sure if that's possible.Once I know that it's useless I'll delete it.If there is any chance to recover the system or install from the recovery partition i just don't ant to loose it. That's all.

@kaktussoft I can get to Advanced Boot Options and I selected "Disable Automatic Restart on System Failure". Instead of starting Windows it took me to installation point.I selected Repair and window saying ''Windows found problems with your computer's startup options. Do you want to apply changes and restart computer?'' And below ''View details''. After clicking on ''View details'' another window pops-up and says ''Repair details: The following startup details will not be repaired:Name{bootmgr}
Identifier : {9DEA862C-5CDD-4E70-ACC1-F32B344D4795}

The followind startup options will be added : Name : Windows 7 Ultimate (recovered)
Path : Windows Windows device : Partition=E: (309172MB)

Name : Windows Recovery Enviroment (recovered)
Path : Recovery\0fbae092-4eae-11e4-96e2-a62d99195141\Winre.wim
Windows Device : Partition=E: (309172MB)

A copy of the current boot configuration data will be saved as C:\Boot\BCD.Backup.0001''

So I clicked Repair and restart.

It brought me back to System recovery options.
I chose Repair computer and restarted as requested.

Suddenly working desktop is here. It seems to be working.
I will be back with updates.

 

[Kaktussoft]

Which partition is marked ACTIVE?? Run disk management to invetigate that.
Also: In http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html do

bcdedit/enum all>bcd.txt
notepad bcd.txt

Post that ouput. You may delete bcd.txt later.

 

[ryanek011]

The partition marked as ACTIVE is the factory RECOVERY partition. I still think that it had a lot to do with recent boot problems. Now I am sending the outcome of bcedit :

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {6b18be13-4eb2-11e4-97de-94541b677106}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {6b18be11-4eb2-11e4-97de-94541b677106}
device ramdisk=[C:]\Recovery\0fbae092-4eae-11e4-96e2-a62d99195141\Winre.wim,{6b18be12-4eb2-11e4-97de-94541b677106}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\0fbae092-4eae-11e4-96e2-a62d99195141\Winre.wim,{6b18be12-4eb2-11e4-97de-94541b677106}
systemroot \windows
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {6b18be15-4eb2-11e4-97de-94541b677106}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {6b18be13-4eb2-11e4-97de-94541b677106}
nx OptIn

Windows Boot Loader
-------------------
identifier {6b18be15-4eb2-11e4-97de-94541b677106}
device ramdisk=[C:]\Recovery\6b18be15-4eb2-11e4-97de-94541b677106\Winre.wim,{6b18be16-4eb2-11e4-97de-94541b677106}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\6b18be15-4eb2-11e4-97de-94541b677106\Winre.wim,{6b18be16-4eb2-11e4-97de-94541b677106}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {6b18be13-4eb2-11e4-97de-94541b677106}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume1
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {6b18be12-4eb2-11e4-97de-94541b677106}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\0fbae092-4eae-11e4-96e2-a62d99195141\boot.sdi

Device options
--------------
identifier {6b18be16-4eb2-11e4-97de-94541b677106}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\6b18be15-4eb2-11e4-97de-94541b677106\boot.sdi

 

[gregrocker]

I doubt if Recovery will still boot to run. Most models won't and since you didn't provide model we can't say for sure. Test it now to see if it will boot from its hotkey to run Recovery, then cancel it if so.

If not mark C http://www.sevenforums.com/tutorials/71432-partition-mark-active.html then run http://www.sevenforums.com/tutorials/105541-startup-repair-run-3-separate-times.html until Win7 boots with the System boot files and flag on C.

If you then ever need to run Recovery you can run it this way: http://www.sevenforums.com/installa...ent-roma-1001-laptop-oem-slp.html#post1952871

 

[ryanek011]

Dear gregrocker,thank you for your response. But slow down a bit a read carefully. If you read my original post you will see this ''....make the notebook a bit faster....'' and this ''...desktop screen appears with ASUS logo...'' . So I assumed you will connect these two information into one > It's a notebook and it's ASUS notebook. So I did bother to mention that. Originally I planned to delete the factory partition marked as RECOVERY but I was advised on other forum not to do so. Why? I don't know but now it runs well so I'll leave it there I guess. I will test if it will boot from RECOVERY and let you know.

 

[Kaktussoft]

identifier {6b18be11-4eb2-11e4-97de-94541b677106}: nothing references to it.
{6b18be12-4eb2-11e4-97de-94541b677106} also not referenced.
So do in elevated command prompt:

bcdedit/delete {6b18be12-4eb2-11e4-97de-94541b677106}
bcdedit/delete {6b18be11-4eb2-11e4-97de-94541b677106}

 

[ryanek011]

The notebook works fine now so I think I don't need to delete these do I? What do you think Kaktussoft?

 

[Kaktussoft]

The notebook works fine now so I think I don't need to delete these do I? What do you think Kaktussoft?

They are just unused remains of previous install.

 

[Kaktussoft]

No reference in bcd output to RECOVERY partition. WIN7 reinstall did rewrite the harddrive's MBR.
Recovery to factory settings can't work now in my opinion.

Do you still want to be able to use "restore to factory settings"? If so.... explain how you should start the procedure according to the manual.

 

[gregrocker]

Can we see a screenshot of http://www.sevenforums.com/tutorials/274797-disk-management-post-screen-capture-image.html

You might be able to relink Recovery to the F8 Advanced Boot options menu which is reinstalled with Win7 trying this: http://www.sevenforums.com/installation-setup/164311-need-help-asus-n53jq-recovery.html#post1701145

If not our colleague SIW2 can likely give the commands to rewrite the link to F8 so it is bootable without adding it as a Dual Boot as in the workaround I first gave.

 

[ryanek011]

Guys thank you for all responses and ideas but I think we can consider this thread as solved and closed. The computer is running so there is no point of wasting your energy and brain cells on this one anymore. Thanks.

 

[gregrocker]

I would not have asked for a screenshot of Disk Mgmt if it was wasting anyone's time. More than half the time we see problems when we ask for these.

Likewise, just because you don't need to run Recovery right now doesn't mean that it should not be re-linked and ready if you need it.

We dont do half-baked work here. That's why these are by far the top tech forums in web history .