Hi all,
I had Dragon Age: Origins (Deluxe, DL through Impulse) installed and running at patch 1.03 without any issues, then when patch 1.04 was released I downloaded and tried to install it. During the install I receive a Blue Screen of Death, and the PC reboots. When I go into Impulse afterwards it thinks the install has completed successfully, but when I try to launch DA:O it gives me the message "The game cannot launch because of a misconfiguration. Pleaes reinstall your game and try again".
So I completely uninstalled DA:O, redownloaded the entire thing and tried the install again. Once again during the install I got a BSOD, and same symptoms of Impulse thinking it's installed properly but the game won't launch.
Every BSOD or "crash" message I've searched for in relation to DA:O seems to be in regards to in-game crashes or date back to Nov 2009 from the initial release. Any help would be appreciated!
Windows XP 32-bit
ATI Radeon HD 5800 w\\ version 10.6 drivers
-Rune-
BSOD on install of DA:O
Débuté par
Rune_13
, août 04 2010 09:08
#1
Posté 04 août 2010 - 09:08
#2
Posté 04 août 2010 - 05:02
Hi Rune_13, blue screens of death are usually core system software or hardware related. Providing your computer doesn't reboot immediately, the BSOD itself should provide you with information that can help you diagnose your problem. In your system control panel, under the advanced tab, and under Startup and Recovery settings, you can un-check the "Automatically Reboot" option and that may give you a bit of a longer look at your BSOD.
Here's an example of a Windows XP BSOD: en.wikipedia.org/wiki/File:Windows_XP_BSOD.png
As you can see, there's stop information - a.k.a. a bug check code, and sometimes (but not always) it also references a specific system file related to the error. Here's a list from microsoft of the various bug check codes: msdn.microsoft.com/en-us/library/ff542347.aspx
By way of example, the bug check in the example I listed you can find on the microsoft page at 0x50.
This is a lot of information to sift through, but that is by far the best way to accurately diagnose your problem. My only caution would be that this is not an exact science by any means in that excessive system heat and overclocking can cause BSOD's that are unrelated to those problems, among many other things.
Good luck!
edit: to make the links work.
Here's an example of a Windows XP BSOD: en.wikipedia.org/wiki/File:Windows_XP_BSOD.png
As you can see, there's stop information - a.k.a. a bug check code, and sometimes (but not always) it also references a specific system file related to the error. Here's a list from microsoft of the various bug check codes: msdn.microsoft.com/en-us/library/ff542347.aspx
By way of example, the bug check in the example I listed you can find on the microsoft page at 0x50.
This is a lot of information to sift through, but that is by far the best way to accurately diagnose your problem. My only caution would be that this is not an exact science by any means in that excessive system heat and overclocking can cause BSOD's that are unrelated to those problems, among many other things.
Good luck!
edit: to make the links work.
Modifié par Nathan Willis, 04 août 2010 - 05:03 .
#3
Posté 04 août 2010 - 05:33
Catalyst 10.5, 10.6 and 10.7 are known to cause BSOD on Dragon age.
I myself have encountered several GSOD in dragon age under these drivers.
So, I rolled back to my stock driver (catalyst 10.1) and the game is stable.
Edit- There is a way to use the 10.6 driver without getting SOD. If you google about ATI 5000 series getting BSOD or GSOD under 10.6, you will find the solution. It has something to do with default core and memory clock speed of the card not getting along with new drivers, so people who have the problem solve the issue by overclocking the card. Personally, I wouldn't recommend to adjust clock speed manually since it could cause overheating probelm. By the way, catalyst 10.7 is out but it still gave me GSOD yesterday while i was playing awakening.
I myself have encountered several GSOD in dragon age under these drivers.
So, I rolled back to my stock driver (catalyst 10.1) and the game is stable.
Edit- There is a way to use the 10.6 driver without getting SOD. If you google about ATI 5000 series getting BSOD or GSOD under 10.6, you will find the solution. It has something to do with default core and memory clock speed of the card not getting along with new drivers, so people who have the problem solve the issue by overclocking the card. Personally, I wouldn't recommend to adjust clock speed manually since it could cause overheating probelm. By the way, catalyst 10.7 is out but it still gave me GSOD yesterday while i was playing awakening.
Modifié par philjoo, 04 août 2010 - 05:44 .
#4
Posté 04 août 2010 - 08:01
Thanks for the response guys. The BSOD usually reboots itself before I get a chance to write down what it is(because i'm often not sitting at the computer waiting for it at the end of an 8gb install). I've got it archived now, so I'll give it another attempt and see if I can determine the stop-code.
I'm not exactly sure when this first occured, but I think it was a few months ago (I wasn't really playing much at the time so I ignored it..). I'm also pretty sure that i had an Nvidia card at the time too.
If I can't find anything with the stop-code I'll try rolling back to the old drivers.
Cheers, I'll let you know how it goes!
-Rune-
I'm not exactly sure when this first occured, but I think it was a few months ago (I wasn't really playing much at the time so I ignored it..). I'm also pretty sure that i had an Nvidia card at the time too.
If I can't find anything with the stop-code I'll try rolling back to the old drivers.
Cheers, I'll let you know how it goes!
-Rune-
#5
Posté 04 août 2010 - 11:11
Okay I've fixed it. It seems it was due to a conflict with windrvNT.sys which is a file from Folder Lock. I've uninstalled Folder Lock, the file is gone, and now the install works.
***Stop: 0x0000008E (0xC0000005, 0xAFD66703, 0x9D1EAC70, 0x00000000)
*** windrvNT.sys - Address AFD66703 base at AFD65000, Datestamp 409f405c
Thanks for the help guys!
-Rune-
***Stop: 0x0000008E (0xC0000005, 0xAFD66703, 0x9D1EAC70, 0x00000000)
*** windrvNT.sys - Address AFD66703 base at AFD65000, Datestamp 409f405c
Thanks for the help guys!
-Rune-
#6
Posté 04 août 2010 - 11:17
Well. Seems I was a bit premature.
The install completed, I then installed Awakenings, then the patch 1.04 on the top. No problems during the install, but now when I try to launch DA:O or Awakenings I get a stupid message saying "The game cannot launch because of a misconfiguration. Please reinstall your game and try again." !!
Sigh. Back to work I guess.
The install completed, I then installed Awakenings, then the patch 1.04 on the top. No problems during the install, but now when I try to launch DA:O or Awakenings I get a stupid message saying "The game cannot launch because of a misconfiguration. Please reinstall your game and try again." !!
Sigh. Back to work I guess.
#7
Posté 04 août 2010 - 11:52
Just a little quick general advice: you can turn off the auto-reboot on BSOD.
http://pcsupport.abo...t-windows-7.htm
http://pcsupport.abo...t-windows-7.htm
#8
Posté 12 août 2010 - 10:44
So it seems I've got it all working now. Thanks for the help guys. To get around the "cannot launch because of a misconfiguration" I installed the EA Download manager and launched DA:O through there. Now it works normally, even if i don't launch it through the EADM.
-Rune-
-Rune-





Retour en haut






