Windows NT 4.0 Stop Error

[Mike Noble]

We're getting blue screens on a particular Windows NT 4.0 workstation - Stop 0x0000001E in HPBFDF2.DLL. Workstation is running SP 5, our NT print server is running SP 4. Haven't found it on any other workstation, but it's a real problem for our one user. Any ideas welcome.

[Mike McKinlay]

When does the blue screen occur? Can you recreate it at will?

[Jamie Hughes]

Hello Mike,

The STOP 1E is a very common (and somewhat generic) error condition that is most frequently caused by a corrupt or bad driver. It sounds like it is pinpointing the bad driver - hpbfdf2.dll. I believe that driver is part of the LaserJet 4xxx family. You also mentioned your print server so it sounds like the workstation is crashing when they print.

I would first update the driver on the client. The latest driver might be installed but it could be corrupt. If that doesn't resolve the problem, you will most likely have to have the dump read but I don't think it will tell you much more than you have a bad driver. If you were to debug the dump, I believe the exception address would be where that driver is being loaded into memory.

Here is a better description of the parameters referenced in the 1E (in parentheses after the stop code):

1st - the exception code that was not handled
2nd - the address at which the exception occurred
3rd - Parameter 0 of the exception
4th - Parameter 1 of the exception

You might also want to verify that the machine in question is on the Hardware Compatibility List and also running the latest service pack (6a).

Please post another message and let us know how it goes.

Best regards,
Jamie Hughes

[Kamel CHAABENI]

Possible Cause and Workaround
-----------------------------

The STOP 1E message may occur after the first reboot during Windows NT Setup, or
after Setup is finished. Three possible causes of the problem are:

1. Lack of disk space for installation.

2. Third-party video drivers (and the Microsoft Windows NT Win32k.sys driver).

3. System BIOS incompatibilities.

To resolve this issue, use the appropriate method below:

1. Reinstall on another hard disk when disk space is low.

2. Remove the third-party video driver.

3. Upgrade the system BIOS.

This problem should not occur very often. If it occurs repeatedly, make sure a
debugger is connected and the computer is booted with the /debug switch. Refer
to the following Microsoft Knowledge Base article for more information:

Good luck

[Kamel CHAABENI]

Possible Cause and Workaround
-----------------------------

The STOP 1E message may occur after the first reboot during Windows NT Setup, or
after Setup is finished. Three possible causes of the problem are:

1. Lack of disk space for installation.

2. Third-party video drivers (and the Microsoft Windows NT Win32k.sys driver).

3. System BIOS incompatibilities.

To resolve this issue, use the appropriate method below:

1. Reinstall on another hard disk when disk space is low.

2. Remove the third-party video driver.

3. Upgrade the system BIOS.

This problem should not occur very often. If it occurs repeatedly, make sure a
debugger is connected and the computer is booted with the /debug switch. Refer
to the following Microsoft Knowledge Base article for more information:

Good luck

[Dennis Ng]

Hi there,

Apply SP 6a to fix STOP problem. (known problem from SP 3 and 4).

Regards

[Andrew Ogden]

Dear All

Although this is 2 years on from the original message, I have just received the very same "blue screen of death".

I will try the suggestions provided and give you feedback on my progress.

What an excellent resource! Thanks!

Andrew

[James D. Booe]

Hi
I would imediately replace the sp 5 with 6a on the workstation, and highly recomend going to sp 6a on the server(s) too. Without the complete stop code mesage I can't tell if it is an access violation or a driver, but it should be easy enough to solve just with serv. pack.