No I get what you are saying, the thing is that the cosmic ray bit flip fits the razor. https://en.m.wikipedia.org/wiki/Cosmic_ray

Studies by IBM in the 1990s suggest that computers typically experience about one cosmic-ray-induced error per 256 megabytes of RAM per month.

It isn't unlikely for it to have happened on non-ECC hardware. I think they even replicated what happened in the video in an emulator with a single bit flip, so it really just boils down to "what are the chances someone recorded while a bit flip did something noteworthy", and the odds are.... pretty big actually, over so mamy years.

To be honest I kinda suspect you've done no effort to fact check this but are just going with your gut feeling? I don't mind discussing this further, but if so I'd really like to hear what your point is, because if it is that: a) cosmic bit flips doesn't happen or b) a bit flip couldn't have impacted the game like that then I think you're better off watching that video I linked or actually read up on the subject because my impression is that if you apply occam's razor to that mario64 incident... a bit flip is all that's on the table.

for the cost of doing that, it'd probably be better to invest the time and resources in a new satellite all together. it's kinda the same dilemma as the Wait Calculation

Veratisium did a good video about it. https://youtu.be/AaZ_RSt0KP8?si=mR7B5V4qIlhTF0Gc

if you think it's unbelievable, then the video is probably worth a watch

Hi, hope you've found a solution by now. Came across this thread randomly, thought I'd share.

  services.udev.extraRules = ''
    SUBSYSTEM=="drm", KERNEL=="card0", DRIVERS=="amdgpu", ATTR{device/power_dpm_force_performance_level}="high"          
  '';

I'm using an RX6700XT iirc, been having issues with it since day one. Somewhat random DE crashes. For the longest time I ran with only this, and not the above:

      kernelParams = [     # https://gitlab.freedesktop.org/drm/amd/-/issues/1974
      "nvme_load=YES"
      "amdgpu.ppfeaturemask=0xfffd3fff"
      "amdgpu.noretry=0"
      "amdgpu.lockup_timeout=1000"
      "amdgpu.gpu_recovery=1"
      "amdgpu.audio=0"
    ];

disclaimer: I've no idea what this does but it works for me

I'm not sure if the high-power udev rule improved anything, but for me electricity is cheap and my will to troubleshoot ran out.

right now I'm having issues with my monitors blinking at times. My 2nd monitor especially, sometimes 10 'disconnects' in less than a minute, but often hours without a single one.

I've kinda settled on just accepting not knowing exactly what's wrong, cause I'm not sure if it's a bad GPU, bad config, wayland or hyprland screwing me over, and I'm kinda more overwhelmed by learning it than the problem itself.

hope this is of value for someone!