NT server blue screen of death on hpltdrv1.dll

[Sue Graham]

My NT print server keeps has gone into the blue screen of death on several
occassions: The entry is

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e
(0xc0000005, 0xf17b7fc8, 0x00000000, 0x00000258). Microsoft Windows NT
[v15.1381]. A dump was saved in: C:\WINNT\MEMORY.DMP.

The offending file in the KMODE_EXCEPTION_NOT_HANDLED is hpltdrv1.dll

Once the server goes into a blue screen, after several seconds it will reboot.
Many times it will crash again with the same error with in several minutes of
the first hang.

Does anyone have any ideas what would be causing this?

[Michael Cheung_5]

Sue,

Do you have any service packs on the Print server? What else is running on the
print server? Does this happen only when this printer is configured? It might
also be possible that the hpltdrv1.dll is corrupt. Have you tried to download a
new driver for your printer? To stop your server from rebooting when you get
the blue screen make sure that under control panel~system~startup\shutdown tab
under recovery that you don't have automatic reboot checked.

[Andy Paras]

Help! Same problem: KMODE_EXCEPTION_NOT_HANDLED, different driver: EN1207D.SYS
(HP EN1207D-TX PCI 10/100 Fast Ethernet Adapter), downloaded from this site.
Anyone?

[Stephens Bo]

We have approx. 20 systems doing this on a frequent basis in HPBFDF2.DLL. Any
known bugs? Please e-mail me with any info.

Thanks.

[Mark Fuge]

We have a NT 4.0 SP6a Workstation getting a BSOD in a similar way only hpblaf2.dll.
Is this a problem with a printer driver? Our BSOD happens after printing a web page, usually where a graphic is split printed on two consecutive pages. Is there a fix from HP?

[Keith Siqueira]

BSOD..... Hpblaf2.dll is called after the memory dump from NT 4 workstation SP6a similarly to Mark Fuge's experience, however it is only with a HP 4SiMx laserjet and not our 8000 series printers and particularly when sending an Exel file to the aforementioned printer. One instance of printing a word doc also produced the same BSOD and called the same .dll. WHAT TO DO TO CORRECT THIS ????

[Ben Sartori]

We are getting exactly the same problem. It seems to occur completely at random, and has only affected a small number of users (included one very noisy one). I have been tracing and recording the simptoms for quite some time:

OS: NT4 Workstation (only one instance on w2k pro)

Printing from: email in Outlook 2k (1 instance of OL98) with attachment (1 instance without)
emails are usually sent from business collaborators in Japan or Korea - I am suspecting it may have something to do with the character sets

Printing to: HPLJ4100n, HPLJ8150n
Print drivers: Post Script
Print server: NT4 server sp6a
print ports: LP0

Problem is not specific to each client. If I print the users email to the same printer, it will crash my client as well. If I print it to a HPLJ8000n, it will print just fine (go figure)

I have upgraded all printer drivers on the file/print server to the latest revision with no success (this actually increased the occurances of the crash)

Most printers are using a 610n jetdirect card. I am contemplating upgrading the firmware.

This has got me stumped (and I don't like being stumped). The only success I have had so far is to print to the 8000n.

I have found a knowlegde based article on TechNet, but it doesn't apply to my Post Script drivers. Some of you may find this useful:

http://support.microsoft.com/support/kb/articles/Q230/9/36.ASP?LN=EN-US&SD=gn&FR=0&qry=Q230936&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=NTW40

Has anyone asked HP for a comment?? I need this problem solved.