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.

In what is likely to cause some hand wringing or chuckles depending on upon your personality, Microsoft's Windows 10 Insider Preview Slow Ring (beta versions of the OS) has not seen a new release in months. This is due to a common Anti-cheat software running amok and causing GSODs (replacement for BSODs in preview builds). The problem itself has existed for a few months and needs to be fixed by the creators of the software as noted by Chief of the Windows Insider program, Dona Sarkar, on twitter. Apparently, this isn't something Microsoft can fix due to how the software itself functions. Essentially the unspecified anti-cheat software runs in kernel mode and tampers with various aspects of the OS that it is not supposed to tamper with. While it is possible, the software is using allowed hooks in order to function. It is also possible that in the process it is damaging kernel data structures and code. This situation is likely to stir up debate on how effective anti-cheat software is considering it seldom seems to stop determined cheaters and as of now is causing the OS crash and is proving to be a thorn in Microsoft's side.

Still, this has more ramifications than just some system crashes or a software company that needs to edit some code. It directly results in Microsoft having to delay Preview releases. Since these Slow Ring builds can't be tested or validated. Pair that with the fact Microsoft's testing of Windows 10 builds is already considered lackluster with many bugs and issues going unresolved and you end up with a rather grim situation. After all, it was only a few short months ago that the October 2018 update was released after suffering numerous problems and delays. If issues like that continue, it seems the April 2019 update could be delayed as well. To avoid this and to get something done, Microsoft will be pushing out a Slow Ring build to systems that do not have the offending anti-cheat software. Better late than never but you would have thought that this solution would have been implemented sooner.

Have you ever taken your car to the mechanic shop to fix one thing but end up breaking another? Well, that's how Intel CPU owners are feeling right now. Intel previously confirmed that their Meltdown and Spectre firmware updates are causing irritating reboots on systems with Broadwell and Haswell processors. After analyzing the latest customer reports, they are acknowledging that the updates are also causing BSODs on the Kaby Lake, Skylake, Ivy Bridge, and Sandy Bridge platforms. This shouldn't come as a shocker considering how both the Meltdown and Spectre exploits affect Intel processors over the past 20 years. The possibility of all platforms suffering from the same side effects is extremely high. Fear not, though, as Intel is already working on an updated microcode to fix the constant system reboots. Motherboard vendors should have the beta microcode for validation by next week. Expect a new BIOS revision for your motherboard soon.

Finally a fix for the BSOD/disconnect bug that has been plaguing users for months is available for SF-2200 based SSDs. OCZ uses these, has been testing this new firmware for several weeks and now believes that it's fit for release. The new firmware is at version 2.15 for OCZ drives and 3.3.2 for drives that SandForce's standard numbering system. As with any firmware update, it should be used cautiously, all data backed up and perhaps used on a non-mission critical Windows install for a while, for confidence. Note that there may be more unresolved issues and new ones introduced.