System Reboots when trying to print

My computer works perfectly except when trying to print. When I try to
print, my computer reboots, inconsistently. Sometimes I can print fine,
other times, it reboots. I am using an Epson stylus color 600 ink jet
printer. I recently got a blue screen after trying to print, stating

A problem has been detected and windows has been shut down to prevent damage
to your computer

technical information:

***stop: 0x0000008E (0x000001D,0xBF8537BE,0xF47BE2DC,0x00000000)

*** win32k.sys - address BF8537BE base at BF800000, datestamp 41107F7a

Also, after restarting and logging on, I received this message:

The System has recovered from a serious error

Error signatu

BCCode: 1000008e BCP1: C000001D BCP2: BF8BBD05 BCP3: F4140E94
BCP4: 00000000 OSVer:5_1_2600 SP:1_0 Product: 256_1

Files included in error report:
c:\WINDOWS\Minidump\Mini062806-01.dmp
c:\Docume~1\Tom\LOCALS~1\Temp\WER2.tmp.dir00\sysda ta.xml

Does anyone have any advise for me on this problem. I have already
reformatted my hard drive and reloaded my software. My virus program says
my computer is clean. I ran a registry program and have no errors detected.
I ran a windows compatability report, and all my hardware/software is
detected as compatable. I am lost and do not know if this is a software or
hardware problem. I have been told by several people that it can be either.
HELP!
--
Tom D.

win32k.sys handles the fonts and graphics generation of the print data.
Have you sent the dump to Microsoft?

Do you have any special fonts loaded?



description of this type of bugcheck
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804f3ffd, The address that the exception occurred at
Arg3: f06d88a8, Trap Frame
Arg4: 00000000


--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"Tom D." wrote in message
...
My computer works perfectly except when trying to print. When I try to
print, my computer reboots, inconsistently. Sometimes I can print fine,
other times, it reboots. I am using an Epson stylus color 600 ink jet
printer. I recently got a blue screen after trying to print, stating

A problem has been detected and windows has been shut down to prevent
damage
to your computer

technical information:

***stop: 0x0000008E (0x000001D,0xBF8537BE,0xF47BE2DC,0x00000000)

*** win32k.sys - address BF8537BE base at BF800000, datestamp 41107F7a

Also, after restarting and logging on, I received this message:

The System has recovered from a serious error

Error signatu

BCCode: 1000008e BCP1: C000001D BCP2: BF8BBD05 BCP3: F4140E94
BCP4: 00000000 OSVer:5_1_2600 SP:1_0 Product: 256_1

Files included in error report:
c:\WINDOWS\Minidump\Mini062806-01.dmp
c:\Docume~1\Tom\LOCALS~1\Temp\WER2.tmp.dir00\sysda ta.xml

Does anyone have any advise for me on this problem. I have already
reformatted my hard drive and reloaded my software. My virus program
says
my computer is clean. I ran a registry program and have no errors
detected.
I ran a windows compatability report, and all my hardware/software is
detected as compatable. I am lost and do not know if this is a software
or
hardware problem. I have been told by several people that it can be
either.
HELP!
--
Tom D.

Thank you for your response. Unfortunately, I am not good with computers or
its terminology.

I did not send the dump to microsoft. How do I do this? What is the dump.
and what does reporting this do, Does Microsoft help me resolve the problem?

I have not loaded any special fonts.

How do I make sure a debugger gets connected, and the
system is booted /DEBUG.

Please advise. I am very bad with computers and need dummy instructions on
what to do. I treid using the Knowledge base page, but did not know what
keywords to enter for the search.
--
Tom D.


"Alan Morris [MSFT]" wrote:

win32k.sys handles the fonts and graphics generation of the print data.
Have you sent the dump to Microsoft?

Do you have any special fonts loaded?



description of this type of bugcheck
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804f3ffd, The address that the exception occurred at
Arg3: f06d88a8, Trap Frame
Arg4: 00000000


--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"Tom D." wrote in message
...
My computer works perfectly except when trying to print. When I try to
print, my computer reboots, inconsistently. Sometimes I can print fine,
other times, it reboots. I am using an Epson stylus color 600 ink jet
printer. I recently got a blue screen after trying to print, stating

A problem has been detected and windows has been shut down to prevent
damage
to your computer

technical information:

***stop: 0x0000008E (0x000001D,0xBF8537BE,0xF47BE2DC,0x00000000)

*** win32k.sys - address BF8537BE base at BF800000, datestamp 41107F7a

Also, after restarting and logging on, I received this message:

The System has recovered from a serious error

Error signatu

BCCode: 1000008e BCP1: C000001D BCP2: BF8BBD05 BCP3: F4140E94
BCP4: 00000000 OSVer:5_1_2600 SP:1_0 Product: 256_1

Files included in error report:
c:\WINDOWS\Minidump\Mini062806-01.dmp
c:\Docume~1\Tom\LOCALS~1\Temp\WER2.tmp.dir00\sysda ta.xml

Does anyone have any advise for me on this problem. I have already
reformatted my hard drive and reloaded my software. My virus program
says
my computer is clean. I ran a registry program and have no errors
detected.
I ran a windows compatability report, and all my hardware/software is
detected as compatable. I am lost and do not know if this is a software
or
hardware problem. I have been told by several people that it can be
either.
HELP!
--
Tom D.

The system creates a dump of the Operating System when it encounters a
failure and reboots the machine. The default file is \windows\memory.dmp
and is usually the size of your installed physically ram memory.

If you connect to the internet using dialup do not send the file.

Normally after a crash and report, Windows states you have recovered from a
serious error with a dialog asking if you want to send the file to
Microsoft. The file is sent, some tools parse through the OS crash file to
determine if this is a known problem.

I have a debugger attached and send any failure to a developer so they can
debug it. You do not need to attach a debugger.

Since I don't need to send the files, I don't know what the user experience
is after sending the file. I do know that there is a team at Microsoft
diligent at tracking the failures and making sure the vendor causing the
problem is informed even when that vendor is Microsoft.

Since your OS version is XP SP1, this may be fixed with a QFE or SP2

OSVer:5_1_2600 SP:1_0

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

"Tom D." wrote in message
...
Thank you for your response. Unfortunately, I am not good with computers
or
its terminology.

I did not send the dump to microsoft. How do I do this? What is the dump.
and what does reporting this do, Does Microsoft help me resolve the
problem?

I have not loaded any special fonts.

How do I make sure a debugger gets connected, and the
system is booted /DEBUG.

Please advise. I am very bad with computers and need dummy instructions
on
what to do. I treid using the Knowledge base page, but did not know what
keywords to enter for the search.
--
Tom D.


"Alan Morris [MSFT]" wrote:

win32k.sys handles the fonts and graphics generation of the print data.
Have you sent the dump to Microsoft?

Do you have any special fonts loaded?



description of this type of bugcheck
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804f3ffd, The address that the exception occurred at
Arg3: f06d88a8, Trap Frame
Arg4: 00000000


--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base he
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no
rights.

"Tom D." wrote in message
...
My computer works perfectly except when trying to print. When I try to
print, my computer reboots, inconsistently. Sometimes I can print
fine,
other times, it reboots. I am using an Epson stylus color 600 ink jet
printer. I recently got a blue screen after trying to print, stating

A problem has been detected and windows has been shut down to prevent
damage
to your computer

technical information:

***stop: 0x0000008E (0x000001D,0xBF8537BE,0xF47BE2DC,0x00000000)

*** win32k.sys - address BF8537BE base at BF800000, datestamp
41107F7a

Also, after restarting and logging on, I received this message:

The System has recovered from a serious error

Error signatu

BCCode: 1000008e BCP1: C000001D BCP2: BF8BBD05 BCP3: F4140E94
BCP4: 00000000 OSVer:5_1_2600 SP:1_0 Product: 256_1

Files included in error report:
c:\WINDOWS\Minidump\Mini062806-01.dmp
c:\Docume~1\Tom\LOCALS~1\Temp\WER2.tmp.dir00\sysda ta.xml

Does anyone have any advise for me on this problem. I have already
reformatted my hard drive and reloaded my software. My virus program
says
my computer is clean. I ran a registry program and have no errors
detected.
I ran a windows compatability report, and all my hardware/software is
detected as compatable. I am lost and do not know if this is a
software
or
hardware problem. I have been told by several people that it can be
either.
HELP!
--
Tom D.