Beginning a few weeks ago, the Groupwise server will abend sporatically. It sometimes runs a day or two, sometimes less than 12 hours. Any idea how to fix this?

I understand there's a problem with a beta patch for GW7. I'm not aware that I'm running a beta patch, but it's certainly possible. How can I tell?

Below is from the Health.log just before it abended:

Monday, 12-15-2008 1:35 am
Work To Do Response Time on server BH_GW has returned to the GOOD State
Current Value - 0
Peak Value - 1
Max Value - 1
Current SUSPECT threshold = More than 1 Tick(s) and Critical threshold = More than 2 Ticks
Current SUSPECT trigger delay = 10 and Critical trigger delay = 20

The following is from the abend.log (not sure how much you need to see, so I posted a few pieces I think hold the necessary info):

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.06

Server BH_GW halted Monday, December 15, 2008 1:50:08.073 am
Abend 1 on P00: Server-5.70.06: Page Fault Processor Exception (Error code 00000000)

CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 00000001 EBX = 9510394C ECX = 78A5A008 EDX = 78A59FFC
ESI = 00000004 EDI = 78A5A00C EBP = 985E7D00 ESP = 985E7CF4
EIP = 91F7936A FLAGS = 00010282
91F7936A 8B12 MOV EDX, [EDX]=?
EIP in LDAPSSL.NLM at code start +0000536Ah
Access Location: 0x78A59FFC

The violation occurred while processing the following instruction:
91F7936A 8B12 MOV EDX, [EDX]
91F7936C 8B5208 MOV EDX, [EDX+08]
91F7936F 2B5308 SUB EDX, [EBX+08]
91F79372 8955F4 MOV [EBP-0C], EDX
91F79375 837DF400 CMP [EBP-0C], 00000000
91F79379 7507 JNZ 91F79382
91F7937B B800000000 MOV EAX, 00000000
91F79380 EB1B JMP 91F7939D
91F79382 837DF400 CMP [EBP-0C], 00000000
91F79386 7E09 JLE 91F79391

then later in the log:

Running process: GWTCP-BHKM-Handler_6 Process
Thread Owned by NLM: GWPOA.NLM
Stack pointer: 985E7BC0
OS Stack limit: 985D91E0
Scheduling priority: 67371008
Wait state: 5050010 Blocked on a Mutex
Stack: --00020000 (LOADER.NLM|BIOSDriveCount+54AC)
--00000001 (LOADER.NLM|KernelAddressSpace+1)

Additional Information:
The CPU encountered a problem executing code in LDAPSSL.NLM. The problem may be in that module or in data passed to that module by a process owned by GWPOA.NLM.