Windows Server Hangs Up and Reboots Frequently

I have a Windows Server 2003 Server that is running some applications that interface our customer database.  The server seems to be running fine and suddenly hangs with a blue screen and reboots itself.  When you look at the event log it says "The computer has recovered from a bugcheck.  The bugcheck was 0x00000050" and it referneces the arguements that follow.  It saves the memory.dmp in its usual location.  I have run several diag utilities on the memory and they all show the system is okay.  I have reseated the memory and that has not proven to help.  I have un-installed the antivirus on the system also.  

When I analyze the memory.dmp it shows the following output.  I have looked at several versions and they all say the same thing but at a slightly different memory address.  The bf9806e8 is consistent through each message.  It references the nt!KiTrap0e+0xc8.  

Can someone help me through this?

Here is the dump file analysis.

0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arg1: eecfd000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf9806e8, If non-zero, the instruction address which referenced the bad memory
Arg4: 00000001, (reserved)

Debugging Details:

READ_ADDRESS:  eecfd000 Paged pool

bf9806e8 0fb70e           movzx   ecx,word ptr [esi]


IMAGE_NAME:  win32k.sys


MODULE_NAME:  win32k

FAULTING_MODULE: bf800000 win32k




LAST_CONTROL_TRANSFER:  from 8052fa2f to 80543ac9

b1fc819c 8052fa2f 00000050 eecfd000 00000000 nt!KeBugCheckEx+0x19
b1fc81ec 804e2dfc 00000000 eecfd000 00000000 nt!MmAccessFault+0x796
b1fc81ec bf9806e8 00000000 eecfd000 00000000 nt!KiTrap0E+0xc8
b1fc8294 bf981254 00000000 e2a134fe e2a13510 win32k!GrayFastExpAA_CX+0x51
b1fc846c bf8d35bc e2d0e278 e2d0e278 e2d0e240 win32k!FastExpAA_CY+0x42c
b1fc84b0 bf8d5007 e2d0e240 b1fc88f0 00ffffff win32k!AAHalftoneBitmap+0x445
b1fc84e4 bf8d63fe e2d0e118 e1886030 01fc868c win32k!HT_HalftoneBitmap+0x2a9
b1fc88cc bf87c7b3 e105e9c8 ed1ac638 00000000 win32k!EngHTBlt+0xa45
b1fc8b28 bf848700 e105e9c8 ed1ac638 00000000 win32k!EngStretchBlt+0x1a4
b1fc8ca4 bf8479cc 00000200 00000000 00000000 win32k!GreStretchDIBitsInternal+0xb99
b1fc8d1c 804dfd24 7e210615 00000000 00000000 win32k!NtGdiStretchDIBitsInternal+0xd2
b1fc8d1c 7ffe0304 7e210615 00000000 00000000 nt!KiSystemService+0xd0
02e0f27c 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4

STACK_COMMAND:  .bugcheck ; kb

bf9806e8 0fb70e           movzx   ecx,word ptr [esi]



FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  win32k!GrayFastExpAA_CX+51

FAILURE_BUCKET_ID:  0x50_win32k!GrayFastExpAA_CX+51

BUCKET_ID:  0x50_win32k!GrayFastExpAA_CX+51

Followup: MachineOwner

Who is Participating?
Jeffrey Kane - TechSoEasyConnect With a Mentor Principal ConsultantCommented:
Since this is most likely a driver error, you can follow the steps outlined in this article to help you determine which one it is:

wducoteAuthor Commented:
We also received a hotfix from Dell that helped us fix the driver.  Thanks for the troubleshooting tool though.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.