Vanguard Crash Issue

[Meldryn]

When trying to load Vanguard through Innerspace, two of my three computers run perfectly. The third, despite having installed and configured it in the exact same way, repeatedly crashes every time I try to load Vanguard through Innerspace. It opens the window that says it is loading, but when trying to bring up the launchpad, it crashes and gives me a lovely error box telling me what has happened. If anyone else has experienced this and found a solution, I would appreciate any help you could offer.

[RS47]

I'm having the same problem and I can't figure it out.. it used to work perfectly till yesterday, but today it won't work.

I tried to restore the system to a previous backup point but didn't fix the problem.

I haven't installed or updated any software or hardware in the last 10 days, so I really do not know what might be cause of this.

[Shemploo]

Same problem here

[eaglepigjim]

I'm getting the same problem. Everything was working yesterday on my Windows 2000 pro sp4 box. Innerspace patched today and now I get the following 2 errors:

The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.

The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read". Click OK to terminate the program

Thanks[/img]

[craf]

I have same problem, happened right after download of 8/1 patch

[Xavik]

For me, it looks related to audio. When I disable audio in the game through vgclient.ini, it loads up fine. Then the second I enable audio through the settings interface in the game, it crashes with the same data. I've reported the crash data through the Innerspace report method.

Hope this gets fixed soon, I need sound and Innerspace working together!

-Xavik

[misagh]

I'm having an identical problem and it began after the patch on Aug 1st.

Reposting this:

I am unable to provide Windbg debug report because this problem is causing my system to become unresponsive and require a reboot.

Operating System type: Windows XP Home
Amount of RAM: 2 Gigs
Processor type and stats: Intel Core2 Duo 6300
Video card brand and stats (be very specific): ATI Radeon x1950 Pro
ISXVG version and isxGamesPatcher version - Not sure how to check because I can't launch Vanguard through IS at the moment. Since it autoupdates, it is current as of this morning.

The Problem:

Today while I was playing, I crashed to desktop (common with VG) and tried to reload. I noticed IS had crashed as well and relaunched it. It proceeded to update itself. After the update was finished I tried to launch Vanguard via IS as I normally do. It launchs the launcher, asks for my login info, everything works fine until I press PLAY and get the splash screen that signifies the game is loading. My system just hangs up at this point. I can move my cursor, but I can't access anything else.

If I load Vanguard normally, it works fine.

I have tried a file scan, I have tried clearing my bin and cache files in VG, I have tried adware / registry scan. This seems to be a problem directly linked to todays IS patch. While in IRC, it seemed a few other people had logged in and complained of a similar issue.

I can provide any further information which you may think is helpful.

[misagh]

For me, it looks related to audio. When I disable audio in the game through vgclient.ini, it loads up fine. Then the second I enable audio through the settings interface in the game, it crashes with the same data. I've reported the crash data through the Innerspace report method.

Hope this gets fixed soon, I need sound and Innerspace working together!

-Xavik

Tried this, I can verify this is a valid workaround atm.

[Spritzen]

I'm getting the same problem. Everything was working yesterday on my Windows 2000 pro sp4 box. Innerspace patched today and now I get the following 2 errors:

The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.

The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "read". Click OK to terminate the program

Thanks[/img]

Yup this is happening to me!

[Lax]

I'm waiting around for my vanguard client to finish patching up, then I can hopefully fix this problem.

[Xavik]

I run Innerspace with two desktops and one laptop. The above issue I'm having with sound enabled is ONLY a problem on one dekstop. Doesn't appear to be a problem on the second desktop OR the laptop, which are running similar VG configurations. Not sure if this matters or not, but the sound cards on these systems are:

Desktop 1: Soundblaster X-Fi (cannot run Innerspace with sound enabled)
Desktop 2: Soundblaster Audigy w(runs no problem)
Laptop 1: Software Soundblaster Audigy 2 (runs no problem)

Here are the registers indicated in the crash message:

Software: Inner Space Session 1.09 (Sat Jul 28 04:49:26 2007)
Crash: 0x00003844: Exception 0xc0000005 reading from address 0x00003844

Registers:
-----------------------------------
eax=00003844 ebx=07E3897D ecx=0326D950 edx=040320CB
edi=00000014 esi=07EB0000 ebp=0012CBC0 esp=0012C97C

[Lax]

Fixed. Inner Space build 4505 is now live, restart Inner Space to patch up.

[Xavik]

Thanks Lax - running like a champ now.

[degas]

using 4505

still crashing

fired off the error report.

[Weizen]

Mine is doing the same thing. Crashing after the splash screen for Vanguard. It worked until the patch yesterday.

Weizen