IS crashes vanguard

wyal · Post by **wyal** » Thu Mar 22, 2007 4:14 pm

ok when ever I try too use IS to lanch VG it crashish at the loading screan if I just run the game normly everything works fine... but then I cant use IS lol

can anyone give me some help or advice? iv looked through the fourms and dident find anything that helped.

Post by **Lax** » Thu Mar 22, 2007 4:25 pm

Are you loading any extensions? If so, have you tried without them? When the game crashes, does it produce a Lavish crash report? If so, why haven't you clicked send?

Otherwise, make sure you have the latest drivers for your video card. If that's not it, then if you could open the uplink's console window (select Console from the IS menu) and type "diag" and hit enter, it'll open up some info in notepad. If you paste that here or send it to me in email (lax@lavishsoft.com) I may be able to gather better information to help you

wyal · Post by **wyal** » Thu Mar 22, 2007 4:31 pm

Inner Space Kernel 1.09 Build 4402

System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.061219-0316
Process Memory Usage: 15MB
System Physical RAM: 459/1021MB
Page File: 1779/2516MB
Virtual Memory: 1978/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 3.00GHz @ 3000MHz
CPU 2: Intel(R) Pentium(R) 4 CPU 3.00GHz @ 3000MHz
CPU Affinity Mask: 0x3
Video 1: \\.\DISPLAY1/RADEON X700 Series
Video 2: \\.\DISPLAY2/RADEON X700 Series Secondary
Video 3: \\.\DISPLAYV1/NetMeeting driver
Video 4: \\.\DISPLAYV2/RDPDD Chained DD
Sound: ?
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180

Loaded Modules:
-----------------------------------
Module 0x00400000-0x00458000: C:\Program Files\InnerSpace\InnerSpace.exe (Thu Mar 22 01:38:00 2007)
Module 0x00D80000-0x00FE0000: C:\WINDOWS\system32\d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x01470000-0x0148D000: C:\Program Files\InnerSpace\IS-D3D9Engine.dll (Sun Mar 18 20:23:02 2007)
Module 0x018B0000-0x018E8000: C:\Program Files\InnerSpace\IS-VirtualInput.dll (Wed Mar 14 00:47:05 2007)
Module 0x03000000-0x0315A000: C:\Program Files\InnerSpace\IS-Kernel.dll (Thu Mar 22 01:37:54 2007)
Module 0x05000000-0x0513D000: C:\Program Files\InnerSpace\ISUI.dll (Wed Mar 21 17:47:09 2007)
Module 0x0FFD0000-0x0FFF8000: C:\WINDOWS\system32\rsaenh.dll (Wed Jul 07 02:17:12 2004)
Module 0x10000000-0x1001E000: C:\Program Files\InnerSpace\Lavish.dll (Mon Feb 12 18:14:02 2007)
Module 0x11C70000-0x11CA9000: C:\WINDOWS\system32\WMASF.DLL (Thu Oct 19 05:47:23 2006)
Module 0x15110000-0x1536A000: C:\WINDOWS\system32\WMVCore.dll (Thu Oct 19 05:48:18 2006)
Module 0x1C000000-0x1C006000: C:\WINDOWS\HKNTDLL.dll (Mon Jul 02 12:36:29 2001)
Module 0x24000000-0x24007000: C:\PROGRA~1\ZONELA~1\ZONEAL~1\MAILFR~1\mlfhook.dll (Thu Jan 11 02:35:46 2007)
Module 0x4FDD0000-0x4FF76000: C:\WINDOWS\system32\d3d9.dll (Wed Aug 04 07:56:03 2004)
Module 0x5AD70000-0x5ADA8000: C:\WINDOWS\system32\uxtheme.dll (Wed Aug 04 07:56:43 2004)
Module 0x5D090000-0x5D12A000: C:\WINDOWS\system32\COMCTL32.dll (Fri Aug 25 15:45:58 2006)
Module 0x605D0000-0x605D9000: C:\WINDOWS\system32\mslbui.dll (Wed Aug 04 07:58:39 2004)
Module 0x60610000-0x60616000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\fusion.dll (Fri Sep 23 07:13:18 2005)
Module 0x662B0000-0x66308000: C:\WINDOWS\system32\hnetcfg.dll (Wed Aug 04 07:56:16 2004)
Module 0x688F0000-0x688F9000: C:\WINDOWS\system32\HID.DLL (Wed Aug 04 07:56:12 2004)
Module 0x6CE10000-0x6CE48000: C:\WINDOWS\system32\DINPUT8.dll (Wed Aug 04 07:56:32 2004)
Module 0x6D990000-0x6D996000: C:\WINDOWS\system32\d3d8thk.dll (Wed Aug 04 07:56:02 2004)
Module 0x71A50000-0x71A8F000: C:\WINDOWS\system32\mswsock.dll (Wed Aug 04 07:59:20 2004)
Module 0x71A90000-0x71A98000: C:\WINDOWS\System32\wshtcpip.dll (Wed Aug 04 07:57:49 2004)
Module 0x71AA0000-0x71AA8000: C:\WINDOWS\system32\WS2HELP.dll (Wed Aug 04 07:57:39 2004)
Module 0x71AB0000-0x71AC7000: C:\WINDOWS\system32\WS2_32.dll (Wed Aug 04 07:57:38 2004)
Module 0x74720000-0x7476B000: C:\WINDOWS\system32\MSCTF.dll (Wed Aug 04 07:57:30 2004)
Module 0x74D90000-0x74DFB000: C:\WINDOWS\system32\usp10.dll (Wed Aug 04 07:56:42 2004)
Module 0x76380000-0x76385000: C:\WINDOWS\system32\MSIMG32.dll (Wed Aug 04 07:58:31 2004)
Module 0x763B0000-0x763F9000: C:\WINDOWS\system32\comdlg32.dll (Wed Aug 04 07:56:32 2004)
Module 0x76B40000-0x76B6D000: C:\WINDOWS\system32\WINMM.dll (Wed Aug 04 07:57:10 2004)
Module 0x76BF0000-0x76BFB000: C:\WINDOWS\system32\PSAPI.DLL (Wed Aug 04 07:56:58 2004)
Module 0x76C30000-0x76C5E000: C:\WINDOWS\system32\WINTRUST.dll (Wed Aug 04 07:56:41 2004)
Module 0x76C90000-0x76CB8000: C:\WINDOWS\system32\IMAGEHLP.dll (Wed Aug 04 07:56:25 2004)
Module 0x76D60000-0x76D79000: C:\WINDOWS\system32\iphlpapi.dll (Fri May 19 12:59:41 2006)
Module 0x76F20000-0x76F47000: C:\WINDOWS\system32\DNSAPI.dll (Mon Jun 26 17:37:10 2006)
Module 0x76F60000-0x76F8C000: C:\WINDOWS\system32\WLDAP32.dll (Wed Aug 04 07:56:43 2004)
Module 0x76FB0000-0x76FB8000: C:\WINDOWS\System32\winrnr.dll (Wed Aug 04 07:56:35 2004)
Module 0x76FC0000-0x76FC6000: C:\WINDOWS\system32\rasadhlp.dll (Mon Jun 26 17:37:10 2006)
Module 0x77120000-0x771AC000: C:\WINDOWS\system32\OLEAUT32.dll (Wed Aug 04 07:57:39 2004)
Module 0x773D0000-0x774D3000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll (Fri Aug 25 15:45:55 2006)
Module 0x774E0000-0x7761D000: C:\WINDOWS\system32\ole32.dll (Tue Jul 26 04:39:47 2005)
Module 0x77920000-0x77A13000: C:\WINDOWS\system32\SETUPAPI.dll (Wed Aug 04 07:56:32 2004)
Module 0x77A80000-0x77B14000: C:\WINDOWS\system32\CRYPT32.dll (Wed Aug 04 07:56:01 2004)
Module 0x77B20000-0x77B32000: C:\WINDOWS\system32\MSASN1.dll (Wed Aug 04 07:57:23 2004)
Module 0x77C00000-0x77C08000: C:\WINDOWS\system32\VERSION.dll (Wed Aug 04 07:56:39 2004)
Module 0x77C10000-0x77C68000: C:\WINDOWS\system32\msvcrt.dll (Wed Aug 04 07:59:14 2004)
Module 0x77D40000-0x77DD0000: C:\WINDOWS\system32\USER32.dll (Wed Mar 02 18:09:29 2005)
Module 0x77DD0000-0x77E6B000: C:\WINDOWS\system32\ADVAPI32.dll (Wed Aug 04 07:56:23 2004)
Module 0x77E70000-0x77F01000: C:\WINDOWS\system32\RPCRT4.dll (Wed Aug 04 07:56:30 2004)
Module 0x77F10000-0x77F57000: C:\WINDOWS\system32\GDI32.dll (Thu Dec 29 02:54:35 2005)
Module 0x77F60000-0x77FD6000: C:\WINDOWS\system32\SHLWAPI.dll (Thu Jan 04 14:05:30 2007)
Module 0x78130000-0x781CB000: C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_0de06acd\MSVCR80.dll (Fri Sep 23 06:44:37 2005)
Module 0x79000000-0x79045000: C:\WINDOWS\system32\mscoree.dll (Fri Sep 23 11:30:38 2005)
Module 0x79E70000-0x7A3D1000: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll (Fri Sep 23 11:33:00 2005)
Module 0x7C800000-0x7C8F4000: C:\WINDOWS\system32\kernel32.dll (Wed Jul 05 10:55:00 2006)
Module 0x7C900000-0x7C9B0000: C:\WINDOWS\system32\ntdll.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C9C0000-0x7D1D5000: C:\WINDOWS\system32\SHELL32.dll (Tue Dec 19 21:52:11 2006)

Display
-------------------------------------
Adapter resolution: 1280x960
Current display mode: 792x566 (windowed)
Window viewable size: 792x566
Display Scale: 100.0%x100.0%, Distortion: 0.0%
MaxFPS Foreground: Disabled
MaxFPS Background: Disabled

wyal · Post by **wyal** » Thu Mar 22, 2007 4:35 pm

As far as I know im not loading any extensions, just using the defalt one that was autodet, when it crashes it just gives me the message Lp_plugin and vanguard.exe perormeed a illagle action and will now close

IS dosent seam to notice this or isent setup right on my side to create a crash report but then again IS dosent crash

btw I tryed uninstalling and then reinstalling IS same thing

wyal · Post by **wyal** » Thu Mar 22, 2007 4:36 pm

humm something new now il also getting error -114 when I try to log in IS

wyal · Post by **wyal** » Thu Mar 22, 2007 4:42 pm

scrach that last one its letting me log in again.

iv got the win files from when vg crashed would thay be of any help?

AppName: vgclient.exe AppVer: 1.0.0.1780 ModName: kernel32.dll
ModVer: 5.1.2600.2945 Offset: 000edf9c

AppName: launchpad.exe AppVer: 0.0.0.0 ModName: kernel32.dll
ModVer: 5.1.2600.2945 Offset: 000edf9c

iv also got the 30 page long file reports that were creatted to be sent to microsoft if thay would help.

Post by **Lax** » Thu Mar 22, 2007 5:34 pm

ok, a few things.

1. Try shutting down running programs to determine if any of them are interfering. For example, Zone Alarm, Norton Internet Security, and so on.
2. Make sure DEP is not enabled system-wide. System control panel, Advanced tab, Performance settings, Data Execution Prevention tab. The first option should be checked -- "Turn on DEP for essential Windows programs and services only". If the second option ("except those I select") is checked, add exceptions for Inner Space and vanguard (launcher too)

wyal · Post by **wyal** » Thu Mar 22, 2007 5:57 pm

ok ill try that but vanguard runs with out IS with no problems.

wyal · Post by **wyal** » Thu Mar 22, 2007 6:01 pm

ok did all that

"Turn on DEP for essential Windows programs and services only"
was the olny one on so I checked the 2nd option and added is the lancher and vg

no difrance even turnned off everything I dident need to be on line and it is still doing the same thing any thoughts?

wyal · Post by **wyal** » Sat Mar 24, 2007 9:04 am

not sure what happend(eather your super mad skills my by insane butten clicking) but it seams to work now... Thx mate for the super support and advice.

wyal · Post by **wyal** » Sat Mar 24, 2007 9:08 pm

ok i know your getting sick of me (well I am but thats becouse iv got the flu now lol any way) but im having problems again with IS crashing VG i dubbled checked and all the settings are the same as before the 2nd option is enabled that allows all programs for the DEP and iv closed everything that isent needed to run windows and my connection

IS isent crashing its self but somehow its makeing the vangard.exe unstable heres what I got from the bug report.

AppName: vanguard.exe AppVer: 1.0.0.1 ModName: kernel32.dll
ModVer: 5.1.2600.2945 Offset: 000edf9c

wyal · Post by **wyal** » Sun Mar 25, 2007 8:58 am

not sure why but if I keep trying to lanch vg with is it crashes about 10-13 times in a row then it will work... any reasion for this?

Post by **Lax** » Sun Mar 25, 2007 11:53 am

Vanguard itself is unstable, as far as I can tell. I had to stop setting the default exception handler in the program, because I kept getting Lavish crash reports whenever Vanguard crashes. Unfortunately, no I have no idea why it's crashing for you. What I do know is that it works for everyone else including myself, so it's got to be something installed on your PC. Alternatively, it could be something NOT installed, such as critical windows updates.

wyal · Post by **wyal** » Sun Mar 25, 2007 2:37 pm

could be a windows update il gonna check it out and see if im lacking anything.

like I said it works but olny about 23% of the time lol o well ill just keep running it till it clicks.