HP Envy x360 Ryzen F19 BIOS disaster DO NOT UPDATE

[proxyx]

Not to take away from a "driver fix", but... if this was a true solution HP wouldn't have taken down the F.19 BIOS. There's got to be something more to it then just upgrading a display driver. I've had too many issues with stability to believe in just a display driver upgrade. If it works, good... question is only when and how you'll hit a roadblock. For now, it's better then nothing, a solution to keep using the laptop. A real issue is still a bad BIOS. Not everyone is comfortable or verse in manipulating drivers.

[xxalazin]

so this is another HP screwup. On top of no support from AMD except for a vague promise for drivers in 2019. Hp still can't get it's BIOs together. I installed the F19 and so far no isuuess at all I'm not going back. It will probably take HP months if at all to fix a new bio's and still  no new HP graphic driver package.. this Is the last time I ever buy an HP or AMD based computer.....

[xxalazin]

Was there any mention at all the reason for it pulled? I installed am running f19 withthe latest adranline dec 13 with no problems ....

[proxyx]

Seems you came here and didn't even check the title of this thread,  it is not about display driver...

[ron_valen]

---

@proxyx wrote:

Seems you came here and didn't even check the title of this thread,  it is not about display driver...

---

Both Frimeware and driver updates goes together. Offical config for my bq 100 cto, 22.19.655.1 and F.19 (before being widthdrawn) is unstable.  22.19.655.1 driver with F.17 has serveral BSOD events like Windows Vista  and Nvidia drivers. 

I use force update method forAdrenalin 2019 Edition 18.12.2 Driver  (Windows Driver Store Version 25.20.15002.58) driver and group policy to block device id WIndows update.. 

The ideal fix would be Adrenalin 2019 Edition 18.12.2 Driver and F.19's 1GB VRAM without force driver update method..  

Another method to push HP/AMD is  to flood Microsoft's BSOD reporting service with thier official 22.19.655.1.

[ron_valen]

---

@Jo-Kery wrote:

---

@ron_valen wrote:

---

@Jo-Kery wrote:

Please note that the group policy method is only available in the Pro and Enterprise editions of windows.

---

Gpedit.Msc can be installed on Windows 10 Home. 

---

Oh really?  I did not know that.  What steps should I follow to install Gpedit.Msc on W10 Home?

---

Read https://www.itechtics.com/easily-enable-group-policy-editor-gpedit-msc-in-windows-10-home-edition/

[Andrea55]

F.19 increase the Vram to 1Gb?

With F. 17 and stock gpu drivers had no Bsd but i dont use chrome so im not completely sure

[xxalazin]

I installed them had to force install and also manually install vulcan after I used DDU. I however had jumped the gun and am stuck with F19. When I had  installed the dec 13th adrenline and force installed those drivers I would git error 43.  This november driver seem to be working really well and I have the HP x360 R5 2500u. Performance seem to be the same... Hopefully HP won't drag its butt and we'll get to keep that  1024 Vram with a better bios.I had posted earlier that the new adrenoline driver worked great but within a day or two  i started getting error error 43. I now believe it is the Bios not liking a newer driver.  I hope that at least this driver will last until the new bios ........

[ron_valen]

---

@Andrea55 wrote:

F.19 increase the Vram to 1Gb?

With F. 17 and stock gpu drivers had no Bsd but i dont use chrome so im not completely sure

---

For my bq100 cto model, F.19 update increased reserved Vram to 1GB.

I have multiple BSOD with F.17 and 22.19.655.1 Rev.B, hence I force updated to 23.20.821.2560 Rev.D  from  15-cp0000 model.

I use Chrome.

I force update to Adrenalin 18.5.1  (Windows Driver Store Version 24.20.11016.4), Tested Doom 2016's Vulkan API

I force update to Adrenalin 2019 Edition 18.12.2  (Windows Driver Store Version 25.20.15002.58), Tested Doom 2016's Vulkan API

[ron_valen]

---

@xxalazin wrote:

I installed them had to force install and also manually install vulcan after I used DDU. I however had jumped the gun and am stuck with F19. When I had  installed the dec 13th adrenline and force installed those drivers I would git error 43.  This november driver seem to be working really well and I have the HP x360 R5 2500u. Performance seem to be the same... Hopefully HP won't drag its butt and we'll get to keep that  1024 Vram with a better bios.I had posted earlier that the new adrenoline driver worked great but within a day or two  i started getting error error 43. I now believe it is the Bios not liking a newer driver.  I hope that at least this driver will last until the new bios ........

---

Check your actual driver version from device manager. 

Adrenalin 2019 Edition 18.12.2 should have Windows Driver Store Version 25.20.15002.58 markings.