Blue Screen STOP Message C0000135 Appears at Startup
This article was previously published under Q173309 SYMPTOMS When you start Windows NT 4.0, the system stops and
displays the following message: Stop: c0000135 {Unable
to Locate DLL} The dynamic link library FILE_NAME could not be found in the specified path Default Load Path. CAUSE This error can occur for any of the following reasons:
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. For FAT File Systems, an MS-DOS installation disk can be used. 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: Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows NOTE: In every case tested in which the software hive could not be
loaded, the File_name was Winsrv.dll.
Registry Editor could not load the key.
The file is not a valid Registry file. After you have determined the
problem, there are several ways to resolve it. The software hive can be
restored by making a parallel installation from backup files. It can also be
restored from the latest emergency repair disk (ERD), using the procedure
outlined below. Note: Windows NT 4.0 requires the Setupdd.sys file to be copied to disk 2 of the Windows NT Setup disks to perform this repair without a CD-ROM. This file can be found in Service Pack 2 or later. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 150497 (http://support.microsoft.com/kb/150497/EN-US/)
How to Repair Windows NT System Files Without a CD-ROM Attached
146887 (http://support.microsoft.com/kb/146887/EN-US/)
Repairing Windows NT After the Application of Service Pack 3
129037 (http://support.microsoft.com/kb/129037/EN-US/) Windows NT 3.5x and 4.0 Emergency Repair Process Screens
148262 (http://support.microsoft.com/kb/148262/EN-US/) Removing Windows NT 3.51 SP4 or SP5 May Cause Logon Failures
103280 (http://support.microsoft.com/kb/103280/EN-US/) Using an Emergency Repair Disk Created by Windows NT
150947 (http://support.microsoft.com/kb/150947/EN-US/) How to Repair Windows NT System Files Without a CD-ROM Attached
APPLIES TO
| Article Translations
|

Back to the top
