Bug Check

  • Thread starter Thread starter Chuck
  • Start date Start date
C

Chuck

Atleast once a day I am getting a reboot from a bug check
0x0000001e (0xc0000005, 0xa00bd537, 0x00000000,
0x00000000). I am running 2000 server with metaframe
loaded on it. Any help would be appreciated.

Thanks
Chuck
 
http://www.osr.com/ddk/ddtools/bccodes_763r.ht

Do you have 3rd party print drivers loaded on the MF Server? These are notorious for causing BSOD. More info here

http://www.workthin.com/tsp.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Chuck wrote: ----

Atleast once a day I am getting a reboot from a bug check
0x0000001e (0xc0000005, 0xa00bd537, 0x00000000,
0x00000000). I am running 2000 server with metaframe
loaded on it. Any help would be appreciated.

Thank
Chuc
 
I am having the same issue under the same conditions:
Win2k (SP4) TS running Metaframe 1.8 (SP4)

At least once (but more often 2 or 3 times) per day the
server reboots with KMODE_EXCEPTION Stop code 0x0000001e
and always related to win32k.sys

All the printers installed at the terminal server are HP
(2000 and 4000) and were installed directly from Win2k
install (didn't use HP download, HP install CD or other
install).

In addition, all the printers are HP print server
(TCP/IP) connected rather than as shared printers
connected to a local workstation.

All of the MSKB articles indicate that this is/was a
WinNT4 issue that was resolved after SP3, and there are
ZERO KB articles of this issue related to Win2k, but I
can assure you this is not a figment of my imagination.

Any insight would be helpful, and I have read the
referenced material in the previous response to this
suject.
 
I get 38 hits when I search the KnowledgeBase for product Windows
2000 and STOP 0x1E and win32k.sys:

http://support.microsoft.com/search/default.aspx?
InCC_hdn=true&Catalog=LCID%3D1033%26CDID%3DEN-US-KB%26PRODLISTSRC%
3DON&withinResults=&QuerySource=gASr_Query&Product=win2000
&Queryc=STOP+0x1E+win32k.sys&Query=STOP+
0x1E+win32k.sys&KeywordType=ALL&maxResults=100
&Titles=false&numDays=&InCC=on

While a non-compatible printer driver is the most common cause for
STOP errors, there are lots of other possibilities. Other 3th
party services, drivers, anti-virus packages, faultly hardware,
BIOS memory caching, etc.

How long has this problem been going on? Is there anything at all
that changed on your server prior to the start of this problem?
 
Back
Top