Discussion Locked

Windows 2000 Server boot problem

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I was updating my server (Win2k Domain Server) with Service Pack4, during the updation process, the server started dumping and from then on it is rebooting continuously on win 2k server screen loading.

I applied the help posted in the site given below:

http://www.jsifaq.com/SUBA/tip0100/rh0182.htm

from then on i am getting this error with a crash dump.
STOP: c00000135 unable to locate DLL.
The dynamic link library winsrv could not be found in the specified Default local path.

Pl help, its urgent.
Regards,
Vivek

3 replies

by aliz

me too get the same problem on installing the sp4
on my web server.
and i reinstalled the windows 2000

but i had another problem that my partition (NTFS)had damaged and is recognized on fat16!?

by dmiles

CAUSE
This error can occur for any of the following reasons:

File_name.dll is missing from the %SystemRoot%\system32 directory.
Your computer is loading the Sermouse.sys file.
If File_Name.dll exists, the software hive may be corrupted and, therefore, cannot load.
RESOLUTION
The method for checking whether File_name.dll exists varies, depending on the file system in use.

For NTFS file systems, install a parallel copy of Windows NT into an unused directory, and then verify that File_name.dll exists in the %SystemRoot%\System32 directory.

If the file exists, it is possible that the registry software hive has been corrupted. Check the integrity of the software hive by using the following procedure:

For information about how to edit the registry, view the "Changing Keys And Values" online Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" online Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

NOTE: In every case tested in which the software hive could not be loaded, the File_name was Winsrv.dll.

From a parallel installation of Windows NT, click Start, and then click Run.
In the dialog box, type Regedt32.
On the toolbar for Registry Editor, click Window, and then click the window with the following name:
HKEY_LOCAL_MACHINE ON LOCAL MACHI
Select the HKEY_LOCAL_MACHINE key in the left pane of the window.
On the menu bar, click Registry, and then click Load Hive.
Browse to %SystemRoot%\System32\config, where %SystemRoot% is the correct installation of Windows NT that you want to check.
Click the file named Software. In Windows NT 4.0, this will be the file named Software that does not have an extension, and has a generic Windows icon next to it, not the file with the Notepad icon.
The hive is corrupted if you receive the following error message:

by tlath1972

When the machine is booting, hit the "F8" key, and then select "Enable Logging"; reboot, and then, when the machine reboots again, hit the "F8" key again, and select "Last known good configuration".
Boot to the 2000 CD and run a repair. Go through the regular install process untill you get to the option to either install or repair.

OR

This should get you into Windows, and then you can examine the log file to determine what component is causing the issue, and either remove it or correct the issue.

OR

If that doesn't work try taking out the network card or some of the hardware not needed with the computer.

This discussion is closed to new replies.