Bsod

I have multiple machine that are intermittently getting BSOD when opening Excel. The machines are connected together on a domain and the BSOD happens randomly about 1 every 2 weeks on different machine. I have analyzed the mini dump file and it appears to be the same issue on all the machines. The machine are all running Win XP SP2 are all up to date. They are also all running Office 2000 SP3.

 

This is the Dump file:


Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Travis Portenier\Desktop\Dump\Wayne\Mini020608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
Debug session time: Wed Feb 6 18:04:03.810 2008 (GMT-7)
System Uptime: 0 days 8:49:00.876
Loading Kernel Symbols
..............................................................................................................................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e75fb000, 0, 804d9da8, 1}


Could not read faulting driver name


Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+5b )

Followup: MachineOwner
---------

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
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.
Arguments:
Arg1: e75fb000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804d9da8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name



READ_ADDRESS: e75fb000

FAULTING_IP:
nt!memmove+33
804d9da8 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: Excel.exe

LAST_CONTROL_TRANSFER: from bf83a147 to 804d9da8

STACK_TEXT:
b5285868 bf83a147 e7d2e084 e75fafc8 00000040 nt!memmove+0x33
b528588c bf839e00 00000010 b5285b74 b5285acc win32k!vSrcCopyS32D32Identity+0x5b
b5285aa0 bf83349f e7d2e018 00000000 b5285acc win32k!EngCopyBits+0x51a
b5285be0 bf8f7fb5 00000001 e17f73e8 00000000 win32k!GreSetDIBitsToDeviceInternal+0x95a
b5285c4c bf95bce1 f205176a f205176a 00000000 win32k!GreSetDIBitsInternal+0x108
b5285c88 bf91c48b f2010f2d f205176a 00000000 win32k!GreSetDIBits+0x5c
b5285cc4 bf91c970 00000010 00000000 b5285d30 win32k!DIBtoBMP+0xe5
b5285ce8 bf8f986f 894e6370 00000428 894e6370 win32k!xxxGetDummyBitmap+0xc0
b5285d04 bf8f98df 894e6370 00000002 b5285d30 win32k!xxxGetClipboardData+0xb4
b5285d54 804de7ec 00000002 0013ee84 0013eeb0 win32k!NtUserGetClipboardData+0x72
b5285d54 7c90eb94 00000002 0013ee84 0013eeb0 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013eeb0 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!vSrcCopyS32D32Identity+5b
bf83a147 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: win32k!vSrcCopyS32D32Identity+5b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6

FAILURE_BUCKET_ID: 0x50_win32k!vSrcCopyS32D32Identity+5b

BUCKET_ID: 0x50_win32k!vSrcCopyS32D32Identity+5b

Followup: MachineOwner
---------

 

Does anyone have any ideas.