IBM Support

LO78589: NSD PROCESS CRASHING CITRIX SERVERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • SETUP
    Citrix XenApp 6.5 running on Windows Server 2008 R2 Standard.
    Lotus Notes R8.5.3 Fix Pack 3
    NSD process seems to be
    crashing our Citrix servers.  We've received feedback from
    Microsoft
    and they've identified the "NSD.exe binary from IBM" as thee
    cause.
    The Micrsoft call ref is:  [REG:113092610816697].
    
    Technotes given
    1245742
    
    Using Microsofts freely available debugger and symbol files
    to review the dump the following was identified
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is
    available
    
    Symbol search path is:
    srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs)
    Free x64
    Product: Server, suite: TerminalServer
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Machine Name:
    Kernel base = 0xfffff800`01654000 PsLoadedModuleList =
    0xfffff800`01897670
    Debug session time: Thu Oct 24 09:35:44.852 2013 (UTC + 0:00)
    System Uptime: 0 days 7:23:21.551
    Loading Kernel Symbols
    ...............................................................
    
    ................................................................
    
    ..........................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`fffdf018).  Type ".hh
    dbgerr001"
    for details
    Loading unloaded module list
    ........
    ****************************************************************
    ********
    *******
    *
          *
    *                        Bugcheck Analysis
          *
    *
          *
    ****************************************************************
    ********
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa801ef39060, fffffa801ef39340,
    fffff800019d0350}
    
    Probably caused by : _
    Followup: MachineOwner
    ---------
    
    3: kd> kd: Reading initial command '!analyze -v; q'
    ****************************************************************
    ********
    *
           *
    *                        Bugcheck Analysis
          *
    *
          *
    ****************************************************************
    ***************
    
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has
    unexpectedly exited or been terminated.
    Several processes and threads are necessary for the operation
    of the  system; when they are terminated (for any reason), the
    system can no  longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa801ef39060, Terminating object
    Arg3: fffffa801ef39340, Process image file name
    Arg4: fffff800019d0350, Explanatory message (ascii)
    
    Debugging Details:
    ------------------
    
    
    PROCESS_OBJECT: fffffa801ef39060
    IMAGE_NAME:  _
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: _
    
    FAULTING_MODULE: 0000000000000000
    
    PROCESS_NAME:  nsd.exe
    
    BUGCHECK_STR:  0xF4_nsd.exe
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80001a57d22 to
    fffff800016c9c00
    
    STACK_TEXT:
    fffff880`0d231b08 fffff800`01a57d22 : 00000000`000000f4
    00000000
    `00000003 fffffa80`1ef39060 fffffa80`1ef39340 : nt!KeBugCheckEx
    
    fffff880`0d231b10 fffff800`01a0408b : ffffffff`ffffffff
    fffffa80
    `3fbf34c0 fffffa80`1ef39060 fffffa80`249b8060 :
    nt!PspCatchCriticalBreak+0x92
    fffff880`0d231b50 fffff800`01984144 : ffffffff`ffffffff
    00000000
    `00000001 fffffa80`1ef39060 00000000`00000008 : nt! ??
    ::NNGAKEGL::`string'+0x17486
    fffff880`0d231ba0 fffff800`016c8e93 : fffffa80`1ef39060
    fffff880
    `00000001 fffffa80`3fbf34c0 00000000`00007e3c :
    nt!NtTerminateProcess+0xf4
    fffff880`0d231c20 00000000`773a15da : 00000000`00000000
    00000000
    `00000000 00000000`00000000 00000000`00000000 :
    nt!KiSystemServiceCopyEnd+0x13
    00000000`02e1e08 00000000`00000000 : 00000000`00000000 00000000
    
    `00000000 00000000`00000000 00000000`00000000 : 0x773a15da
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0xF4_nsd.exe_IMAGE__
    
    BUCKET_ID:  X64_0xF4_nsd.exe_IMAGE__
    
    Followup: MachineOwner
    ---------
    quit:
    

Local fix

Problem summary

  • This APAR is closed as FIN. We have deferred the fix to a
     future release.
    

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# IFAY9F7FHU.
    This APAR is closed as FIN. We have deferred the fix to a
     future release.
    

APAR Information

  • APAR number

    LO78589

  • Reported component name

    NOTES CLIENT

  • Reported component ID

    5724E6255

  • Reported release

    853

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-09

  • Closed date

    2014-06-25

  • Last modified date

    2014-06-25

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

  • R853 PSN

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTWP","label":"Lotus Notes"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.3","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 June 2014