Windows 10: HP Webcam access fails with bluescreen SPUVCbv x64sys

May be of interest to others - Just noting an issue I encountered with 2 similarly spec'd machines with upgrade to Win 10 2004

On upgrading my HP EliteBook 8470P Win 10 Pro x64 Ver 1909 b18363.900 to W10 Ver 2004[]
Download / Upgrade option available and initiated manually from windows update.
Upgrade took around 1.5hours all up with no issues encountered during the upgrade process.

Issue: Post upgrade testing highlighted a problem when accessing the inbuilt webcam device ie through the Camera App and also Skype.

Error: Fails with bluescreen SPUVCbv x64sys and system recovers/restarts.

Background:
Checked and I have latest HP F.74 Rev A BIOS installed.
Also have latest HP Webcam drivers installed (sp71853.exe).
Downloaded and re-installed latest Webcam drivers (Universal Camera Driver from HP Website) Issue persists
Rolled back the driver for the Webcam device (reloads generic MS Driver dated 2006!) Issue Resolved.

All good but I wonder what functionality may be lost by going back to a driver that old.?

I have sent details to Microsoft (via Feedback) and will also be logging issue with HP Support.

Would be interested if others have encountered this issue also and any thoughts on best course of action.

Still testing but no other issues for me identified so far with the upgrade to Ver 2004.

Thanks!

:)

 

HP Webcam access fails with bluescreen SPUVCbv x64sys

May be of interest to others - Just noting an issue I encountered with 2 similarly spec'd machines with upgrade to Win 10 2004

On upgrading my HP EliteBook 8470P Win 10 Pro x64 Ver 1909 b18363.900 to W10 Ver 2004[…]
Download / Upgrade option available and initiated manually from windows update.
Upgrade took around 1.5hours all up with no issues encountered during the upgrade process.

Issue: Post upgrade testing highlighted a problem when accessing the inbuilt webcam device – ie through the Camera App and also Skype.

Error: Fails with bluescreen SPUVCbv x64sys and system recovers/restarts.

Background:
Checked and I have latest HP F.74 Rev A BIOS installed.
Also have latest HP Webcam drivers installed (sp71853.exe).
Downloaded and re-installed latest Webcam drivers (Universal Camera Driver from HP Website) – Issue persists
Rolled back the driver for the Webcam device (reloads generic MS Driver dated 2006!) – Issue Resolved.

All good but I wonder what functionality may be lost by going back to a driver that old.?

I have sent details to Microsoft (via Feedback) and will also be logging issue with HP Support.

Would be interested if others have encountered this issue also and any thoughts on best course of action.

Still testing but no other issues for me identified so far with the upgrade to Ver 2004.

Thanks!

 

HP Webcam access fails with bluescreen SPUVCbv x64sys

Thanks for responding zbook - some good info and specifics there.

To me then, that would confirm it is an incompatible HP driver issue as I downloaded and installed the latest driver from HP website and the BSOD persisted. As mentioned, I have had this happen on 2 machines which helps confirm it's not just my setup. I will open a case with HP and work through it with them.

In the meantime, hopefully the Microsoft generic 2006 driver will serve as a stable workaround (for using Skype especially).

 

HP Webcam access fails with bluescreen SPUVCbv x64sys

All Microsoft drivers are deliberately dated 2006 for driver ranking.

When default drivers are offered by Microsoft they compete with component manufacturer drivers first by year.

This way if available all component manufacturer drivers should be newer than Microsoft drivers and have preference.

In case Microsoft and component manufacturer drivers match by year the next ranking is by version.

New operating systems can become corrupt.

Drivers are files and can become corrupt.

To test for corruption versus incompatibility you can reinstall the driver directly from the HP website.

If there is another BSOD then you have established cause and effect incompatibility.

If there is no new BSOD then you had likely a corrupted driver.