Crash Thread...

[rhohltjr]

Originally posted by Erik Rutins
We are still monitoring everything. Information confinues to be gathered and 1.2 is still on track as a bug-fixing (particularly crash-fixing release).

Regards,

- Erik

[Nixuebrig]

Originally posted by Erik Rutins
We are still monitoring everything. Information confinues to be gathered and 1.2 is still on track as a bug-fixing (particularly crash-fixing release).

Keep posting relevant info here if you still have crashes after updating to v1.11. Everyone who has already sent me or another Matrix staff person a save, no need to worry. We'll be in touch if we need more info.

Regards,

- Erik

games works fine at my PC, except for P39s strafing my bases on New Guinea. The message is: .50 Browning hits, belt armor penetration and Crash. Guess the strafing is the reason for my crashes.

[AP514]

Hey
Well, I guess im not out of the woods yet. Crashed again today......Im sure it has to do with my mouse.......every time I have crashed is when my mouse is moving. I have a Logitech Optical mouse that is supposed to be USB but Im usung a Ps2 adapter. After each Crash besides the Dfix Windows runs I MUST defrgg or the game locks up 100% of the time.
I really like this game BUt it is testing my limits........Also the PBEM game is taking a hit bue to all the Crash delays.


HELP US PLEASE......................

[AP514]

Hey
I forgot to say when the game crashes 100% of the time after it crashes the first time is right at the start up.....Cd starts to spin and screen goes blk with an hour glass.........thats is the next thing that hppens when game starts is you see the loading screen.......I hope this helps

If a fix does not come soon I will have to put another MATRIX game into the TRASH...............Matrix you guys are on your last chance with me.

AP514

[Erik Rutins]

For those of you still experiencing crashes, monitoring your system activity (CPU, Memory Usage) is definitely helpful in knowing what might be going on.

Also, if you started experiencing crashes in 1.10 or 1.11, by all means uninstall and return to 1.00 for the time being to see if that helps. If you suspect a particular peripheral could be responsible, try unhooking it or temporarily hooking up a more standard substitute peripheral to see if the game gets along with it any better.

If you have a friend with some time and interest, bring your copy over there and give it a shot to make sure that your CD and/or the patch file you downloaded have not in some way been corrupted.

In the meantime, please be patient, we know it's frustrating. We're moving as fast as we can - you are the main mission for v1.2, fixing all remaining crash bugs and other key bugs we can find.

Regards,

- Erik

[ladner]

Erik,

May not be the best board ettiquette but I'm finally out of the woods with crash bug. It was necessary to download all new drivers. One driver in particular seemed to be the fix, if I can recall which device I will edit my post to pass that info on to others. Thanks for the support.

I've been derelict in updating this sorry guys.

I updated all of the drivers on my PC starting with the usual culprits the sound and video drivers. For sound driver I already had the most current driver for the SBLive Value, video I upgraded to the NVDIA Detonator driver, which covers multiple devices mine is GeForce2 Ultra. Initially I figured these are the usual suspects so no worries, wrong the game continued to crash. So after reading Erik's Crash FAQ I went through the process again and at least from my experience the "magic bullet" for my system was the VIA 4in1 driver. Since, I've made the updates the game has not crashed a single time. I strongly urge those who are still experiencing the crash bug to update all of the drivers, which I know is a pain.

[Erik Rutins]

Greg,

Good news! I'm very interested to hear which drivers you updated and what versions you updated to. If you know which specific driver helped you out, that would be very valuable.

Regards,

- Erik

[Sparadicus]

I am having similar problems as gfish22, except when mine locks up, the sound does not continue playing. In fact, it's the opposite. The first thing that happens to me is a sound effect stalls on it's first tone and continues on this single tone until I reboot (ussually having to hit the reset button). I usually can only play 2 to 4 turns before a crash. Also, when I am able to complete a game (using multiple reboots and saves) it ALWAYS locks up the same way when I try and launch a second scenario. Right when I hit the start scenario button (with the soild tone of the bell resulting).

My sound card is a Yamaha XG 64V and yes, I have the latest DirectX driver installed. I am a hard core gamer, playing numerous titles, and do not currently have crash problems with any other game.

Other system info - Pent III 500 Mhz, 128 SDRAM, 32 MB Diamond Viper V770D

I have been waiting a long time for this game. In my younger years, I played countless hours of the board game "Flattop" and the old PC game "Carrier Strike". I had high hopes that this would be the game I've been waiting for, and believe it will be, IF IT STOPS CRASHING. Please help.

[Nixuebrig]

Originally posted by Erik Rutins
Greg,

Good news! I'm very interested to hear which drivers you updated and what versions you updated to. If you know which specific driver helped you out, that would be very valuable.

Regards,

- Erik

Unisntalled Direct X with Direct X Buster and Installed 8.1 new.

The only crash that occurs now are the P39s strafing. Starting Scen 17 i got the message Akagi hit by Browning and game runs on, but in an PBEM game starting in August(A hard road ahead) the message is Browning hits Belt armor(without a ship name) and then the game crashes. Guess it has something to do with the database, In scen 17 akagi is ship nr 1 in scen14 slot 1 for the ships is empty. I am sure that causes the crash.

Greg

[Reiryc]

Originally posted by Sparadicus
I am having similar problems as gfish22, except when mine locks up, the sound does not continue playing. In fact, it's the opposite. The first thing that happens to me is a sound effect stalls on it's first tone and continues on this single tone until I reboot (ussually having to hit the reset button). I usually can only play 2 to 4 turns before a crash. Also, when I am able to complete a game (using multiple reboots and saves) it ALWAYS locks up the same way when I try and launch a second scenario. Right when I hit the start scenario button (with the soild tone of the bell resulting).

My sound card is a Yamaha XG 64V and yes, I have the latest DirectX driver installed. I am a hard core gamer, playing numerous titles, and do not currently have crash problems with any other game.

Other system info - Pent III 500 Mhz, 128 SDRAM, 32 MB Diamond Viper V770D

I have been waiting a long time for this game. In my younger years, I played countless hours of the board game "Flattop" and the old PC game "Carrier Strike". I had high hopes that this would be the game I've been waiting for, and believe it will be, IF IT STOPS CRASHING. Please help.

Try turning off all sounds in the game to see if you still crash.

Also go out and get the latest sound driver for your sound card, that may be the problem area.

Reiryc

[elmo3]

Just had my first crash with 1.11 while strafing an airbase. Saw a combat message about "belt armor" just before the crash. I don't think there were any ships parked at the airbase. No save game as it was turn 1.

I was playing on a Dell Optiplex GX110 with 128MB RAM and an old NVIDIA TNT2 M64 and DirectX 8.1.

[elmo3]

Originally posted by elmo3
Just had my first crash with 1.11 and playing green Hell head to head while strafing the Buna airbase. Saw a combat message about "belt armor" just before the crash. I don't think there were any ships parked at the airbase. No save game as it was turn 1.

I was playing on a Dell Optiplex GX110 with 128MB RAM and an old NVIDIA TNT2 M64 and DirectX 8.1.

[Nixuebrig]

Originally posted by elmo3
Just had my first crash with 1.11 while strafing an airbase. Saw a combat message about "belt armor" just before the crash. I don't think there were any ships parked at the airbase. No save game as it was turn 1.

I was playing on a Dell Optiplex GX110 with 128MB RAM and an old NVIDIA TNT2 M64 and DirectX 8.1.

Is it one of the later scenarios? If so, just put a AP or and SC in slot one, then the crashing stops and the ship you assigne in slot One will be hit. In the earlier scens Akagi (i think) is in slot one, so she will always be strafed. but in the later scens there is no ship in slot 1 so it will crash.

Never looked if the ship really gets damaged.

[willgamer]

Continuing to ctd after installing 1.2. In my case it's always on a left click to select after about 1 1/2 to 2 hours of play (5-6 turns). Playing solo Yamamatos Prophecy.

My machine:
Athlon 800 on Asus K7V mb; 512MB ram; 300MB virtual (fixed)
Creative Graphics Blaster Riva TNT video w/16MB
Soundblaster Live value edition

Win98se; starts w/ systray, explorer, poproxy only
DX8.1

Afaik current drivers.... most haven't changed in over a year...

Anything else I can add?

[Erik Rutins]

Everyone still experiencing crashes, please try to duplicate your crashes with a fresh install of v1.20 and using only games that have been started under v1.20, since we fixed some OOB glitches that could theoretically cause crash behavior.

If you are still experiencing crashes after re-checking as described above and have gone through the FAQ, please post here to confirm. The absolute top of the next patch list is entirely filled with the crash bugs that have been reported, but some of these remain very difficult to track down.

Anyone who can send us a save file that causes a repeatable crash with a game started in v1.20 will get a big thank you. We do have all the saves already sent and they have been cataloged and tests have been run. I have been able to duplicate some crashes here after running through multiple of these saves in one session. Mike has not been able to get them to crash on his computer though, so more saves are much appreciated.

As far as I can tell, for some folks strafing contains some sort of crash catalyst as does zooming and scrolling the map. If you are having crashes and can avoid using these methods to see if it improves stability, a report would be appreciated.

Many folks have posted or e-mailed reporting that driver updates did clear up their crash problems. This is always the first thing to check, as recommended in the FAQ. In the case of folks with TNT or GeForce cards, there are almost always newer drivers available from nVidia. Don't go to your card vendor's site, instead go to nVidia's site and get the latest reference drivers. If you are brave, you can also try one of the sites listed in the FAQ to try even more recent beta drivers (the majority of which work just as well as the non-beta drivers).

Since sound drivers are such a prevalent problem, also make sure you try disabling your sound card and seeing if that improves stability. Any and all such insight that you can give us into what might be the specific cause for your system will only help us get your UV working smoothly. I know I've been over this ground before, but it bears reminding because of the continued success stories we hear.

We also hear of good results from folks running the more stable Microsoft OSes like Windows 2000 or Windows XP. Windows 98 / ME are much more testy when it comes to bad drivers, hardware glitches or memory leaks in the program.

Ultimately, there will be some crash situations that can't be fixed and that most likely indicate a system problem. However, we will continue to diligently approach every crash problem as potentially UV's problem and as potentially fixable.

Regards,

- Erik

[Erik Rutins]

Willgamer,

Thanks for the report, was this with a game started in v1.20?

If you haven't updated drivers in a year, there should be newer drivers for you motherboard chipset, sound card and graphics card. Check the FAQ and your vendor/chipset manufacturer's sites for the best selection of new drivers.

Regards,

- Erik

[willgamer]

Erik,

The game was started under 1.11.

After checking, the drivers all seem to be up to date.

The only other thing that I can relate is that I can sometimes anticipate the ctd is coming soon when the background music cuts out briefly then returns (perhaps sounding just a little "off").

The game always restarts just fine and never ctds on the restarted turn.

Bill

[willgamer]

O'k, I started a new game (#17) under 1.2 and played straight through to the 5/15 turn. At that point, I ctd on my first left click to select something after the new turn weather message.

[Sparadicus]

I have finally been able to stop the sound related crashes and it was by installing a different driver. Unfortunately, it is not technically the correct driver for my sound card and I am now having sound problems in several other titles I play regularly. They are not as severe as the lock up/crashes I was having in UV, but did not occur at all prior to this new driver. UV is playing flawlessly, go figure(??).

The new driver is 'dsxgwdm'
The correct driver for my card (I believe) is 'Yamaha_dsxg_driver'.

My card is a Yamaha XG 64V Wavetable Sound

I just updated to v1.20, but will keep the new driver for now, as it doesn't appear v1.20 addressed any of the crash issues. Hopefully I'll be able to switch back after the next patch.

Thanks,
REB

[fabius]

I wasn't getting any crashes with 1.11, but I am getting them with 1.2. I have a game that I started in 1.2 that consistently crashes in the same place, if you'd like me to send you the saved game file.

My system:

Win95
Pentium 500
128 RAM
GeForce II mx 400
Soundblaster Live value

I updated the sound and video drivers, did a clean reinstall of the game and the 1.2 update (didn't start a new game, though). I defragged and manually set virtual memory at over three times RAM. I disabled the sound card. Always crashes at the same place.