Error Winsrv Windows Xp
Contents |
360 games PC games
Winsrv Not Found Blue Screen Windows Xp
Windows games Windows phone games Entertainment All Entertainment stop c0000135 unable to locate component csrsrv dll Movies & TV Music Business & Education Business Students & educators what is winsrv not found Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Stop C0000135 Unable To Locate Component Winsrv
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All
Csrsrv.dll Missing Server 2003
Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 04:04:03 GMT by s_ac15 (squid/3.5.20)
Frames Image Optimizer FavIcon Generator FavIcon Editor new Animated Gif Email Riddler .htaccess Password .htaccess Banning Gradient Image Button Maker Ribbon Rules List Scrubber Tool DD Whois Service Register Help Remember Me? Advanced Search DD Home http://www.dynamicdrive.com/forums/showthread.php?36785-XP-Bluescreen-halt-Winsrv-not-found-stop-c0000135-MS-help-not-working Forum New Posts FAQ Calendar Forum Actions Mark Forums Read Quick Links Today's Posts View http://superuser.com/questions/610687/stop-c0000135-winsrv-dll-bsod-etc-on-previously-stable-windows-x Site Leaders What's New? Blogs Forum Community Computer hardware and software XP-Bluescreen halt: Winsrv not found, stop:c0000135 - MS help not working? If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select not found the forum that you want to visit from the selection below. Results 1 to 6 of 6 Thread: XP-Bluescreen halt: Winsrv not found, stop:c0000135 - MS help not working? Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search 09-21-2008,12:25 PM #1 schorhr View Profile View Forum Posts Private Message View Blog Entries Junior Coders Join Date Sep 2008 Posts 26 Thanks 2 Thanked 4 Times in 4 Posts XP-Bluescreen halt: winsrv not found Winsrv not found, stop:c0000135 - MS help not working? Hello, the computer of my dad-in-law(-to-be) is not working anymore. When booting it halts with a beatifull blue screen stating winsrv not found , stop: c0000135. Well, I thought "Oh, another bluescreen of death. No big deal, that's something I have seen before", and did a little search. Almost all instructions/forum topics redirect to the microsoft help pages adressing the issues. "Boot with the XP CD, R/Console, ..." Unfortunaly it only works up to step 5: "type cd $ntservicepackuninstall$\spuninst" because the directory is not found. I then followed a different solution posted in some forum, where its simply solved via "expand d:\i386\winsrv.dl_ c:\windows\system32\winsrv.dll" Unfortunaly it states "unable to expand" even though the files exists and I renamed winsrv.dll to winsrv.old. I also tried copying the winsrv.dl_ to c: first but it did not make any difference. Is there any way I can avoid re-installing XP? I also tried the usual (safe mode, use last known working version, yadayada...) Thanks in advance for any help & thoughts on how to get this machine running again :-) /EDIT I managed to use another XP CD and expanding the winsrv.dl_ worked, but it did not solve to problem? Last edited by schorhr; 09-21-2008 at 02:39 PM. Reply With Quote 09-28-2008,02:59 AM #2 lainlives View Profile View Forum Posts Priv
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Stop: c0000135…winsrv.dll…BSOD etc. on (previously) stable Windows XP SP3 installation up vote 1 down vote favorite My PC was working fine last night. It was previously a perfectly stable, well protected and carefully maintained Windows XP SP3 system. After shutting down then restarting, Windows gets to the XP logo screen (with the blue progress meter) but then generates this error just before displaying the login/welcome screen (or just reboots if restart-on-failure is enabled): STOP: c0000135 {Unable to locate component} This application failed to start because winsrv was not found. Re-installing the application may fix this problem. I tried booting into Safe Mode, Last Known Good etc. All boot modes result in the same error. Safe Mode gets to mup.sys before the STOP occurs. I installed a fresh copy of Windows XP on another drive that's in the PC, updated to SP3, and that boots up just fine. So I don't think this is a hardware related failure. Even so, the motherboard is new. The power supply is new. Two of the 4 memory sticks are new. The only other component is an Nvidia graphics adapter (7800 GTX). I thought the problem might be registry related, so I followed the steps described by Microsoft in repairing a cor