BelindaSenpai Your new dxdiag shows more crashes of the graphics driver, but the clean uninstall and reinstall should have addressed any driver-related issues. This suggests the problem might be the graphics card itself. It's not definitive, but the next step here would be to test with a different GPU, if you can.
Do you have a friend or family member who'd be willing to let you test with their graphics card? If the game is fine, that's a pretty clear sign that the GPU is the issue. If it's not, then we can keep digging, but the problems that would lead to this are more rare than a defective graphics card, which is why I'm suggesting you test now.
For another Nvidia card, you don't need to do anything aside from physically swapping them; for an AMD GPU, you'd need to DDU the Nvidia driver and install the newest one from AMD. Make sure the card has the appropriate power delivery; you can check its specs online if you're not sure.
If you can't test with a different GPU, at least not now, I'd suggest checking the power cables, on both ends, removing and reseating them. The card should have two 8-pin connectors. If that alone doesn't help, remove the GPU and reinstall it to the other PCIe x16 slot, a little below the one it's currently using. This slot is significantly slower, to the point that it would bottleneck the GPU, but it's usable for testing purposes.
You can see for yourself whether you're getting more crashes of the graphics driver; just check the Reliability Monitor as you go. This particular type of crash is called a LiveKernelEvent 141: the driver failed to respond in what Windows deems an appropriate amount of time (two seconds by default), so Windows kills the driver. A LiveKernelEvent 144 is a crash of the USB 3 driver, like we talked about before, if you get curious and end up poking around a bit.
