Terminal Server Stops Responding and Error 0x0000000A Appears on a Blue Screen

RoyATokeshi
March 1, 2004 7:42 pm

Microsoft states in their article: KB330305

Terminal Server Stops Responding and Error 0x0000000A Appears on a Blue Screen
View products that this article applies to.
This article was previously published under Q330305
SYMPTOMS
If all the following conditions exist, a server that is running Terminal Server may intermittently stop responding and display error code 0x0000000A on a blue screen:
The server is under heavy load.
Users frequently log on and log off.
One or more large printer driver is loaded in Kernel mode.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
--------------------------------------------------------------
06-Apr-2002 01:38 4.0.1381.33535 170,256 Gdi32.dll
12-Nov-2002 00:02 4.0.1381.33544 1,004,032 Ntkrnlmp.exe
12-Nov-2002 00:02 4.0.1381.33544 983,040 Ntoskrnl.exe
12-Nov-2002 00:09 4.0.1381.33544 332,048 User32.dll
10-Oct-2002 00:24 4.0.1381.33543 1,280,176 Win32k.sys
12-Nov-2002 00:09 4.0.1381.33544 196,368 Winsrv.dll

Note Because of file dependencies, this hotfix requires Windows NT Server 4.0, Terminal Server Edition, Service Pack 6.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The information in this article applies to:
Microsoft Windows NT Server 4.0 Terminal Server Edition
Microsoft Windows NT Server 4.0 Terminal Server Edition SP4
Microsoft Windows NT Server 4.0 Terminal Server Edition SP5
Microsoft Windows NT Server 4.0 Terminal Server Edition SP6
Last Reviewed: 6/18/2003 (4.0)
Keywords: kbbug kbfix kbQFE KB330305



Primary links

Custom Search

User login

Who's new

  • maczugaher
  • locksgydff
  • isotheces
  • ahundredyears7
  • Jacomijntjefu

Who's online

There are currently 0 users and 4 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.