When I say crash I am referring to a popup message that states KIX32.exe has stopped working and has the following error in the event log:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 3/1/2012
Time: 9:51:42 AM
User: N/A
Computer: VORTEX
Description:
Faulting application KIX32.EXE, version 0.0.0.0, faulting module KIX32.EXE, version 0.0.0.0, fault address 0x0002281f.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 4b 49 58 ure KIX
0018: 33 32 2e 45 58 45 20 30 32.EXE 0
0020: 2e 30 2e 30 2e 30 20 69 .0.0.0 i
0028: 6e 20 4b 49 58 33 32 2e n KIX32.
0030: 45 58 45 20 30 2e 30 2e EXE 0.0.
0038: 30 2e 30 20 61 74 20 6f 0.0 at o
0040: 66 66 73 65 74 20 30 30 ffset 00
0048: 30 32 32 38 31 66 02281f


When run in a command prompt
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\eappelstein>\\2003 Domain Controller with issue\netlogon\kix32.exe

C:\Users\eappelstein>\\2008 Domain Controller that works\netlogon\kix32.exe
KiXtart 2010 4.53 / Copyright Ruud van Velsen 2006
Microsoft Windows (logon) script processor.

Note: KiXtart is CareWare, please consult the manual for full details
on distribution and licensing.

Usage :

KIX32 [script1] [...] [$var=123] [/f[:yyyy/mm/dd]] [/r:irel] [/u:password] [/d] [/t]

Options:
/d = enable debug mode
/f = flush token cache (optionally only if older than date specified)
/r = KXRPC search order (see manual for details)
/u = password to lock or unlock a pre-tokenized script
/t = tokenize scripts (see manual for details)


C:\Users\eappelstein>\\2003 Domain Controller that works\netlogon\kix32.exe
KiXtart 2010 4.53 / Copyright Ruud van Velsen 2006
Microsoft Windows (logon) script processor.

Note: KiXtart is CareWare, please consult the manual for full details
on distribution and licensing.

Usage :

KIX32 [script1] [...] [$var=123] [/f[:yyyy/mm/dd]] [/r:irel] [/u:password] [/d] [/t]

Options:
/d = enable debug mode
/f = flush token cache (optionally only if older than date specified)
/r = KXRPC search order (see manual for details)
/u = password to lock or unlock a pre-tokenized script
/t = tokenize scripts (see manual for details)




This server is in a branch office so swapping out ther RAM would be very difficult and there are no other issues with this servers. The other domain controllers that work some are older and some newer.

My concern is if the file is corrupt what is the best way to replace since these folders replicate to each other and I do not want to make things worse. The current work around is people in that office are running their logon script from a different domain controller in a different office.