1. Esta web utiliza cookies propias y de terceros, puedes ver nuestra política de privacidad y cookies. Si continúas navegando, consideramos que aceptas su uso.

    Cerrar notificación

windows logon process terminó inesperadamente con un estado de xc0000135

Tema en 'Windows XP' comenzado por marceloalayo, 19/9/09.

Estado del tema:
No está abierto para más respuestas.
  1. marceloalayo

    marceloalayo Nuevo Miembro Miembro

    STOP: c000021a {error grave del sistema}

    El proceso del sistema Windows logon process terminó inesperadamente con un estado de xc0000135(0x0000000000 0x00000000).

    Se ha apagado el sistema
     
  2. viru

    viru Super Moderador Super Moderador

    Cómo solucionar el STOP: c000021a

    Operating system comes up with Blue Screen Error: Stop c000021a

    In this blog we are going to discuss about how we can decode and fix operating system crashes with Stop c000021a.


    Below is the first screen you will see after POST, followed by the bugcheck information.

    [​IMG]


    Here is the detail bugcheck information:


    The session manager initialization system process terminated unexpectedly with a status of 0xc000003a(0x00000000,0x00000000)

    [​IMG]


    The second parameter “0xc000003a” resolves to “STATUS_OBJECT_PATH_NOT_FOUND”.


    The first reboot after bugcheck you may not be able to get Advanced Boot Options when you press F8 and may only get Windows Error Recovery screen, as seen below.

    [​IMG]


    In such scenarios there is no crash memory Dump generated.


    Next thing we need to do is launch Startup Repair from Window Recovery Environment (WinRE). If you do not have WinRE installed on the machine you can boot from either Windows Server 2008/R2/Windows 7 boot disc.


    Once booted into WinRE launch Command prompt and open regedit

    [​IMG]


    Highlight HKEY_LOCAL_MACHINE

    [​IMG]


    Click on File & Load hive

    [​IMG]


    Note: Whenever you are booting into WinRE you are actually booted into a RAMDRIVE. When opening registry editor you are seeing the hives from RAMDRIVE and NOT from installed Windows. Make sure you are loading the hives from your Windows.


    Consider D: as your installed drive. Browse to “D:\Windows\System32\Config” folder and select “System” hive. See image below.

    [​IMG]


    Now click open and name it as “Test”.

    [​IMG]


    Next step is to navigate to HKEY_LOCAL_MACHINE\Test\Select and check the value “Current”.


    This dword value tells us the correct ControlSet to use.

    [​IMG]



    Since we know the correct ControlSet is “1”, navigate to Controlset001 and access the following key HKEY_LOCAL_MACHINE\Test\ControlSet001\Services\mountmgr

    [​IMG]


    Selecting “mountmgr”, on the right side pane look for “NoAutoMount” dword value & modify the value to “0”.


    Once done, Select Test Key from top and click on File to Unload Hive. Click Yes if prompted.

    [​IMG]



    Close the registry editor and reboot the server in normal mode.


    More Information:


    If the “Automount” is disabled it brings any Volume or Disks without drive letter offline. Additionally, entries under HKEY_LOCAL_MACHINE\System\MountedDevices key will be missing especially for Windows Boot Drive, which results in this BSOD.


    Refer the link for more information on AutoMount: http://technet.microsoft.com/en-us/library/cc753703(WS.10).aspx


    Jaspreet Singh
    Support Engineer
    Microsoft Enterprise Platforms Support

    Saludos.
     
Estado del tema:
No está abierto para más respuestas.

Comparte esta página