6d error

[RiriRilu]

@Packetdancer: Thanks for your help! I appreciate it \ o /

I'm not exactly that great with computers so please bear with me..;; I took a look using Nvidia Inspector, but if I'm not wrong it doesn't even seem to reach the threshold if that is even the correct term to use: "Current clock 300MHz/ Memory 405 MHz vs "GPU Clock 1455 MHz/ Memory 6001 MHz/ Boost 1590 MHz". It is highly possible I am looking at the wrong section and just completely not understanding what I am reading though..

[Packetdancer]

@Packetdancer: Thanks for your help! I appreciate it \ o /

I'm not exactly that great with computers so please bear with me..;; I took a look using Nvidia Inspector, but if I'm not wrong it doesn't even seem to reach the threshold if that is even the correct term to use: "Current clock 300MHz/ Memory 405 MHz vs "GPU Clock 1455 MHz/ Memory 6001 MHz/ Boost 1590 MHz". It is highly possible I am looking at the wrong section and just completely not understanding what I am reading though..

Glad to help, but don't thank me yet; you're still not able to get into the game, after all. :/

Short form: Inspector is saying that your GPU clock's base speed is 1455 Mhz, but that when a game really wants power it will boost the clock to 1590 Mhz. (Which is fairly standard for a GeForce card of the most recent generations.) So you're not really overclocked. If you think it might still be a problem, you can reduce the base clock speed (the 1455) to something smaller, which in any sane world will reduce the boost value as well. That should exercise the card less extensively, and could clear up some issues. (Though if you have to underclock the card to make it work, I'd argue the card is broken and should be returned to the manufacturer for an exchange.)

That said, I admittedly really don't think GPU clock speed is likely to be the culprit here; it seems far more likely to be at fault when folks get a cascading list of DX11 failures.