STOP Error when printing from ReportViewer

[Guest]

I am supporting a WinForms application at 10 sites with approximately 20
computers. This morning, the sites with a particular model of printer (HP
LaserJet 1300 or 1320) started getting STOP errors when printing certain
reports using ReportViewer.

Notes:
- My WinForms application has not changed
- Only some reports cause the STOP error (no pattern yet)
- Unable to cause STOP error from other programs (Excel, Word, etc)
- Updating the printer drivers does not help
- Error occurs on computers with printer attached locally and using shared
printer
- Error does not occur on any other printer models

It seems that there is a problem with the way ReportViewer uses the HP
drivers for these printer models.

Is anyone else having similar problems today?

 

[Guest]

The cause of the problem is a critical update from Microsoft (KB925902).
Removing the update has fixed the problem on 3 computers so far -- I still
have to remove it about 12 more.

What are the proper channels for reporting this problem to Microsoft?

 

[Bryan Phillips]

You need to contact Product Support Services (PSS) to report the bug
and/or get a hotfix. I had another weird problem with the ReportViewer
before that occurred when the logged on user did not have a default
printer selected.

--
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
Web Site: http://www.composablesystems.net

 

[Guest]

I spent yesterday afternoon on the phone with PSS. We don't have a solution
yet, but we have confirmed that KB925902 is the problem. I will post again
when a solution is available.

 

[Andy]

The cause of the problem is a critical update from Microsoft (KB925902).
Removing the update has fixed the problem on 3 computers so far -- I still
have to remove it about 12 more.

What are the proper channels for reporting this problem to Microsoft?

Well, the problem in this case is actually a misbehaving application.
I had an issue after installing that patch as well; the program was a
tray icon which allowed you to modify more sound settings than the
normal volume control.

The problem is that the program was loading an ocx control into a
reserved portion of system memory, which was previously allowed but
shouldn't have been, as this can lead to a security hole. The
'proper' solution would be for those with misbehaving programs to fix
their program to not load components into fixed parts of memory.

Don't report the problem to MS; instead report it to the application
vendors who have programs which no longer function.

 

[Guest]

I am actually the application developer and vendor.

It is *possible* that my application is loading an OCX control into a
reserved portion of memory, but since it's a .Net app with no unmanaged code
I find that unlikely.

Even in cases where the app vendor is at fault, MS should be notified.
Additional fixes such as the one for the Realtek audio problem may be created.

 

[Andy]

It is *possible* that my application is loading an OCX control into a
reserved portion of memory, but since it's a .Net app with no unmanaged code
I find that unlikely.

Is it possible you have a 3rd party assembly which is loading
unmanaged resources? That would seem pretty likely to me.

Even in cases where the app vendor is at fault, MS should be notified.

Why? What do you propose they do? Rollback the security fix, and
leave a hole which could allow code to take over the machine? Make an
exception for 'good vendors?' Neither of those seem like good options
to me.

Additional fixes such as the one for the Realtek audio problem may be created.

I'd rather lose the system tray icon (which is rather pointless
anyway) and have this patch than remove the patch and leave my system
vulnerable... or worse have a patch that allows exceptions that could
lead to further security holes..

 

[Bryan Phillips]

Can you post the details of the stop error? You can download a tool
called BlueSave from www.sysinternals.com that will save BOD's to the
file system when they occur.

--
Bryan Phillips
MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
Web Site: http://www.composablesystems.net

 

[Guest]

The solution to our printing problem was to replace the HP LaserJet 1300 and
1320 drivers. The PCL6 drivers caused the problem but the PCL5 or PCL5e
drivers work fine.

Andy, your diagnosis of a misbehaving application was incorrect. The problem
was the printer driver that was bundled with Windows and was WHQL signed.

 

[Guest]

--
Thorsten Gragert
http://www.thorsten.org

 

[Guest]

I'm having similar problems as you are experiencing.

Some reports using the ReportViewer control give a Stop error, blue screen
of death..

There are two workarounds that prevent the stop error from happening:
* Replace the Laserjet 4350 PLC 6 drivers by PS drivers
or
* Uninstall KB925902 security update

Both feel unsatisfactory.

The stop debug info is:

Arguments:

Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO

Arg2: 00000000

Arg3: 00000000

Arg4: 00000000



Debugging Details:

------------------





BUGCHECK_STR: 0x7f_0



TRAP_FRAME: 9cf279e8 -- (.trap ffffffff9cf279e8)

ErrCode = 00000000

eax=ffffffff ebx=e17aede4 ecx=00000000 edx=00000000 esi=00000000 edi=e32b6008

eip=bf903230 esp=9cf27a5c ebp=9cf27a94 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

win32k!UMPDDrvDitherColor+0x7d:

bf903230 f7f6 div eax,esi

Resetting default scope



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: DRIVER_FAULT



PROCESS_NAME: CustomerOrders.



LAST_CONTROL_TRANSFER: from 805a11d1 to 804f9dc6



STACK_TEXT:

9cf27984 805a11d1 0000007f bf903230 00000000 nt!KeBugCheck+0x14

9cf279dc 80541474 9cf279e8 9cf27a94 bf903230
nt!Ki386CheckDivideByZeroTrap+0x41

9cf279dc bf903230 9cf279e8 9cf27a94 bf903230 nt!KiTrap00+0x84

9cf27a94 bf81af4d e4df2008 00000002 00cc6600 win32k!UMPDDrvDitherColor+0x7d

9cf27b24 bf826e70 00000000 e4df2008 bf8c610c win32k!bGetRealizedBrush+0x2bd

9cf27b3c bf82f869 e17aede4 9cf27ccc e5532000 win32k!pvGetEngRbrush+0x1f

9cf27b98 bf805363 e4df2008 00000000 00000000 win32k!EngBitBlt+0x283

9cf27be8 bf80bd41 e17aede4 9cf27c6c 9cf27ccc win32k!GrePatBltLockedDC+0x1ea

9cf27d54 8054083d 00000124 03edc768 03edc7a4 win32k!NtGdiFlushUserBatch+0x689

9cf27ddc 8054532e ba73f450 9d86dab0 00000000 nt!KiFastCallEntry+0xcd

9cf27ea4 80519902 9cf277d8 ffdff548 03ffffff nt!KiThreadStartup+0x16

9cf27f30 00150000 7c910732 00000078 00151d08 nt!MiProcessValidPteList+0xf4

 

[Guest]

That confirms that the HP PCL6 drivers for recent printer models are the
problem.
We have a HP LaserJet 1160 that works fine even with the PCL6 driver.
I have reported the problem to HP.