View Full Version : Crashing Because of Dual Wielding?


Maxinion
Sun, 31st Oct '04, 12:23am
Recently, I've tried to install BG2 and ToB on my brand new computer... Windows XP Home Service Pack 2, Athlon 64 3400+, Asus K8NVSE Mobo, 1 Gb ram, Nvidia Geforce 6800 GT, etc, etc. The game goes all well and dandy... until I equip a weapon (or shield) into my offhand.

I get an error message, though, but it's very strange: "Memory location 00x0000EFF (or somesuch... don't have the EXACT number down, but I know its a hex memory location) is unable to be written to." The game then crashes. This persists after 3 separate install/ uninstall runs, each time using the latest ToB patch and no mods. In fact, I can also confirm that it exists in SoA, with no ToB. I know the discs are not corrupted since I am able to play on an older machine (Windows XP Home, SP 1, 512 Mb RAM, Radeon 9800, etc.).

So my question to the community: any ideas? I've come to the conclusion that it may be a SP2 problem, as SP2 has been known to break compatibility with older programs, but I'm not willing to test this out on my own and risk ruining my only BG2 capable box. I've found no information on this online, so I'm looking to you guys for help. Any comments and suggestions are more than appreciated!

Celesialraven
Sun, 31st Oct '04, 12:32am
I don't belive its SP 2. I've got a similar rig with SP 2, and I don't have any problems (aside from the known slowdown-on-new-computers thing that's caused by the infinity engine.

Maxinion
Sun, 31st Oct '04, 12:37am
Thanks Celesial... that throws out my main idea. Shucks...

I forgot to mention some other tidbits... I have the latest drivers for mobo and vid card installed (I doubt that that would be a problem with such an old game anyway), and I have no problems running Far Cry and Doom 3, et. al.

Yirimyah
Mon, 1st Nov '04, 11:23am
Stop showing off! :D
Personally, i wish I had a new computer to complain about.

Emmanuel Julius
Thu, 4th Nov '04, 7:28am
Hmm that is strange, maybe try checking your configuration...it could be that 3D acceleration is enabled and this may be causing the problem and it might also be worth a shot to set the hardware settings to average, above average, or maximum and see if any these settings helps at all...