Ever since the latest update, my TF2 crashes every time the server map changes. This happens on any server, no matter what.
The message is that generic "The memory could not be read" error.
Specs:
Intel Core 2 Duo @ 2.6Ghz (By the way, I have Multi-core off [It didn't do any better on])
Dual 9800GT's Superclocked
2048MB of RAM @ 800Mhz
nVidia 780i Motherboard
Anyone else getting this problem?
I have the same problem, not only every map change but also at random times. Every single time it happens, i have to verify my game cache files or reinstall the game for it to start again...it's really starting to piss me off
tf2 sucks, play halo - its better
[highlight](User was banned for this post ("Trolling" - Rusty100))[/highlight]
[QUOTE=Foxsune;14266452]tf2 sucks, play halo - its better[/QUOTE]
hahhahahahah
There can be a few causes
1. Memory damage - try to do a memtest
2. VRAM damage - this one can be a bit tricky
3. Hard drive damage - again diagnostics
4. Damaged system .dll - reinstall system
You could also remake the swap file, disable it, reset the PC, and enable it again, and obviously restart
I don't know what's happening but can't you just play on 24/7 servers?
[QUOTE=BISCUIT_TINS;14272451]I don't know what's happening but can't you just play on 24/7 servers?[/QUOTE]
From the sorts of players who play on those types of servers, I'd really rather not play on them.
Also, if it is any difference, one of those "9800GT's" is actually an 8800GT, with it's BIOS flashed.
I have the same problem, but the message is different.
I've been having this too, happens on map change and occasionally on round start.
God damn, it won't even save the stats I got. It's really annoying.
I got 79 teleports and 32 sentry kills in one life on Goldrush (100-something points in a life). :<
[QUOTE=Porcupine162;14281970]From the sorts of players who play on those types of servers, I'd really rather not play on them.
Also, if it is any difference, one of those "9800GT's" is actually an 8800GT, with it's BIOS flashed.[/QUOTE]
Yeh, but either card will easily run tf2 on high graphics so i don't think that would be the problem unless the card was faulty.
[img]http://img14.imageshack.us/img14/2788/errorhfx.jpg[/img]
Just in case you needed the actual error, there it is in all it's frustrating glory. I also get it when I normally quit the game, so there is no way my stats will ever be saved.
Did you try any of the stuff I posted?
I remember that I simply had broken RAM
[QUOTE=Kumagoro;14286073]Did you try any of the stuff I posted?
I remember that I simply had broken RAM[/QUOTE]
I'm doing a memory test now. I'm not sure how I'm supposed to test the others, but I trust they are fine, anyway.
[B]EDIT: [/B]Nothing wrong with my memory, I did a full check.
[QUOTE=Foxsune;14266452]tf2 sucks, play halo - its better
[highlight](User was banned for this post ("Trolling" - Rusty100))[/highlight][/QUOTE]
Joke of the week :D
If you use an autoexec with multithreading in it, this is what that part should look like.
[CODE]// Multithreading (1/4 Life's settings, which he tweaked for stability)
host_thread_mode 1 //Forces on multithreading. Defaults to 0.
//mat_queue_mode 0 //Default is -1. Single Synchronized thread. CAUSES INSTABILITY ON MOST SYSTEMS.
r_threaded_client_shadow_manager 1 //Threaded world and flashlight shadows.
r_threaded_particles 1 //Threaded particles (Defaults to 1)
r_threaded_renderables 1 //Threaded renderables
//r_queued_decals 1 //Queued decals. CAUSES INSTABILITY ON MOST SYSTEMS.
//r_queued_post_processing 1 //Queued post processing. CAUSES INSTABILITY ON MOST SYSTEMS.
//r_queued_ropes 1 //Queued ropes. CAUSES INSTABILITY ON MOST SYSTEMS.
//cl_threaded_bone_setup 1 //Threaded bones and animations. CAUSES INSTABILITY ON MOST SYSTEMS.
//cl_interp_threadmodeticks 1 //ONLY USE IN SINGLEPLAYER GAMES! Adds some extra interpolation ticks for multithread mode.
//snd_mix_async 1 //Multithreaded sound. Causes the first few milliseconds of sounds to be cut off on some systems.[/CODE]
The Classless Update came with dual-core support, which broke some of the old multithreading commands in the process.
Dude. Fully over a year ago. Quit posting your fucking scripts.
[editline]02:23AM[/editline]
And I just bumped it, fuck I'm a dumbass.
Edit: Please just box me and refrain from posting, let this slide down the list again.
Sorry, you need to Log In to post a reply to this thread.