Non SP2 c0000135 Blue Screen

[PTech9500]

One of our users has a laptop he broke and now he's asking IT to fix it. The laptop Blue Screens on boot with

STOP: c0000135 {Unable To Locate Component}
This application has failed to start because winsrv was not found.

(something very close to this. I know it was winsrv and the error number)

I'm unable to get normal, safe mode, or last known good configurations to boot. The PC is a Media Center Edition XP. Based on the manufacture date it had Service Pack 2 on it when it was delivered. He said he rarely does updates but he was doing them when this happend. He shut it down with the "Install updates and shut down" function XP seems to have now. He said it was doing a batch of about 70 updates so it could be just about anything. I was able to use a XP Pro cd to boot up recovery console and I ran a chkdsk /r however no change. I tried removing SP2 but since it came with it that didn't work either. If I can figure out which Service Pack caused the error, I can remove it through the recovery console. I still need to find my copy of UBCD so I can take a look at the drive to see if any obvious things are wrong but that's my last hope. Unfortunately he lost his original OS CDs and we don't have any XP Media Center SP2 copies laying around so repair is not an option and neither is reinstall. Any suggestions?

 

[linney]

To replace a CD or Product Key, you must contact PSS. To locate the appropriate phone number for your product, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

326246 - How to Replace Lost, Broken, or Missing Microsoft Software or Hardware

http://support.microsoft.com/default.aspx?scid=kb;en-us;326246&FR=1&PA=1&SD=HSCH

This procedure will get you back to a Restore Point before all the Updates. It only requires the Recovery Console.

An easy to follow recovery console description when unable to start computer due to corrupt registry.

http://www.digitalwebcast.com/2002/03_mar/tutorials/cw_boot_toot.htm

This is a layman's version of Q307545 in simple language.

 

[BadBigBen]

0xC0000135: UNABLE_TO_LOCATE_DLL
Windows attempted to load a DLL file and encountered some error condition. Among the many possible causes are that the file is missing or damaged, or that there is Registry corruption.

Blue Screen STOP Message C0000135 Appears at Startup

http://support.microsoft.com/?kbid=173309

Damaged Registry Repair & Recovery in Windows XP

http://support.microsoft.com/?kbid=318159

source:

http://aumha.org

Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[PTech9500]

Ok, the exact stop message is

STOP: C0000135 {Unable To Locate Component}
This application has failed to start because winsrv was not found. Re-installing the application may fix this problem.

It appears after the Windows XP logo with the progress bar that you see when XP boots.

I tried replacing C:\Windows\System32\winsrv.dll with winsrv.dll from the C:\i386 folder but that didn't work. I have no OS access to the drive, in other words, I can't install or uninstall anything. I'm only able to connect the drive to my machine as an external storage device for file access or using Ultimate Boot CD I can boot it and play with the registry and run diagnostics on the hard drive and such.

The first link you posted is for NT.

APPLIES TO
• Microsoft Windows NT Workstation 3.51
• Microsoft Windows NT Workstation 4.0 Developer Edition
• Microsoft Windows NT Server 3.51
• Microsoft Windows NT Server 4.0 Standard Edition


And the second link, although very close to what I'm experiencing, I cannot install service packs or hotfixes because I can't get it to boot.. Unless I can install those from Recovery Console? Can I?

 

[PTech9500]

Sorry Linney, I didn't see your post. I'll try that last thing now and let you know if it works.

 

[BadBigBen]

believe it or not, the FIX still applies to XP...

but good luck, that what Linney wrote is usually very sound information... and if that does not work, then you will head towards a complete fresh install (which would probably be the best anyway) there...


Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[linney]

You receive a "Stop: c0000135" and "winsrv was not found" error message after you install Windows XP Service Pack 2

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

http://www.google.com/search?q=application+has+failed+to+start+because+winsrv+&rls=com.microsoft:

http://groups.google.com/groups?q=application+has+failed+to+start+because+winsrv+&rls=com.microsoft:

These two articles in the RegEdit Help are a good explanation of the following process process if it becomes necessary or possible to use it.

To load a hive into the registry
To unload a hive from the registry

This will also enlighten you on a recovery process involving Registry Hives.

Cannot logon to winxp...losing lots of valuable documents
thread779-975236

 

[PTech9500]

Linney, the third article in your first post was a good idea, but after I switched all the registry hive files to the ones in c:\windows\repair it still didn't boot so that method won't work.

 

[PTech9500]

Linney, the problem was this cam with SP2 and I can't uninstall it.

 

[PTech9500]

Success!!! I'm not sure which link I saw it on but I uninstalled all the service packs dated on the 22nd which is when it went down. I booted into recovery console and did a "batch spuninst.txt" on each update of about 10. After which the system booted up just fine. Here's a list of the KBs that I uninstalled.

890859
894391
896428
908519
913580
914389
920683
928843
935839

Not sure which one fixed it but Hooray! Now I can get this off my desk and back to the user. Thanks you two.

 

[BadBigBen]

Glad you got it working...



Ben

"If it works don't fix it! If it doesn't use a sledgehammer..."

 

[linney]

I suppose the next step is to put the updates back on one at a time and reboot until you find the guilty one?

Running without the latest updates is not a wise move in my opinion. When you find the problem causing update we may be able to take that a bit further with Microsoft and find out the actual cause.

 

[PTech9500]

That's a good idea. I'll take it up with the user and hopefully have an answer in the next week.