Bluescreen B801FE66 and other printing errors with HP OfficeJet Pro 9010 series on Windows 11 on ARM

[plaufer1980]

I got my wife a Dell Inspiron 14 (5441) with Windows 11 on ARM and a Snapdragon X Plus X1P-42-100 CPU. Since the laptop is in use she's struggling with printing issues that don't exist in the same wifi network with the same OfficeJet Pro 9010 series when using her old laptop with Windows 11 on an Intel x86 CPU. 

First the OfficeJet printer driver would install automatically, but printing was dead slow. The printer was pausing multiple times for a single page at the same quality settings used on the Windows x86 PC. I tried to install the full driver package downloaded from the HP website, but the installation process always fails with an error. I then removed the printer from the Windows device manager and reinstalled it again. This time some generic Windows printer driver for ARM got used and it seemed to work fine. Printing was fast with no apparent issues ... for a few days. Now occasionally the printer goes into bluescreen showing error B801FE66 and can only be made operational by removing the power plug and reseting the printer. At times it doesn't print correctly leading to page content being cut off. None of this happens when the old laptop with the Intel x86 CPU is used for printing the exact same documents.

Unfortunately, my wife is a teacher and relies on printing A LOT. As it stands I might have to return the Snapdragon powered laptop as I'm out of ideas how to fix this. I followed all reset, reinstall, default settings, HP doctor, whatnot tools and recommendations and nothing seems to help.

Is a new ARM driver coming directly from HP any time soon or is there any trick available that hasn't been posted in the community with the keywords ARM, Snapdragon, etc.?

Any help highly appreciated!

[Garp_senchau]

@plaufer1980, Welcome to HP Support Community,

Thank you for posting your query; I’m here to help by guiding you through steps to resolve this issue

It sounds like the issues you're facing with the Dell Inspiron 14 on ARM and the HP OfficeJet Pro are related to driver compatibility. 

I suggest you reinstall the printer if possible, with the HP Smart app, as it will download the compatible drivers for the unit you have.

You can install the universal drivers for printing and scanning for the unit depending on the OS version. HP OfficeJet Pro 9014e All-in-One Printer Software and Driver Downloads | HP® Support

Also, update the firmware, as this would solve most of the problems. Update the firmware on an HP printer | HP® Support

Let me know how it goes.

Please feel free to reply here if you have any questions or if you need further clarification on any of the steps. 

Take care and have a good day. 

If my response helped, please mark it as an Accepted Solution! ✅ It helps others and spreads support. 💙 Also, tapping "Yes" on "Was this reply helpful?" makes a big difference! Thanks! 😊

Regards,

[plaufer1980]

Hi Garp_senchau,

I tried reinstalling the printer via universal drivers (always fails with a generic error message at some point) and via the HP Smart app as I mentioned in my post. Both ways didn't work properly and only the uninstall via device manager afterwards got Windows to reinstall the printer with some generic Windows ARM drivers that were working for some time only. The last couple of days the printer didn't bluescreen at least, but I didn't do any deliberate fixing and I expect it to bluescreen any time soon again. As both Windows and the printer are installing updates and firmware updates automatically, I cannot really say if anything changed there in the last week. My printer is on firmware version MANHTNPP1N005.2450B.00 atm.

My question was rather if HP is aware of the issues with their printer driver on ARM and if they are currently putting effort into improving this or if ARM is still considered an edge case and no real developer effort is spent on fixing issues there?

[Garp_senchau]

@plaufer1980, thank you for your response

Yes, I have informed the concerned team about this issue, and they are actively working on improving compatibility. Till then, I suggest you use the generic drivers.

I hope this helps

Regards,