BSOD error c0000135 winsrv missing

[dceola]

Hi, and thanks in advance for any assistance anyone can provide.

I am running Windows XP x64, with an AMD cpu, Asus motherboard - and the
part that really really makes me want to not reload the os - two identical
hdd's setup on a stripe raid.

This morning, i awoke to my computer being off (was on when i went to bed
lastnight), my backup power supply beeping, and the 2nd computer hooked to
the same ups still running.

Upon turning on the computer in question, it proceeded to reboot itself
everytime it got just past the screen which showed the windows xp x64 logo.

I tried to load in safe mode (normal, w/ networking, and w/ cmd prompt).
Tried to boot to 'last known config', and booted once with 'disable auto
reboot on system error' (which is how i received my error message).

The system gave me the BSOD w/ stop error c0000135 .... winsrv is missing or
corrupt.

I have searched the net for a while, and thus far have only found info on
this related to having just instapped SP2. My computer is currently up to
date w/ all avail patches and fixes from the windows update page; and since
it has been quite some time since SP2 was installed, i feel certain that this
is not related to my problem.


I have read some things that indicate that running the recovery console off
of my xp install CD would somehow allow me to fix this; however i have no
experience with the recovery console.

Any suggestions on what / how I can fix this, without having to reload my OS
and losing 300+ gigs worth of my data???

 

[dceola]

RE: BSOD error c0000135 winsrv missing

Oh, and also- i have a system restore point created as recently as yesterday
- so if there is a way to restore to that, from a dos / command prompt
method, that'd be awesome

 

[Pegasus \(MVP\)]

Re: BSOD error c0000135 winsrv missing


"dceola" <dceola@discussions.microsoft.com> wrote in message
news:E1092118-1856-49F4-BE65-FCE70538FD61@microsoft.com...
> Hi, and thanks in advance for any assistance anyone can provide.
>
> I am running Windows XP x64, with an AMD cpu, Asus motherboard - and the
> part that really really makes me want to not reload the os - two identical
> hdd's setup on a stripe raid.
>
> This morning, i awoke to my computer being off (was on when i went to bed
> lastnight), my backup power supply beeping, and the 2nd computer hooked to
> the same ups still running.
>
> Upon turning on the computer in question, it proceeded to reboot itself
> everytime it got just past the screen which showed the windows xp x64
> logo.
>
> I tried to load in safe mode (normal, w/ networking, and w/ cmd prompt).
> Tried to boot to 'last known config', and booted once with 'disable auto
> reboot on system error' (which is how i received my error message).
>
> The system gave me the BSOD w/ stop error c0000135 .... winsrv is missing
> or
> corrupt.
>
> I have searched the net for a while, and thus far have only found info on
> this related to having just instapped SP2. My computer is currently up to
> date w/ all avail patches and fixes from the windows update page; and
> since
> it has been quite some time since SP2 was installed, i feel certain that
> this
> is not related to my problem.
>
>
> I have read some things that indicate that running the recovery console
> off
> of my xp install CD would somehow allow me to fix this; however i have no
> experience with the recovery console.
>
> Any suggestions on what / how I can fix this, without having to reload my
> OS
> and losing 300+ gigs worth of my data???

Yes, you can perform a manual System Restore from the Recovery
Console - see here about the recipe:
http://support.microsoft.com/kb/307545

About your 300+ GBytes worth of data: You really need to decide
if this data is important or not. If it is not important then you can let
it go - it's no big deal. If it is important then you MUST back it up
regularly (e.g. weekly) to an independent medium. In your case it
would probably have to be a 600 GByte hard disk in an external
USB case. Next time you might lose the lot permanently if you do
not act now.

 

[dceola]

Re: BSOD error c0000135 winsrv missing

Thanks! I will attempt the ASR as soon as i get my install cd from work
monday. As for backing up the data; yeah i definitely need to get another
drive to do that to (i'll prob just pop another sata drive inside, strictly
for system backups) althought that'll mean i will have to learn how to
restore a system from a backup, haha.


THanks!

"Pegasus (MVP)" wrote:

>
> "dceola" <dceola@discussions.microsoft.com> wrote in message
> news:E1092118-1856-49F4-BE65-FCE70538FD61@microsoft.com...
> > Hi, and thanks in advance for any assistance anyone can provide.
> >
> > I am running Windows XP x64, with an AMD cpu, Asus motherboard - and the
> > part that really really makes me want to not reload the os - two identical
> > hdd's setup on a stripe raid.
> >
> > This morning, i awoke to my computer being off (was on when i went to bed
> > lastnight), my backup power supply beeping, and the 2nd computer hooked to
> > the same ups still running.
> >
> > Upon turning on the computer in question, it proceeded to reboot itself
> > everytime it got just past the screen which showed the windows xp x64
> > logo.
> >
> > I tried to load in safe mode (normal, w/ networking, and w/ cmd prompt).
> > Tried to boot to 'last known config', and booted once with 'disable auto
> > reboot on system error' (which is how i received my error message).
> >
> > The system gave me the BSOD w/ stop error c0000135 .... winsrv is missing
> > or
> > corrupt.
> >
> > I have searched the net for a while, and thus far have only found info on
> > this related to having just instapped SP2. My computer is currently up to
> > date w/ all avail patches and fixes from the windows update page; and
> > since
> > it has been quite some time since SP2 was installed, i feel certain that
> > this
> > is not related to my problem.
> >
> >
> > I have read some things that indicate that running the recovery console
> > off
> > of my xp install CD would somehow allow me to fix this; however i have no
> > experience with the recovery console.
> >
> > Any suggestions on what / how I can fix this, without having to reload my
> > OS
> > and losing 300+ gigs worth of my data???
>
> Yes, you can perform a manual System Restore from the Recovery
> Console - see here about the recipe:
> http://support.microsoft.com/kb/307545
>
> About your 300+ GBytes worth of data: You really need to decide
> if this data is important or not. If it is not important then you can let
> it go - it's no big deal. If it is important then you MUST back it up
> regularly (e.g. weekly) to an independent medium. In your case it
> would probably have to be a 600 GByte hard disk in an external
> USB case. Next time you might lose the lot permanently if you do
> not act now.
>
>
>

 

[Gerry]

Re: BSOD error c0000135 winsrv missing

http://support.microsoft.com/kb/885523

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


dceola wrote:
> Oh, and also- i have a system restore point created as recently as
> yesterday - so if there is a way to restore to that, from a dos /
> command prompt method, that'd be awesome

 

[Pegasus \(MVP\)]

Re: BSOD error c0000135 winsrv missing

You can use a humble batch file with some robocopy or
xcopy commands to back up your files, in which case you
don't need any special skills to retrieve your files from
backup.


"dceola" <dceola@discussions.microsoft.com> wrote in message
news:AD88C93F-4FD8-491F-8A7A-DF823BC62904@microsoft.com...
> Thanks! I will attempt the ASR as soon as i get my install cd from work
> monday. As for backing up the data; yeah i definitely need to get another
> drive to do that to (i'll prob just pop another sata drive inside,
> strictly
> for system backups) althought that'll mean i will have to learn how to
> restore a system from a backup, haha.
>
>
> THanks!
>
> "Pegasus (MVP)" wrote:
>
>>
>> "dceola" <dceola@discussions.microsoft.com> wrote in message
>> news:E1092118-1856-49F4-BE65-FCE70538FD61@microsoft.com...
>> > Hi, and thanks in advance for any assistance anyone can provide.
>> >
>> > I am running Windows XP x64, with an AMD cpu, Asus motherboard - and
>> > the
>> > part that really really makes me want to not reload the os - two
>> > identical
>> > hdd's setup on a stripe raid.
>> >
>> > This morning, i awoke to my computer being off (was on when i went to
>> > bed
>> > lastnight), my backup power supply beeping, and the 2nd computer hooked
>> > to
>> > the same ups still running.
>> >
>> > Upon turning on the computer in question, it proceeded to reboot itself
>> > everytime it got just past the screen which showed the windows xp x64
>> > logo.
>> >
>> > I tried to load in safe mode (normal, w/ networking, and w/ cmd
>> > prompt).
>> > Tried to boot to 'last known config', and booted once with 'disable
>> > auto
>> > reboot on system error' (which is how i received my error message).
>> >
>> > The system gave me the BSOD w/ stop error c0000135 .... winsrv is
>> > missing
>> > or
>> > corrupt.
>> >
>> > I have searched the net for a while, and thus far have only found info
>> > on
>> > this related to having just instapped SP2. My computer is currently up
>> > to
>> > date w/ all avail patches and fixes from the windows update page; and
>> > since
>> > it has been quite some time since SP2 was installed, i feel certain
>> > that
>> > this
>> > is not related to my problem.
>> >
>> >
>> > I have read some things that indicate that running the recovery console
>> > off
>> > of my xp install CD would somehow allow me to fix this; however i have
>> > no
>> > experience with the recovery console.
>> >
>> > Any suggestions on what / how I can fix this, without having to reload
>> > my
>> > OS
>> > and losing 300+ gigs worth of my data???
>>
>> Yes, you can perform a manual System Restore from the Recovery
>> Console - see here about the recipe:
>> http://support.microsoft.com/kb/307545
>>
>> About your 300+ GBytes worth of data: You really need to decide
>> if this data is important or not. If it is not important then you can let
>> it go - it's no big deal. If it is important then you MUST back it up
>> regularly (e.g. weekly) to an independent medium. In your case it
>> would probably have to be a 600 GByte hard disk in an external
>> USB case. Next time you might lose the lot permanently if you do
>> not act now.
>>
>>
>>