Older HP Envy Video Crashes: Match the Model Before the Driver
Updated
Which driver fits this older HP Envy? Check the full model name and the Windows release first.
The old guide covered an Envy x360 with a Ryzen 5 2500U and Vega 8 graphics. That doesn't prove the same driver fits your laptop today.
Write Down What You Have
I'd note the full HP product number, Windows release and graphics-driver version. A similar name on another laptop doesn't mean the parts or support are the same.
Then describe the fault. Does video fail in one browser, or does the whole computer freeze? Note any error message and when the trouble began.
Keep track of what changed just before the fault appeared. Those details are a better start than picking a download because an old article mentions it.
Check the Model's Support
Use HP's support details for that exact model and Windows release. If the combination isn't supported, an old driver found elsewhere doesn't prove it will work.
AMD says its reference drivers have limits for some features specific to a laptop maker. A maker's own package may cover those features. Newer isn't a complete answer on its own.
Read the package requirements before making a change. Keep important files safe and establish how to restore the prior setup. I wouldn't force a driver past a mismatch warning.
The Earlier Catalog Link
The old article pointed to Microsoft's results for 24.20.11016.12001. The catalog still lists 2018 graphics entries with Windows 10 descriptions.
That is a historical reference. No package was installed for this rewrite, and no current laptop was checked. The listing alone doesn't show that it will solve your fault.
The old CAB and forced Device Manager steps are no longer offered as instructions here. First establish that a package belongs on the machine.
Keep Different Changes Separate
The earlier Chrome ANGLE suggestion was an old workaround. There is no current reproduction here, so it isn't a general browser fix to follow today.
A BIOS update is a separate choice. Use the exact model's directions if that step is needed. Don't add it to a driver change simply because it appears in an old guide.
I'd change one thing for a clear reason, note the result and keep a way back. If the fault stays, those notes give the next person something useful to work with.