Startup Failure

Hi.

The last couple of days I had a few times a startup error.

It said something like Windows couldn't start normally.

Run Startup Recovery (Recommended)
Start Windows Normally

I did the Startup Recovery and then it worked again but the next day or so
the same thing, otherwise my system runs fine.
Please give a hand here to get to the grounds of it.

Thanks in advance,

Tommy wrote:

> Hi.
>
> The last couple of days I had a few times a startup error.
>
> It said something like Windows couldn't start normally.
>
> Run Startup Recovery (Recommended)
> Start Windows Normally
>
> I did the Startup Recovery and then it worked again but the next day or so
> the same thing, otherwise my system runs fine.
> Please give a hand here to get to the grounds of it.

This could be caused by hardware or software. There isn't any way for people
reading your post to tell.

To eliminate software as the cause, look in Event Viewer for clues and also
try clean-boot troubleshooting.

Start Orb>Search box>type: eventvwr.msc

How to troubleshoot a problem by performing a clean boot in Windows Vista -
http://support.microsoft.com/default...b;EN-US;929135

For hardware, here are some general hardware troubleshooting steps. Without
knowing anything about your computer, I can't be more specific:

http://www.elephantboycomputers.com/...ardware_Tshoot

Malke
--
MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!

........thanks for your reply.
Where exactly do I have to check for an error report in the event viewer?
I don't think that it has something to do with hardware because there isn't
anything new.
Anyway, if I know where to look for an error report in the event viewer I
might find out what is causing all this of a sudden.

Thanks again.......Tommy.......

"Malke" wrote:

> Tommy wrote:
>
> > Hi.
> >
> > The last couple of days I had a few times a startup error.
> >
> > It said something like Windows couldn't start normally.
> >
> > Run Startup Recovery (Recommended)
> > Start Windows Normally
> >
> > I did the Startup Recovery and then it worked again but the next day or so
> > the same thing, otherwise my system runs fine.
> > Please give a hand here to get to the grounds of it.
>
> This could be caused by hardware or software. There isn't any way for people
> reading your post to tell.
>
> To eliminate software as the cause, look in Event Viewer for clues and also
> try clean-boot troubleshooting.
>
> Start Orb>Search box>type: eventvwr.msc
>
> How to troubleshoot a problem by performing a clean boot in Windows Vista -
> http://support.microsoft.com/default...b;EN-US;929135
>
> For hardware, here are some general hardware troubleshooting steps. Without
> knowing anything about your computer, I can't be more specific:
>
> http://www.elephantboycomputers.com/...ardware_Tshoot
>
> Malke
> --
> MS-MVP
> Elephant Boy Computers
> www.elephantboycomputers.com
> Don't Panic!
>

Tommy wrote:

> .......thanks for your reply.
> Where exactly do I have to check for an error report in the event viewer?
> I don't think that it has something to do with hardware because there
> isn't anything new.
> Anyway, if I know where to look for an error report in the event viewer I
> might find out what is causing all this of a sudden.

Did you run Event Viewer like I suggested? Because if you had, the answer
would be self-evident! Run Event Viewer and click on the items in the
left-hand pane. Look through the items on the right-hand pane and see if
anything is marked with a red Warning X or yellow Exclamation.

As for your idea that hardware couldn't be the cause because nothing is new,
that is spurious reasoning. Hardware fails. Real troubleshooting requires
being systematic and deductive, not guessing or assuming.

If you can't do the troubleshooting yourself - and there is absolutely no
shame in admitting this isn't your cup of tea because we all have our areas
of expertise - then take the machine to a local computer professional. This
will not be someone at a BigComputerStore/GeekSquad type of place.

Malke
--
MS-MVP
Elephant Boy Computers
www.elephantboycomputers.com
Don't Panic!

Maybe this will help you get started. It helps to know what time and date
the error occurs. That way you can search for the error by looking for
errors that are close to that time. This link is a video that helps
understand just a little bit of Event Viewer.

http://youtube.com/watch?v=mcjCKMMb7_Y&feature=user

Mark


"Tommy" <> wrote in message
news:9F508C94-3E24-489E-AFFA-...
> Hi.
>
> The last couple of days I had a few times a startup error.
>
> It said something like Windows couldn't start normally.
>
> Run Startup Recovery (Recommended)
> Start Windows Normally
>
> I did the Startup Recovery and then it worked again but the next day or so
> the same thing, otherwise my system runs fine.
> Please give a hand here to get to the grounds of it.
>
> Thanks in advance,

........Malke, thanks again for the quick reply.
I know how to perform the selective startup but I don't see how this could
help because the PC starts 9 out of 10 times without a problem.
If there would be a startup problem all the time, selective startup would be
ok to eliminate the problem but not in this case I think.
Please correct me if I'm wrong.
The only thing I found in the event viewer under administrative events was
this:

The following boot-start or system-start driver(s) failed to load:
BTHidMgr

Maybe this gives you an idea what is causing it.
By the way, if the error was present and I choose Start Windows Normally
instead of Run Startup Recovery (Recommended) the system was starting but
then on the next boot the error screen was there again.
Not if I choose Run Startup Recovery (Recommended), in this case evrything
was ok again for a while but then out of a sudden I got the startup error
again.
I do appreciate your help and hope you can help me a little further......




"Malke" wrote:

> Tommy wrote:
>
> > .......thanks for your reply.
> > Where exactly do I have to check for an error report in the event viewer?
> > I don't think that it has something to do with hardware because there
> > isn't anything new.
> > Anyway, if I know where to look for an error report in the event viewer I
> > might find out what is causing all this of a sudden.
>
> Did you run Event Viewer like I suggested? Because if you had, the answer
> would be self-evident! Run Event Viewer and click on the items in the
> left-hand pane. Look through the items on the right-hand pane and see if
> anything is marked with a red Warning X or yellow Exclamation.
>
> As for your idea that hardware couldn't be the cause because nothing is new,
> that is spurious reasoning. Hardware fails. Real troubleshooting requires
> being systematic and deductive, not guessing or assuming.
>
> If you can't do the troubleshooting yourself - and there is absolutely no
> shame in admitting this isn't your cup of tea because we all have our areas
> of expertise - then take the machine to a local computer professional. This
> will not be someone at a BigComputerStore/GeekSquad type of place.
>
> Malke
> --
> MS-MVP
> Elephant Boy Computers
> www.elephantboycomputers.com
> Don't Panic!
>

........hi Mark.
Thanks to you too for the video tutorial but I think I allready found the
entry in the event viewer but can't figure out what to do with it yet.
The entry says;

The following boot-start or system-start driver(s) failed to load:
BTHidMgr

Any idea what to do with that info...?...

"Mark" wrote:

> Maybe this will help you get started. It helps to know what time and date
> the error occurs. That way you can search for the error by looking for
> errors that are close to that time. This link is a video that helps
> understand just a little bit of Event Viewer.
>
> http://youtube.com/watch?v=mcjCKMMb7_Y&feature=user
>
> Mark
>
>
> "Tommy" <> wrote in message
> news:9F508C94-3E24-489E-AFFA-...
> > Hi.
> >
> > The last couple of days I had a few times a startup error.
> >
> > It said something like Windows couldn't start normally.
> >
> > Run Startup Recovery (Recommended)
> > Start Windows Normally
> >
> > I did the Startup Recovery and then it worked again but the next day or so
> > the same thing, otherwise my system runs fine.
> > Please give a hand here to get to the grounds of it.
> >
> > Thanks in advance,
>
>
>

I don't know how to fix it but it has to do Bluetooth.

Mark

"Tommy" <> wrote in message
newsCAF19F7-D30A-49F4-BD8B-...
> .......hi Mark.
> Thanks to you too for the video tutorial but I think I allready found the
> entry in the event viewer but can't figure out what to do with it yet.
> The entry says;
>
> The following boot-start or system-start driver(s) failed to load:
> BTHidMgr
>
> Any idea what to do with that info...?...
>
> "Mark" wrote:
>
>> Maybe this will help you get started. It helps to know what time and date
>> the error occurs. That way you can search for the error by looking for
>> errors that are close to that time. This link is a video that helps
>> understand just a little bit of Event Viewer.
>>
>> http://youtube.com/watch?v=mcjCKMMb7_Y&feature=user
>>
>> Mark
>>
>>
>> "Tommy" <> wrote in message
>> news:9F508C94-3E24-489E-AFFA-...
>> > Hi.
>> >
>> > The last couple of days I had a few times a startup error.
>> >
>> > It said something like Windows couldn't start normally.
>> >
>> > Run Startup Recovery (Recommended)
>> > Start Windows Normally
>> >
>> > I did the Startup Recovery and then it worked again but the next day or
>> > so
>> > the same thing, otherwise my system runs fine.
>> > Please give a hand here to get to the grounds of it.
>> >
>> > Thanks in advance,
>>
>>
>>

"Tommy" <> wrote in message
newsCAF19F7-D30A-49F4-BD8B-...
> .......hi Mark.
> Thanks to you too for the video tutorial but I think I allready found the
> entry in the event viewer but can't figure out what to do with it yet.
> The entry says;
>
> The following boot-start or system-start driver(s) failed to load:
> BTHidMgr
>
> Any idea what to do with that info...?...
>
> "Mark" wrote:
>
>> Maybe this will help you get started. It helps to know what time and date
>> the error occurs. That way you can search for the error by looking for
>> errors that are close to that time. This link is a video that helps
>> understand just a little bit of Event Viewer.
>>
>> http://youtube.com/watch?v=mcjCKMMb7_Y&feature=user
>>
>> Mark
>>
>>
>> "Tommy" <> wrote in message
>> news:9F508C94-3E24-489E-AFFA-...
>> > Hi.
>> >
>> > The last couple of days I had a few times a startup error.
>> >
>> > It said something like Windows couldn't start normally.
>> >
>> > Run Startup Recovery (Recommended)
>> > Start Windows Normally
>> >
>> > I did the Startup Recovery and then it worked again but the next day or
>> > so
>> > the same thing, otherwise my system runs fine.
>> > Please give a hand here to get to the grounds of it.
>> >
>> > Thanks in advance,
>>
>>
>>

Seems to be Bluetooth related.
BTHidMgr is Bluetooth HD Manager.

Chris

On Sun, 27 Apr 2008 08:08:00 -0700, Tommy
<> wrote:

>.......Malke, thanks again for the quick reply.
>I know how to perform the selective startup but I don't see how this could
>help because the PC starts 9 out of 10 times without a problem.
>If there would be a startup problem all the time, selective startup would be
>ok to eliminate the problem but not in this case I think.
>Please correct me if I'm wrong.
>The only thing I found in the event viewer under administrative events was
>this:
>
>The following boot-start or system-start driver(s) failed to load:
>BTHidMgr

Time to go to the toolbox. Download AutoRuns and learn more about it
here:

http://technet.microsoft.com/en-us/s.../bb963902.aspx

What a lot of people don't know is Windows doesn't always start up the
same way. The more complex your system the more likely different
drivers get loaded into memory in a different sequence. Sometimes a
particular driver don't load at all. Either can cause random errors
while other times things work fine. Also a ton of junk can get loaded
at startup. Much of it you don't need and worse probably aren't even
aware of.

What AutoRuns does better than anything I've found is generate a
comprehensive report. A REALLY comprehensive report! This may give
clues to why sometimes things don't work or go bump in the night. It
is also a great tool to help customize your system and just maybe for
the first time understand why it takes so damn long to boot your
system. A hell of lot of things are going on BEFORE you hear that
Windows greeting sound that suppose to tell you things are peachy.

This isn't for the faint of heart. Grab a cup of coffee and really
study the results. Since AutoRuns comes as a compressed file you'll
need WinRAR or a similar tool to uncompress the contents.

Once you do drag the column boundaries to expand columns so you can
more easily read. To use, once uncompressed just click on AutoRuns in
the folder you uncompressed to. There is nothing to install. Runs as
soon as it is uncompressed once clicked on. Works with all versions of
Windows including Vista.

The default setting is to show everything. A bit overwhelming. You can
limit contents by clicking on the various tabs like Logon and
Scheduled Tasks until you get more comfortable with it.

Finally AutoRuns confirms what I've been saying. Vista is a
exceedingly complex load of code. THAT in part is why it is prone to
crash from so many different things. This tool shows you some of the
"why" that's true.