Service Control Manager errors XP Home???

My Vaio PCG K27 is freezing up on me a couple of times a day-- I am running XP Home.

I looked at the Events Viewer and found two types of errors

1) DCOM errors Event ID 10010

(I have traced this through Regedit to Symantec symWSC.exe)
I will work with Symantec to figure this out (though any hints will be appreciated)

and 2) Service Control Manager errors Event ID 7001.

These seem to be related to a TCPIP service.
In command prompt -- sc query tcpip, the win32_exit_code is 0 <0X0>

According to Microsoft instructions

"View the WIN32_EXIT_CODE error that SCM encountered when trying to start the program. To do this, at the command prompt, type
sc query service name
If the WIN32_EXIT_CODE is zero, then SCM did not attempt to start the service because the error was detected first. "

OK, so the exit code is 0, there is a detected error, now what?

I am attaching part of the Event Log for your help in solving what the problems may be (my apologies that it is so long).

Thanks,

Steve
sjschloeder@sbcglobal.net
------------------------------




Type Date Time Source Category Event User Computer
Information 8/26/2004 7:20:50 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:20:46 PM Service Control Manager None 7035 SYSTEM VIO

Error 8/26/2004 7:20:41 PM Service Control Manager None 7001 N/A VIO

Information 8/26/2004 7:19:11 PM Tcpip None 4201 N/A VIO
Information 8/26/2004 7:19:02 PM eventlog None 6005 N/A VIO
Information 8/26/2004 7:19:02 PM eventlog None 6009 N/A VIO
Information 8/26/2004 7:18:20 PM eventlog None 6006 N/A VIO
Information 8/26/2004 7:18:10 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:16:02 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 7:15:47 PM Service Control Manager None 7035 SYSTEM VIO
Error 8/26/2004 7:15:47 PM Service Control Manager None 7001 N/A VIO
Information 8/26/2004 7:14:32 PM Tcpip None 4201 N/A VIO
Information 8/26/2004 7:14:19 PM eventlog None 6005 N/A VIO
Information 8/26/2004 7:14:19 PM eventlog None 6009 N/A VIO
Information 8/26/2004 7:12:07 PM eventlog None 6006 N/A VIO
Information 8/26/2004 7:11:53 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 7:05:23 PM Application Popup None 26 N/A VIO
Information 8/26/2004 6:17:10 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:17:09 PM Service Control Manager None 7035 SJS VIO
Error 8/26/2004 6:12:29 PM DCOM None 10010 SJS VIO
Information 8/26/2004 6:12:03 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:12:00 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:11:59 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 6:08:11 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 6:08:01 PM Service Control Manager None 7035 SYSTEM VIO
Error 8/26/2004 6:08:01 PM Service Control Manager None 7001 N/A VIO
Information 8/26/2004 6:07:53 PM W32Time None 35 N/A VIO
Information 8/26/2004 6:06:46 PM Tcpip None 4201 N/A VIO
Information 8/26/2004 6:06:33 PM eventlog None 6005 N/A VIO
Information 8/26/2004 6:06:33 PM eventlog None 6009 N/A VIO
Error 8/26/2004 4:16:53 PM DCOM None 10010 SJS VIO
Information 8/26/2004 4:16:27 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:16:24 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:16:23 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 4:12:36 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 4:12:23 PM Service Control Manager None 7036 N/A VIO
Error 8/26/2004 4:12:22 PM Service Control Manager None 7001 N/A VIO
Information 8/26/2004 4:12:13 PM W32Time None 35 N/A VIO
Information 8/26/2004 4:11:01 PM Tcpip None 4201 N/A VIO
Information 8/26/2004 4:10:52 PM eventlog None 6005 N/A VIO
Information 8/26/2004 4:10:52 PM eventlog None 6009 N/A VIO
Error 8/26/2004 10:32:06 AM DCOM None 10010 SJS VIO
Information 8/26/2004 10:31:39 AM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 10:31:36 AM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 10:31:36 AM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 10:27:57 AM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 10:27:37 AM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 10:27:37 AM Service Control Manager None 7036 N/A VIO
Information 8/26/2004 10:27:37 AM Service Control Manager None 7035 SYSTEM VIO
Information 8/26/2004 10:27:37 AM Service Control Manager None 7035 SJS VIO
Information 8/26/2004 10:27:37 AM Service Control Manager None 7035 SYSTEM VIO
(snip)

 

Hi schloeder and welcome to the forum.

Nice bit of sleuthing to track down specifics on that DCOM error. It does need fixing but almost certainly is not causing a freeze/lockup.

The SCM one could be but again, probably not.

Things to do at this point:
- power down, unplug, remove the cover, and blow out any dust you find plus clean any filters you have. Also give any fans you see a spin to make sure none are frozen.
- with the case still off, power up and see if there are any obvious fan problems. With a newer system the fans may well be temp controlled and not try to start when things are cool but you may see something.
- put your XP CD in the CD drive then click on start, click on run, put in

Code:

sfc /scannow

and OK. It will run quickly and not tell you much but will be examining all system files for damaged or missing ones and will replace those from the CD as needed. You can see details in an event log entry if you wish.

If none of those help, go back into the event logs and open the most recent Service Control Manager errors Event ID 7001 then click on the icon below the up/down arrows to send a text copy to the clipboard and paste it in a reply here. Do the same with one of the Information 8/26/2004 7:19:11 PM Tcpip None 4201 events.

 

Hi Newt:

I appreciate the reply and advice. 2 things:

1) this is a brand new Viao laptop -- only 6 weeks old, so I am concerned about cracking the case and voiding the warrantee...

2) what are the chances are that it is an overheating problem? (I think that is what you are suspecting, right?

So, is there a relationship between the SCM and the DCOM and the TCPIP (I thought TCPIP was some sort of dial-up modem protocol, and I am runnning on wifi cable, so I am confused...)

At any rate, I am away for a few days and when I return will do as you suggest with the XP CD and paste the info on the board.

Thanks again,

Steve

 

You got it in one. I was thinking of heat as a very likely suspect. With a new laptop it isn't real likely unless you have a bad part in there though and I agree that leaving the case intact is your best bet.

TCP/IP = Transmission Control Protocol / Internet Protol = the standard language for talking on the internet and on most business network. Only a few (and fewer each day) business networks are using any other protocol. If you use the internet via dial-up or broadband, all the stuff you send will be translated into TCP/IP on the way out and any that come to you will come as TCP/IP and be translated on the way in.

DCOM = Distributed Component Object Model - a protocol that enables software components to communicate directly over a network in a reliable, secure, and efficient manner. It uses both TCP and UDP packets & ports. You really don't want to know much more but if you do, I can point you to some great reading if you have lots of time. For any old timers reading this, DCOM was called Network OLE (object linking & embedding) by Microsoft until they decided to play by the same networking rules as everyone else and changed to the standard name. I sorta thought their term was more descriptive.

SCM = Service Control Manager - in this case I'll assume we are dealing with DCOM's SCM. The SCM always operates at a fixed network port on every computer. For the Internet this is always port 135 (for both TCP and UDP). The SCM offers several RPC-based services which handle housekeeping type operations for clients that ask for particular things.

So yes, SCM/TCP/DCOM are related.

schloeder - this may all get a little deep before we are done and if there were a single place for you go for help such as Microsoft (it's their OS) or the hardware vendor (their stuff except for the wi-fi) or the wi-fi vendor, I'd suggest that in the interest of saving you time. But the reality is that Microsoft will probably charge you since I'm guessing your OS is an OEM version from the laptop vendor and does not have any free microsoft support, that the laptop vendor's tech support will be clueless, and that the wi-fi tech support will blame Microsoft and your laptop vendor so you may be stuck with us here. If we hit a stone wall, Microsoft might do a support case for their usual $35 fee and it may be worth every nickle to you.

That being said, we can certainly try the simpler things that may cure the problem and maybe tap some resources for some more complex items.

 

Hi Newt:

I was searching on another BBS, and someone recommended powering down, taking out the battery and unplugging the lap top over night. In the Event Viewer I am still getting DCOM errors, but the computer has not crashed or seized up since I did that procedure-- and that was over two weeks ago.

I can live with the DCOM error as long as it doesn't crash the laptop.

I appreciate the help -- you were able to communicate things way beyond my expertise at a level I was able to comprehend!

Hopefully I won't need to write back about this, though I do have another issue I'll post on a separate thread!

Best regards,

Steve

 

Thanks for posting back and I will put the "battery out, power down, leave for a day" idea into my bag of tricks. I have lots of hardware-ish things that seem to work fine even though I have absolutely no clue why.