windows 2000 advanced server recent rollup

[Chris M]

The recent rollup has caused my server not to be able to boot (windows
2000 advanced server). I get a kmode_exception_not_handled in ntoskrnl.exe

Stop: 0x0000001E (0x0000005,0x804A6467,0x00000000,0x00000000)
KMode_Exception_not_handled
Address 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe

these two links report similar or identical problems.

http://groups-beta.google.com/group...q=5.0.2195.7045&rnum=1&hl=en#631feda7eadfd08b

http://www.broadbandreports.com/forum/remark,13795318

I looked and i did notice that the ntoskrnl.exe in my system32 directory
is different from the one in my dllcache directory. the one in the
cache directory appears to be the right one. I tried with recovery
console to replace the one in my system32 directory and that just gets
my windows handing at the end of the starting windows black screen.

Does anyone have any idea how i can resolve this? manually repair the
patch, or manually uninstall the rollup?

thanks.

 

[Guest]

Hi,
Yes, this is a known issue with this roll up package. i would recommend you
to uninstall the rollup package.

Lukesh

 

[George Hester]

Any KB article on this or again are we left "trusting" everything Microsoft
wants in our puters? The old adage once burned never again really should
apply the first time.

 

[Guest]

HI,
There is no KB aricle so far but I am sure they are not gonna come up with
any KB article stating that there is something wrong with the package.
They'll probably review the package and re-publish it.

Lukesh

 

[Slart Bartfast]

Hi Chris,

We had exactly the same problem.

We ran this MS update last week;

Update Rollup 1 for Microsoft Windows 2000 Service Pack 4 that is dated June
28, 2005
Article ID : 900345
Last Review : July 8, 2005
Revision : 2.0


We have two Domain Controllers, and one of them - the FSMO GC, blue screened
with A Stop ..1E ntoskrnl.exe error.

There was no way to get out of it except when we paid $300 for a 'five day
only' version of Winternals ERD Comander. We were able to boot with the ERD
CD and 'roll back' the MS Rollup.
After that it was OK. Just to test if this was a 'one off' error, we ghosted
the Domain Controller and tried the MS Rollup again and got blue screened
again.



--


Regards,

Slarty Bartfast



Laugh alone and the world thinks you're an idiot.

 

[Chris M]

Hi Chris,

We had exactly the same problem.

We ran this MS update last week;

Update Rollup 1 for Microsoft Windows 2000 Service Pack 4 that is dated June
28, 2005
Article ID : 900345
Last Review : July 8, 2005
Revision : 2.0


We have two Domain Controllers, and one of them - the FSMO GC, blue screened
with A Stop ..1E ntoskrnl.exe error.

There was no way to get out of it except when we paid $300 for a 'five day
only' version of Winternals ERD Comander. We were able to boot with the ERD
CD and 'roll back' the MS Rollup.
After that it was OK. Just to test if this was a 'one off' error, we ghosted
the Domain Controller and tried the MS Rollup again and got blue screened
again.

I was able to uninstall the update with the spuninst.txt at the recover
console and now I'm back up and running. now I remember why I seem to
never do any updates. they scare me.

 

[George Hester]

ME TOO!

 

[Slart Bartfast]

I couldn't even get to the Recover Console.

--


Regards,

Slarty Bartfast



He that is down needs fear no fall.