A GPU bench might raise temps in a way that would cause the problem to recur, but I’m not sure you’d see anything without doing something to get data flowing to the drive at the same time, so maybe try running the GPU bench and at the same time run sudo dd if=/dev/{your drive} of=/dev/null bs=1M status=progress (just pull data from the drive and write it to nowhere, but be careful about the of and if or you might overwrite your whole drive), and while those are going, run sudo dmesg -w in another terminal and watch for the same error you were getting before. If you don’t get errors, the problem was probably just some power state problem that the kernel parameter fixed. But I have to tell you, unfortunately, that the presence of the error under windows is a bad sign that points to a hardware problem, so I don’t feel very hopeful. Independent of all the other suggestions, could you try running sudo nvme smart-log /dev/{your drive}? That might give you some data.