ccSvcHst error message on shut down

Today I typed in cd\Program Files\Common Files\Symantec Shared\Backup and pressed return (this time with no quotation marks) and cd\Program Files\Common Files\Symantec Shared\Backup came up this time with no error message. I then typed in at the end of this line:   regsvr32 /u buShell.dll and pressed return and the message "DllUnregisterServer in buShell.dll succeeded." I then pressed return again and cd\Program Files\Common Files\Symantec Shared\Backup came up. I then closed the Run program. Then when I shut down, the error message: "The execption Privlidge instruction" and I couldn't write down all the numbers in the error message before the computer shut down.

What was I to do after it told me the buShell.dll succeeded in the run program? I also went to Explore and right clicked on the program files, but I had not idea what to look for.

I just got the rest of the error message on the second shut down

The exception Privlidge instruction

0xC0000096 occured in application location 0x6fb8f59f

I don't know if this is of any help

No that it. You have down the  zombie workaround, you have deregistered bushell.dll and you have a success.

 

You need to reboot and shutdown again, and see what error messages you are getting. If you continue to get an error, then I am not surprised because as I said, I did not think yours was a classic ccsvchst error on shut down.

 

As I prepare this, I just seen your 2nd post. Ok you are still getting an error but now different.

The exception Privlidge instruction

0xC0000096 occured in application location 0x6fb8f59f

 

I need the exact version of your operating system please . I know it is XP but is it XP Home Edition or what, and what SP has been applied 1,2,3?

 

As I said I am not convinced from the info to date that the problem is any more related to ccsvchst. It could, for all I know, be another program causing the error on shutdown. In that case I would suggest getting Autoruns (Microsoft) and temporarily turning off certain programs from running, but leaving all Norton Symantec untouched.

 

All I can so far find on the exception privilidge is that it is driver related. Again you might want to check your system devices and make sure there are no yellow marks.

When I went into the system properties folder in the control panel, it says I am operating XP Media Centre Edition 2002, SP 2.

You suggested to check my system devices for a yellow mark. How do I get into system devices?

I found the device manager and went through all the folders and found no yellow marks. by the way, is there an easier way to get to the device manager other than using the Run command: devmgmt.msc   ?

yes, control panel, system, hardware, device manager. I use classic view.

 

In category view, I think it is Performance & Maintenance, System, hardware.

 

Sorry I still do not have an answer.

 

I would suggest downloading Autoruns from Microsoft. Run and go to Logon tab when the status at the bottom shows scanning has finished.

 

Now the logon shows all progs loaded at startup, if you uncheck the tick box, they will not load the next time, and when you tick the box, it is restored. (do not right mouse click and delete - thats something else). You should be able to figure out what each one does.

Leave anything Symantec and try to turn everything non essential off.

Shutrdown reboot, shutdown and see if error still there.

 

Sorry I am cluching at straws here. Hopefully something will come up shortly, as I am stumped

 

 

AllanMac, have you tried the fixes I suggested in post number four of this thread, you haven’t made this clear? If not, I suggest you try that fix,  it may just help. Here is the direct link: Link .

Message Edited by johna on 07-22-2008 11:20 PM

cgoldman:

Today when I shut down, I had the same error message:

ccSvcHst at the top and then, The instruction at 0x7c91fea....The memory could not be written.

I checked the Microsoft website for the Autoruns download and read a bit, but I'm not sure what to turn off and it would seem like a lengthy trial and error exercise.

Do you think trying Johna's suggestion about changing the wait times will have any effect?

How can I get back to my original error message?

Do think that this is caused by Norton's 360?

It does not get better does it. So now we are back to the beginning with the same msg as before - yet you have applied Zombie workaround and changed autoendtaks to 1. Last time the shutdown msg was something quite different, and now suddenly you have the original msg. I would check zombie and autoendtasks in registry and make sure they are stil set.

 

If you are unhappy with Autoruns you could run msconfig from the "Run" command instead, and select selective startup and check everything except "load startup items", then see if the problem is resolved. Another time you go to Startup and selectively add each program back in. As I say Autoruns can do the same, but in my view it is easier to work with.

 

Yes, you can try Johna;s suggestions. At this point, nobody knows. For one user only, running the 3rd fix worked in removing shutdown issue. I have said here and elsewhere, that I see no logic to it. But if it works for you, then that is great. If not then you simply undo the changes i.e. change them back to their original values.

 

I have no idea if it is Norton's. The only way is  by disabling all other programs and seeing if the problem goes away. I.e. we try to prove that it is Symantec and nothing else. Sorry I am not very helpful because I have no explanation for your problem.

cgoldman: Thanks so much for your help, I'll give those suggestions a try.

I had the same problem as Spotted_lady and think that I have fixed it.  I have Norton 360 version 2 on a HP Media Center with Windows XP SP3.  I was getting the error CCSRVHST.exe instruction at "0x00450044" referenced memory at "0x00450044" could not be read.  I ended up deleting the HP Updates out of the Start Up list and the error disapeared. 

Start - then select Run - type in msconfig - select Start up - deselect HP Update.

 

I hope this helps.

I guess I posted my remark too soon!  The error is back!  Sorry!

Don't feel bad.  I thought mine was fixed, but I get two errors now.  One says memory can't be read and one says memory can't be written.  So far it is more of an annoyance than a problem.  I am not thrilled with this product, and I never heard back from tech support.

 

I just want to be clear before I try some more trouble shooting on this, have you applied the work arounds I suggested here ? Thanks.

Message Edited by johna on 08-05-2008 03:31 AM

The latest error at shutdown is: The instruction at “0x7c91b1fa” referenced memory at 0x00000010.  The memory could not be “written”.  Click on OK to terminate the program  Click on CANCEL to debug the program.  I usually get the error that the memory could not be “read”, but every 3rd or 4th shutdown I get this one.  Very seldom does it shutdown without one of these two errors.  And still no help from tech support.

1 Like

Hi spotted_lady. Can you please let me know if you applied all the work arounds mentioned two posts up. Thanks

see message 16 & 18 for the things I tried.  I can’t really say it has helped since I now get another error message.

Hi All,

 

I had approximately the same problem. I didn't have it until I installed Java RE (version 6 update 7). Once I uninstalled it the error message diappeared at shutdown. First I thought it could be the Java Automatic Update service, but it isn't

 

I have tried older versions (Java 1.4.2 update 17 and Java 5.0) and have the same issue. Seems like Symantec needs to look into this.

 

Does this also happen with Service Pack 2?

Message Edited by aguseo on 10-03-2008 03:47 AM

aguseo

 

At this time, the issue has not been narrowed down to a conflict with JRE.  Engineering is investigating the root cause of this issue and it is a top priority for the coming N360v2 patch.  In the interim, there is a work-around to help address this issue.  Please follow the KB doc HERE for this work-around.

1 Like

try this workaround go to msconfig set normal startup not selective startup click apply click restart hey presto error gone did on mine anyway

cheers

Steve (gorby)