Windows Minidump

[jholyak]

I'm having issues with computer getting the BSOD and I'm able to capture the minidump and expand it but I'm not very good at reading what they mean. I was hoping someone could help me and see if we can figure out why the computers are behaving this way. It seems the minidump points to an office product and I have uninstalled and reinstall MS Office but some machines still experience the BSOD. Other computers seem to work fine. Am I missing something? Any help or tips would be very much appreciated. Below is the analysis of the minidump. I have many more but each minidump either points to Outlook.exe, winword.exe or excel.exe.

Thank you in advance!
Joshua

*******************************************************************************
* *
* 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: ea317000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80539b13, 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: ea317000

FAULTING_IP:
nt!memmove+33
80539b13 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: OUTLOOK.EXE

LAST_CONTROL_TRANSFER: from bf83a147 to 80539b13

STACK_TEXT:
a7b011e8 bf83a147 ea1a5084 ea316fc8 00000040 nt!memmove+0x33
a7b0120c bf839e00 00000010 a7b014f4 a7b0144c win32k!vSrcCopyS32D32Identity+0x5b
a7b01420 bf83349f ea1a5018 00000000 a7b0144c win32k!EngCopyBits+0x51a
a7b01560 bf8f7fb5 00000001 e1a6f2d0 00000000 win32k!GreSetDIBitsToDeviceInternal+0x95a
a7b015cc bf95bce1 1e051457 1e051457 00000000 win32k!GreSetDIBitsInternal+0x108
a7b01608 bf91c48b a60114ec 1e051457 00000000 win32k!GreSetDIBits+0x5c
a7b01644 bf91c970 00000010 00000000 a7b016b0 win32k!DIBtoBMP+0xe5
a7b01668 bf8f986f 864ca038 00000428 864ca038 win32k!xxxGetDummyBitmap+0xc0
a7b01684 bf8f98df 864ca038 00000002 a7b016b0 win32k!xxxGetClipboardData+0xb4
a7b016d4 8054086c 00000002 0013ea24 0013ea50 win32k!NtUserGetClipboardData+0x72
a7b016d4 7c90eb94 00000002 0013ea24 0013ea50 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013ea50 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

 

[linney]

Are you using 2007 Office products, if so SP1 was released this week, which may help solve your problems, or conversely be causing them if you have already installed it?


These threads will give you some insight into debugging your dump file.

Debugging a DUMP file in XP
thread779-1292544

I wonder what if anything is the significance of this comment in your dump text, "Could not read faulting driver name"? Have you installed other hardware or software that may have preceded this BSOD error message?

When did this problem first occur? What if anything changed on your systems prior to it occurring?

If it is a driver problem of sorts then this article might help to discover a faulty driver.

HOW TO: Verify Unsigned Device Drivers in Windows XP

http://support.microsoft.com/support/kb/articles/q308/5/14.asp