OK, I think I understood better now why irpfind is a bad idea. Now in the list I have Corsair drivers that I didn't have before. So in short, this command simply shows the loaded drivers themselves when a failure occurs, and they may not necessarily be responsible for it. So I have to face the truth and accept that the Gigabyte driver is guilty? It is a bit strange that suddenly it started to cause blue screens now, and before it worked without a problem, but oh well
I tried to start Driver Verifier, but after restarting the computer did not start, but the symptoms were strange. Even very strange. The computer at startup displayed only a black screen, but even the BIOS screen did not show, only black (the monitor received a signal from HDMI because it displayed the appropriate message). The third time the system started automatic repair and in safe mode I could turn off Driver Verifier. When I did that, I could start my computer normally. I have never encountered such a thing in my life