Startup Windows 2000 Server occur Problem

[Guest]

When I startup the Server, the Blue Screen exist. the information is as the
following:
STOP: 0x0000001E (0xC0000005,0x804A6467, 0x00000008,0x0000000B0)
KMODE_EXCEPTION_NOT_HANDLED
***Address 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe.
I can't go to Safe Mode too.
How to solve it except re-install the Server OS??

 

[Jerold Schulman]

When I startup the Server, the Blue Screen exist. the information is as the
following:
STOP: 0x0000001E (0xC0000005,0x804A6467, 0x00000008,0x0000000B0)
KMODE_EXCEPTION_NOT_HANDLED
***Address 804A6467 base at 80400000, DateStamp 427b58bb - ntoskrnl.exe.
I can't go to Safe Mode too.
How to solve it except re-install the Server OS??

Here are the documentented possible reasons and resolutions for your STOP 0x0000001E:

http://support.microsoft.com?kbid=257956 "Error Message Appears When You Restart Windows After Installation of Nero CD-Recording Software "
http://support.microsoft.com?kbid=264994 "'Stop 0x0000001E' After Installing WriteDVD#33 for Windows 2000 with Easy CD Creator "
http://support.microsoft.com?kbid=287524 "'Stop 0x0000001E' Error Message When You Mount a Volume "
http://support.microsoft.com?kbid=288602 "Windows Setup Stops Responding with the VIA Apollo KX133 Chip Set "
http://support.microsoft.com?kbid=289001 "'STOP: 0x0000001E' Error Message When You Load Windows 2000 System Registry Hive "
http://support.microsoft.com?kbid=294690 "'Stop 0x0000001E' Error Message in Ntoskrnl.exe "
http://support.microsoft.com?kbid=304245 "Hard-Coded Breakpoint Is Encountered in GetARPBuffer "
http://support.microsoft.com?kbid=329850 "You Receive a 'STOP 0x0000001E' Error Message When You Try to Log On to Your Exchange 2000 Server-Based Computer "
http://support.microsoft.com?kbid=810558 "'Stop 0x00000051 REGISTRY_ERROR' Error Message When You Back Up the Registry Hive "
http://support.microsoft.com?kbid=811014 "'STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED in NTOSKRNL.EXE' Stop Error Message After You Install PcAnywhere "

 

[J.Vana]

I have a same problem, registry restore is not correct this.
Jirka V.

 

[Guest]

Hi,
Did you install update rollup on your server prior to getting this error
message?
Lukesh

 

[sumguyb]

Here is the solution:
* Reboot off you floppies with your 2000 CD in the tray.
* If you have odd SCSI controllers press F6 when prompted on disk 1 and

after Disk 2 it will ask for the driver disk.
* Choose to repair the installtion and then choose recovery console.
If it tells you there is no drive, you needed the driver disks above.
* cd to your windows directory
* cd $NtUpdateRollupPackUninstall$
* cd spuninst
* do a dir and make sure there is spuninst.txt file in there
* use the command "batch spuninst.txt" It runs and the first 5 or so
messages may say Access Denied. That was OK for me.
* exit the recovery console by typing exit.


Reply

 

[Slarty Bartfast]

Has MS fixed this problem with the Rollup package? We had the same blue
screen.

--


Regards,

Slarty Bartfast

 

[Guest]

Hi,
Yes MS has resolved the problem with the rollup package. Once you install
the rollup package, it gives you a stop 1e because the rollup package can not
update scsiport.sys.
Boot to recovery console.
Navigate to c:\winnt\system32\drivers and rename scsiport.sys to scsiport.old
navigate to c:\winnt\$ntupdaterolluppackuninstall$ and copy scsiport.sys to
c:\winnt\system32\drivers.
Reboot and it should take you to desktop. Contact MS for the latest fix for
scsiport.sys. All the hotfixes are free cases.

Lukesh

 

[Slarty Bartfast]

Thanks Lukesh,

I got that fix from Microsoft, but I was still not able to get into Recovery
Console because 'no hard drive detected'.
No wonder if it is the HDD SCSI drivers that were corrupted.

I was able to put the crashed HDD in as a slave and get at the files there
and changed and swapped a few ie; ntosknl.exe. I didn't know at the time it
was scsiport.sys in particular that was the problem. If I did I could have
copied it over from the working HDD.
Instead we paid $300 for a five day usage of Winternals boot CD that was
able to 'roll back' the update.

--


Regards,

Slarty Bartfast


Growing old is mandatory, growing up is optional

 

[Guest]

Hi there,

i had the same stop error (0x0000001E) on 5 of my server systems (Dell
PowerEdge 500SC) after applying "Windows 2000 Hotfix Update Rollup 1" on 13th
and 14th of july.

Figured out two ways to recover this.

Solution-1:
Performa a "Windows Repair installation" using Windows 2000 Setup.
On two systems i had to do the repair installation twice.

Solution-2:
Uninstall / Remove the "Windows 2000 Hotfix Update Rollup 1" through
recovery console. 911ComputerGuy has written a very good guidance at ieXbeta
Board - thanks for that. Here is the link:
http://board.iexbeta.com/lofiversion/index.php/t56004.html

After re-applying all Windows-Updates on two machines the stop error never
came up again.

Questions:

- Has Microsoft revised the "Windows 2000 Hotfix Update Rollup 1" after
14the of july without announcement?
- Has Microsoft confirmed these issues, i haven't seen any announcements yet??

Greetings from Munich / Germany
unplugged

 

[drrconsulting]

I have the same BSOD, everything was fine until i installed some
windows updates- I guess one of them was that hotfix update rollup 1.
My server was 100% fine, i installed the windows updates, and during
that process, i got the BSOD. I reinstalled the OS fresh, did the SP4
update, then the remaining updates, and the BSOD comes again. I am
running windows 2000 server on a dell precision 610. I am going to try
911 computer guys suggestion, and see what happens.