PC Review


Reply
Thread Tools Rate Thread

BSOD stop error c0000135

 
 
Joe LeDu
Guest
Posts: n/a
 
      20th Oct 2003
I ran a microsoft update a week ago and since have recv'd
the BSOD stop error c0000135. Most of the info I find is
for XP and NT. I'm using windows 2000 professional. Any
help would be appreciated.

Thanks,

Joe
 
Reply With Quote
 
 
 
 
Joseph Conway [MSFT]
Guest
Posts: n/a
 
      20th Oct 2003
Typically those are registry errors. When do you get the blue screen?
Right on boot or during operation?

Does it specify a hive?

--
Joseph W. Conway, MCSE
Windows 9x/NT/2000/XP/2003 Server Group

This posting is provided "AS IS" with no warranties, and confers no rights.

"Joe LeDu" <(E-Mail Removed)> wrote in message
news:043d01c396a7$f672f660$(E-Mail Removed)...
> I ran a microsoft update a week ago and since have recv'd
> the BSOD stop error c0000135. Most of the info I find is
> for XP and NT. I'm using windows 2000 professional. Any
> help would be appreciated.
>
> Thanks,
>
> Joe



 
Reply With Quote
 
Joe LeDu
Guest
Posts: n/a
 
      20th Oct 2003
I receive the BSOD on boot. Once the win2k splash screen
completes loading, the error appears.

Stop: c0000135 {unable to locate DLL}
The dynamic link library winsrv could not be found in the
spcifiied path Default load Path

Then it reports possible fixes.

Safe mode does not work. I tried replacing the file from
another pc and also from a copy of a win2k cd.

-Joe
(E-Mail Removed)
>-----Original Message-----
>Typically those are registry errors. When do you get the

blue screen?
>Right on boot or during operation?
>
>Does it specify a hive?
>
>--
>Joseph W. Conway, MCSE
>Windows 9x/NT/2000/XP/2003 Server Group
>
>This posting is provided "AS IS" with no warranties, and

confers no rights.
>
>"Joe LeDu" <(E-Mail Removed)> wrote in

message
>news:043d01c396a7$f672f660$(E-Mail Removed)...
>> I ran a microsoft update a week ago and since have

recv'd
>> the BSOD stop error c0000135. Most of the info I find

is
>> for XP and NT. I'm using windows 2000 professional.

Any
>> help would be appreciated.
>>
>> Thanks,
>>
>> Joe

>
>
>.
>

 
Reply With Quote
 
kwak
Guest
Posts: n/a
 
      21st Oct 2003
I went to the recovery console and backed out KB82414 and
I can now boot OK again. No more C0000135!

>-----Original Message-----
>Typically those are registry errors. When do you get the

blue screen?
>Right on boot or during operation?
>
>Does it specify a hive?
>
>--
>Joseph W. Conway, MCSE
>Windows 9x/NT/2000/XP/2003 Server Group
>
>This posting is provided "AS IS" with no warranties, and

confers no rights.
>
>"Joe LeDu" <(E-Mail Removed)> wrote in

message
>news:043d01c396a7$f672f660$(E-Mail Removed)...
>> I ran a microsoft update a week ago and since have

recv'd
>> the BSOD stop error c0000135. Most of the info I find

is
>> for XP and NT. I'm using windows 2000 professional.

Any
>> help would be appreciated.
>>
>> Thanks,
>>
>> Joe

>
>
>.
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD error c0000135 winsrv missing dceola Windows XP General 5 10th Feb 2008 09:06 PM
BSOD and STOP C0000135 with MSVCRT.DLL Error message =?Utf-8?B?VG9ueSBW?= Windows XP Setup 1 28th Mar 2007 07:54 PM
BSOD error C0000135 Andrew M. Saucci, Jr. Windows XP General 1 17th Nov 2004 05:45 AM
STOP: c0000135 error after SP2 *UNinstall*. Kim Windows XP Setup 1 2nd Nov 2004 12:39 AM
Stop error C0000135 Anguel Windows XP Setup 3 2nd Sep 2004 12:17 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 10:05 AM.