Asrock AB350 Pro4 4.70 Attempted_Write_to_ReadOnly

You should use BIOS 3.xx (AGESA 1.0.0.6b) with a Ryzen 1700. Make sure you use the Bridge BIOS 3.40 to downgrade.

BIOS 4.xx are for the new Ryzen 2x00 processors and have many bugs (some users even bricked their boards upgrading). See my replies in another thread to see how I got my system to a rock solid state using BIOS 3.20 for my X370 board (ASROCK AB350M Pro4 - Freezing).

A mod added a sticky this morning about the new BIOS issues

Moba wrote: You should use BIOS 3.xx (AGESA 1.0.0.6b) with a Ryzen 1700. Make sure you use the Bridge BIOS 3.40 to downgrade. BIOS 4.xx are for the new Ryzen 2x00 processors and have many bugs (some users even bricked their boards upgrading). See my replies in another thread to see how I got my system to a rock solid state using BIOS 3.20 for my X370 board (ASROCK AB350M Pro4 - Freezing). A mod added a sticky this morning about the new BIOS issues

vmx86.sys ?

Srsly?

If this dmp was created in a VM say so now.




Edited by wardog - 23 Mar 2018 at 7:02am

TachyonParticle wrote: wardog wrote: vmx86.sys ? Srsly? If this dmp was created in a VM say so now. this is the host PC running. Somehow I have VMware installed in this machine.

It needs to be said that some users are not experiencing issues with the new updates and they do bring something to the table when they are stable but they do not appear to be fully tested (the AGESA) on enough system variations.  If you have updated and all is well with your machine, my post should not be taken as a cause to backflash to an older BIOS. That post exists exclusively for us moderators to link to in instances where users have experienced issues as a result of updating to the new Raven Ridge supporting BIOSes  Again, if you have updated and all is stable you have no need for concern.

Sadly, most users who post in forums don't have the technical knowledge to troubleshoot when something goes wrong. That's why they seek help online. The latest anything regarding computers should be considered BETA at best these days (even updates from Microsoft). IMO most users (i.e. non power users) should never update a BIOS or firmware unless they absolutely must. Even idiot proof hardware with dual BIOS features or recovery software tools can be bricked to a non usable state. And only a very small number of users have the knowledge and the tools to reflash/replace a chip at that point (and they are not the ones asking for help online). While warranty claims are usually possible, the cost to return, time lost without a system and overall trouble is disheartening and a very frustrating experience to the average user who invested a lot of money for a new system. The number of bad reviews online for many AM4 boards, regardless of brand (including my own X370 Killer SLI), and the DDR4 used with them is a clear testament to that.

AMD has a 20% market share from what I read online, which means they have a lot less resources than Intel to test the millions and millions of possible combinations of system builds with their products. It's also a new platform and I'm hopeful this will change with the new Ryzen processors this year.

All this doesn't matter to power users and heavy overclockers who regard their systems as disposable if something goes terribly wrong and don't mind spending weeks getting every last decimal of performance out of their rig. For me, I'd rather use my computer than fix it and I am very happy with my system so far (coming from Intel too). It did take a little effort and common sense to get up and running for production work - still a far cry from the Prescott or VIA chipset days. AMD will certainly continue tweaking the platform to make it more plug and play, but users must be patient and careful with the updates they do...








Edited by Moba - 23 Mar 2018 at 11:08pm