No Hang Dog this, it's somin' else.

[Tram 1]

My new mobo is an ASUS M3A78-EM and I rely on the on board graphics, the installed HD is a Seagate Barracuda Sata 2 affair

The problems lay with starting up or a reboot.

I've been reading all the advise and following tutorials and so on, some fun, interesting and successful, some tedious but nothing ventured...... in an attempt to try and resolve boot hangs and delays.

On boot up or restart, I get the boot log sequence, this takes about 15 seconds, from there it goes to Starting Windows and logo, it hangs there for 35 seconds, then the screen goes black for 20 seconds, then it reverts back to a "starting Windows" and logo screen for about 20 seconds, then goes to the welcome screen and desk top.

I don't understand the reason why the 1st or 2nd "starting windows" screens.

A few days ago, briefly I had 2 internal HDs fitted, both with WIN 7 installed, one HD has now been removed completely but I'm wondering if this might be a reason for the 2 start windows, if there is any remnants left from the removed HD? if that makes sense.

I’ve checked the BIOS and boot sequence, all appears in order anything, else I should check?

If one of the "starting windows" could be eliminated, that would speed things up.

I’ll try and explain a little further, upon start or reboot, when the first "starting windows screen" appears the HD remains silent, there is no sound of a spin, for 35 seconds it’s silent, ( I think ), when the 2nd "windows starting" screen appears, then I hear the HD click and whirl, could any of this be connected?

During this 2nd "starting windows" the screen flickers for about 15 seconds and then settles, I am wondering also what might be the cause of this.
　
Lastly, the HD, in Win 7, I have not enabled XP mode in any shape or form, I’m doing without it so that can’t be a cause and no issues with the PC shutting down, ( didn’t know if that info’ was relevant/ important or not).

 

[Uber Philf]

I dont know, but maybe a format to the new 7127, or the coming ( i think) 7137, might help?

Enzo.

 

[skunksmash]

My new mobo is an ASUS M3A78-EM and I rely on the on board graphics, the installed HD is a Seagate Barracuda Sata 2 affair

The problems lay with starting up or a reboot.

I've been reading all the advise and following tutorials and so on, some fun, interesting and successful, some tedious but nothing ventured...... in an attempt to try and resolve boot hangs and delays.

On boot up or restart, I get the boot log sequence, this takes about 15 seconds, from there it goes to Starting Windows and logo, it hangs there for 35 seconds, then the screen goes black for 20 seconds, then it reverts back to a "starting Windows" and logo screen for about 20 seconds, then goes to the welcome screen and desk top.

I don't understand the reason why the 1st or 2nd "starting windows" screens.

A few days ago, briefly I had 2 internal HDs fitted, both with WIN 7 installed, one HD has now been removed completely but I'm wondering if this might be a reason for the 2 start windows, if there is any remnants left from the removed HD? if that makes sense.

I’ve checked the BIOS and boot sequence, all appears in order anything, else I should check?

If one of the "starting windows" could be eliminated, that would speed things up.

I’ll try and explain a little further, upon start or reboot, when the first "starting windows screen" appears the HD remains silent, there is no sound of a spin, for 35 seconds it’s silent, ( I think ), when the 2nd "windows starting" screen appears, then I hear the HD click and whirl, could any of this be connected?

During this 2nd "starting windows" the screen flickers for about 15 seconds and then settles, I am wondering also what might be the cause of this.
　
Lastly, the HD, in Win 7, I have not enabled XP mode in any shape or form, I’m doing without it so that can’t be a cause and no issues with the PC shutting down, ( didn’t know if that info’ was relevant/ important or not).

do you have a floppy drive..??, if not make sure this is also disabled or it will sit there trying to detect it.....



SK

 

[Dwarf]

Hi Tram 1,

It sounds as though you might have 2 versions of the OS still listed on the boot screen, and it is trying to load the missing one by default, failing and then defaulting to the alternative which still exists. You should be able to get rid of this entry by following the instructions here http://www.sevenforums.com/tutorials/2676-bcdedit-how-use.html
For example, here is my boot configuration:

Microsoft Windows [Version 6.1.7100]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\system32>bcdedit
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=D:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {dfa4d7f0-ee22-11dd-9151-80c0e23d2d5c}
displayorder            {current}
                        {dfa4d7ed-ee22-11dd-9151-80c0e23d2d5c}
                        {10b463b1-edca-11dd-b04d-b24914808d20}
                        {3fe3de61-ed67-11dd-ade0-981e9c5a65a3}
toolsdisplayorder       {memdiag}
timeout                 10
Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             W7 RC 7100 64-bit
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {dfa4d7f2-ee22-11dd-9151-80c0e23d2d5c}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {dfa4d7f0-ee22-11dd-9151-80c0e23d2d5c}
nx                      OptIn
Windows Boot Loader
-------------------
identifier              {dfa4d7ed-ee22-11dd-9151-80c0e23d2d5c}
device                  partition=F:
path                    \Windows\system32\winload.exe
description             W7 RC 7100 32-bit
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {dfa4d7ee-ee22-11dd-9151-80c0e23d2d5c}
recoveryenabled         Yes
osdevice                partition=F:
systemroot              \Windows
resumeobject            {dfa4d7ec-ee22-11dd-9151-80c0e23d2d5c}
nx                      OptIn
Windows Boot Loader
-------------------
identifier              {10b463b1-edca-11dd-b04d-b24914808d20}
device                  partition=E:
path                    \Windows\system32\winload.exe
description             Windows Vista Ultimate 64-bit SP1
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=E:
systemroot              \Windows
resumeobject            {10b463b2-edca-11dd-b04d-b24914808d20}
nx                      OptIn
Windows Boot Loader
-------------------
identifier              {3fe3de61-ed67-11dd-ade0-981e9c5a65a3}
device                  partition=D:
path                    \Windows\system32\winload.exe
description             Windows Vista Home Premium 32-bit SP1
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=D:
systemroot              \Windows
resumeobject            {3fe3de62-ed67-11dd-ade0-981e9c5a65a3}
nx                      OptIn
C:\Windows\system32>

If I wanted to remove my W7 RC 7100 32-bit from the menu, I would type the following:

bcdedit /delete {dfa4d7ed-ee22-11dd-9151-80c0e23d2d5c}

Note that you will need to substitute the correct identifier string from YOUR system.

 

[Tram 1]

Great Dwarf and thanks.

 

[Tram 1]

Hi Dwarf,

Here is a screen shot of my boot configuration, are you able to tell if I have an issue with my boot loadings from the attached.

I suspect it is the 1st boot loader entry I need to alter or delete, do I need to delete the whole entry or just a line in it.

You wrote "Note that you will need to substitute the correct identifier string from YOUR system."

I'm a little confused by this, if I delete the whole or a single line of the 1st entry do, I need to substitute with anything?

Before taking screen shot, I disconnected my external HD, I guess this was ok to do.

 

[Dwarf]

Hi Tram 1,

Having viewed your image, and compared it to the relevant part of mine, I think that I can see where the trouble is. I've highlighted it in the image below.

This would seem to indicate that the boot manager was in fact installed on the HDD that you removed from your system. To correct this, type the following:

bcdedit /set {bootmgr} device partition=C:

 

[Tram 1]

Hi Tram 1,

Having viewed your image, and compared it to the relevant part of mine, I think that I can see where the trouble is. I've highlighted it in the image below.
View attachment 12358
This would seem to indicate that the boot manager was in fact installed on the HDD that you removed from your system. To correct this, type the following:

bcdedit /set {bootmgr} device partition=C:

Hi Dwarf,

Are you saying open command prompt delete the high lighted entry/line and type/replace it with bcdedit /set {bootmgr} device partition=C:

OR

are you saying open command prompt and at the curser type, bcdedit /set {bootmgr} device partition=C:

 

[Dwarf]

Hi Tram 1,

The latter option,

open command prompt and at the curser type, bcdedit /set {bootmgr} device partition=C:

 

[Tram 1]

Hi Tram 1,

The latter option,

Thanks Dwarf,

Would you check the attatched.

Questions, why does it still show 2 boot loaders, can I despense/delete top one all together, is this advisable and how do I do this?

At the bottom of the 2nd boot loader, last line, it says "system 32, I thought Windows 7 was a 64 bit system, I'm curious as to why it shows 32?

 

[Dwarf]

Hi Tram 1,

That looks better. Is it booting up any better?

As regards your question about system32, don't worry about it, as that is the correct name. Many programs use files that are found in this folder, and if it was renamed then a lot of them will not work without extensive re-writing of the code.

To answer your other question, it is NOT showing 2 boot loaders. You have a Boot Manager and this is followed by 1-4 Boot Loader(s).

 

[Tram 1]

Hi Tram 1,

That looks better. Is it booting up any better?

As regards your question about system32, don't worry about it, as that is the correct name. Many programs use files that are found in this folder, and if it was renamed then a lot of them will not work without extensive re-writing of the code.

To answer your other question, it is NOT showing 2 boot loaders. You have a Boot Manager and this is followed by 1-4 Boot Loader(s).

Hi Dwarf,

Thank you very much for the advise, it has helped so much and another learning curve for me, I had a feeling it was something else and not a clue where to start.

I had never seen or heard of bcdedit until your reply to me today.


I had last night been playing with the bios and I posted a thread today about my bios settings and I got some advise as I did from Enzo and Skunkmash here, I knocked a few seconds off boot, got it down to 87 seconds, steady.

But by far the advice and help you gave me has knocked spots off the boot time, much, much, much better and now between 45 and 51 seconds.

It still hangs, I think or maybe I expect to much but stone me, what a massive improvement, thank you.

I played yesterday with BVs RC1 suggestions, in fact I did the whole damn lot and manged to slow the system even further, I went for broke and didn't get any where but lessons learned but as I wrote I can see there are services I can disable or set to manual, so I'm going to have other goes with BV.

25 seconds is my target, start to desk top if that's at all possible.

Much appreciated Dwarf, thanks.