ASRock, a global leader in motherboards, graphics cards, mini PCs, power supplies, and gaming monitors, has observed reports on Reddit from users experiencing unexpected boot issues and error codes when using ASRock AM5 motherboards paired with minority proportion of AMD Ryzen 9000 series processors. To enhance user experience, ASRock promptly released the latest 3.20 Beta BIOS for its AM5 series motherboards, further improving AMD Ryzen 9000 series processors boot issues.

Users can download and install the BIOS from the official ASRock website or use the BIOS Flashback function on their motherboard for a quick update. ASRock also promises to continue enhancing the compatibility of its products.

Halo 5: Guardians has remained exclusive to Microsoft Xbox gaming systems since launching back in October 2015, during the Xbox One era—an approaching ten-year anniversary has fans wishing for a possible port over to PC platforms. Hopes were elevated late last week due to an intriguing image popping up on Lenovo's Legion Go S product page. A certain promo image depicts screen content featuring a Steam menu session with an entry for Halo 5. This discovery (courtesy of Rebs Gaming) prompted much online chatter about the possible PC port being unveiled at the next Xbox Developer_Direct—scheduled for broadcast on January 23.

343 Industries (now Halo Studios) has ported five titles over to PC—neatly compiled in the form of Halo: Master Chief Collection—but the absence of Guardians has been a lingering sore spot. Over the past weekend, Lenovo senior community manager—Ben Green—dampened expectations. In a curt response to a query (on social media) regarding the alleged leak, he shot down the notion that Lenovo had inadvertently leaked the existence of a Halo 5: Guardians PC port. It is possible that Lenovo's marketing department had mocked-up the image in error. Microsoft's gaming division has committed to spreading its most visible IPs to "rival" platforms, so the upcoming Xbox Developer_Direct could harbor a surprise or two.

The homebrew and modification community has delved deeper into the recent bout of bricked Nintendo Wii U consoles, unlucky owners are seeing their systems throwing up error codes that indicate an internal memory failure. As covered on TPU almost two weeks ago, it was speculated that leaving a Wii U in a long-term state of unuse was a root cause of the problem. It is now theorized that a simple choice of memory chip is the real issue behind the corruptions, and not a case of leaving your unplugged Wii U stashed in a box somewhere.

An online database has been established on hackmd.io, and a member is collecting hard data from Wii U owners across various online communities and sources. Early indications show that consoles fitted with a Hynix eMMC are leading the pack in terms of number of system failures, Samsung-equipped models are placed in a distant second place, and the Toshiba variant is reported as having zero problems.

It has been reported by multiple users across several online communities that their Wii U consoles are no longer functioning properly. The error codes 160-0103 and 160-2155 are the dreaded indicators of memory corruption. It has been discovered that the NAND Flash within the Wii U's internal eMMC is prone to failure. According to details gleaned from teardowns of the console's hardware, Nintendo has implemented either Toshiba or Samsung flash storage boards for the various revisions of the console. There has been an uptick in the rate of bricked Wii U consoles across recent months, but the problems seem to have occurred as far back as 2015, according to archived posts on the GBA Temp forum. It is speculated that leaving the Wii U inactive for long periods of time can lead to the memory corruption issues.