Aller au contenu

Photo

DirectX error causing CTD


  • Veuillez vous connecter pour répondre
94 réponses à ce sujet

#51
Tanash

Tanash
  • Members
  • 55 messages

Still getting this error with new drivers and stuff previously tried, was able to play quite sometime though  but now it just crashed again while selecting a perk.



#52
Arenthas

Arenthas
  • Members
  • 5 messages

I am still having this problem after the driver updates with GTX 660. Thankfully it's not very often, maybe once every 4 hours. 



#53
Mitzux

Mitzux
  • Members
  • 1 messages

Yeah I get the DirectX "HUNG" about every 20 minutes with a NVidia 780ti SLI, BTW does anyone know if SLI is supported yet, when I have it enabled in NVCP I get about 1/3 (20 fps) the frames I get with SLI disabled (55 ish)? never the less this is unacceptable for DA:I, the only game this year I was really looking foreword to. 

p.s  the new driver 334.75 is useless when it comes to the CTD's.



#54
Firebug6

Firebug6
  • Members
  • 23 messages
I had the same issue after updating to the most recent nvidia drivers on my 980.

Rolled the drivers back, and have not crashed to desktop again after 7 hours of play.

Good luck!

#55
Hax_the_unjust

Hax_the_unjust
  • Members
  • 46 messages

Still getting this error with new drivers and stuff previously tried, was able to play quite sometime though  but now it just crashed again while selecting a perk.

Same but not as often.  I am crashing once about every 4th or 5th cut scene, still quite annoying.


  • frylock23 aime ceci

#56
Ansa

Ansa
  • Members
  • 69 messages

Confirmed, same DirectX crashing every 1-4 hours of play.

Seems like really bad coding got released into the wild.

Can we have a developer post here???



#57
Hax_the_unjust

Hax_the_unjust
  • Members
  • 46 messages

Confirmed, same DirectX crashing every 1-4 hours of play.

Seems like really bad coding got released into the wild.

Can we have a developer post here???

Devs haven't said anything about all the funk with this title.  They're currently hidden away in their tower counting the money.  When devs feel the dust has settled and the angry mob of peasants has disbursed from the grounds below they will peak their heads out.  Then cautiously come out and say they're releasing a patch to fix some issues... but by that time some people will have already beaten the game or quit playing. LOL :(



#58
JonWoo89

JonWoo89
  • Members
  • 10 messages

Same error for me. And when that's not causing me to crash my game keeps freezing in cutscenes. I've given up trying to play for the time being and I'm hoping someone figures out what the problem is soon.



#59
TyrantCS

TyrantCS
  • Members
  • 2 messages

Same issue, two PC's.

 

Wife's PC

i5-2500k

Geforce 760

8 gig of ram

Windows 7

All drivers updated, nothing overclocked.

Large case with very good airflow.

 

My PC

i5-2500k

Geforce 770

8 gig of ram

Windows 7

All drivers updated, CPU slightly overclocked.

Large case with wind tunnel like airflow.



#60
Hektik

Hektik
  • Members
  • 1 messages

Finished downloading DA:I Today, and It seems like it will be a great game, if I could play longer in any given session.

It seems the CTD for me only occurs during cutscenes. Literally only cutscenes. I made a new character and rushed through all dialogue cutscenes until after the Pride Daemon fight and waking up/talking to Cassandra in the Chantry. Not a single CTD During that time.

Rewind to my first time playing, CTD On nearly every dialogue depending on the duration. I have tried every proposed fix to no avail. It has gotten to the point where if it crashes once, I have to restart my entire computer to even get the game to boot up again. I feel this is a massive oversight on the part of Bioware, one that has yet to receive a proper response from them. I read their announcement post and there was no mention of this issue in it only control issues, and general stuttering of the game (Of which I never received any). Until this is fixed I feel like this has been the biggest waste of $65 to date.


  • Mushashi7 aime ceci

#61
Baffle

Baffle
  • Members
  • 2 messages

I'd just like to add that changing my display to windowed mode, or borderless window mode stopped my directx crash for a while.  I haven't had a crash since I did that.  I heard of this solution elsewhere so it probably works for some other people as well.  


  • drake2511 aime ceci

#62
JerZey CJ

JerZey CJ
  • Members
  • 2 841 messages

My game hadn't crashed since the drivers released but I just randomly got it again. I'll chalk it up to having played for a long while, so I'll let my PC and game have a break for now.



#63
JerZey CJ

JerZey CJ
  • Members
  • 2 841 messages

Just had it happen two more times. damn, I hope a patch fixes this soon.



#64
ShadowLordXII

ShadowLordXII
  • Members
  • 1 228 messages
First day that I played the game, I had no problems, stuttering or FPS drops whatsoever from the prologue, through Haven and in the Hinterlands.
 
Second day, I crash twice, once in-game and the second time while the game was connecting to DA servers. I updated my VG's drivers and didn't have any problems through the rest of that day.
 
Third day, I play through a lot of stuff for a few hours and quit with no problems. The second time, I tried out multiplayer and the game crashes after I exit to the main menu. I try to play again and it crashes when connecting to DA servers yet again.
 
I'm running the following specs:
 
AMD Phenom X4 945 Quad-Core 3.ghz - Meets requirements
 
Radeon HD 6970 2 GB VG - Power equals recommended specs
 
8 GB DDR3 Ram.
 
Windows 7 64-Bit
 
All drivers have been updated and as I said before, I had no trouble playing the game on high settings when it first came out. Whatever is causing these problems, it does not appear to be related to hardware or else the symptoms would be more obvious.
 
And it sounds like I'm not the only one have these same/similar problems either. I'm not one to sling mud at Bioware because after 10 hours of gameplay, I can say that this is the best game that the developers have made in the past few years.
 
So when I've encountered 4 crashes, with 2 being in the same day within the same time frame for no real reason, you'll have to forgive me for being very upset. You held back this game and delayed release by another month, how could something this bad still happen across multiple pcs that fit your stated hardware requirements? What software related issue did you fail to fix before the release date for this to happen?
 
More importantly, what can be done to resolve this problem? If I thought that I simply had to lower some settings in the graphics options then I wouldn't be making this post. But since I have 10 hours worth of proof that my hardware is sufficiently supporting the settings for the game, graphics settings appear to be the least likely suspect. I've also updated my drivers which are stated to boost FPS and help with stability, and now I've crashed twice more.
 
If it happens again, I may refuse to play at all until this issue is resolved.
 
Well, given Bioware's track record for the past few releases, something was bound to get screwed up, wasn't it?


#65
MrProb

MrProb
  • Members
  • 1 messages

Has there been any reply from Bioware about this problem yet ? because this is not a small problem since almost everyone gets this error, not to mention crashing during cutscene could be annoying since there'll be a lot of cutscene and you never know when is it going to crash.



#66
BlackHawk01x

BlackHawk01x
  • Members
  • 34 messages

Well the only answer so far I found was a troubleshooting-faq which says:

1. Check if drivers are uptodate

2. Check if your hardware is actually good enough for the game

3. better don't use overclocked GPU at the moment

 

All besides that it's just hoping they already work on a fix for that problem and it won't take too long till that fix appears...

 

If that "not overclock the GPU" actually works I cannot tell. I bought my video-card already overclocked (like so many are overclocked as standard these days) and now I try to find a way how to 'easily' see if I can downclock it without breaking anything... (since I'm really terrible when it comes to technic and stuff like that...)



#67
Scrydragon

Scrydragon
  • Members
  • 10 messages

I didn't get a single crash since I updated to a new driver and switched to a borderless window mode from a fullscreen.

Try playing on a borderless window. That's what truly did the job for me.

 

 

I was very skeptical, but this worked for me.  After many, many hours of game play, I've only had one crash to desktop, and even then, the program just quietly closed itself.

 

Bordeless window looks JUST like fullscreen, so I don't have any issues with it.  Thank you so much for mentioning it.



#68
frylock23

frylock23
  • Members
  • 3 037 messages

It's the cutscenes. I can run around in the Hinterlands all I want, do just about whatever I want, talk to as many people as I want, no problems. I can go somewhere with cutscenes, and after each one, my performances gets just that much worse until it gets to be too much and the game crashes with this bug. Whatever it is is progressive and gets a little worse after each cutscene until it finally crashes out your machine.


  • ddman12 aime ceci

#69
Heldarion

Heldarion
  • Members
  • 6 171 messages

I'm crashing all over the place, cutscenes or not, I even crashed while checking journal. My GFX is Radeon HD 5850, and most of the settings are on LOW.

 

I've probably crashed 20+ times in half as many hours.



#70
BroBear Berbil

BroBear Berbil
  • Members
  • 1 512 messages

I'm having this problem too and I can't figure out how to fix it. Fullscreen or borderless windowed, low settings, lowering resolution, latest drivers, updated DirectX, nothing really seems to help from graphics settings. Usually the CTD happens in a loading screen for me anyway, or it'll successfully load and then CTD a second later.

 

This happens over and over until I sometimes get lucky and can play without issue for awhile, then the process starts all over again.



#71
Krishna2009

Krishna2009
  • Members
  • 18 messages

same problem, geforce 760 gtx



#72
Tanash

Tanash
  • Members
  • 55 messages

Crash crash...crash.............. and another crash while in a cutscene dialogue in Skyhold.

 

I am getting quite some hours between every crash but now its getting tiresome and old.



#73
PuPpEt

PuPpEt
  • Members
  • 1 messages
DirectX function "device->CreateTexture2D( &texDesc,desc.subResourceCount !=0 reinterpret_cast<constD3D11_SUBRESROUCE_DATA*>(desc.subResourceData) : 0, &texture->m_texture2D)" failed with E_OUTOFMEMORY ("Direct3D could not allocate sufficient memory to complete the call"). GPU: "NVIDIA GeForce GTX 970", Driver 344,75. Free virtual memory 4291078280kb / 4294967168kb. Total resource memory: 0kb. Make sure you have the supported graphics card with at least 512MB.

 

I just bought the game, and i can't play it.. i get this error just after the first intro scenes, can't get past.. my asus gtx970 have 4gb of memory i don't know why i get this error



#74
Zaknus

Zaknus
  • Members
  • 2 messages

I had the same problem as most people on this forum topic, and tried everything I found. Right now i put the stats from automatic to High and turned off the MSAA. Also I changed the screen from fullscreen to borderless window and so far no crushes. I have two  AMD 6850 GTs, and the newest drivers I could get,



#75
Mushashi7

Mushashi7
  • Members
  • 824 messages

Same DirectX error and CTD here.

I can't get through the intro and make my first save. DA:I crashes to desktop  right after the graphics disappear and I hear the sound getting wierd. It happens exactly where 'your charcater' reaches out for the figure op top of the stairs.

Looking at the taskbar shows a DirectX error every time.
First I thought it was a matter of tesselation conflict. Turning it of did it for Tombraider (2013). But the problem stayed.
Then I thought it might be a problem with the FPS cap at 30 fps and added this to the command line:

-GameTime.MaxSimFps 60 -GameTime.ForceSimRate 60+

It did not help.

What I did was changing every setting to Low (lowest), and I was able to get into the first map and fight a few demons. But it looked awfull. The graphics was boring and simple (even the hair of the characters were shiny as glass, as if they used a lot of grease in it). Not a nice experience at all.

I am on an i5 with 8 GB RAM and GForce GTX 660 (4 GB).

I noticed in the NVidia GeForce Experience that they haven't released optimised settings for the game yet, although the new drivers claim they are prepared for this game. They are probably on it as we speak. It is after all one of the major games.

I'll await the NVidia solution and play more Skyrim or something in the meanwhile.

[Edit] I noticed the game very fast reaches the 2 GB RAM limit, Maybe I should try to free up more, but I don't like this as Win7 usually is pretty good at this job. [/Edit]


Modifié par Mushashi7, 21 novembre 2014 - 10:20 .