Exploit targeting kernel power issues on all ASUS AMD Ryzen boards
Exploit targeting kernel power issues on all ASUS AMD Ryzen boards
Right? I mean, application memory is supposed to be separate from kernel memory in Windows... and Windows is supposed to have some sort of data execution prevention. I'm no expert either, but maybe it's a driver issue? I didn't have any ASUS programs installed when I tried reinstalling Windows, and it still happened... so who knows. Could also be a hardware level defect with the PCB that causes a short of sorts. /shrug
It might also be related to DEP now that you bring it up. It could simply cause the PC to restart without warning, something I experienced during the XP era...? Whatever you mentioned could be contributing to the issue. Installing ASUS bloatware likely wouldn't have improved things, except perhaps by updating chipset drivers from ASUS and upgrading from AMD. I doubt this would help unless the problem stems from the power plan settings, though that seems unlikely.
I tested multiple power plans and different chipset driver versions (ASUS and AMD x470 drivers). I'll direct those here to see if disabling DEP in Cura works.
So, fun update on this story. They decided to retract their previous resolution of sending me an Intel replacement after months of trying to diagnose the issue with them. They told me twice now that they won't send me the replacement even though we agreed on it previously (even after I explained the situation again). So today I told them how I really feel after being on hold with them for months. ASUS support can seriously suck it. I really hope this doesn't become an exploit for the sake of the market share of AMD Ryzen users, but I really hope this becomes an exploit for ASUS's sake.
You might have misinterpreted the details. It seems you're questioning whether the issue stems from a misunderstanding of the software interaction with the Windblows OS, and you suspect Asus is involved. However, the explanation points to other manufacturers like Corsair, SK Hynix, and various motherboard brands such as AsRock, MSI, Gigabyte. The problem appears to be related to memory compatibility and BIOS settings rather than a specific brand fault.
It's actually quite normal for many programs to function this way... things like afterburner, nzxt cam, windows metro app, and even the Windows Metro app itself can cause issues. Most of these problems stem from Windows or the motherboard's BIOS. After a long time, my PC would crash repeatedly, and nothing seemed to resolve it. The final fix came when I turned off all Windows updates completely. It turned out the real issue was the "Windows update orchestrator."
As for who to blame, it's complicated. MSI might have released a faulty board or BIOS that can't handle videos, and Microsoft likely had problems with Ryzen power management and the update service running constantly. AMD probably didn't fix their update handling either. I personally don’t use the Metro app and prefer the media player instead.
Updating past 1809 is impossible for me, and I keep getting BSODs. It’s hard to pinpoint responsibility—Asus customer support seems unreliable, and I suspect some third-party app issues too. While the hardware and Windows are involved, it’s not just one company’s fault. Still, I agree with @ShrimpBrime—it might be related to RAM or AMD Ryzen, and even Discord caused trouble. The damage took weeks to recover from, so blaming a single brand isn’t fair. It’s not just about Asus anymore.
They confirmed the developers don't use Ryzen systems. This was the second reply from the moderators to the link you shared.