-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Software and How To Questions
- HP Envy x360 Ryzen F19 BIOS disaster DO NOT UPDATE

Create an account on the HP Community to personalize your profile and ask a question
12-23-2018 06:51 AM - edited 12-23-2018 07:22 AM
Well, it is a sad constatation of the facts. Had Ryzen mobile been widely adopted and flying of the shelves we'd have more input from AMD. It's been adopted by a small number of laptop manuf. like HP, Acer, Dell and Lenovo, and in a limited number of products. Number of supporting drivers is a direct consequence of that. Small market = little support. Ryzen offers negligable improvement over Intel 8250 + Nvidia MX, price is not significantly lower to make a dent in Intel's market position and that translates into AMD's poor showing.
Don't forget about the fact that within last year there's been 3-4 driver editions for Ryzen line (all) but none from HP. Ryzen, especially mobile, from a market point of view is a flop, small margin. There's no denying that newer drivers discussed here are from who? AMD... How many have HP adopted to its mobile product line? Zero.
HP creates a product and... drops the ball. It's a fact. All they need to do is place an order with AMD to customise the drivers... Obviously this hasn't been done.They are just riding the wave with minimal, if any, involvement. Again, low sales numbers mean zero input from HP.
Add to that a knife in the back from HP = F.19 BIOS. HP knows it's a mess and has not posted a simplest fix in the world: downgrade option. Windows has restore option... but HP gave us NOTHING so far. THAT should normally take 2-3 days. They pulled the BIOS like cowards and gave NOTHING to repair the problem. They showed all of us a middle finger. What else would you call it?
12-23-2018 12:15 PM
I call it a pair of ripoff companies both AMD and HP. Sick and tired of having to deal with lack of support. Just had a crash copying files. **bleep** caused that? Going to strip this machine down to original hardware. Will try to sell on Ebay for a couple of bucks thats all it worth... It is NOT the responsiblety of the USER to deal with this garbage. Gone all the way back to original HP drivers, what a sad and pathetic situation.. NEVER again will I deal with HP or AMD products.....Intel and Nvidia from now on never had any issues with their chips or drivers.......
12-23-2018 06:37 PM - edited 12-23-2018 06:42 PM
@xxalazin wrote:I call it a pair of ripoff companies both AMD and HP. Sick and tired of having to deal with lack of support. Just had a crash copying files. **bleep** caused that? Going to strip this machine down to original hardware. Will try to sell on Ebay for a couple of bucks thats all it worth... It is NOT the responsiblety of the USER to deal with this garbage. Gone all the way back to original HP drivers, what a sad and pathetic situation.. NEVER again will I deal with HP or AMD products.....Intel and Nvidia from now on never had any issues with their chips or drivers.......
I have issues with Microsoft supplied OEM drivers for Surface Pro 4 with i5 6300U Skylake which has it's own restore from sleep issues, but it's largely resolved. Intel HD 520 is very similar to HD 620. Atm, Surface Pro 4 and 5 has grounding issues in certain countries that causes track pad to have jerking movement when connected to wall power (not a problem during battery mode and touch/mouse control methods).
Intel supports it's iGPU when the user preforms force driver install which removes OEM block marker which open the paths for any future Intel driver updates from normal install methods. I use Intel's DCH drivers instead of older MS OEM supplied drivers.
Mobile Ryzen situation is mostly AMD's problem not HP.
12-23-2018 06:53 PM - edited 12-23-2018 07:09 PM
@proxyx wrote:And that is more relevant. Fixing atikmpag.sys doesn't help. Disabling TDR or manipulating delay value does nothing as well.
Who cares about your laptop/desktop specs. btw.
The only method to fix atikmpag.sys is a driver update since it's part of the driver stack. I don't have access to atikmpag.sys source code nor access to driver code siging process to modify INF with mobile Ryzen hardware IDs on newer drivers.
BIOS includes ACPI tables which includes device configuration settings.
12-24-2018 02:46 AM
I only found this thread by accident, thinking the hardware was faulty. Now that i know HP has done this they will be copping a spray as soon as the helpline reopens. I have lost hours of work over the last week in my professional practise because of these crashes. I should send HP my invoice. it is insane this was not properly vetted before causing so much greif.
12-24-2018 01:05 PM
I spoke too soon. At first boot the alternating black and snow screen shows. After a hard shut down by holding the power button for 5 seconds, the laptop boots as normal. I wish I could go back to F.17 it was stable.
12-24-2018 04:21 PM - edited 12-24-2018 04:25 PM
@SCTech65 wrote:I spoke too soon. At first boot the alternating black and snow screen shows. After a hard shut down by holding the power button for 5 seconds, the laptop boots as normal. I wish I could go back to F.17 it was stable.
Disable fast boot which is not a problem for SSD equiped laptop.
I use 18.12.2 with fast boot disabled.
12-24-2018 07:07 PM
I have this hp x36015M-BQ121DX,w R2500u 16gb 2400, NVme960 250gb and Micron 2TB Oem SSD. I only get random blue screen TDR error or screen lockup. I am going to give AMD and HP a month or two. Then I will reinstall the 8GB and the original 1tb mechanical drive. and pull the nvme 960 out. Put the thing on Ebay for whatever I can get? Buy a reliable Intel Nvidia combo using the 16gb and 960. If I can't get it reliable or sell it Mount the thing on the wall with the caption NEVER AGAIN AMD or HP..........