Crashing on Vanguard consistently =(

Discussion of Inner Space

Moderators: Lavish Software Team, Moderators

Post Reply
bohicaseti
GamingTools Subscriber
Posts: 3
Joined: Wed Jun 29, 2005 12:22 pm

Crashing on Vanguard consistently =(

Post by bohicaseti » Sun May 13, 2007 8:43 pm

I have always crashed several times a day since I started to use InnerSpace & the ISXVG plugin a few months ago. Usually its only about once every hour or 2 and it was tolerable. My system specs are a Dual Opteron 270 (dual cores) , 4 gig RAM, 2x GeForce 7950's in SLI mode (have also tried without SLI mode), 4x raptors in RAID & the Tyan S2895 Thunder K8WE Motherboard. As far as Operating System, I get the same results in XP 32-bit, XP-64bit, & Vista 32bit (never bothered to install 64bit Vista as the 32bit was hellish enough). I know it's not the ISXVG plugin as I will get the crash without it loaded but just having Innerspace going. Under Win XP it kicks me to desktop and freezes everything but my mouse. I have to hit reset and hardboot back up. In Vista it CTD's but the OS is still stable and I don't need to reset. I have tried multiple sets of drivers for my chipsets and a plethera of different graphics drivers with the same results. I have even flashed my BIOS to an older version just in case. There are occasionally times where I can go up to 3 hours without a crash but rarely. But after the InnerSpace patch today I seem to crash about every 10-20 minutes and I'm at a loss of what to do to try and fix it or even lessen the frequency of crashes. If I run the game by itself and no InnerSpace launcher, the games stays up and running for hours with no issue. I'm sure this has to do with my odd set of hardware, but I can't win this fight on my own it seems. Do you have any suggestions ? Thanks :?

eqjoe
GamingTools Subscriber
Posts: 221
Joined: Wed Oct 13, 2004 2:34 pm

Post by eqjoe » Tue May 29, 2007 2:14 pm

I don't have those problems on any of my systems. I am running XP x32, XP x64 and Vista x64.

Are you getting any kind of crash dump?

-j

eqjoe
GamingTools Subscriber
Posts: 221
Joined: Wed Oct 13, 2004 2:34 pm

Post by eqjoe » Tue May 29, 2007 2:15 pm

I should add that I have a SLI dual 7950 setup as well. Using an Abit AN8 5000+ dual core with 4 Gigs of Ram.

-j

bohicaseti
GamingTools Subscriber
Posts: 3
Joined: Wed Jun 29, 2005 12:22 pm

Post by bohicaseti » Wed May 30, 2007 3:51 pm

I don't get any kind of crash dump. I just get blinked to a desktop and I can move my mouse and that is it. Nothing else works. CTRL-ALT-DEL doesn't even do anything. I can't seem to do something in game to replicate it on purpose either. I've loaded up the game and then just sat there watching the chat go by while searching the broker (without the ISXVG plugin loaded) and had it crash/freeze to desktop. I thought maybe it had something to do with video memory so I used a flush script to make sure I wasn't getting bogged down that way and forcing a crash but it does it then also. I've just grown accustomed to having to hit RESET around once every hour or 2 and bringing the system back up. Tried multiple BIOS's, chipset drivers & video card drivers with the same result. I'm not sure if this is an AMD Opteron CPU issue or not, it seems to be the only thing that makes a link to all possible scenarios that I have.

tms
Non-Subscriber
Posts: 3
Joined: Tue Aug 16, 2005 4:14 pm

Post by tms » Sat Jun 02, 2007 3:20 am

My system with ISXVG + Innerspace dont crash, but if i alt-tab in fullscreenmode to the desktop Vanguard do crash, so i have to strg-alt-del and kill it.

and this work every time, if i play in windowed mode it work. In fullscreen = crash if switching to desktop. It's a bit annoying.

bohicaseti
GamingTools Subscriber
Posts: 3
Joined: Wed Jun 29, 2005 12:22 pm

Post by bohicaseti » Sun Jun 03, 2007 10:18 pm

Yea, I keep it in windowed mode at all times. Have since about a week after using innerspace. Just makes things easier in the end. Not sure what my issue is, but today alone, I have crashed at least a 8 times in a 6 hour period. I can only attribute it to either Opteron processors or chipset drivers. Considering it happends on XP Home, XP Pro 32bit, XP Pro 64bit, Vista Business 32bit & Vista Business 64bit, I'm throwing this one at the Opteron Processor. I can find no other common denominator in the equation. Either that or it's God, but I'm agnostic so that's out of the question to. :P

Post Reply