Crash with exception code 0xc0000005, offset 0x000d332d

Any issues with the XWAU or X-Wing Alliance? Please let us know here!
Post Reply

Crash with exception code 0xc0000005, offset 0x000d332d

Turgidson
Cadet 2nd Class
Posts: 52
Joined: Sun Aug 25, 2019 10:02 pm

Post by Turgidson » Fri Sep 27, 2019 12:33 am

I'm having a crash with exception code 0xc0000005, offset 0x000d332d, despite having the Hook_Res1200.dll - whilst playing at 1920x1200 resolution.
It seems that when selecting 1920x1080 instead, the crash isn't occurring anymore (or I was lucky).

Game has DSUCP 2.6, last hooks from Jeremy (using XwaHooksSetup), and also ddraw.dll and dynamic cockpit from blue_max (but it already crashed with Jeremy's ddraw.dll).

To get 1920x1200, I patched Xwingalliance.exe with xwahacker-3.2, parameters were 1920 1200 1.49 86.30.

Did I make a mistake with my patching? Or is there still a bug with the 1200 vertical resolution?

My crash occurs in skirmish, with some capital ships (enemy VSD or ISD for example). Seems to happen when the ISD is being attacked by the fighters (it seems OK as long as it's dogfighting). Other settings would probably also be able to trigger the crash, I haven't tested this extensively...

Turgidson
Cadet 2nd Class
Posts: 52
Joined: Sun Aug 25, 2019 10:02 pm

Post by Turgidson » Sat Sep 28, 2019 9:15 pm

It seems I was lucky it initially did not crash at 1920x1080. Played some other skirmishes, and it crashed even at 1920x1080.

However, when deactivating the Hook_Res1200.dll, it seems this crash doesn't occur anymore at 1920x1080. So maybe that was the culprit?

User avatar
JeremyaFr
XWAU Member
Posts: 3921
Joined: Mon Jan 18, 2010 5:52 pm
Contact:

Post by JeremyaFr » Sun Sep 29, 2019 3:11 pm

Yes, it may be that.

User avatar
guru_redeye
Cadet 2nd Class
Posts: 62
Joined: Wed Oct 06, 2004 11:01 pm

Post by guru_redeye » Thu Nov 21, 2019 1:26 pm

Turgidson wrote:
Fri Sep 27, 2019 12:33 am
I'm having a crash with exception code 0xc0000005, offset 0x000d332d, despite having the Hook_Res1200.dll - whilst playing at 1920x1200 resolution.
It seems that when selecting 1920x1080 instead, the crash isn't occurring anymore (or I was lucky).

Game has DSUCP 2.6, last hooks from Jeremy (using XwaHooksSetup), and also ddraw.dll and dynamic cockpit from blue_max (but it already crashed with Jeremy's ddraw.dll).

To get 1920x1200, I patched Xwingalliance.exe with xwahacker-3.2, parameters were 1920 1200 1.49 86.30.

Did I make a mistake with my patching? Or is there still a bug with the 1200 vertical resolution?

My crash occurs in skirmish, with some capital ships (enemy VSD or ISD for example). Seems to happen when the ISD is being attacked by the fighters (it seems OK as long as it's dogfighting). Other settings would probably also be able to trigger the crash, I haven't tested this extensively...
Experiencing exactly the same crash on DSUCP 2.6, with the same exception code at the same code address when attacking an ISD/VSDII with an a-wing in a skirmish.

Been experiencing this crash from XWAUCP v1.6, since april (2019).

Turgidson
Cadet 2nd Class
Posts: 52
Joined: Sun Aug 25, 2019 10:02 pm

Post by Turgidson » Thu Nov 21, 2019 4:27 pm

In my case, removing Hook_Res1200.dll solved the issue (or maybe I've been lucky?).

User avatar
guru_redeye
Cadet 2nd Class
Posts: 62
Joined: Wed Oct 06, 2004 11:01 pm

Post by guru_redeye » Thu Nov 21, 2019 6:00 pm

WoW! CONFIRMED!

Since I don't use any screen resolution mod/hack - I run XWA on a 4:3 monitor in full screen windowed mode - I was sure it had nothing to do with any resolution hook and stuff but then I read the description of Hook_Res1200.dll and removed it to give it a try.

It seems there are no crashes since I've done that! Thanx for sharing your experience @Turgidson :2thumbs:

Justagai
Cadet 1st Class
Posts: 218
Joined: Mon Dec 08, 2014 10:59 pm

Post by Justagai » Fri Nov 22, 2019 2:05 am

I actually did get a crash a few days ago with that same offset. This was with version 1.0.0.1.

User avatar
JeremyaFr
XWAU Member
Posts: 3921
Joined: Mon Jan 18, 2010 5:52 pm
Contact:

Post by JeremyaFr » Thu Jan 30, 2020 9:04 pm

Hello,
Here is a workaround:

See Crash at offset 0x000d332d

Post Reply