8 réponses à ce sujet

[hellbiter88]

I don't want to be the pessimist of the group, but is anyone else finding that every new patch to fix bugs just brings more bugs?!

 

I am SO endlessly overjoyed that the last PC hotfix managed to squash the keydrop glitch in MP. HOWEVER, now my game (SP & MP both) are riddled with constant CTDs. I can't go 15 minutes now without a CTD everytime I load a new area or change to a different map. On MP the CTDs occur as soon as we reach the end battle or sometimes earlier.

 

It's NOT a driver crash--it's a straight-up CTD. (Although I do have driver crashes on occassion). I'm running 2 SLI GTX 980's with the recent driver. But I never used to get CTDs in this game of any kind until the last couple patches.

 

 

Is anyone else experiencing this? Is this a known issue with the recent patches? And is there anything I can do to minimize this?

 

Edit: To be fair, the CTDs seem to occur in streaks in MP. SP mode they're still constant. But it seems that I can go an entire day without a CTD in MP in some cases.

[Richardian]

That sucks.  I'm running 2x gtx680s in SLI, and I haven't experienced any CTDs after the most recent set of patches.  Prior to that, in December, I did get some CTDs on the second day of two back-to-back days of heavy playing.  A computer restart fixed this.

[Kantr]

That sucks.  I'm running 2x gtx680s in SLI, and I haven't experienced any CTDs after the most recent set of patches.  Prior to that, in December, I did get some CTDs on the second day of two back-to-back days of heavy playing.  A computer restart fixed this.

980 is a completely different beast to a 680.

[hellbiter88]

That sucks.  I'm running 2x gtx680s in SLI, and I haven't experienced any CTDs after the most recent set of patches.  Prior to that, in December, I did get some CTDs on the second day of two back-to-back days of heavy playing.  A computer restart fixed this.

 

What version of windows r u running? I just read somewhere that it might be a windows 7 thing--which is what I play on.

 

Also, I wish a comp restart would fix my CTDs

[Richardian]

What version of windows r u running? I just read somewhere that it might be a windows 7 thing--which is what I play on.

 

Also, I wish a comp restart would fix my CTDs

As someone else mentioned, the 980 and the 680 are different chips, so it's not necessarily an apples to apples comparison.  I am running windows 8.1.  I put my computer specs in my profile.  I hope you get everything running properly.

[DanteYoda]

Disable SLI its a fail idea and it ruins a lot of games, i bet your CTD is SLI..or newer driver related.

 

No Crashes in DA:I since i rolled back my drivers to 344.75 but i do still get a strange stutter (i've had that since the beginning)

 

Core i5 2500 3.3ghz

Asus GTX 770 2gb

16gb DDR ram

 

Win 7 home premium x64

[Ieldra]

I recommend disabling SLI. It causes a lot of problems and you don't need it for DAI if you're running a '980. I'm running DAI on a single 980 and Windows 8.1 and I have the occasional CTD here and there, maybe once every 20 hours, no big problem, and the only other graphic-related problem I have is microstutter in one cutscene panning across the Skyhold Undercroft. 

[hellbiter88]

I recommend disabling SLI. It causes a lot of problems and you don't need it for DAI if you're running a '980. I'm running DAI on a single 980 and Windows 8.1 and I have the occasional CTD here and there, maybe once every 20 hours, no big problem, and the only other graphic-related problem I have is microstutter in one cutscene panning across the Skyhold Undercroft. 

 

I will try that, then. Thanks.

[Realmzmaster]

This points out both the strength and weakness of the PC customization. While a patch may solve many problems for a lot of gamers that same patch can cause errors for other gamers because of PC configurations. No developer is going to be able to test every possible PC configuration. Even given minimum and recommended standards there will still be issues with some configurations.

 

The consoles are easier to debug because the hardware configurations are known. The developer can only fix a bug if they can replicate it. That is why when bugs are reported the PC configuration has to be stated also. Even then as I stated fixing a bug can introduce bugs elsewhere.

 

Q & A testing is done but even then all the errors may not be found because of the configuration being used.