HP Envy x360 Ryzen F19 BIOS disaster DO NOT UPDATE

[ron_valen]

---

@kurtd wrote:

---

@xxalazin wrote:

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

---

Same here, no issues since manually updating the display driver from AMD.  It could be that they want to wait until they release new display drivers for the varioius modles and give users time to update before they release f19 again.  Still no new video driver listed for HP ENVY x360 - 15-bq101na https://support.hp.com/gb-en/drivers/selfservice/hp-envy-15-bq100-x360-convertible-pc/16851053/model...

---

I haven't encoounted show stopper issues with "my bq100 cto" model which includes F.19 and  manual install Adrenalin 2019 edition 18.12.2 

Still no new video driver listed for HP ENVY x360 - 15z-bq100 CTO

https://support.hp.com/us-en/drivers/selfservice/hp-envy-15-bq100-x360-convertible-pc/16851053/model...

[gsoul5005]

Seems like the new BIOS isnt compatable with the old GPU drivers HP has on their support website.

Easy Fix is that you Force install new Radeon Drivers..

The F.19 version fixes a lot of issues(improves performance too), its just that they should have updated the drivers first.. then the BIOS.

I am using the F19 drivers with force installed adrenalin 2019 Drivers.. The laptop hasnt been more stable than this before!
I can even use the hardware acceleration in chrome without issues where it used to crash so often that i had to disable it before.

[Andrea55]

Revision and microcode are the same, only difference are the instruction underlied

[xxalazin]

Yeah I did all that too. It seemed the the new Adrenoline drivers were good then I started getting error 43 and they no longer would work. I  used DDU forced install everything you guys did now I using an Oct version.  AMD just came out with another set of drivers, but whats the point? I'm NOt spending endless time troubleshooting AMD's  total lack of support , That crap about OEM support is nothing but a lazy companies excuse....

[proxyx]

Some problems may be ralated to graphics software under F.19 BIOS but some may also be a result of BIOS/CMOS corruption.

The upgrade may not have gone as planned... ending with a corrupted CMOS.

Just wondering if anyone can check status of F.19 BIOS. It is done by pressing Win key + V while starting the laptop.

Press power for 2-3 sec while holding Win+V. Release power, keep holding Win + V few more secs and then release Win + V keys. The CMOS check status will be displayed. Any errors?

If no msg, try again. 

Power key (2-3 secs) + Win + C, wait few secs and relese >>> resets the CMOS.

Anyone? 

see here: https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/CMOS-Checksum-Error-on-Startup/...

[Andrea55]

Updated video driver, no crash for now.

CMOS cechk says: "CMOS cechksum is invalid. The CMOS will be reset to the default configuration..."

CMOS Reset (502)

[ron_valen]

---

@proxyx wrote:

Some problems may be ralated to graphics software under F.19 BIOS but some may also be a result of BIOS/CMOS corruption.

The upgrade may not have gone as planned... ending with a corrupted CMOS.

Just wondering if anyone can check status of F.19 BIOS. It is done by pressing Win key + V while starting the laptop.

Press power for 2-3 sec while holding Win+V. Release power, keep holding Win + V few more secs and then release Win + V keys. The CMOS check status will be displayed. Any errors?

If no msg, try again. 

Power key (2-3 secs) + Win + C, wait few secs and relese >>> resets the CMOS.

Anyone? 

see here: https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/CMOS-Checksum-Error-on-Startup/...

---

My bq100cto's Win+V displayed CMOS error and has reset it. 

CMOS cechk says: "CMOS cechksum is invalid. The CMOS will be reset to the default configuration..."

CMOS Reset (502)

It disables AMD VT features which needs to be re-enabled for my VMware work. 

[ron_valen]

---

@Andrea55 wrote:

Revision and microcode are the same, only difference are the instruction underlied

---

I enabled AMD VT features from the BIOS. 

[proxyx]

@Andrea55 wrote:

Updated video driver, no crash for now.

CMOS cechk says: "CMOS cechksum is invalid. The CMOS will be reset to the default configuration..."

CMOS Reset (502)

---

Interesting, isn't it? Corrupted CMOS??? Either this procedure (came from HP Support) is flawed or... **bleep**?

What does it mean in reality "CMOS checksum is invalid"? Is this to be taken seriously???!!! or maybe not and why?

As a result of F.19 BIOS we are forced! to cook our own drivers for crashing systems while HP is sitting/watching on the sidelines. 

F.19 is pulled with no explanation, no fix.

Summarizing: cooked drivers may work but are unsupported, current BIOS is unsupported. Zero help/reaction from HP... what we do here is a DIY project to fix mess HP created but doesn't admit, support or even condone.

So tell me: what do we have?

1. messed up laptops patched temporarily with unsupported AMD drivers or

2. functioning laptops with a crooked Windows we have to fix

Whatever scenario you pick it doesn't add up. Either way, it looks more like a Frakenstein then a valid solution.

If the system doesn't work properly with a supplied stock, default Windows 10, it is not a working system.

Did I sign up and pay for that? 

I admire the enthusiasm and loooong hrs ppl put in finding a satisfactory solution but...

as @xxalazin wrote:

Yeah I did all that too. It seemed the the new Adrenoline drivers were good then I started getting error 43 and they no longer would work. I  used DDU forced install everything you guys did now I using an Oct version.  AMD just came out with another set of drivers, but whats the point? I'm NOt spending endless time troubleshooting AMD's  total lack of support , That crap about OEM support is nothing but a lazy companies excuse....

My laptop, after F.19 update, doesn't work with with a stock Windows anymore, whatever version you pick.

Am I missing something or this is a support nightmare I never anticipated.

To download drivers I need to start a browser, the moment I do it, hang, crash, hang... etc. HP site unreachable, blank...
If I factory restore... (unable to finish, LOL, thanx HP!), assuming it will finish some day, it's back to crash again.

How about HP releases a new working Windows version for F.19 plague victims or fixes the **bleep** F.19 BIOS.

I'm not getting something...

Btw. looks like BIOS is a **bleep** shhhhh.... here, a voodoo no one dares to even talk about... **bleep**?

[DwaDuzeDe]

Simple bios downgrade option would be helpful here.