David E. Ross wrote:
On 2/9/2015 4:46 PM, David E. Ross wrote:
On 2/6/2015 7:32 PM, David E. Ross wrote:
Windows 7 Ultimate SP 1 (x64)
Hewlett Packard LaserJet Pro 200 Color (M251nw)

I have been using Windows 7 for well over a year now. Until yesterday,
I never had a crash (the blue screen of death). Yesterday, I installed
a HP LaserJet Pro 200 printer. Since then, I am getting frequent crashes.

I scanned my PC with AVG Free 2015, Malwarebytes Free, and Microsoft
Security Essentials (not all at once but sequentially). None of them
found anything.

Has anyone else seen such a problem? If so, were you able to fix it?


The crashes occur with the first print opertation after I powerup the
printer. Then, I might have several print operations before the next
crash. I got three such crashes today. Before installing this printer,
I never had Windows 7 crash.

Looking at the crash dumps via Nirsoft's BlueScreenView, none of them
contain any reference to HP software. Each dump cites a different
driver: pacer.sys, tcpip.sys, and ntoskrnl.exe. All are Microsoft
products.

Shortly after posting the above, I did a search of the HP Web site for
"crash Windows LaserJet". From that, I found
http://h30434.www3.hp.com/t5/Printing-Issues-Troubleshooting/Laserjet-Pro-200-color-MFP-M276nw-Crashes-PC-with-BSOD/m-p/2635007/highlight/true#M46221,
which suggested that the problem is that the printer is plugged into a
USB 3 port and might do better with a USB 2 port.

My USB ports are not labeled. I moved the printer's USB plug from the
second row to the first, I have now printed three times without a crash.
I then looked up "universal serial buss" on Wikipedia. It said that
USB 3 ports are blue. Yes, the port I had been using was blue; the one
I am now using is black.

Other than my tax returns, I don't print much. Thus, I am not entirely
sure the crash problem is gone. However, I would have seen at least one
crash since changing the ports; but I have not had any.

By the way, this indicates that backwards compatibility of USB 3 is not
always true. If USB 2 ports are not available in future systems, there
will be some serious problems.


A USB3 port has nine pins in it.

Four pins connect to a USB2 logic block.
Five pins connect to a USB3 logic block.

Using a USB2 cable, has only the USB2 pins connected.
It cannot use USB3 protocol. The five USB3 contacts
don't even touch.

There still has to be a driver for that USB2 block,
and I don't know if it's the bog-standard (Windows
built-in) driver or not.

I would be checking the branding on the USB3
controller chip, and see if it is Etron or not.
They had some driver problems after chip release.
If it is a separate controller chip and not on the
Southbridge, a driver update may fix the problem
for you.

This is the only set of entries I see for Etron.
In Device Manager, check the Properties list
for that USB3 entry, and try to find a HardwareID
for comparison.

1b6f Etron Technology, Inc.
7023 EJ168 USB 3.0 Host Controller
7052 EJ188/EJ198 USB 3.0 Host Controller

HTH,
Paul