win32k.sys error page fault in nonpaged area

[Guest laith.mustafa@gmail.com]

We installed a 2003 Standard x64 bit SP1 server 4 months ago to serve

as Terminal Server for 200 thin client users.

 

No changes were made to the operating system but the server started

crashing a month ago every 2-3 days with the following error messgae:

 

win32k.sys error page fault in nonpaged area

 

I found the following article about this error that relates to Windows

2000:

 

http://support.microsoft.com/kb/q129845/

 

Is this relevant to 2003 64 bit SP1?

 

Is this fixed in SP2?

 

Any help is appreciated.

 

Laith

[Guest Vera Noest [MVP]]

Re: win32k.sys error page fault in nonpaged area

 

PAGE_FAULT_IN_NONPAGED_AREA is the description for Bug Check code

0x50.

 

Detailed information and troubleshooting tips for STOP error 0x50:

http://msdn2.microsoft.com/en-us/library/ms793437.aspx

 

Post-SP1 hotfix:

 

926128 - You receive a "STOP 0x50" error message that is related to

win32k!HmgDecrementShareReferenceCount+0xb on a Windows Server

2003-based terminal server

http://support.microsoft.com/?kbid=926128

 

If you use Cisco Security Agent:

909445 - Error message when you start a Terminal Services session

on a Windows Server 2003-based computer: "STOP: 0x00000050

(0xffffffe8, 0x00000001, 0x8083fb88, 0x00000000)"

http://support.microsoft.com/?kbid=909445

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

laith.mustafa@gmail.com wrote on 06 nov 2007 in

microsoft.public.windows.terminal_services:

> We installed a 2003 Standard x64 bit SP1 server 4 months ago to

> serve as Terminal Server for 200 thin client users.

>

> No changes were made to the operating system but the server

> started crashing a month ago every 2-3 days with the following

> error messgae:

>

> win32k.sys error page fault in nonpaged area

>

> I found the following article about this error that relates to

> Windows 2000:

>

> http://support.microsoft.com/kb/q129845/

>

> Is this relevant to 2003 64 bit SP1?

>

> Is this fixed in SP2?

>

> Any help is appreciated.

>

> Laith