Crashing with 1.03? Try this.
#51
Posté 26 mars 2010 - 12:18
For everyone in general still having issues:
Something to note that many people in today's system security conscious world may not be considering... having a virus protection program active during a software installation is actually a good way to get a corrupted installation (and even if its not, it can result in a less than optimal file placement which will affect load times). Firewalls can also cause problems. The difficulty, of course, is in installing cleanly without getting hacked during the process. The solution is to ensure that you download all applicable files while your security is active. Then disconnect yourself from any online access (pull the cable or disconnect the modem, whatever it takes) before shutting down your virus protection and firewalls. Install the software. Restart the computer. This is a good plan after any software installation, but also serves to ensure that all protections are restarted as part of your standard boot up process. Then reconnect to the internet and run your program.
#52
Posté 26 mars 2010 - 12:42
#53
Posté 28 mars 2010 - 11:33
Jokes aside, my computer only blue-screens with DAO, so I have been looking for other possible causes. I have found another possible culprit: Zinio Reader has a module that goes online and checks for new digital magazine issues. It had reported a problem on screen after rebooting each time I had a crash. I checked the log and the time seems to match when DAO crashed. I've since upgraded Zinio Reader and not installed the module that checks for updates automatically.
Here is another thought: I installed the previous patches using the "run as administrator" option in Windows 7 but had forgotten to do this for patch v1.03. Could that be a source of the problem, in addtion to the anti-virus software issues mentioned by Jaesic?
#54
Posté 28 mars 2010 - 01:31
Worked for me!! :]
#55
Posté 28 mars 2010 - 02:19
Is anyone else who has issues with Windows 7 able to run 1.02a? I briefly installed 1.03 in the OC, and was running OK (think I had 1 crash when I exited), but I panicked and reinstalled 1.02a when I read all the horror stories.
#56
Posté 28 mars 2010 - 02:36
So this online stuff worth trying...though Awakening still crashes...in same places!
#57
Posté 28 mars 2010 - 04:28
#58
Posté 28 mars 2010 - 04:55
@gediv
Have you tried any of the things on here? If you're having problems on the retail version try the DX fix a page back.
#59
Posté 09 avril 2010 - 12:28
#60
Posté 09 avril 2010 - 03:56
#61
Posté 09 avril 2010 - 09:30
In my case the crash always occurs in combat when a spell/talent is used. It occured for example when using the glyph combo, activating stealth, activating holy smite, ...
It doesn't occur always, for example today I was able to play 2-3 hours without issues and suddenly the glyph combo caused a crash (while I had been using it before in that 2-3 hour timespan)
Same here. With the auto-save and online features disabled, per the instructions, I was able to play without issue for almost an hour. I activated stealth and crashed to desktop.
Win 7, 64 bit
Athlon II x3 440
4 GB RAM
ATI Radeon 5780, just one card, no Crossfire
#62
Posté 09 avril 2010 - 11:13
#63
Posté 10 avril 2010 - 03:36
Modifié par cmessaz, 10 avril 2010 - 03:36 .
#64
Posté 10 avril 2010 - 03:58
#65
Posté 10 avril 2010 - 04:07
#66
Posté 10 avril 2010 - 04:47
#67
Posté 10 avril 2010 - 05:42
#68
Posté 10 avril 2010 - 06:20
Jaesic wrote...
Yes, whatever Pope. Assigning blame doesn't solve it though. Some of us prefer to make an effort to help fix the problems instead of standing around demanding someone else do it for us... a statement that is true about far more in some parts of the world than a game for which you paid LESS THAN 4 HOURS of wages for most educated and experienced labor.
I tried what you had posted and 10 minutes in a battle caused another crash. Before patch 1.03 I had 2 crashes in 40+ hours of play. Now that patch 1.03 is out it crashes every time I play. I have a question for people that aren't having the crash issues. Are you guys running a 32 bit OS or a 64. I read an email from EA that lead me to believe this may be a 64 bit issue. Will Darrian the elf slay the archdemon I have no idea because I can't play the game anymore. I really can't believe this it seems Bioware and EA are handling this situation poorly. I know one guy that won't be playing Awakenings, and before these crash issues I had fully intended to.
#69
Posté 10 avril 2010 - 04:18
#70
Posté 10 avril 2010 - 04:23
cmessaz wrote...
I am running Windows 7 64 bit, but the thing is I shouldn't have to change my settings or anything just to play the game, as I was able to play just fine before the patch, it never crashed on me. Not once, and I have been playing this game since it was released.
Same here. I definately agree with you. I'm also on Win 7 x64. I didn't have a single crash playing OC in 250ish hours of play. One little patch and now it's a daily, if not hourly, thing.
#71
Posté 10 avril 2010 - 04:58
#72
Posté 10 avril 2010 - 05:06
Jansaadi wrote...
it tells the game to run off of 1 processor only, my brother set mine up through the shortcut to always run off of 1 but you can start the game then through the task manager right click and set to 1 processor. This way you have to do it each time you play and you are not messing with the shortcut or anything.
Affinity tells the application how many processing threads to use. It sounds a lot scarier than it actually is - just right-click in task manager, then select "set affinity" and uncheck everything except core 0. It won't affect anything else. Out of interest, are you running and AMD or Intel setup?
#73
Posté 10 avril 2010 - 05:13
Modifié par cmessaz, 10 avril 2010 - 05:15 .
#74
Posté 10 avril 2010 - 05:29
cmessaz wrote...
I am running Windows 7 64 bit, but the thing is I shouldn't have to change my settings or anything just to play the game, as I was able to play just fine before the patch, it never crashed on me. Not once, and I have been playing this game since it was released.
I couldn't agree more. I saw an email to a friend who had dealt with EA tech support directly it said that they do not support 64 bit OS systems. Why they would say that is beyond me because it also worked for me for so long, windows 7 64 bit here. You shouldn't have to screw with your computer to play a game. Especially retarding your processor to run off one what is that all about. So if I was to try and run this game on my old outdated rig it would look like crap but it would not crash??? This whole thing is amazing I've never heard of a company patching a game and having the patch make the game unplayable, 30 some odd days later still nothing. Their is a reason they are not stepping up and handling this I wish I knew that reason. By the time they make the game playable again I may have forgotten about it. Having to disable things to play a game means the game is broken plain and simple. I would expect this from some small startup developer but not a company thats renowned for its games. To me they will always be known for ruining a game and doing nothing about it. And if they are they aren't telling the community much of anything, bad form EA and bioware. Sorry guys I'm still angry need to go play an FPS.
Modifié par JJTheDamager, 10 avril 2010 - 05:31 .
#75
Posté 10 avril 2010 - 05:37





Retour en haut






