Server abends with EIP in MBMMPRV.NSS at code start +00000C33h

[jdavis37]

Can anyone tell me what this means? See below:

Server OPDEV halted Wednesday, November 12, 2003 7:58:41.888 am
Abend 1 on P00: Server-5.00k: Page Fault Processor Exception (Error code 00000002)

Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = D2B49340 EBX = D2B49AC0 ECX = 00000000 EDX = 00000000
ESI = D2B49B20 EDI = D2B76100 EBP = 00000005 ESP = D71AFC68
EIP = D7F0CC33 FLAGS = 00010297
D7F0CC33 894204 MOV [EDX+04]=?,EAX
EIP in MBMMPRV.NSS at code start +00000C33h
Access Location: 0x00000004

The violation occurred while processing the following instruction:
D7F0CC33 894204 MOV [EDX+04],EAX
D7F0CC36 89C2 MOV EDX,EAX
D7F0CC38 8B03 MOV EAX,[EBX]
D7F0CC3A 8902 MOV [EDX],EAX
D7F0CC3C 8B4338 MOV EAX,[EBX+38]
D7F0CC3F 8B15F851F1D7 MOV EDX,[D7F151F8]=D2B49040
D7F0CC45 C70300000000 MOV [EBX],00000000
D7F0CC4B 895008 MOV [EAX+08],EDX
D7F0CC4E 8B531C MOV EDX,[EBX+1C]
D7F0CC51 83C408 ADD ESP,00000008



Running process: Server 18 Process
Created by: NetWare Application
Thread Owned by NLM: SERVER.NLM
Stack pointer: D71AF95C
OS Stack limit: D71A8040
Scheduling priority: 67371008
Wait state: 3030070 (Yielded CPU)
Stack: --D2B49AC0 ?
--00000002 ?
--D2B76100 ?
--D2B7610C ?
D7F107E0 (MBMMPRV.NSS|(Code Start)+47E0)
--D2B49AC0 ?
--00000000 ?
--D2B76100 ?
--00000005 ?
--00000005 ?
D7F10757 (MBMMPRV.NSS|(Code Start)+4757)
--D2B76100 ?
D07F9EF6 (NWPA.NLM|CDM_Alert_Routine+46)
--00000005 ?
--D2B76100 ?
D7F1063C (MBMMPRV.NSS|(Code Start)+463C)
--00000002 ?
--1FF4A440 ?
--00000003 ?
--00000002 ?
--1A9CC300 ?
D07FBDB0 (NWPA.NLM|CDI_Object_Update+57C)
--1A9CC300 ?
--00000297 ?
FC02A971 (SERVER.NLM|AllocMemoryDefault+A9)
--D0727A74 (NBI.NLM|SCISaveParms+E3C0)
--00000297 ?
--00000297 ?
--D1B5DA40 ?
--1A9CC5FC ?
--00606400 ?
--1A9CC5FC ?
-FC53A9AC (SERVER.NLM|AllocSizeTable+18)
--006063F8 ?
--00000000 ?
--00000002 ?
--00000000 ?
--D71AFD50 ?
FC02A75E (SERVER.NLM|AllocSleepOK+1AE)
--1A9CC300 ?
--00000100 ?
D0784943 (MM.NLM|MediaAlertRoutine+C7)
--1A9C3AE0 ?
--00000001 ?
--00000297 ?
FC02A971 (SERVER.NLM|AllocMemoryDefault+A9)
--D0727A74 (NBI.NLM|SCISaveParms+E3C0)
--00000297 ?
--00000297 ?
--00000000 ?
D7F105E0 (MBMMPRV.NSS|(Code Start)+45E0)
--00606700 ?
D0773EDE (MM.NLM|MM_CallApplicationAlert+86)
-FC53A9AC (SERVER.NLM|AllocSizeTable+18)
--006066F8 ?
--00000000 ?
--00000005 ?
--00000000 ?
--D71AFDA4 ?
FC02A75E (SERVER.NLM|AllocSleepOK+1AE)
--D0727A74 (NBI.NLM|SCISaveParms+E3C0)
--00000044 ?
--D07BD040 ?
--00000001 ?
--00000000 ?
FC0194AC (SERVER.NLM|kRWWriteUnlock+114)
--D0EC9FA4 ?
--1A9C3AE0 ?
--00000002 ?
D077575B (MM.NLM|MM_UnlockObject+7B)
--1A9CB78C ?
--00010000 (DS.NLM|DSD2418080+CCCD)
--1A9CB760 ?
--00000001 ?
--1A9CB760 ?
D0774A8B (MM.NLM|MM_ReleaseReservationHandles+77)
--00000000 ?
--00000005 ?
--1A9C3AE0 ?
--00000046 ?
--0000000B ?
--00000246 ?
D0775289 (MM.NLM|MM_ScheduleEvent+201)
--00606700 ?
--00000000 ?
--00000004 ?
--00000005 ?
--1A9C3AE0 ?
D07817E6 (MM.NLM|DeactivateIOObject+E6)
--00000000 ?
D0773F28 (MM.NLM|MM_CallNotifyRoutines+0)
--0000000B ?
--00000004 ?
--00000000 ?
--00000008 ?
--00000001 ?
--00000000 ?
--FFFFFFFF ?
--1A9CC300 ?
--00000000 ?

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

 

[marvhuffaker]

It means your server crashed.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[TheLad]

You cannot analyse every abend log and get an answer as every abend generated is different and often what is reported in the log is actually a red herring to why the server actually crashed in the first place.

As long as the server is up and running and does not suffer regularly from abends, you should be ok.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[shouldbblank]

Hello,

Just to be a bit more verbose than prior repies.

From your abend info I can tell you that one of the NSS (netware storage modules that control the newer style partitons and volumes) modules timed out one of the threads that the processor was working on. If it is a one time occurance that is fine but repeats are very bad. Ensure that you are running a current service pack release. There are NSS updates that are updated aside from the service packs.

I am currenly fighing a serious data loss due to NSS problems in ZLSS. Be careful, have two SMS backups of the data before updating anything.

HTH,
shouldbblank