Could you post more details about his system (RAM, CPU, ect.), and some monitoring information, such as task manager running to capture the RAM usage before and after this crash, windows version (could help?), and any other useful thing they have to pinpoint this error.

I unfortunately cannot help, but I'm sure people experienced with the source engine would be able to help.

happened to me when using mastercoms, after i got rid of it, i never got this error again

this happened to me but it sorta just stopped happening. sorry can't be too much help

For me it was discord causing it but I can't exactly remember the fix for it or what caused it in the first place

MORE VRAM

I was not able to monitor my task manager yesterday because I somehow didnt crash. I have 16gbs of ram and AMD Ryzen 5 1600x Six-Core Processor 3.2GHz. I am on windows 10. I always kill most of the programs running in the background, such as: Discord or my browser.

I remember not having this issue during the summer, perhaps halloween could be causing it? I have never ever experienced before that my game crashes every night I scrim. I was also planning on re-installing windows, so that might fix it as well.

I have switched from mastercoms to a different confing, that seemed to help a bit but I still crash every night I scrim.

Tonight I monitored my CPU after I crashed (https://cdn.discordapp.com/attachments/743079186842910801/770972242221596672/122942328_707427173202272_3757614574066644323_n.png). I even switched to dx81, updated my GPU drivers (I was not crashing with the previous one and I didnt update my GPU drivers for like 6 months), verified the game chache, deleted soundchache and nothing has worked.

Any other suggestions?

I don't have an explanation, but last night me and two other friends all crashed with this exact error for the first time ever after playing on a tf2 smash bros server, then on a tf2ware server. I really don't think it's your hardware but I have no clue what causes it.

I think its because TF2 eventually dies if you leave it on for too long.
Try restarting the game
before and between matches/half

had it once 2 days ago
removed all "vpk.sound.cache" files in Custom
haven't gotten it since
this came from some random steam forum post

Can't be 100% sure if this is the correct fix. The crash only happened to me once and 2 days isn't a long time to say with full certainty the crashes are gone

I have no clue why a sound cache file would have any effect on a texture quality crash. However there is no harm in trying it. All custom vpk.sound.cache files rebuild themselves by launching the game so you get all the deleted ones back

Try this https://www.youtube.com/watch?v=OhyLH9rO9VQ&ab_channel=Mike%27sunboxing%2Creviewsandhowto
It clears your stand by list depending on the parameters you set.

You could use ISLC which does the same thing but is easier to use with a GUI.
I would recommend setting max value to half your ram size and initial size to be about 300 MB.

This used to happen to me when increasing texture quality, fixed after decreasing, it also only happened on certain maps (community servers only). changing cfg or lowering texture if not already lowest might help, but it's not the best solution, only a temporary one

not sure which one fixed it but you guys managed to fix the error. Thank you!

Try turning off ISLC and see if the problem still exists. Will be helpful in the future for people having the same problem

just gonna add some info here in the meantime:

• Still no crashes on my end. About 6-7 hours of playtime since I removed the .sound.cache files. Idk if that's helpful. Maybe the crash will occur very rarely on my PC and it's gonna happen again eventually
  
• someone else tried removing .sound.cache files and they still have crashes
  
• mastercomms doesn't appear to be the issue. that other person uses mostly default settings without mastercomms
  
• Could be linked to certain map textures? The one time I crashed was on gullywash. Other person also crashed last night on gullywash. I didn't think about asking them at the time so maybe they crash on other maps too. I doubt it's this, but maybe other people can confirm/deny

i remember i used to crash quite often on gullywash, i'd say it's the map's fault
hopefully collaide can resolve some of this in his update