PC does hard reset (intermittantly) when printing

  • Thread starter Thread starter Lang Murphy
  • Start date Start date
L

Lang Murphy

Fairly recent problem (within last two months... of which I was on the road
for a month...)

eMachines AMD box with a NEC 1260 hanging off it. When print jobs are sent
the PC does a hard reset, no BSOD, no entries in the event logs, no dump
files created. Just BANG! back to POST. Can only assume the root cause is
the print spooler because I've sent print jobs from another computer on the
local net and the eMachines hard reset when the job was sent to the printer.
Well... and this could be important... at a specific point because the
printer starts blinking like the job is being sent but when the printer
actually starts to print the job is when the PC dies.

This PC and printer have been working for a couple of years without issue. I
am not aware of specific new software that might be causing this problem.
The problem is intermittant. (Lovely! NOT!) Could it be that the printer
itself is causing the hard reset when it starts to print the job? I'm lost
at this point...

Thanks,

Lang
 
How is the printer connected to the PC or the LAN?
That question aside, have you considered a power problem of some type?
Grounding for instance?
Are the PC and printer operating from the same wall wart (AC plug), or
connected to the same plug strip?
Is the printer a laser printer? These can have a large momentary AC load
when the guts start churning around.
It may be time to check for bad grounding and AC power voltage sag under the
printer load.
Some printers obtain power from the USB port for communications and start
from standby reasons. It's remotely possible that this is causing the
problem.
There is also a possibility that the PC power supply is sick, and quitting
momentarily due to input AC sag.
 
Chuck said:
How is the printer connected to the PC or the LAN?
That question aside, have you considered a power problem of some type?
Grounding for instance?
Are the PC and printer operating from the same wall wart (AC plug), or
connected to the same plug strip?
Is the printer a laser printer? These can have a large momentary AC load
when the guts start churning around.
It may be time to check for bad grounding and AC power voltage sag under
the
printer load.
Some printers obtain power from the USB port for communications and start
from standby reasons. It's remotely possible that this is causing the
problem.
There is also a possibility that the PC power supply is sick, and quitting
momentarily due to input AC sag.
Click to expand...


Chuck,

Thanks; good info.Both the PC and the printer are plugged into an APC
back-up power supply. From the very beginning of using these two components,
when a print job was sent, the APC would beep but the print job would
complete. Now it seems that the APC does not beep... so maybe the APC's
battery is marginal and sometimes it lets the job print and sometimes it
blows everything up?

Thanks,

Lang
 
I had the same problem a couple of months ago with KB925902. A couple of
users blue screen every time they printed to a Ricoh multifunction. After
removing MS patch 925902, everything was A OK.

good luck

jamie
 
Alan Morris said:
Jama's probably correct. There is another patch for this.



GDI security patch

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

Stop 0x0000007F error when you try to print from computers that are
running Windows XP or Windows 2000 and that have GDI security update
925902 installed




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

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

jama said:
I had the same problem a couple of months ago with KB925902. A couple of
users blue screen every time they printed to a Ricoh multifunction.
After
removing MS patch 925902, everything was A OK.

good luck

jamie
Click to expand...
Click to expand...


But I'm not getting a BSOD (so no dump file) or entries in the event logs;
the PC does a hard reset. I disconnected the PC from the APC power backup
and was able to print this morning. Guess I have to continue to test
throughout the day as it's an intermittent problem. If the problem persists
after disconnecting the PC from the APC unit then I will follow up with both
yours and the OP's patch recommendations.

Thanks!

Lang
 
Sorry I read the message as you got BSOD.

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

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

Lang Murphy said:
Alan Morris said:
Jama's probably correct. There is another patch for this.



GDI security patch

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

Stop 0x0000007F error when you try to print from computers that are
running Windows XP or Windows 2000 and that have GDI security update
925902 installed




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

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

jama said:
I had the same problem a couple of months ago with KB925902. A couple of
users blue screen every time they printed to a Ricoh multifunction.
After
removing MS patch 925902, everything was A OK.

good luck

jamie




:

How is the printer connected to the PC or the LAN?
That question aside, have you considered a power problem of some
type?
Grounding for instance?
Are the PC and printer operating from the same wall wart (AC plug),
or
connected to the same plug strip?
Is the printer a laser printer? These can have a large momentary AC
load
when the guts start churning around.
It may be time to check for bad grounding and AC power voltage sag
under
the
printer load.
Some printers obtain power from the USB port for communications and
start
from standby reasons. It's remotely possible that this is causing the
problem.
There is also a possibility that the PC power supply is sick, and
quitting
momentarily due to input AC sag.


Fairly recent problem (within last two months... of which I was on
the
road
for a month...)

eMachines AMD box with a NEC 1260 hanging off it. When print jobs
are
sent
the PC does a hard reset, no BSOD, no entries in the event logs, no
dump
files created. Just BANG! back to POST. Can only assume the root
cause is
the print spooler because I've sent print jobs from another computer
on
the
local net and the eMachines hard reset when the job was sent to the
printer.
Well... and this could be important... at a specific point because
the
printer starts blinking like the job is being sent but when the
printer
actually starts to print the job is when the PC dies.

This PC and printer have been working for a couple of years without
issue.
I
am not aware of specific new software that might be causing this
problem.
The problem is intermittant. (Lovely! NOT!) Could it be that the
printer
itself is causing the hard reset when it starts to print the job?
I'm
lost
at this point...

Thanks,

Lang





Chuck,

Thanks; good info.Both the PC and the printer are plugged into an APC
back-up power supply. From the very beginning of using these two
components,
when a print job was sent, the APC would beep but the print job would
complete. Now it seems that the APC does not beep... so maybe the APC's
battery is marginal and sometimes it lets the job print and sometimes
it
blows everything up?

Thanks,

Lang
Click to expand...
Click to expand...


But I'm not getting a BSOD (so no dump file) or entries in the event logs;
the PC does a hard reset. I disconnected the PC from the APC power backup
and was able to print this morning. Guess I have to continue to test
throughout the day as it's an intermittent problem. If the problem
persists after disconnecting the PC from the APC unit then I will follow
up with both yours and the OP's patch recommendations.

Thanks!

Lang
Click to expand...
 
Alan Morris said:
Sorry I read the message as you got BSOD.

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

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

Lang Murphy said:
Alan Morris said:
Jama's probably correct. There is another patch for this.



GDI security patch

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

Stop 0x0000007F error when you try to print from computers that are
running Windows XP or Windows 2000 and that have GDI security update
925902 installed




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

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

I had the same problem a couple of months ago with KB925902. A couple
of
users blue screen every time they printed to a Ricoh multifunction.
After
removing MS patch 925902, everything was A OK.

good luck

jamie




:

How is the printer connected to the PC or the LAN?
That question aside, have you considered a power problem of some
type?
Grounding for instance?
Are the PC and printer operating from the same wall wart (AC plug),
or
connected to the same plug strip?
Is the printer a laser printer? These can have a large momentary AC
load
when the guts start churning around.
It may be time to check for bad grounding and AC power voltage sag
under
the
printer load.
Some printers obtain power from the USB port for communications and
start
from standby reasons. It's remotely possible that this is causing
the
problem.
There is also a possibility that the PC power supply is sick, and
quitting
momentarily due to input AC sag.


Fairly recent problem (within last two months... of which I was on
the
road
for a month...)

eMachines AMD box with a NEC 1260 hanging off it. When print jobs
are
sent
the PC does a hard reset, no BSOD, no entries in the event logs, no
dump
files created. Just BANG! back to POST. Can only assume the root
cause is
the print spooler because I've sent print jobs from another
computer on
the
local net and the eMachines hard reset when the job was sent to the
printer.
Well... and this could be important... at a specific point because
the
printer starts blinking like the job is being sent but when the
printer
actually starts to print the job is when the PC dies.

This PC and printer have been working for a couple of years without
issue.
I
am not aware of specific new software that might be causing this
problem.
The problem is intermittant. (Lovely! NOT!) Could it be that the
printer
itself is causing the hard reset when it starts to print the job?
I'm
lost
at this point...

Thanks,

Lang





Chuck,

Thanks; good info.Both the PC and the printer are plugged into an APC
back-up power supply. From the very beginning of using these two
components,
when a print job was sent, the APC would beep but the print job would
complete. Now it seems that the APC does not beep... so maybe the
APC's
battery is marginal and sometimes it lets the job print and sometimes
it
blows everything up?

Thanks,

Lang
Click to expand...


But I'm not getting a BSOD (so no dump file) or entries in the event
logs; the PC does a hard reset. I disconnected the PC from the APC power
backup and was able to print this morning. Guess I have to continue to
test throughout the day as it's an intermittent problem. If the problem
persists after disconnecting the PC from the APC unit then I will follow
up with both yours and the OP's patch recommendations.

Thanks!

Lang
Click to expand...
Click to expand...


No problem; I appreciate all efforts at assistance.

Lang
 
I'd likely do the patches anyway.
(Although I have run XP32 SP2 in the past, currently, my main production
machine is actually between SP-1a and 2 due to some hardware driver
compatibility problems.
XP 64 is just starting to become useful, again, due to hardware drivers.
(Shared multifunction printer, and some network storage devices.)
Vista has some application related issues, such as having to update the
application before Vista is installed, since the updates will not install
after an upgrade to Vista.

Lang Murphy said:
Alan Morris said:
Sorry I read the message as you got BSOD.

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

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

Lang Murphy said:
Jama's probably correct. There is another patch for this.



GDI security patch

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

Stop 0x0000007F error when you try to print from computers that are
running Windows XP or Windows 2000 and that have GDI security update
925902 installed




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

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

I had the same problem a couple of months ago with KB925902. A couple
of
users blue screen every time they printed to a Ricoh multifunction.
After
removing MS patch 925902, everything was A OK.

good luck

jamie




:

How is the printer connected to the PC or the LAN?
That question aside, have you considered a power problem of some
type?
Grounding for instance?
Are the PC and printer operating from the same wall wart (AC plug),
or
connected to the same plug strip?
Is the printer a laser printer? These can have a large momentary AC
load
when the guts start churning around.
It may be time to check for bad grounding and AC power voltage sag
under
the
printer load.
Some printers obtain power from the USB port for communications and
start
from standby reasons. It's remotely possible that this is causing
the
problem.
There is also a possibility that the PC power supply is sick, and
quitting
momentarily due to input AC sag.


Fairly recent problem (within last two months... of which I was on
the
road
for a month...)

eMachines AMD box with a NEC 1260 hanging off it. When print jobs
are
sent
the PC does a hard reset, no BSOD, no entries in the event logs, no
dump
files created. Just BANG! back to POST. Can only assume the root
cause is
the print spooler because I've sent print jobs from another
computer on
the
local net and the eMachines hard reset when the job was sent to the
printer.
Well... and this could be important... at a specific point because
the
printer starts blinking like the job is being sent but when the
printer
actually starts to print the job is when the PC dies.

This PC and printer have been working for a couple of years without
issue.
I
am not aware of specific new software that might be causing this
problem.
The problem is intermittant. (Lovely! NOT!) Could it be that the
printer
itself is causing the hard reset when it starts to print the job?
I'm
lost
at this point...

Thanks,

Lang





Chuck,

Thanks; good info.Both the PC and the printer are plugged into an APC
back-up power supply. From the very beginning of using these two
components,
when a print job was sent, the APC would beep but the print job would
complete. Now it seems that the APC does not beep... so maybe the
APC's
battery is marginal and sometimes it lets the job print and sometimes
it
blows everything up?

Thanks,

Lang





But I'm not getting a BSOD (so no dump file) or entries in the event
logs; the PC does a hard reset. I disconnected the PC from the APC power
backup and was able to print this morning. Guess I have to continue to
test throughout the day as it's an intermittent problem. If the problem
persists after disconnecting the PC from the APC unit then I will follow
up with both yours and the OP's patch recommendations.

Thanks!

Lang
Click to expand...
Click to expand...


No problem; I appreciate all efforts at assistance.

Lang
Click to expand...
 
Chuck said:
I'd likely do the patches anyway.
(Although I have run XP32 SP2 in the past, currently, my main production
machine is actually between SP-1a and 2 due to some hardware driver
compatibility problems.
XP 64 is just starting to become useful, again, due to hardware drivers.
(Shared multifunction printer, and some network storage devices.)
Vista has some application related issues, such as having to update the
application before Vista is installed, since the updates will not install
after an upgrade to Vista.

Lang Murphy said:
Alan Morris said:
Sorry I read the message as you got BSOD.

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

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

Jama's probably correct. There is another patch for this.



GDI security patch

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

Stop 0x0000007F error when you try to print from computers that are
running Windows XP or Windows 2000 and that have GDI security update
925902 installed




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

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

I had the same problem a couple of months ago with KB925902. A
couple
of
users blue screen every time they printed to a Ricoh multifunction.
After
removing MS patch 925902, everything was A OK.

good luck

jamie




:

How is the printer connected to the PC or the LAN?
That question aside, have you considered a power problem of some
type?
Grounding for instance?
Are the PC and printer operating from the same wall wart (AC plug),
or
connected to the same plug strip?
Is the printer a laser printer? These can have a large momentary AC
load
when the guts start churning around.
It may be time to check for bad grounding and AC power voltage
sag
under
the
printer load.
Some printers obtain power from the USB port for communications and
start
from standby reasons. It's remotely possible that this is causing
the
problem.
There is also a possibility that the PC power supply is sick, and
quitting
momentarily due to input AC sag.


Fairly recent problem (within last two months... of which I was on
the
road
for a month...)

eMachines AMD box with a NEC 1260 hanging off it. When print
jobs
are
sent
the PC does a hard reset, no BSOD, no entries in the event logs, no
dump
files created. Just BANG! back to POST. Can only assume the root
cause is
the print spooler because I've sent print jobs from another
computer on
the
local net and the eMachines hard reset when the job was sent to the
printer.
Well... and this could be important... at a specific point because
the
printer starts blinking like the job is being sent but when the
printer
actually starts to print the job is when the PC dies.

This PC and printer have been working for a couple of years without
issue.
I
am not aware of specific new software that might be causing this
problem.
The problem is intermittant. (Lovely! NOT!) Could it be that the
printer
itself is causing the hard reset when it starts to print the
job?
I'm
lost
at this point...

Thanks,

Lang





Chuck,

Thanks; good info.Both the PC and the printer are plugged into an APC
back-up power supply. From the very beginning of using these two
components,
when a print job was sent, the APC would beep but the print job would
complete. Now it seems that the APC does not beep... so maybe the
APC's
battery is marginal and sometimes it lets the job print and sometimes
it
blows everything up?

Thanks,

Lang





But I'm not getting a BSOD (so no dump file) or entries in the event
logs; the PC does a hard reset. I disconnected the PC from the APC power
backup and was able to print this morning. Guess I have to continue to
test throughout the day as it's an intermittent problem. If the
problem
persists after disconnecting the PC from the APC unit then I will follow
up with both yours and the OP's patch recommendations.

Thanks!

Lang
Click to expand...


No problem; I appreciate all efforts at assistance.

Lang
Click to expand...
Click to expand...


OK... I'll check out the patches... not sure what you mean about apps on
Vista. I've only done clean Vista installs; I assume you're talking about
Vista upgrades?

Lang
 
Lang Murphy said:
Fairly recent problem (within last two months... of which I was on the
road for a month...)

eMachines AMD box with a NEC 1260 hanging off it. When print jobs are sent
the PC does a hard reset, no BSOD, no entries in the event logs, no dump
files created. Just BANG! back to POST. Can only assume the root cause is
the print spooler because I've sent print jobs from another computer on
the local net and the eMachines hard reset when the job was sent to the
printer. Well... and this could be important... at a specific point
because the printer starts blinking like the job is being sent but when
the printer actually starts to print the job is when the PC dies.

This PC and printer have been working for a couple of years without issue.
I am not aware of specific new software that might be causing this
problem. The problem is intermittant. (Lovely! NOT!) Could it be that the
printer itself is causing the hard reset when it starts to print the job?
I'm lost at this point...

Thanks,

Lang
Click to expand...


Just a follow-up... disconnecting my PC from the UPS seems to have fixed the
problem. Haven't had a single hard reset since removing PC from UPS. Odd...
but glad I found the core problem.

Thanks for everyone's feedback: appreciated!

Lang
 
Back
Top