.png?width=100&auto=webp&quality=80&disable=upscale "Picture of John Savill")
.png?width=400&auto=webp&quality=80&disable=upscale "John Savill")
Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
I'm getting a BSOD at startup with error C0000135.
John Savill
October 5, 1999
3 Min Read
A. There are various flavors of this Blue Screen of Death but all willhave the text:
Stop: c0000135 {Unable to Locate DLL}
The dynamic link library could not be found in the specified
path Default Load Path."The could be a number of different DLL files, a common oneis WINSRV.DLL.
There are a number of causes for this error:
File_name.dll is missing from the %SystemRoot%system32 directory.
Your laptop is loading the Sermouse.sys file.
If .dll does exists, the software hive may be corrupted and, therefore, cannot load.
If you Windows NT installation is FAT you can just boot from a floppy diskand change that the DLL it is listing as the error cause is there and if indoubt replace with the latest service pack version. If its NTFS you can eitheruse something like ERD Commander to access the NTFS drive (http://www.winternals.com)or install a parallel copy of Windows NT.
If after checking the DLL you still have problems it is likely a registryhive corruption and if WINSRV.DLL is listed as the missing DLL it is always thesoftware hive. The way to test this is to again use a parallel copy of WindowsNT and try to load each hive from your original NT installation:
Start REGEDT32.EXE
Select the HKEY_LOCAL_MACHINE on Local Machine window
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%System32config, where %SystemRoot% is the original installation of Windows NT that you want to check.
Click the file software. This will be the software file with the generic Windows icon next to it, not the file with the Notepad icon
The system will prompt for a key-name to use in loading the hive. You can type whatever you prefer in the dialogue box, for example probsoft.
The hive is corrupted if you receive the following error message:
'Registry Editor could not load the key. The file is not a valid Registry file.'
The only course of action now is to replace the problem registry hive withthe most recent backup which is your emergency repair disk:
Start the system with the Windows NT Setup disks.
At the first screen, press R for repair.
Use the arrow keys to move the cursor to Inspect Registry Files, and then press ENTER to select that option. Next, move the cursor to Continue (Perform Selected Tasks) and press ENTER.
Let Windows NT perform the mass storage detection. When prompted, select S to specify additional drivers if your computer requires OEM drivers.
When prompted to do so, insert the emergency repair disk that was originally created for this computer, or press ESC to let Windows NT search for repair information.
Setup will then ask which registry files should be replaced. Using the arrow keys, move the cursor to Software (Software Information) and press ENTER. Next, move the cursor to Continue (Perform Selected Tasks) and press ENTER.
When finished, restart your computer when Setup prompts you to do so.
About the Author
You May Also Like
.jpg?width=700&auto=webp&quality=80&disable=upscale)
