Share via

Error in logg: Sessionen "Circular Kernel Context Logger" 0xC0000035

Anonymous
2010-08-17T17:11:59+00:00

I have recently install a clean new Windows 7 64-bit on my new computer, and installed some few programs.

I get this error Sessionen "Circular Kernel Context Logger" failed to start 0xC0000035 everytime user A has logged in and then switches over to user B and login, when I then return to user A there comes a lot of errors in the logg 10-15 in just a few seconds. And they all say as above.

I have no idea where to find whats causing this error, some one out there who can help me?

(It seems like other people on the net having the exakt same problem, but there is no one with a solution)

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

10 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-08-13T18:33:50+00:00

    I have only MS Security Essentials, and the errors are the same for me. I'm pretty sure mine happen at first logon or logon of different user. Mine always end with Kernel ET error 3:

    Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

    Do you get that, too?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-08-26T14:45:10+00:00

    I have now tested a clean boot , but I havn't got the error in the logg for some days now. So I still can't say if it's there or not with a clean boot.

    I'll get back if I get some lead of some kind.

    It's a mystery, that's all I can say! :-)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2010-08-22T17:45:09+00:00

    I have done the SFC check, and there where no errors, everything ok.

    I now have discovered that this 20 errors only appears once a day, if it have happend it's not possible to get the error again, unless it has gone what I think about 24 hours. That's strange!? (But I think everyone else on the net that's getting this error also having it once a day.)

    And it happens when user B swithes back to the login screen.

    It has nothing to do with getting back from standby, IPv6, NIC, the file setup.etl as other hassuggest.

    I haven't tried method 1 from shinmila yet, couse I already have had the error today, so I must wait until tomorrow.

    I have installed Windows 7 twice from scratch and the error is still there.

    (Maybe this error doesn't make any problems, but I just want to find out why, and get rid of it.

    I have Norman Security Suite installed, if someone else having this problem and also running Norman.)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2010-08-18T06:36:54+00:00

    Nothing to worry about, the system repeatedly tries to start the logger session until it succeeds. A temporary failure to start mostly (but not always) happens during a system state transition from standby -> running.

    If this doesn't fit your case, this other article states:

        The system state is a set of kernel events generated by taking a snapshot of the Circular Kernel Context Logger.

    It's then possible (but improbable in my opinion) that the problem is related to system snap-shots. You might then verify in Control Panel / System / System protection, that everything seems well defined.

    If none of the above ideas are useful, my only other idea would be to do a system repair.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2010-08-18T04:18:40+00:00

    HeyNicce70,

    Here are two things you can try.

    Method 1:

    To see if the issue is related to third party services, put the computer in clean boot configuration.

    Please refer this article for detailed information on how to do this.

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

    **Note:**Ensure that you put your computer back to normal startup mode after completing the troubleshooting steps. Steps are available in the article given above.

    Method 2:

    Run System File Checker (SFC) scan.See if it finds any integrity issues. If so, System File Checker will try to replace those missing or corrupted files.

    Information available at:

    How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

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

    In case SFC scan doesn’t repair the files, follow the steps given in the link above on how to repair those corrupted files

    Regards,

    Shinmila H - Microsoft Support

    Visit our Microsoft Answers Feedback Forum and let us know what you think.

    Was this answer helpful?

    0 comments