PDA

View Full Version : This is a bit wierd? Help if you can please!

Shintaz
30-11-2007, 05:01 PM
http://i163.photobucket.com/albums/t298/Shintaz/Problem.jpg

This crashes sometimes when switching level/server on team fortress 2. Sometimes it can load about 6+ maps before saying this, some just 1. I really need to know what I have to stop this happening!

Plus, the blackness in the background - when the game crashes, it gets rid of my background.

Suggestions please?
Wahoo
30-11-2007, 06:31 PM
Is it a certain map that is doing this? Or is there a certain map you haven't yet played that could be doing it?
Erskien_Parkour
30-11-2007, 06:34 PM
Did you check steam forums first?

Thats best place to get advice about this kinda thing...
Shintaz
30-11-2007, 06:49 PM
I checked google THEN steam forums. People are saying they're having the same problem but there are no answers. Plus, these are on different games, but happen at the same time - when a new map/level is loading.

And Wahoo, it happens on practically every map from time to time.
Pilk Man
30-11-2007, 09:33 PM
Try verifying game cache?
Twatybollocks
01-12-2007, 02:20 AM
Try verifying game cache?

You shoot people randomly in CS...I have proof! Don't you dare come on these forums spreading your cache flilth!
Pilk Man
01-12-2007, 02:24 AM
You shoot people randomly in CS...I have proof! Don't you dare come on these forums spreading your cache flilth!

...

?
Twatybollocks
01-12-2007, 02:29 AM
...

?

Lobs Flashbang, shoots in head



Fixed!!
Fishmonster
01-12-2007, 03:06 AM
That gibberish looks like memory related gibberish to me. Which I would assume means it hasn't properly unloaded the previous map from memory before loading the new one. Which would result in there not being enough memory to load the new map.

Of course this is just random speculation. If does happen to be the case then there isn't much you can do. Try limiting the number of applications running in the background.
woody_tng
01-12-2007, 03:08 AM
That gibberish looks like memory related gibberish to me. Which I would assume means it hasn't properly unloaded the previous map from memory before loading the new one. Which would result in there not being enough memory to load the new map.

Of course this is just random speculation. If does happen to be the case then there isn't much you can do. Try limiting the number of applications running in the background.

Or install more memory.
Shintaz
01-12-2007, 12:54 PM
Me:
BFG GeForce 8800 320MB graphics.
Intel Pentium D CPU 3.00GHz
3 gb RAM
Two HDD: One = 226 GB, other 232GB.
32-Bit operating system.
Windows Vista Home Premium

I wouldnt think it's be a problem with memory, unless it tries to load it too fast? Plus, I wouldn't say so, but could it be vista? I'm downgrading to XP soon anyways, but... More suggestions? Thanks for all help also. :)
Timmeh
02-12-2007, 01:47 AM
My god people in this thread don't understand memory in the slightest.

Quite simply, memory could not be allocated, there could be a million reasons for this; your best bet is to hope someone stumbles on the right one or valve fix whatever's causing it.
woody_tng
02-12-2007, 01:53 AM
I was considering that he may not have enough memory. 3Gb is obviously enough for pretty much anything on the market at present.
Timmeh
02-12-2007, 02:42 AM
Read me. (http://en.wikipedia.org/wiki/Virtual_memory)
Shintaz
02-12-2007, 06:55 PM
This error may be related to the way in which Windows Vista handles memory allocation. If you are using Windows Vista, please see the Virtual address space usage in Windows game development topic at the Microsoft Help and Support center.

From Valve staff. I'm downing it to XP anyways, so I guess it should be alright. Probs next weekend.
ObUk
03-12-2007, 12:36 AM
As Timmeh has pointed out this is might have something to do with the way Vista assigns and uses Virtual memory (hard disk space as a little bit of a gimpy substitute for RAM).
Ive never used Vista for gaming so i dont really know how well its system works.
I used to get Virtual memory errors in XP on certain programs until i manually set the min-max size of the Virtual memory swapfile instead of letting Windows manage it.

If you type "Vista Virtual Memory" into google the fourth link will tell you how to change the virtual memory settings on vista. (incase u didnt know already :D)
Sorry cant post links yet >_<

This procedure is very similar on XP as well.

Hopefully downgrading (or upgrading as i see it at the moment) to XP will fix your problem.
If not this is one of the first things i would look at.

I hope this helps

ObUk