Windows 2000 Service Pack 4

  • Thread starter Thread starter Mike T.
  • Start date Start date
M

Mike T.

Dear Microsoft,

I tried to install "Windows 2000 Service Pack 4 Express
Install for End Users" twice and received the following
blue screen message during bootup:

"
*** STOP: 0x0000080A
(0xBAD0BC,0x00000FF,0x00000000,0x80416B67)
IRQL_NOT_LESS_OR_EQUAL

*** Address 80416B67 base at 80400000, DateStamp 3ee6c002 -
ntoskrnl.exe

If this is the first time you've seen this Stop error
screen, restart your computer. If this screen appears
again, follow these steps:

Check to make sure any new hardware or software is
properly installed. If this is a new installation, ask
your hardware or software manufacture for and Windows 2000
updates you might need.

If problems continue, disable or remove any newly
installed hardware or software. Disable BIOS memory
options such as caching or shadowing. Check your hard
drive to make sure it is properly configured and restart
your computer, press F8 to select Advanced Startup
Options, and then select Safe Mode.

Refer to your Getting Started manual for more information
on troubleshooting Stop errors."



I tried to recover from this error using your standard
boot-up recovery procedures (F8); but was unsuccessful.
Thank God, I had Norton Ghost backup to recover my image.

What's up with this error? Please advise.

Thanks,
Mike
 
I've had the same blue scren installing SP4 Express on my
computer.
I presume that the error come from the module ntoskrnl.
I found no reference in the knowledge base.
My solution was to uninstall SP4 (by the mean of F8
function).
Who can help us ?
Thanks.
 
I got into the same problem, still trying to look for an
answer. Any help would be greatly appreciated.

Regards,

KB
 
Hey! I think I know this one!

Service Pack 4 updates a LOT of core drivers and such...

One of those it updates is "ATAPI.SYS" you know, the file
that lets your hard drive and windows talk to each other.

Unfortunately an old motherboard/BIOS/Hardrive combo may
not be compatable with this NEW version they so
thoughtfully included in the Service Pack!

What I did, was to go to the original CD for Win2K, and
did a search for this file in the CAB files, I extracted
it out to my root directory, then after Service Pack 4
loads, and it gets to the "STOP" error, I throw in an old
boot disk, and copy the old file (over the top of the
undoubtably nicer, but unusable new one), to the following
location:

C\WINNT\system32\drivers\atapi.sys

actually, I wrote a batch file for this
called: "FixBillsSP4"
reads like this: (watch for wrap it's all on one line)

copy /v /y /b c\atapi.sys c\WINNT\system32
\drivers\atapi.sys

saved it and ATAPI.SYS in my root as FixBillsSP4.bat , and
now I just automatically toss in the boot disk, and while
at the DOS Prompt, type in "FixBillsSP4"

It is so common, with all my older systems, that when I
was called upon to groom my sisters Dell Latitude (older,
2nd hand of course - us not being in the 'get a new PC
with every OS Upgrade' crowd, I automatically copied her
old ATAPI.SYS file to HER root, and wrote the batch file.

MUCH to my surprise, I didnt get that normal (to me) Blue
Screen of Death, instead, I get this oh so fascinating,
cylclic restart, with no end in sight. cant even get it
to boot with a boot disk, hence my presence here tonight.

Am thinking I will have to reload Win2K from scratch, and
all the associated hassles with trying to find Dell's
Hardware drivers without one of their premium Dear to Your
Wallet service plans.

anyway, any of you allhear anything about this restart
thing, please drop me a line at: (e-mail address removed)

thanks

metatron
 
Yeah.. they should just quit with the service packs and only issue new OSes
or hotfixes if there is something wrong. A service pack is too
comprehensive of a change of the OS without enough safety measures in place
to be advisable. See my new post "Service Packs and Uninstalling."
 
I try your solution but it doesn't work.
But, it gives me a track. I suspected my graphic card 3dfx
Voodoo5 to create the problem.
So I uninstalled it by the config panel starting the W2K
with the low resolution of W2K standard.
I applied W2K SP4 and ignored the new material at the
startup.
W2K SP4 has started ok.
I then installed the 3dfx Voodoo5 drivers.
Magic, the system is now OK.
 
Back
Top