Anika A.

for me it was the BIOS. swapped it and boom, fixed

lol same thing happened to me try turning off the cable first, fixed it for me. same issue here on my moms pc. following this thread good luck man!

ahh classic on teh GameCube remake, The Twin Snakes, Mantis comments on Nintendo save files instead.

ok so code 43 means teh driver loaded but teh device reported a failure, sooo it can be either... the fact that it works on another PC points toward drivers, power, or teh port on this machine.

pin teh Node version, add an .nvmrc or teh engines field in package.json, and make CI use the same major version. Compare node v and npm v locally and in CI; many nothing changed failures are actually a new Node version on the runner.…

ok so commit your lockfile and use npm ci in CI. It installs exactly what the lockfile says and fails if package.json and the lockfile disagree, which surfaecs drift early instead of resolving different versions on different machines.

hmmmm quick q what does media info say about the frame rate mode: constant or variable?

help!! reading this at 2am instead of sleeping, no regerts. +1 same here

hmmm after a driver update, games often rebuild their shader cache, which causes stutter for the first sessions. give it a couple of runs, or clear the driver shader cache manually in the control panel / %LocalAppData% cache folder and…

yeahhh try turning off the cable first, fixed it for me