There are a variety of reasons why a STOP 0x0000001E might occur. You may
wish to collect a memory dump for analysis and open a support incident with
Microsoft.
129845 Blue Screen Preparation Before Contacting Microsoft
http://support.microsoft.com/?id=129845
From the symptoms, it sounds like it might be a problem with your printer
driver? Can you see if updates are available for your printer model?
294690 "Stop 0x0000001E" Error Message in Ntoskrnl.exe
http://support.microsoft.com/?id=294690
247908 STOP 0x0000001e Error Occurs in Ntoskrnl.exe at Blue Build Screen
http://support.microsoft.com/?id=247908
--
--
Daniel Chang
Server Setup Team
Search our Knowledge Base at
http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at
http://www.microsoft.com/ntserver/
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.
: > Running Windows 2000 Professional on a Dell Inspiron 8000. Supposedly,
Dell doesn't have diagnostics tool for this model. Blue Screen of Death
occurs when laptop is on for awhile, and attempt to print anything that uses
up a lot of memory (ie from a browser, graphic filled word doc, etc.).
Complete error message is:
: >
: > ***STOP: 0x0000001E (0xC0000005, 0x8046B179, 0x00000001, 0x0909080C)
: > KMODE_EXCEPTION_NOT_HANDLED
: > ***Address 8046B179 base at 80400000, DateStamp 3ec6c002 - ntoskrnl.exe
: >
: > Been looking around in different newsgroups, etc. but can't find this
specific address, etc.
: > Appreciate any help.
:
: I'HAVE THE SAME PROBLEM (0x8046B179) BUT NOT THE SOLUTION.
