0 Replies Latest reply on Oct 15, 2008 1:06 PM by mrgui

    Winlogon Crash (sometimes SAS errors)

      Just sharing with the communtity, since I had to find my own answers. If you have machines that start to boot Windows, then crash with either Winlogon BSOD (blue screen of death) or SAS errors, you probably have a GINA problem. Our problem was that there was a GINA logical loop. Windows loaded SBGINA, then CSGINA, which passed back to SBGINA... and crash. This fix should be similar for any other third party GINA components. Since the machine is broken in normal mode, you will have to fix it in Safe Mode.

      Basically, you tell Windows to load SBGINA.DLL as first logon component. SBGINA then passes this control to CSGina.dll, which should then pass it to MSGina.dll. If you do not have any third party GINA components, set SB-OrigGinaDLL to blank.

      Windows Registry Editor Version 5.00

      [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\VPN Client]
      "PreviousGinaPath"="MSGina.dll"

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
      "SB-OrigGinaDLL"="CSGina.dll"
      "GinaDLL"="C:\\Program Files\\SafeBoot\\SBGINA.DLL"