W:ET keeps crashing! Help!

(Blaster_Jr) #21

Im not saying that i know what it is but i also had this prob before fixed it and it just started reacurring… all i did was uninstalled et(server files will overite et’s original ones if it is a mod server)… so i uninstallled and deleted every folder and item that was there i reinstalled and it was gone but now somthings is jacked up like hell and i dont know what it is i hope this helps any of you.

P.S. i have 2 Wolfenstien E.T.'s installed because i make maps…

3 fans and open case
1.2 amd athalon prosser
N Vidia Geforce 3
A ASUS Motherboard

anything wrong with this?

(=TAC=Chron) #22

If you’re hitting 44c idling with a water cooling system, you need to check the connection between your heat sink and your CPU. Fancy water cooling does nothing if it can’t absorb any heat.RK[/quote]

was getting ready to point out the same thing… :clap:

i mean that is the temp that my 1U server runs under load… :eek3:

(BADASS_SJ) #23

Well, I swapped motherboards and now the cpu is running around 33-34C which is much cooler than before however…the f****** thing still shuts down while playing ET. Sometimes I make it 1-8 maps before it croaks and sometimes it dies twice on the same map.

I also see the check com crashed errors. If I exit and restart they are gone. This is a great game but starting to not be worth the frustration it brings when the comp goes down. All other games work fine and never crash on this system. Any suggestions would be appreciated.

I have swapped the following items to test and it still dies:
motherboard
cpu
ram
power supply

Only things left are video card and hard drive

(NOP) #24

This is probably not the case for most of you people with the crashing problem but I would get those same error messages when I started the game and my internet connection wasn’t working. I have cable and if you start the game and the cable is not working then the game crashes imediately. Like I said, probabaly not the case for most of you but still might wanna check to make sure your internet connection is properly configured(firewalls and what have you).

(^POTATO) #25

So this is a windows error message coming up? (you know the one, do you want to send error repot etc.)

(BADASS_SJ) #26

I get no error message…the machine powers off.

(^POTATO) #27

I have no idea what the problem is then. My cpu temp stays fine even when playing ET for a long time (7 hours is the longest ive been able to play).
My specs:
P4 2.4 gig
1 gig ram
Geforce ti4600 128 mb (running older drivers 41.09 I think, oh and I know)

Maybe its the hyper threading or the 800 mhz fsb, i dont know im not a tech expert. Im just happy im not having the same problem, I love this game.

(BADASS_SJ) #28

Well, I was able to find the fix to my problem. After replacing all the components I was able to finally address it by replacing the video card. I went from a NVIDIA 5600FX to an ATI card. That did the trick.

(shao) #29

well i’ve not played ET in a while, a month, maybe2 due to connection problems. Last week i was able to join a server for an hour or two, no problems at all. Exactly like i used to be able to.

This week i am unable to join any server without it crashing almost instantly after joining a server. it’s a hard crash, i have to turn the pc off. Nothing EVER crashes my pc to such an extent, EVER, only a game which worked last week, and has worked since it was installed.

I can rule out heat as the room i play in is really effected by sunlight, during the summer it was VERY warm in here, and i was still able to play okay. Now in december it is considerably cooler, I also have 9 fans in my in my pc, and further more i am able to play other games without a single problem.

I reinstalled ET from scratch, applied patch, tried to connect to a server. Kicked for some pb issue. Run PBWEB.exe, update punkbuster, try to connect again… CRASH

this kind of problem plagued RTCW for a while where it would simply lock up the game when checking what processes it was running. If i find a fix i’ll post it.

(The Donster) #30

I had exactly the same problem. The reason for it, or mine anyway, was that I had just upgraded to the newest Nvidia drivers from their website. On removing the new driver and installing an older version (from August), the problems were gone!