Re: After Updates, StartUp Menu F8 on boot not working

"Galen" <galennews@xxxxxxxxx> wrote in message
news:%23s7uIZJ5FHA.2816@xxxxxxxxxxxxxxxxxxxxxxx
> In news:a%Ubf.120490$Ph4.3704836@xxxxxxxxxxxxxxxxxxxxxxx,
> Dugie <d_fren@xxxxxxxxxxxxxxxxx> had this to say:
>
> My reply is at the bottom of your sent message:
>
> > "Galen" <galennews@xxxxxxxxx> wrote in message
> > news:%23fwaL534FHA.1536@xxxxxxxxxxxxxxxxxxxxxxx
> >> In news:IRvbf.119926$Ph4.3683085@xxxxxxxxxxxxxxxxxxxxxxx,
> >> Dugie <d_fren@xxxxxxxxxxxxxxxxx> had this to say:
> >>
> >> My reply is at the bottom of your sent message:
> >>
> >>> "Galen" <galennews@xxxxxxxxx> wrote in message
> >>> news:%23hpCnoo4FHA.1476@xxxxxxxxxxxxxxxxxxxxxxx
> >>>> In news:Rtebf.119617$Ph4.3669673@xxxxxxxxxxxxxxxxxxxxxxx,
> >>>> Dugie <d_fren@xxxxxxxxxxxxxxxxx> had this to say:
> >>>>
> >>>> My reply is at the bottom of your sent message:
> >>>>
> >>>>> "Galen" <galennews@xxxxxxxxx> wrote in message
> >>>>> news:epWa3Wn4FHA.2676@xxxxxxxxxxxxxxxxxxxxxxx
> >>>>>> In news:S2dbf.119587$Ph4.3668637@xxxxxxxxxxxxxxxxxxxxxxx,
> >>>>>> Dugie <d_fren@xxxxxxxxxxxxxxxxx> had this to say:
> >>>>>>
> >>>>>> My reply is at the bottom of your sent message:
> >>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> I hope someone can help.
> >>>>>>>
> >>>>>>> Win 2K Pro, SP4.
> >>>>>>> After installing all 10 of the latest from Win Update, I noticed
> >>>>>>> that pressing F8 at boot doesn't work. It worked fine before the
> >>>>>>> updates. Everything else
> >>>>>>> seems ok.
> >>>>>>>
> >>>>>>> When pressing F8, at times the screen will flash the Startup
> >>>>>>> Menu, but the boot continues.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Dugie
> >>>>>>
> >>>>>> What does your boot.ini look like? Copy/paste it into a response
> >>>>>> to this if you want.
> >>>>>>
> >>>>>> --
> >>>>>> Galen - MS MVP - Windows (Shell/User & IE)
> >>>>>> http://dts-l.org/
> >>>>>>
> >>>>>> "A man should keep his little brain attic stocked with all the
> >>>>>> furniture that he is likely to use, and the rest he can put away
> >>>>>> in the lumber-room of his library where he can get it if he
> >>>>>> wants it."
> >>>>>>
> >>>>>> Sherlock Holmes
> >>>>> Boot.ini:
> >>>>>
> >>>>> [boot loader]
> >>>>> timeout=40
> >>>>> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> >>>>> [operating systems]
> >>>>> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
> >>>>> Professional" /fastdetect
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> Dugie
> >>>>
> >>>> That looks to be okay by my reckoning? Hmm... Curious... What
> >>>> happens if you try to force it by editing the boot.ini?
> >>>>
> >>>> http://support.microsoft.com/?kbid=239780
> >>>>
> >>>> --
> >>>> Galen - MS MVP - Windows (Shell/User & IE)
> >>>> http://dts-l.org/
> >>>
> >>> Not sure what can be forced. What would you suggest to forcc?
> >>>
> >>> I visited the http://support.microsoft.com/?kbid=239780 link. It's
> >>> not simple. :-) Explanations for the switches are minimal.
> >>> I'll try /safeboot:minimal /sos /bootlog /noguiboot and leave
> >>> /fastdetect in place. It's a home computer with no networking. Also
> >>> backed up my boot.ini file.
> >>>
> >>> Thanks!
> >>> Dugie
> >>
> >> When you use the sample boot.ini file provided on the page does it
> >> boot into safe mode? I'm basically trying to see what solutions
> >> there are to offer you because, well, I'm not sure of the reason
> >> that this has happened. It's something I've not seen before and when
> >> I try to find an answer for you via the normal search routines I
> >> come up with nothing specific though it could be that I'm just using
> >> flawed search terms. <g>
> >>
> >> --
> >> Galen - MS MVP - Windows (Shell/User & IE)
> >> http://dts-l.org/
> >>
> >
> > Hi Galen,
> >
> > When I tried the switches above:
> > /safeboot:minimal /sos /bootlog /noguiboot /fastdetect
> >
> > I got a blue screen:
> > STOP: 0x0000000A (0xEB915354,0X000000FF,0x00000001,0x804640791)
> > IRQL_NOT_LESS_OR_EQUAL
> > Address 80464079 base at 80400000, Date Stamp 427b58bb - ntoskrnl.exe
> >
> > Took me a while to remember to use the Recovery Console to ren the
> > old .ini so I could boot. :-(
> >
> > My C: drive is a fairly new WD 160GB, so I'm using Western Digital's
> > Dynamic Drive Overlay v9.85. Using only 128G (binary?), since I don't
> > trust the overlay... yet. Other drives: 20G & 30G. Machine is 902Mhz.
> >
> > I'll try the sample file & report results, assuming it's:
> > [boot loader]
> > timeout=30
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
> > Advanced Server" /fastdetect /SAFEBOOT:MINIMAL(ALTERNATESHELL)
> >
> > I won't be around for a few days.
> > If an MVP is having problems researching this, I don't feel so badly
> > about finding no solutions. :-)
> >
> > Thanks for your suggestions and help!
> >
> > Dugie
>
> Hmm... A BSOD... Well that throws a monkey wrench into it.
>
> Here's general information on your error?
> http://support.microsoft.com/default.aspx?scid=kb;en-us;130802
>
> I'd say that it's time to go back and double check to make sure the
updates
> (these specific ones) did this... I'd then also consider rooting about for
> driver issues - what drivers (I'd actually start with video on this one I
> think) might need to be updated after having done the recent updates at
> Microsoft?
>
> So, this is where I'd go if this was on my system. I'd start by going to
the
> manufacturer's sites and looking for drivers. I guess I'd start with the
> video drivers. You mentioned no networking - surely there's some form?
Even
> if it's just internet - 'tis still a network... Or is this really a
> completely disconnected PC without the internet at all? If so is there a
NIC
> in it? Does the behavior change if you disable the device?
>
> If that's no go then, well, you can try disabling any BIOS caching though
> that issue was meant to be fixed in SP3 and tended to show up in multi-CPU
> server type computers. It's worth a shot at any rate.
>
> Assuming, and at this point I am, then I'd start removing the most recent
> updates. Start by removing all of them. Reboot and try safe mode. Does it
> work? No? Then we know it's not the updates? Yes... Well, this is going to
> be a lot like fun... Install them one by one until it breaks again. When
you
> find the one that breaks it you're entitled to free support. Give 'em a
> call... <g> Really, at the least let us know what's going on.
>
> I've gone ahead and dug down to the "best" information I could find on the
> subject at the Microsoft site. This link should take you there for what
it's
> worth... (Yes, I have no social life and have no been sitting here typing
> this response (though it's not much - most of the time was spent doing
> additional searches hoping I'd find something I'd already missed) for a
> couple of hours. Feel free to take a look, as it's your system there's a
lot
> more that might make sense to you than will to me because you'll perhaps
> know something about it that I am not aware of.
>
>
http://search.microsoft.com/search/results.aspx?View=en-us&p=1&s=0&c=3&st=a&qu=0x0000000A&qp=windows+2000&swc=3&na=33&cm=512
>
> I'm not sure what effect you're going to get with the alternate boot.ini,
> I'm glad you were able to remember how to use RC to restore the backup. I
> generally make it a point to make a boot.ini backup on any system. I don't
> suppose this is that interesting to anyone but a geek but in the process
of
> searching I did stumble across this site (note that this hasn't a darned
> thing to do with your problem but it might give you something to read
while
> you're fuming) that has managed to make it's way into my bookmarks now:
>
> http://www.dewassoc.com/support/win2000/setupwin2000.htm
>
> Anyhow, I have no social life so don't mind putting in more hours. I'd
give
> the above a try and see what you come up with.
>
> --
> Galen - MS MVP - Windows (Shell/User & IE)
> http://dts-l.org/

Hi Galen,

By installing the Recovery Console on my hd, I now have access to the F8
boot choice menu. It's a workaround for the original problem. :-)
I've updated my video driver (dated 2002) from the manufacture's site. Next
to update are the Realtek RTL8139/810x Family Fast Ethernet NIC, and
Efficient Networks Enternet P.P.P.o.E Adapter. So I do have a network. :-)
My computer and the web.
Also checked those sites you gave, but saw nothing to help. The
setupwin2000.htm page is saved, will take some time to read.

Results so far, using the boot.ini you suggested:
- Safe mode still gives the BSOD, same variables.
- Disabling both CPU Internal & External Caching in the BIOS, Safe mode
starts, then freezes on the "Windows is starting up" screen, after waiting
10 minutes. No BSOD.
- Enabling CPU Cache, disabling only External, Safe Mode starts, then gives
a BSOD.
- Enabling the External Cache, disabling only the CPU Internal cache, Safe
Mode freezes as above on the "Windows is starting up" screen. No BSOD.

I haven't yet tried disabling my NIC.
I'm assuming that getting Safe Mode to work is important.

Dugie

P.S. Can we <snip> some of the older parts of messages on replying?

.

Relevant Pages

  • Re: File Dumping, and Blue Screen of Death
    ... if the PC will run in safe mode for a good period of time without ... crashing, and not in normal mode, this is because a lot of the devices ... aren't loaded i.e. your video drivers, network drivers, audio drivers, etc. ... When you say "most recent updates" does that mean most of the recent ...
    (microsoft.public.win2000.general)
  • RE: Stop:0X0000007E
    ... I couldnt find any updated drivers for it on the Promise ... After installing SP2 I receive the following BSOD ... > 4) Disabling services that were not started up in Safe mode and then trying ...
    (microsoft.public.windowsupdate)
  • Protection Stub
    ... I've been trying to play Fable: the lost chapters in Windows Vista Ultimate, ... I have the latest drivers and updates for it, and I also tried disabling the ...
    (microsoft.public.windowsxp.games)
  • Re: Same Problem - My computer will only run in safe mode
    ... Device drivers are what RKs *use* to invade a system. ... Once I looked at the updates I found that I did not get an Windows update the night that the computer failed to boot. ... restart in safe mode okay but I've picked restore points over a week ago and nothing changes. ...
    (microsoft.public.windowsupdate)
  • Re: My computer will only run in safe mode
    ... I've turned boot logging on and now have a 15 page file which I've printed ... Can I now load the drivers one by one manually and see which crashes the PC ... when pressing F8 to reach Safe Mode. ... my updates manually and purposely didn't update NET Framework. ...
    (microsoft.public.windowsupdate)