firmware error in event log when back from sleep

ionioni wrote: my config: Asrock H110M-HDV R3.0 / I5 7400 / 8GB whenever back from sleep this error gets in the system event log Level | Date and Time | Source | Event ID | Task Category Error | 5/31/2212 ... | HAL | 12 | None The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system. from what i read around is about the bios improperly modifying the low 1 MB of physical memory and when Windows detects this it complains with this error and the suggestion MS makes is to contact the maker of the motherboard/bios in order to fix his firmware. it seems this error is harmless, because that 1MB of memory is not used by Windows ever since Vista (XP had issues with this), specifically the firsttmegabytepolicy boot entry has the default USE_NONE on Windows  the question is, will Asrock release a fixed bios that addresses this issue? even if it is mostly an aesthetically one

What version of Windows are you using that writes that message to the Event Log?

Using Windows 10 on a different system (Z270), I don't get that message in the Event Log.

ionioni wrote: parsec wrote: What version of Windows are you using that writes that message to the Event Log? Using Windows 10 on a different system (Z270), I don't get that message in the Event Log. Windows 10 here too... but that's not very important as long as it's not XP (starting with Vista MS didn't used anymore that crazy low 1MB that firmware makers seems to have fun poking with while sleeping). Your MoBo is a different one and naturally the firmware is also another (no issues on yours), this thing happens only on some models of MoBos (and not only Asrock of course), don't know to say if 1 model in 2 or 1 in 100 is affected by this, anyhow this error is nothing else but a minor thing, was just wondering is maybe Asrock could fix this so i can have my lovely event log clean of any red stuff :) This thing being logged as an error is just MS trying to freak people in order to put pressure on firmware makers to comply with the rules, while on standard comps 1MB is not really important so the default policy MS has to simply not use that MB is ok, on embedded WinCE could be that even that counts. For me is like i said, just an aesthetic issue (funny thing is that even if that error wouldn't show, having a compliant firmware, it still wouldn't count since that MB isn't used anyway). Bottom line neither me nor you are using that 1MB regardless of having or not errors after sleep. *if any AR engineer reading this, the memory is modified by the firmware while on sleep on page 87 and only that one.

Sorry, just curious if you were using something like XP or Vista. Many times in problem threads when information is not supplied, the person is not proud of something related to the issue, and may be related to it.

I'm glad you understand the underlying motivation of MSoft in this instance. The Windows Event Log has almost become a joke with some of its content, whose worth is only useful in unusual situations. Also, what event qualifies as an error can be very arbitrary.

I cannot tell you if and when this error log entry can be removed by a UEFI/BIOS update. Things are rather busy in the mother board universe lately, with many new platforms being released very close together.

If you haven't created an official support request about this, go to the ASRock mother board information page in your region of the world, click the Support link at the top of the page, and click on the Contact Technical Support link to create it.