Member Avatar for finalheaven

I get this error when I boot my comp. The comp posts fine, and then I see the xp pro symbol faded out, then it focuses, the blue bar rolls, then I get a blue screen. Something about "TOP: c0000135 {couldn't locate file}
WINSRV is missing. Reinstalling the application may fix this problem." Can anyone help me please?! I'm so worried. I built this thing and it's such a clean system. Why would I get this error.

When I try recovery with my OS CD, it doesn't work. Safe mode doesn't work. Because my HDD is on my RAID connector, I entered the F6 to load raid drivers mode and it says it was unable to load support for any mass storage devices. Then it gives me an option S to load other SCSI or CD-rom devices or something, an Enter option to continue, or F3 to quit. Should I be loading drivers from a different CD? I can't believe all this for freakin winsrv. I'm screwed.

EDIT: Sorry, I didn't include the necessary information. I'm running XP pro with SP1 (yes, I bought the OS myself). Built the rig myself. I hadn't installed any new programs in awhile (although I started playing Knight of the Old Republic and CounterStrike a lot). I run ZoneAlarm Pro always, and Regsupreme sometimes. That's about it. The problem occurs everytime I boot. At first, I had two or three boots where xp pro wanted to run a checkdisk and it did, and passed successfully. I thought this was odd. And now, I get the above problem

  • 5 Contributors
  • 5 Replies
  • 527 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by Tyran

Dani AI

Generated

A short, practical diagnosis and recovery plan based on the thread so far.

This STOP / c0000135 message means Windows can’t load a core subsystem DLL (winsrv); common root causes are an actually missing/quarantined winsrv DLL or the Windows “SubSystems” registry value being damaged so the kernel can’t find the user-mode server DLLs. (learn.microsoft.com)

Non‑destructive first steps (least risk)

  • If you can boot the XP Recovery Console (or an equivalent WinPE/boot CD), run a full disk check first (chkdsk /r) to correct file-system errors.
  • From the Recovery Console check whether C:\Windows\System32\winsrv.dll (and the copy in C:\Windows\System32\dllcache) exists; if a good copy is present, restore it to System32. If not, extract the file from the matching XP installation media or ServicePackFiles on disk. These simple file fixes often recover the system. (learn.microsoft.com)

If that doesn’t fix it (registry corruption suspected)

  • A registry hive problem (Session Manager/SubSystems entry altered) will also produce this symptom — registry‑level recovery (restore System hive from a restore point or use the Microsoft offline‑hive recovery procedure) is the documented next step. Follow the official “recover registry” procedure carefully and work from a copy/backup; it’s technical and risky if done blind. (learn.microsoft.com)

When the Recovery Console/CD can’t see the RAID disk

  • Older XP setup requires text‑mode (F6) mass‑storage drivers to be loaded from a floppy; if you don’t have that, either slipstream the correct RAID drivers into an XP install CD (or build a WinPE with drivers) or remove the drive and attach it to another PC/USB adapter to fix files offline. Do not change BIOS RAID mode on a live RAID array without confirming you won’t break the array — that can destroy data. ()

Notes tied to the thread: ’s use of a registry sweeper and the earlier / repeated chkdsk runs are classic clues pointing at either a missing winsrv DLL or a damaged Session Manager value; ’s Recovery‑Console idea is on the right track but avoid copying files from mismatched SP media. If unsure, move the drive to a working machine and fix or back up files there before attempting registry repairs.

Recommended Answers

All 5 Replies

Member Avatar for finalheaven

Well, I have since found a fix for the problem (although I have not implemented it).

I also might have the cause as well. At least in my case. I use RegSupreme every so often to do a very shallow sweep of my registry for temp keys and entries that are no longer needed. I think I might have damaged the system key pointing to winsrv or something.

I went to the link you gave, but I can't contact him because I'm not a member of that board (to pay for a monthly fee for an online forum? How absurd)

Member Avatar for ashishanand2

Hi,
I also got the same problem this afternoon.
Please tell me how to solve it.

I am using windows 2000 professional.

Member Avatar for rbk25

i have read that this may solve the problem.

create a .txt file on a floppy with this line in it.

COPY "C:\WINNT\$NtUninstallKB835732$\kernel32.dll" "c:\winnt\system32\kernel32.dll"

use the boot disketts or cd to get to the "repair console". insert the floppy and type:
batch a:\"file name".txt

this should replace the Kernel32.dll with the old one. remove the floppy and type exit.

hopefully this should do it.

Member Avatar for Tyran

Well,

Here is a common solution for that problem:

Good luck!

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.