PAGE_FAULT_IN_NONPAGED_AREA (50)
Hi,
I have a problem with my server. The server runs Windows Server 2003 SP2 and it provides terminal services for some users, but yesterday the server restarted automatically, when I logged in to the server I noticed the following error:
Error code 00000050, parameter1 bc09aff4, parameter2 00000000, paraneter3 bf92af11, parameter 00000000
After that the server has been working and no problems have been reported, but I opened the dump file and noticed that RDPDD.dll was the possible culprit. I looked online to see if I could update the driver, but I did not find anything. Can someone
check the following and help me with a solution to the server restarting by itself. I would appreciate it, thank you.
Here is the Bugcheck analysis
7: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*
*
* 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: bc09aff4, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf92af11, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
READ_ADDRESS: bc09aff4 Paged session pool
FAULTING_IP:
win32k!bUMPDSecurityGateEx+11
bf92af11 8b80cc000000 mov eax,dword ptr [eax+0CCh]
MM_INTERNAL_CODE: 0
IMAGE_NAME: RDPDD.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 45d70aaf
MODULE_NAME: RDPDD
FAULTING_MODULE: bf800000 win32k
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 1
TRAP_FRAME: b9e6bf94 -- (.trap 0xffffffffb9e6bf94)
ErrCode = 00000000
eax=bc09af28 ebx=00000000 ecx=fffffff0 edx=bc39c5f0 esi=00000000 edi=bc01d5a8
eip=bf92af11 esp=b9e6c008 ebp=b9e6c060 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
win32k!bUMPDSecurityGateEx+0x11:
bf92af11 8b80cc000000 mov eax,dword ptr [eax+0CCh] ds:0023:bc09aff4=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8085ed25 to 80827c83
STACK_TEXT:
b9e6bf04 8085ed25 00000050 bc09aff4 00000000 nt!KeBugCheckEx+0x1b
b9e6bf7c 8088c800 00000000 bc09aff4 00000000 nt!MmAccessFault+0xb25
b9e6bf7c bf92af11 00000000 bc09aff4 00000000 nt!KiTrap0E+0xdc
b9e6c004 bf8ad7da bc01d5b8 b9e6c450 00000000 win32k!bUMPDSecurityGateEx+0x11
b9e6c060 bff6209a bc01d5b8 00000000 00000000 win32k!EngBitBlt+0x31
b9e6c3c8 bf89997b bc01d5b8 bc012018 00000000 RDPDD!DrvBitBlt+0x1b0
b9e6c418 bf899b77 bc39c5f8 b9e6c46c b9e6c450 win32k!GrePatBltLockedDC+0x1ea
b9e6c4b0 bf8b3292 b9e6c4e0 0000f0f0 b9e6c510 win32k!GrePolyPatBltInternal+0x17c
b9e6c4ec bf8b32fc 3201070d 00f00021 b9e6c510 win32k!GrePolyPatBlt+0x45
b9e6c524 bf894287 3201070d b9e6c568 01100068 win32k!FillRect+0x58
b9e6c548 bf894353 be380d20 be380d20 3201070d win32k!xxxPaintRect+0x70
b9e6c578 bf894308 be380d20 be380d20 3201070d win32k!xxxFillWindow+0x3e
b9e6c590 bf8ae2a7 be380d20 00000014 3201070d win32k!xxxDWP_EraseBkgnd+0x51
b9e6c5f0 bf8b4a29 be380d20 00000014 3201070d win32k!xxxRealDefWindowProc+0x318
b9e6c614 bf8a12cf be380d20 00000014 3201070d win32k!xxxDefWindowProc+0x10b
b9e6c654 bf8a132f be380d20 00000014 3201070d win32k!xxxSendMessageTimeout+0x18a
b9e6c678 bf8c1622 be380d20 00000014 3201070d win32k!xxxSendMessage+0x1b
b9e6c69c bf85e099 be380d20 00000000 00000001 win32k!xxxSendEraseBkgnd+0x5c
b9e6c6bc bf85ded9 be380d20 be380d20 be380d20 win32k!xxxSimpleDoSyncPaint+0xc6
b9e6c6d8 bf85d8f5 be380d20 00000004 00000000 win32k!xxxInternalDoSyncPaint+0x12
b9e6c734 bf85de2e be380d20 00000000 00000000 win32k!xxxEndDeferWindowPosEx+0x258
b9e6c750 bf87a343 be391810 00000000 00000000 win32k!xxxSetWindowPos+0xb1
b9e6c788 bf84abaf 00000010 00000097 000002f8 win32k!xxxShowWindow+0x201
b9e6c7d8 bf83c96d 00000000 b9e6c83c bf8b83c4 win32k!xxxDestroyWindow+0x1e9
b9e6c7e4 bf8b83c4 be1123a0 bc45c320 bc45c2a0 win32k!HMDestroyUnlockedObject+0x1c
b9e6c7f8 bf8b8775 8958b020 00000000 00000000 win32k!DestroyThreadsObjects+0x72
b9e6c83c bf8b701a 00000001 b9e6c864 bf8b7e77 win32k!xxxDestroyThreadInfo+0x206
b9e6c848 bf8b7e77 8958b020 00000001 00000000 win32k!UserThreadCallout+0x4b
b9e6c864 8094c38a 8958b020 00000001 8956cb78 win32k!W32pThreadCallout+0x3a
b9e6c8f0 8094c647 c0000005 b9e6c94c 8082e0d6 nt!PspExitThread+0x3b2
b9e6c8fc 8082e0d6 8956cb78 b9e6c948 b9e6c93c nt!PsExitSpecialApc+0x1d
b9e6c94c 8088a10f 00000001 00000000 b9e6c964 nt!KiDeliverApc+0x1ae
b9e6c94c 07889d3f 00000001 00000000 b9e6c964 nt!Kei386EoiHelper+0x37
WARNING: Frame IP not in any known module. Following frames may be wrong.
015e9ec4 00000000 00000000 00000000 00000000 0x7889d3f
STACK_COMMAND: kb
FOLLOWUP_IP:
RDPDD!DrvBitBlt+1b0
bff6209a 894524 mov dword ptr [ebp+24h],eax
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RDPDD!DrvBitBlt+1b0
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x50_RDPDD!DrvBitBlt+1b0
BUCKET_ID: 0x50_RDPDD!DrvBitBlt+1b0
Followup: MachineOwner
May 28th, 2010 10:52pm
Hi,
Please check if the following hotfix can help resolve the issue.
Stop error message on a terminal server that is running Windows Server 2003 SP1 or Windows Server 2003 SP2: "Stop 0x000000AB (SESSION_HAS_VALID_POOL_ON_EXIT)"
http://support.microsoft.com/kb/951749
If it does not help, I suggest that you contact Microsoft Customer Support Service (CSS) so that the dump file can be analyzed. To obtain the phone numbers for specific technology request, please take a look at the website listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBER
Thanks.This posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2010 9:20am
Hi,
In the future, it may be useful to also enable driver verifier,
http://mikemstech.blogspot.com/2011/12/troubleshooting-0x50.html-- Mike Burr
Technology
December 9th, 2011 3:14pm