I know this question was probably asked before but I keep on getting a PAGE_FAULT_IN_NONPAGED_AREA (50).
Included is my dump file. I have tried moving the ram on the laptop to different slots.
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Mini083007-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Aug 30 09:04:26.245 2007 (GMT-6)
System Uptime: 0 days 1:11:58.791
Loading Kernel Symbols
……………………………………………………………………………………………………………………………..
Loading User Symbols
Loading unloaded module list
……………..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {e1e9c000, 0, 80539b13, 1}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+5b )
Followup: MachineOwner
———
1: 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: e1e9c000, 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: e1e9c000
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: WINWORD.EXE
LAST_CONTROL_TRANSFER: from bf83a147 to 80539b13
STACK_TEXT:
a9c3d868 bf83a147 e421a084 e1e9bfc8 00000040 nt!memmove+0x33
a9c3d88c bf839e00 00000010 a9c3db74 a9c3dacc win32k!vSrcCopyS32D32Identity+0x5b
a9c3daa0 bf83349f e421a018 00000000 a9c3dacc win32k!EngCopyBits+0x51a
a9c3dbe0 bf8f7fb5 00000001 e27bd480 00000000 win32k!GreSetDIBitsToDeviceInternal+0x95a
a9c3dc4c bf95bce1 25050abe 25050abe 00000000 win32k!GreSetDIBitsInternal+0x108
a9c3dc88 bf91c48b a201034b 25050abe 00000000 win32k!GreSetDIBits+0x5c
a9c3dcc4 bf91c970 00000010 00000000 a9c3dd30 win32k!DIBtoBMP+0xe5
a9c3dce8 bf8f986f 89b89300 00000428 89b89300 win32k!xxxGetDummyBitmap+0xc0
a9c3dd04 bf8f98df 89b89300 00000002 a9c3dd30 win32k!xxxGetClipboardData+0xb4
a9c3dd54 8054086c 00000002 0012ae70 0012ae9c win32k!NtUserGetClipboardData+0x72
a9c3dd54 7c90eb94 00000002 0012ae70 0012ae9c nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ae9c 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!vSrcCopyS32D32Identity+5b
bf83a147 83c40c add esp,0Ch
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6
SYMBOL_NAME: win32k!vSrcCopyS32D32Identity+5b
FAILURE_BUCKET_ID: 0x50_win32k!vSrcCopyS32D32Identity+5b
BUCKET_ID: 0x50_win32k!vSrcCopyS32D32Identity+5b
Followup: MachineOwner
