There’s a rash of WDF_VIOLATION blue screens on Win10 HP computers with an as-yet unknown cause

It’s been a wild Thursday morning in patch land, with quite a lot of BSODs to move round, cumulative updates, keyboard drivers, and a solid of suspects worthy of an Agatha Christie novel.

Get started with a complete document at the Microsoft Solutions discussion board, the place poster Mikael Sillman says:

After putting in KB4464330 (construct 17763.55) [on] my HP EliteDesk 800 G3 the system refuses in addition, finishing with BSOD WPF_VIOLATION. I used to be in a position to get the PC running once more the use of an previous repair level. It sort of feels that this drawback a minimum of HP machines:

I contacted MS toughen and was once advised that:

MS Agent: If truth be told HP computer systems aren’t the one product affected for this factor different computer systems as smartly like DELL and so forth. That is why for now, we’ve quickly paused the replace for individuals who search to test for updates, to analyze an remoted reported factor and can make it to be had for obtain once more as soon as able.

Me: Adequate, so that is recognized factor for 17763.55 cumulative replace?

Agent: That is proper and different factor has been reported as smartly however our upper stage of toughen already running on it

To spherical out the outline, the connection with Bleepingcomputer issues to a collection of feedback that get started with confuishus:

KB4462919 BSOD’s all HP workstations we examined on up to now. Cant do gadget repair, restoration level, and so forth. Must re-image. Dont kick this out till it will get revised otherwise you totally check. All BSOD presentations Forestall Code: WDF VIOLATION.

Adopted by means of this remark from goddo:

Drawback fastened for us, we needed to delete the HP driving force “HpqKbFiltr.sys” in an effort to steer clear of the WDF VIOLATION on each and every boot. The entire machines that had been affected at the moment are operating advantageous for us after taking away that driving force.

After which this, later, from goddo:

It isn’t the KB4462919 replace this is inflicting this crash in any respect, it’s the failed set up of the “HP Building Corporate, L.P. – Keyboard -7/11/2018 12:00:00 AM –” in Home windows replace. Ahead of this replace the HpqKbFiltr.sys driving force does no longer exist. So in our state of affairs it’s protected to put in KB4462919 on those machines. This will not be the case for all however I assumed I must mean you can guys know.

On AskWoody, an nameless poster says:

Leave a Reply

Your email address will not be published. Required fields are marked *