Question Locked

PAGE_FAULT_IN_NONPAGED_AREA

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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

12 replies

by gary56789

winword.exe is trying to read from a memory location that it is not priviledged to read from. I would encourage you to uninstall/reinstall the program (MS Word/MS Office)and see what happens.

by geno291977

Thanks for your reply, after I got the error I reistalled the OS/ programs office apps. And it worked for a while but then it started happening again.

by matthewtrue

We were thinking that the issue may be caused by PPC E-tools add-in but we have not been able to stop the errors. I was just wondering do you use FX Engagement or PPC E-tools? We have tried reinstalling office and that doesn't work to fix the problem. We have had crashes caused by Outlook, Excel, and Word which is why we started looking into the possibility of it being caused by an add-in. The same error has occured on 3-4 different models of computers, desktop and laptops. The blue screens started shortly after we pushed out an updated e-tools version so that is why we looked at it. Manually uninstalling the framework then reinstalling seemed to fix the issue, but now on Jan 18th there was another update and uninstalling the framework and reinstalling it doesn't fix the issue. Our issues all started on Aug 27th just a couple days before yours. If you are not using E-tools then I think I will start looking at windows updates. The Arg3 is 80539b13, the FOLLOWUP_IP:
win32k!NtGdiAlphaBlend+b0b
bf83a147 ?? ???
also the Last Control Transfer matches bf83a147 to 80539b13

Thanks,
Matt

by geno291977

We are curently using PPC's e-Tools ver.2007.1.0.33. My reboots also happen when opening any of microsoft office apps. Every research I have done points to faulty RAM but we have purchased new notebooks and have had the reboot a day or two later.

by kburd

I have about 8-10 Dell laptops that this is happening on - same dump readout. We use Engagement and E-Tools... I did do an Engagement update to 5.0 as well as various windows updates along the way. It is my opinion that these are caused by Engagement add-ins to Office 2003...Perhaps the right words are "as Engagement relates to Office 2003. I am, however unable to qualify this with a specific driver. my reports from users are that they usually have Engagement opan and are working in a binder, when they switch to outlook to respond to or open an email. In the very least both Outlook and Engagement are open. I will post any updates.
Thanks

by nutshell02

We have the same problem on smoe user's computers and called Prosystem fx Engagement Support. They told us that this behavior was caused by a Microsoft critical or security update; they do not know which one, but Microsoft has released a hotfix: http://support.microsoft.com/kb/935198. You can get the hotfix from fx Enaggement Support, Microsoft, or TheHotfixShare.net. They say this has helped many users but not all. They are soliciting full kernel dumps and Microsoft Product Support Reporting cabinets. I was told that this would be fixed by Engagement 5.5, but a lot of good that does me right now! Your best bet is to talk to Support, I think.

by tuga_13

I have this error now, when i orinting Visio picture or loading Java runtime my laptop is restarting itself

by matthewtrue

We have applied the http://support.microsoft.com/kb/935198
hotfix which also has a patch 872797 included that has to do with dual monitors causing blue screens and we have not had anymore blue screens on any of our users that were having issues. One of the other things we did on all of these systems was remove E-tools from Add/Remove programs and reinstall it, so you may want to try that as well. We had the issue with engagement 4.9 and 5.0 so I don't think that engagement 5.0 is the cause. Seems like an e-tools update or windows update caused the issue since many of us started having the issue at almost exactly the same date. Good luck and I will post again if we find anything else out.

by adefiant1

I have a few users that are receiving the same error (Probably caused by : win32k.sys ( win32k!vSrcCopyS32D32Identity+5b ))

The few users that are having the issue have both Engagment and PPC E-Tools installed. Other users do not have those programs installed and are not having any issues.

Has anyone found a solution yet?

by tp

I also seem to have a very simular issue on multiple machine on our network I have downloaded and installed the hot fix mentioned earlier unsure if this is a fix yet. I see it happen whe users are opening a word or excel document. All the machine with the issue have PFX Engagement and PPC Etools they are running Office 2000. When I contacted PFX Support the tech did not seem to beleave my issue would be resolved by the patch said it was related to Office XP not 2000. Any help is greatly appreciated

by adefiant1

I uninstalled PPC etools on a Users computer first thing yesterday morning and they had no problems all day. This afternoon, they needed it reinstalled to do work for another client. Within and Hour of reinstalling Etools their computer locked up to a white-screen (anyone else's users have this issue? When accessing a file in Engagment, it white-screens and freezes for a few minutes, but sometimes recovers?) and then shortly after, the blue-screen and shutdown again.

We are using
Windows XP PRO SP2
Office 2003 SP3
Engagement 5.0.1029
PPC-Etools:
PBSE 1-07
PCNE 6-07
PCRE 7-07
PEBE 2-07
PLSE 2-07

This discussion is closed to new replies.