Games Quit bug.
Games Quit bug.
I'll be playing random multiplayer and Quake would shut down completely, back to desktop... woulda thought there be a error message at least. :icon33:
-
- Posts: 7
- Joined: Sat Oct 22, 2005 12:58 am
same here ...man
I heard several ppl having this problem actually ...SO am I 
Playing for some ramndom time...then game (wether its MP or SP) , crashes on desktop...without any particular error...leaving gamma all screwed..
MY PC perfectly ran DOOM 3...
Athlon 3200 64bit (@2.3) 300mhz OC
1024 kingston 333mhz 1- 512x2
GeForce6800 BFG OC (128mb)
Onboard sound
Soltek K8Tpro mobo (such a shit)LOL...
any ways ...post your specs...maybe well see whats wrong

Playing for some ramndom time...then game (wether its MP or SP) , crashes on desktop...without any particular error...leaving gamma all screwed..
MY PC perfectly ran DOOM 3...
Athlon 3200 64bit (@2.3) 300mhz OC
1024 kingston 333mhz 1- 512x2
GeForce6800 BFG OC (128mb)
Onboard sound
Soltek K8Tpro mobo (such a shit)LOL...
any ways ...post your specs...maybe well see whats wrong
I get the same random desktop crashes. Doom 3 ran fine (in that regard).
My system hardware is pretty dodgy:
AMD 2600+ (underclocked from a 3000+ due to stability issues)
1gb RAM
Geforce 6800 GT 256mb (agp)
I'm probably going to get an AMD 64 3500+ (to remove this performance bottleneck) with a mobo capable of both AGP and PCI-e gfx cards so I can easily upgrade later if PCI-e becomes the dominant standard.
My system hardware is pretty dodgy:
AMD 2600+ (underclocked from a 3000+ due to stability issues)
1gb RAM
Geforce 6800 GT 256mb (agp)
I'm probably going to get an AMD 64 3500+ (to remove this performance bottleneck) with a mobo capable of both AGP and PCI-e gfx cards so I can easily upgrade later if PCI-e becomes the dominant standard.
Last edited by d3fin3d on Sat Oct 22, 2005 1:36 am, edited 1 time in total.
-
- Posts: 7
- Joined: Sat Oct 22, 2005 12:58 am
-
- Posts: 7
- Joined: Sat Oct 22, 2005 12:58 am
I was thinkin here ...all of us have Geforce's GFx , so might be that or drivers (i use newest ones), i doubt it has anything to do with CPU or MOBO. Then it could also be the software issue...wich i hope it is. 
Ill try reistallin windows freshly and will post my results later.
Any luck with you guyes?

Ill try reistallin windows freshly and will post my results later.
Any luck with you guyes?
I've had this error probably 3 times since I've been playing and I've probably put 20 hours or more into the game. So, it's not a constant problem, but obviously it's never fun when it happens, and it leaves my windows environment in fullbright mode and I have to reboot.
My system specs are 3.2 MHZ P4 with 2GB of RAM and GeForce 6800 Ultra with 256MB of RAM.
The first time the error occurred was during a FFA battle on Bloodwork - I was strafing from the SSG to an enemy coming up a bounce pad.
The second time the error occurred, I was at the end of a FFA battle and wanted to manually set/check my weapon binds. I got to the menu and it suddenly crashed - it's possible the server map was changing at that time, too.
The third time, I had been waiting to participate in a Tourney and had "readied up". It counted down to put us in the bracket, but sadly for me, it crashed.
I downloaded the latest Nvidia drivers released on October 20, 2005 before the third crash.
My system specs are 3.2 MHZ P4 with 2GB of RAM and GeForce 6800 Ultra with 256MB of RAM.
The first time the error occurred was during a FFA battle on Bloodwork - I was strafing from the SSG to an enemy coming up a bounce pad.
The second time the error occurred, I was at the end of a FFA battle and wanted to manually set/check my weapon binds. I got to the menu and it suddenly crashed - it's possible the server map was changing at that time, too.
The third time, I had been waiting to participate in a Tourney and had "readied up". It counted down to put us in the bracket, but sadly for me, it crashed.
I downloaded the latest Nvidia drivers released on October 20, 2005 before the third crash.
- Jason
this problem happened to me once in quake 3, all i did was go on the game again then exit it, dont reeboot, its a waste of timeclkou wrote:I've had this error probably 3 times since I've been playing and I've probably put 20 hours or more into the game. So, it's not a constant problem, but obviously it's never fun when it happens, and it leaves my windows environment in fullbright mode and I have to reboot.
.
[img]http://i26.photobucket.com/albums/c134/fireboy93/Nearlyfinishednarutcopy.png[/img]
my computer reboots faster than quake4 starts up, loads menu's and quits again 
also, my q4 crashed last night (left the screen fullbright). i restarted quake4 and played some, quit the game and windows was still too bright. so it seems restarting quake4 doesnt always help

also, my q4 crashed last night (left the screen fullbright). i restarted quake4 and played some, quit the game and windows was still too bright. so it seems restarting quake4 doesnt always help
[url=http://profile.mygamercard.net/Emka+Jee][img]http://card.mygamercard.net/sig/Emka+Jee.jpg[/img][/url]
-
- Posts: 18
- Joined: Sun Mar 12, 2000 8:00 am
I was having this issue but mostly on servers running PunkBuster. I rolled back my video drivers to 77.77 and still experienced the issue. I forwarded port 24349 for Punkbuster in my router and all is fine now. I played for about an hour straight with no crashes or lock ups. This was on the same server that kicked me out 3 times in a row at the start of a second match.
-
- Posts: 18
- Joined: Sun Mar 12, 2000 8:00 am
When the game crashes and windows is to bright just run this file.MKJ wrote:my computer reboots faster than quake4 starts up, loads menu's and quits again
also, my q4 crashed last night (left the screen fullbright). i restarted quake4 and played some, quit the game and windows was still too bright. so it seems restarting quake4 doesnt always help
http://www.quake2evolved.com/odium/gammafix.exe
Will correct it instantly.
-
- Posts: 18
- Joined: Sun Mar 12, 2000 8:00 am
I tried that for Quake 4 hoping it would behave as Quake 3 did, but alas, it didn't, so I had to reboot. But, for kicks and giggles, I'll try loading up Quake 3 if Quake 4 ever does that to me again and see what happens.RooKie wrote:this problem happened to me once in quake 3, all i did was go on the game again then exit it, dont reeboot, its a waste of time
- Jason