OK
Before anybody Jumps down my throat, this seems to affect a small number of users and there are of course a million things that could also contribute to driver instability.
However......
I had an issue with Elite Dangerous where I would jump to hyperspace and the game would CTD with a D3D error. This started happening after a patch
In my testing I did the usual stuff and then started down clocking my card in increments and tetsing. When I got to below 1200 MHz base clock, the issue went away... fully away... If I overclocked/returned it to my Card's clock speeds 1233 MHz... it crashed... any sort of Overclock from my factory speeds and it would just crash....
I passed all this info onto support along with my testing results.. they eventually replied saying it was reported by other users and my work around was being past on.
Come GTA V
I have started getting the dreaded ERR_GFX_D3D_INIT CTD after the last patch
Again loads of messing around, raised a ticket with R* then found a steam discussion.
It would seem that again this issue might be resolved for some (me included) by down clocking their cards from Factory set clocks speeds to near reference clocks....
I have mine running at a base clock of 1199 and it has not crashed after 4 hours of game play.... put it back to stock clocks for my card and it crashes, overclock it and it crashes even quicker.....
As I said, not all are having this issue, not all people are getting it resolved....
My point.
Is this an issue with Nvidia, Direct 3D or our cards being factory overclocked?????
As I said, It's gone away for me and I can now play without crashing....
Before anybody Jumps down my throat, this seems to affect a small number of users and there are of course a million things that could also contribute to driver instability.
However......
I had an issue with Elite Dangerous where I would jump to hyperspace and the game would CTD with a D3D error. This started happening after a patch
In my testing I did the usual stuff and then started down clocking my card in increments and tetsing. When I got to below 1200 MHz base clock, the issue went away... fully away... If I overclocked/returned it to my Card's clock speeds 1233 MHz... it crashed... any sort of Overclock from my factory speeds and it would just crash....
I passed all this info onto support along with my testing results.. they eventually replied saying it was reported by other users and my work around was being past on.
Come GTA V
I have started getting the dreaded ERR_GFX_D3D_INIT CTD after the last patch
Again loads of messing around, raised a ticket with R* then found a steam discussion.
It would seem that again this issue might be resolved for some (me included) by down clocking their cards from Factory set clocks speeds to near reference clocks....
I have mine running at a base clock of 1199 and it has not crashed after 4 hours of game play.... put it back to stock clocks for my card and it crashes, overclock it and it crashes even quicker.....
As I said, not all are having this issue, not all people are getting it resolved....
My point.
Is this an issue with Nvidia, Direct 3D or our cards being factory overclocked?????
As I said, It's gone away for me and I can now play without crashing....