MegaGlest Forum

Archives (read only) => Vanilla Glest => Bug report => Topic started by: Tom on 25 September 2004, 09:24:40

Title: Glest crashes on WinXP (Radeon Cards) (fixed on 1.1.0-rc1)
Post by: Tom on 25 September 2004, 09:24:40: Glest version 1.0.1 crashes on WinXP SP1 after some time playing the game. I've noticed this effect on former versions of Glest as well.

Start it: fine.
Start a new game: fine.
Play for app. 10 minutes: you get an error and the game crashes.

Either by displaying a WinXP popup window saying "access violation in module XYZ". Or a Glest error message pops up. It seems, Glest is unable to access a spec. memory location.

This looks like some kind of null pointer error to me (just my 2 cents).

Since this is a permanent error, I'm unable to play Glest 1.0.1.
Title:
Post by: martiño on 25 September 2004, 17:46:29: I also have WinXP SP1 and I had no problems, please send us the crash.txt file in glest folder.
Title:
Post by: Tom on 25 September 2004, 20:33:34: Here it is:

Crash
Version: v1.0.1
Time: Sat Sep 25 21:20:47 2004
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

Still I'm not sure if it is of use. This message isn't into too much detail, is it?
Title:
Post by: martiño on 25 September 2004, 20:37:00: Yes it's usefull because it tells me the address of the crash. If I'm lucky it may give me enough info to solve it.
Title:
Post by: martiño on 25 September 2004, 20:58:42: one more question, can you tell me what video card and sound card do you have?
Title:
Post by: Tom on 25 September 2004, 21:13:12: Well, I run a ATI Radeon 9600 card with the latest Catalyst 4.6 driver, Direct X 9.0b and Creative Soundblaster Live.
Title:
Post by: Antastan on 26 September 2004, 15:53:27: same crashes happen to me too at winxp sp1 :(

crash.txt:
Crash
Version: v1.0.1
Time: Sun Sep 26 17:41:43 2004
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

i'm using a radeon 9600xt and an athlon 64bit +3200. soundcard is a creative soundblaster 128
Title:
Post by: Tom on 26 September 2004, 21:57:43: Oh, this is the same error and even the same ATI graphics card, same OS and a similar sound card.

So at least: I'm not the only one experiencing this problem. ;)
Title: error 0x84c1!!
Post by: Lt.Rochus on 5 October 2004, 17:41:14: I downloaded Glest yesterday and I played about ten minutes also. My OS is WinXP and My VideoCard is 9600 ATi with the lastest drivers. I am also experiencing the crash. I believe it is the same error as 0x84c1 or something like that. I not sure because I'm at school and I didn't bring the error file.
Title:
Post by: martiño on 5 October 2004, 18:22:08: All the cards are radeon cards. Strange. We will investigate...
Title:
Post by: Lt.Rochus on 6 October 2004, 16:06:50: Here is the crash file.

Crash
Version: v1.0.1
Time: Mon Oct 04 23:24:50 2004
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

Crash
Version: v1.0.1
Time: Mon Oct 04 23:36:12 2004
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

Here is what I have:

Hewlett-Packard Pavilion m370n
Windows XP Media
Pentium 4 CPU 2.8 GHz
1 GB of RAM
Radeon 9600 Driver Date 6/10/2004 Version 6.14.10.6458
Title:
Post by: Lt.Rochus on 7 October 2004, 05:25:24: I just found out that there is a new driver version for ATi 9600 (Version: 6.14.10.6476)

I can't try it out now because it would take me all night to download, so I will install the new driver tomorrow and see if that helps. Good nite.
Title: ATi 9600 Driver Updated
Post by: Lt.Rochus on 10 October 2004, 06:37:35: I updated the drivers for my 9600 Radeon and the new drivers did not correct problem.
Title:
Post by: BombTrack on 15 October 2004, 12:17:18: hi,

i have a similar problem on two different xpsp1 machines.
crash to desktop after 10 min. without! error message.

machine 1: athlon xp3000 - radeon 9700pro - ati catalyst 4.9 - c-media ac97 onboard sound
machine 2: p4 northwood 3.4ghz - radeon x800pro - ati catalyst 4.9 - sb audigy player
Title:
Post by: martiño on 15 October 2004, 19:45:33: We have been investigating and we think that this is a problem of catalyst drivers, soon we will post a list of drivers versions that work ok with the game.
Title:
Post by: martiño on 28 October 2004, 19:04:33: Radeon cards again, there must be some buggy radeon driver version around there, because two of us (tucho and enveloop) have also radeon cards and the game never crashed.

Please tucho, post here the driver version that worked ok with glest.
Title:
Post by: tucho on 28 October 2004, 21:21:51: If I remember rightly, the driver version is Catalyst 3.7

download here (http://http://www.ati.com/support/products/radeonwin2kpreviousdrivers.html)
Title:
Post by: enveloop on 29 October 2004, 17:12:50: I believe my driver is 4.4, and the game runs with no problem; however I remebered that some time ago I downloaded a newer version and it gave me some trouble (the resources didnÂ´t show up in the screen for instance) so I went back to this one. Anyway, tucho plays very often and for long periods of time so you may test his driver first.
Title: Glest 1.06 crashed again
Post by: Lt.Rochus on 3 November 2004, 06:29:56: Goat smelling, tittie sagging, viagra using, loser of a video card.
My game crashed when I was having so much fun.

My crash details:

Crash
Version: v1.0.6
Time: Tue Nov 02 22:19:14 2004
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1
Title: To Panda
Post by: Lt.Rochus on 7 November 2004, 00:51:52: :D Thanks Panda, I followed your advice and Qlest 1.06 has not crashed on me since.

Are you a programmer Panda?
Title:
Post by: martiño on 7 November 2004, 01:24:47: So this has to be something related with night lighting, I will try to debug it but it will be quite difficult sonce I dont have a radeon card to test it,. enveloop, can you try downloading those drivers (4.1) and testing if it crashes?
Title:
Post by: martiño on 7 November 2004, 01:59:26: Anyone of you can enable debug mode (in glest.ini) and send me a secreen of the game just in the moment of the crash?
Title:
Post by: martiño on 7 November 2004, 16:19:50: Can anyone also try disabling shadows and checking if the game still crashes?
Title:
Post by: tucho on 22 March 2005, 04:01:30: do you have some crash.txt file in the glest directory?

Anyway Martin-o is still away, and he is who can know the reason of the crash...
Title: -
Post by: gattschardo on 12 April 2005, 18:33:37: hello guys, I got the same problem too.

Crash
Version: v1.0.9
Time: Tue Apr 12 16:03:03 2005
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

Crash
Version: v1.0.9
Time: Tue Apr 12 16:11:37 2005
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

Crash
Version: v1.0.9
Time: Tue Apr 12 16:33:54 2005
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

Crash
Version: v1.0.9
Time: Tue Apr 12 18:55:57 2005
Description: Access violation (Reading address 0x84c1)
Address: 0x84c1

I tried it three times, always the same thing. is there no solution?
i got xp with service pack 2 (build 2600) bot a friend of mine (xp, too) doesn't have this problem. i think its really about these radeon cards - i got a 9600SE and he's just using his onboard.

PS: has nothing to do with the day/night change, i tried it.

PPS: i already sent more details to game-^-glest.org, same name
Title: new ati-driver
Post by: gattschardo on 13 April 2005, 13:50:42: i just visited the ati homepage and found out, theres a new driver version: catalyst 5.4 from april 7. i'm just downloading this now, i'll tell you, if this will fix the problem. ->
Title:
Post by: martiño on 13 April 2005, 13:54:42: You wont be able to run Glest until next version with those drivers, since they support opengl 2.0 and the GL version detection stuff in Glest has a bug.
Title:
Post by: gattschardo on 13 April 2005, 13:59:15: so there is yet no other solution to this problem than downloading the old 3.7 driver?
Title:
Post by: martiño on 14 April 2005, 12:51:20: Try this workaround: http://www.glest.org/board/viewtopic.php?t=221 (http://www.glest.org/board/viewtopic.php?t=221)
Title:
Post by: gattschardo on 23 April 2005, 09:15:12: Quote from: "martin-o"
Try this workaround: http://www.glest.org/board/viewtopic.php?t=221 (http://www.glest.org/board/viewtopic.php?t=221)

Well this doesn't work with my card, too, I already tried.
Title:
Post by: martiño on 14 May 2005, 22:33:36: This bug should be fixed in 1.1.0-rc1, using the default configuration.
Title:
Post by: martiño on 22 October 2005, 19:26:25: Good to know that ATi fixed that at last.
Title:
Post by: Butter on 11 March 2006, 22:11:45: Crash
Version: v1.2.2
Time: Sat Mar 11 22:34:51 2006
Description: Access violation (Reading address 0x84c1)
Address: 000084C1

with Ati FireGl 8800 (8.062 driver) on W2k
just updated from v1.1.1
tried everything that iÂ´ve read here
turn everything on,off,high,low....
the game runÂ´s for ca. 10 mins, but i have one game that lasts nearly 20 mins because of loosing 80% of my population under attack.
maybe it has something to do with the count of units in the game.

but itÂ´s a very nice game

greets from germany
Stephan
Title:
Post by: xiro.xiro on 9 November 2006, 16:00:37: It crashes on my system too. I have a Radeon card, of course.

I think I solved it setting the shadows off as Martinho told. Still didn't play for more than 30 minutes, though.

Nice game, I suck at RTS, but I'll do my best cause I like the fantasy ambient! :P Bye!
Title:
Post by: xiro.xiro on 9 November 2006, 20:03:29: I was kidding. Was having fun and the same frakking error occurred:

Crash
Version: v2.0.0
Time: Thu Nov 09 21:00:34 2006
Description: Access violation (Reading address 0x84c1)
Address: 000084C1

Don't know if I have the latest Catalyst drivers... will check it out and report as usual.
Title:
Post by: xiro.xiro on 10 November 2006, 05:08:26: Solved upgrading the drivers.
Title:
Post by: Rilder on 6 October 2007, 02:19:16: Im getting this problem, ATI Radeon, Radeon x1950Pro, Catalyst Version 7.7

Crash
Version: v2.0.1
Time: Fri Oct 05 21:04:07 2007
Description: Access violation (Reading address 0x34)
Address: 7C901010

Happens right when I try and play.

Edit: was a driver issue.
Title:
Post by: superlogan on 3 April 2008, 16:04:49: it also crashes for me! I hope you can fix this cuz I want to play but I cant!
Title: XP Problem :o(
Post by: horusofoz on 21 April 2008, 02:37:31: Im having again what seems to be a very common problem as I use XP SP2 and cant play the game for more than five mins without a crash. I know my pc has the juice to play it and I'm using a Raedon 9600. I can play oblivion, civilization and doom 3 so the graphics power is good enough just the game is screwing up 5 minutes in. The game seems great and reminds a lot of warcraft so I hope yous can fix this bug soon. Cant wait to play and try out some campaigns.

Many thanks for a great game

Horusofoz

(PS sorry for using the wrong lingo but I'm an Aussie that don't know squat about computers)

Cheers
Title:
Post by: hailstone on 21 April 2008, 12:53:57: Welcome to the forum. There seems to be problems with playing Glest on ATI graphics cards. I'm not sure what can be done about it, sorry.
Title: Re: Glest crashes on WinXP (Radeon Cards) (fixed on 1.1.0-rc1)
Post by: horusofoz on 8 December 2008, 05:46:09: Thanks Hailstone. Also good to see an Aussie on the GAE Team : )

Just to confirm it was the Raedon Card as I have since a new PC and have had no trouble with Glest period. Look forward to a campaign/story and maybe another couple factions : )

Thanks
Title: Re: Glest crashes on WinXP (Radeon Cards) (fixed on 1.1.0-rc1)
Post by: Omega on 11 December 2008, 01:44:48: Great, Horusofoz. I don't think it neccessarily is radeon cards in general. I have an ATI Radeon X1200 graphics card with 831MB of graphics memory. Glest works great! It might just be specific (older ?) versions. ATI is a very popular graphics card. I tried glest on my dads NVidia graphics computer, which is a desktop to put my laptop to shame, and to my surprise, it DIDN'T work. Odd that it can work on ATI radeon, which is known to have bugs, but not the Nvidia... Doesn't matter to me, though. He bought a new computer because a lightening strike whiped his motherboard and now his sucky new one looks puny compared to my laptop.

THE BEST SOLUTION TO ATI CRASHES IS TO UPDATE! :D