Yes, this is a 4 hour long review of a hotel that's already closed.

UPDATE: Ahoyoo has confirmed that Trimming the Herbs was uploaded with TAS tools, meaning that The Last Dance was the final legitimate level all along! Congrats to kazeihinn on the Last First Clear! The journey continues in Super Mario Maker 2...

ORIGINAL POST:

Team 0% is attempting to clear every level in Super Mario Maker before the servers shut down on April 8. (New level uploads have been disabled since 2021, so there is no danger of new levels appearing at the last minute.) As of a few days ago, only a single level remains: Trimming the Herbs, uploaded in 2017 by Ahoyoo. (See also Ahoyoo's original upload video.)

The level is short but extremely precise, requiring Mario to use Bob-ombs to precisely remove Piranha Plants and collect coins while navigating a tight space filled with spikes. There have been over 200,000 attempts so far! If you have a Wii U and feel like you might be a Mario master, this is your opportunity to pick up the final First Clear in Super Mario Maker history.

Archive.org link

The system:

MSI Raider GE67 HX 12UHS

Intel Core i9-12900HX

nVidia GeForce RTX 3080Ti (laptop)

32GiB RAM

Win11 Pro 64-bit

The problem:

Once in a while (usually 2-3 times per day), the system crashes, usually resulting in a blue screen with one of various error codes. Codes I've seen include:

HYPERVISOR_ERROR

CLOCK_WATCHDOG_TIMEOUT

VIDEO_TDR_FAILURE

IRQL_NOT_LESS_OR_EQUAL

Sometimes the system hangs but the blue screen never comes, and I have to power it off manually. When this happens, the fans go to full speed and yet the laptop quickly becomes incredibly hot if I don't power it off as soon as possible, suggesting that the CPU or GPU is maxing out for some reason.

Checking with Event Viewer shows nothing out of the ordinary in the lead up to the crash.

Things I've ruled out:

I initially thought it only happened while plugged in, and bought a new power supply. That didn't seem to affect the frequency of the issue, and I also have now seen it happen while on battery. I also initially thought it was more frequent while playing games that use the dedicated graphics card, but I'm not sure that's actually true; I have seen it happen even while just watching Youtube. At one point I felt that it happened more when I moved the laptop or plugged in USB devices, but I think that may be magical thinking; I have never been able to make it happen on purpose by doing those things. It does seem to be true that after it happens, if I let the laptop restart automatically, it often happens again in a short time, but shutting down and then turning it back on gives more time before the next incident.

Solutions I've tried:

I tried updating the BIOS and the Intel firmware to the latest available on MSI's website, but that doesn't seem to have helped. I also updated my nVidia drivers.

A possibly related issue:

A week or so before this happened for the first time, I updated the BIOS to fix a different issue. What happened then was: I was playing a game on battery unintentionally, and didn't notice until that "low battery - switching to Super Battery" warning appeared and began throttling system performance. I plugged the laptop in, but performance didn't improve. I restarted and performance was terrible across all applications, even Firefox. I checked Resource Manager and noticed that the CPU was being throttled down to around 0.16GHz. Event Viewer was showing warnings about this that said the processor was being limited by system firmware.

I tried using various Windows and MSI power management settings to resolve the issue, which persisted across restarts, fully charging the battery, etc. In the end, I solved it by updating the BIOS (to a version that is now one version back from the most current one).

It was a while, maybe a week, after running the update that the crash happened for the first time.

Current theory:

Is it possible I screwed up the BIOS update somehow? I noticed that it instructs you to return clock speeds to stock before doing the update. I don't think I've manually adjusted them, but MSI's "MSI Center" software seems to offer automatic adjustment. It was set to "Balanced" when I did the most recent update, but it may have been set to "Auto" when I did the first one, which I guess could be a problem if the CPU was automatically overclocked.

I'm crouched in an empty room, stealing everything. My stealth meter randomly changes to Detected so I stop for a while and wait for it to go back to Hidden. I steal the next item and get a notification that a bounty has been added. I'm still Hidden.

I finish looting and stand up. Suddenly: "You're under arrest!" A cop charges into the room and starts giving me a spiel. I unload my fully automatic Grendel into their chest at point blank range. Somehow this attracts less attention than quietly picking up comestibles did; no reinforcements arrive, and I remain free to wander around.

I come back to this room about five minutes later for an unrelated conversation. Everyone politely ignores the dead body.

I know this is all, like, just Bethesda game things, but for some reason this time it seems funnier than usual.

Also, minor companion spoilers:

::: spoiler spoiler I broke into Wyrm's Rock and assaulted Gortash at his coronation, where Wyll's dad, Lord Ravenguard, was present. I won the fight by falling back to the parapets (by the ballista) and forcing all the enemies to walk through Hunger of Hadar and Wall of Fire to get to me; they really hate pathing through Hunger of Hadar, so most of them waited politely in the main room while I killed the rest a couple at a time.

I knocked out Ravenguard and then shoved him to a safe place so that he wouldn't get hit by any AOEs. However, now that we're done, the post-fight cutscenes are over, etc., he's still just KO'd. Wyll doesn't have anything to say about him, and the quest journal entry about rescuing him is still on the step where it says that he's being held at Wyrm's Rock. Well, yes, I know, I found him.

So what do I do with him now? He's infected, it doesn't seem like I should wander off without him. I tried going to camp and there's still no quest update or word from Wyll. I tried healing him in case we need to talk to him, but I learned that KO'd characters don't get up when healed.

Update: If I long rest, the journal updates to say he is dead and his body disappears. It also implies the existence of a next quest step at camp, but Wyll says nothing about it. Also all my companions had the wrong dialog after a certain camp event, as though I had not yet killed Gortash who is very dead. Curiouser and curiouser. I think it's definitely true that they didn't plan for you to try to use the nonlethal toggle this way.

Sometimes I can tell when my current DM fudges a roll to miss an attack or reduce damage. He has a tell in the specific way he pauses and breathes before announcing the roll, then tries to hurry to the next turn, which only seems to happen when someone is in a life-or-death scenario, but "luckily" survives.

Should I let him know he has a tell? Will it be less fun (or more stressful) for him if he knows I know?