Number of copies in print queue increases "automatically"

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Larry - 01 May 2005 04:37 GMT

This just started happening last week. When I send one document to the
printer, to print one copy, initially it shows 1 copy of 1 page. But as
the document prints, the number of copies indicated keeps increasing.
Have seen it go as high as 56 copies, before cancelling the job. It will
print continuously unless I cancel the job.

Sending the document direct rather than spooling, seems to result in 1
document.

The printer is fairly new (HP PSC-1315v). I did try removing, and
installing the latest HP driver, but it made no difference.

Any help will be very much appreciated.

Thanks,
Larry

Reply to this Message

PattyL - 01 May 2005 14:43 GMT

I would first try clean booting using the Msconfig utility to see if
something loading at Startup is causing the problem. See this article:

How to Troubleshoot Using the Msconfig Utility with Windows 98
http://support.microsoft.com/?kbid=281965

PattyL

> This just started happening last week. When I send one document to the
> printer, to print one copy, initially it shows 1 copy of 1 page. But as
[quoted text clipped - 12 lines]
> Thanks,
> Larry

Reply to this Message

Larry - 03 May 2005 03:46 GMT

PattyL,

Thanks for the reply. This problem is taking off in a slightly different
direction. I was using msconfig to remove some of the startup items and
then restarted, which resulted in a BSOD. Fatal Exception
OE@0028:C027EA63 in Vxd VMM(06) + 00003A63. Looking that up seems to
indicate registry corruption. Same BSOD when I tried again to restart.
So went to Safe Mode and undid the msconfig changes. It came up ok then.

At any rate, it reminded me, the secretary did say that it BSOD'd one
day last week on bootup, with the same Fatal Exception OE. She rebooted
and it came up with corrupted registry message, it offered to load an
earlier copy, and so then it came up ok. Maybe we have a memory problem?
Think I'll run a memory test...any other ideas are welcome!

Thanks,
Larry

> I would first try clean booting using the Msconfig utility to see if
> something loading at Startup is causing the problem. See this article:
[quoted text clipped - 20 lines]
>>Thanks,
>>Larry

Reply to this Message

PattyL - 06 May 2005 03:04 GMT

I'd be very curious to know which item that you removed caused the BSOD.
You might try configuring items loading at startup by opening the
application, then finding options or preferences and then look for a way to
disable loading at startup.

PattyL

> PattyL,
>
[quoted text clipped - 38 lines]
>>>Thanks,
>>>Larry

Reply to this Message

Larry - 08 May 2005 19:52 GMT

I don't recall exactly which startup items, I removed about half of
them. I'm still suspicious of a memory problem. IIRC, we had not altered
anything just prior to the problem's occurrence. It's behind a hardware
firewall, has AVG antivirus running, and checked by SpybotS&D and
Adaware on a regular basis.

Cleaning/reseating and testing the memory module will be my next move,
then back to msconfig.

Larry

> I'd be very curious to know which item that you removed caused the BSOD.
> You might try configuring items loading at startup by opening the
> application, then finding options or preferences and then look for a way to
> disable loading at startup.
>
> PattyL

Reply to this Message

Larry - 10 May 2005 06:10 GMT

Re-seated memory, ran DocMem (short test) and it tested good. Also ran
scandisk and let it do a surface scan on the "used" portion of the h.d.
No problems found. Then ran scanreg /fix. Started Windows, went to
msconfig, and unchecked all options. (Not to load Autoexec.bat,
config.sys, system.ini, win.ini, and startup items). Re-started Windows,
and as it came up, it reported registry corruption, and loaded a prior
registry copy. When it again re-started, msconfig had the startup items
checked. Next thing, I guess I'll try one startup item at a time.

BTW, it's clean of viruses, worms, trojans, etc. according to AVG v.7,
Spybot S&D 1.3, AdAware SE, and Stinger.

Larry

Reply to this Message