Windows event log says this:

Faulting application BGMain.exe, version 2.5.0.2, time stamp 0x3b71b6f4, faulting module BGMain.exe, version 2.5.0.2, time stamp 0x3b71b6f4, exception code 0xc0000005, fault offset 0x00637715, process id 0x178c, application start time 0x01cb89266e70dc62.

About the only thing that tells me is the game is having a meltdown. Past that, I don't know what's wrong. It does it without mods, it does it with mods. I installed with no UAC enabled and ran vanilla. Crash. I installed with no UAC enabled and then installed Fixpack (still with no UAC enabled). Crash.

Basically, playing with my character inventory results in crash. This happens after looting the very first chest in the next room over from where you start the original BG2 adventure.

I'm crapping my pants with excitement at finally being able to play this to the end, but something about inventory'ing is killing my buzz!

Just to start the ball rolling for you:

did you install the game as Admin?
do you run it as admin?
did you set compatibility mode to Win XP SP3?
have you tried a complete reinstall?

Omg I got so wrapped up in the swirling UAC poopoo around the mods that I forgot. *Facepalm*

Reinstalling. I'm guessing that will fix the issue, so I'll go back to crapping my pants with excitement. Will let you know what happened. I guess I left my brain at work in the excitement to get home and play :-)

Good luck! Hope it works for you.

'ello

Quick question, cause I ran into this a few years back: If you don't use the Widescreen mod and set the resolution to something greater than 1024x768 the game crashes on the inventory screen. At least it did so for me.

Did you ever find a way to fix this? If so, tell me what you did. If not, try adding the game folder to all exception lists on your virus scanner, some people report that that works.

Missed this, but what TheBlackKnight typed Same with me. NOTE: These are UnSupport resolution modes were not support by the original developers so your on your own (with the communities help) if you run into issues (but again gog.com community will help where it can if you pose the question/situation well).

.. running the risk, getting banned from the GOG forums for necromancing on a zombie-thread:

I just had this type of crash in Linux with WINE (OpenGL) and did not waste a thought about the "unsupported resolution" config screen. WINE is reproducing this 'bug' faithfully in Linux and crashes equally with an error dump.

If somebody googlebings this topic in the distant future (like me) - there's your answer, above. Stick to default resolutions or use widescreen fix.