Server BlueScreens with 0x00000050 (0xea9ec008, 0x00000000, 0xbe38

[Guest]

Compaq Server running W2K SP3

From System log:
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050
(0xea9ec008, 0x00000000, 0xbe3850ae, 0x00000001). A dump was saved in:
Microsoft Windows 2000 [v15.2195].


I originally thought this was related to Open Transaction Manager
(otman5.sys) running on the server, but I have removed this driver and the
issue persists.

I'm not sure if its related but on reboot the following error is reported in
the System Log:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Description:
Application popup: Windows - Virtual Memory Minimum Too Low : Your system is
low on virtual memory. Windows is increasing the size of your virtual memory
paging file. During this process, memory requests for some applications may
be denied. For more information, see Help.


I am in the process of updating NIC drivers and possibly drivers for the
RAID controller.

I haven't found any information on this particlular stop message. If anyone
has suggestions...

 

[Mark-Allen Perry]

Check: http://support.microsoft.com/search...&cat=false&query=0x00000050+bugcheck&srch=sup

But it appears to be a driver problem. Can you get back to the "Last Known Good Configuration"? Use F8 on boot.

And you should address the virtual memory (pagefile) problem, which could be causing this.

See if you can get into Safe Mode, the Control Panel, System, Advanced, Performance, Virtual Memory, Change. Set it to begin with 512, 512. This should at least remove this problem.

Then post back the results.

--

Always try the MS KB first before posting.
MS KB: http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO
And the answer could have already been posted, so try searching this and other newsgroups first.
----
Mark-Allen Perry
ALPHA Systems
Marly, Switzerland
mark-allen_AT_mvps_DOT_org

Compaq Server running W2K SP3

From System log:
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050
(0xea9ec008, 0x00000000, 0xbe3850ae, 0x00000001). A dump was saved in:
Microsoft Windows 2000 [v15.2195].


I originally thought this was related to Open Transaction Manager
(otman5.sys) running on the server, but I have removed this driver and the
issue persists.

I'm not sure if its related but on reboot the following error is reported in
the System Log:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Description:
Application popup: Windows - Virtual Memory Minimum Too Low : Your system is
low on virtual memory. Windows is increasing the size of your virtual memory
paging file. During this process, memory requests for some applications may
be denied. For more information, see Help.


I am in the process of updating NIC drivers and possibly drivers for the
RAID controller.

I haven't found any information on this particlular stop message. If anyone
has suggestions...

 

[Guest]

Thanks for the information Mark-Allen.

I have updated to the latest compaq softpaq (which updates all drivers), no
success in resolving the issue.

I have requested the memory.dmp from the server. I will review it and post
my findings.

As for making changes to the virtual memory settings, I have not tried this
yet. This will be my next step.

 

[Guest]

Another update. I have taken a look at the memory dump from the server.
The results are listed below. I have done research and it looks like this
may be related to bad memory or NIC drivers (as I had suspected). I will be
replacing memory and contacting compaq for more information. If any one has
anything to add....




Probably caused by : ntkrnlmp.exe ( nt!Kei386EoiHelper+173f )
Followup: MachineOwner
--------
0: kd> k
ChildEBP RetAddr
WARNING: Stack unwind information not available. Following frames may be
wrong.
00000000 00000000 nt!Kei386EoiHelper+0x173f
0: kd> !analyze -v
******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

BUGCHECK_STR: 0x7f_8

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 00000000 to 80468cff

STACK_TEXT:
0000000 00000000 00000000 00000000 00000000 nt!Kei386EoiHelper+0x173f
FOLLOWUP_IP:
nt!Kei386EoiHelper+173f
80468cff ebef jmp nt!Kei386EoiHelper+0x1730 (80468cf0)

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!Kei386EoiHelper+173f

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 40d1d19a

STACK_COMMAND: kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------