So the last few weeks or so i'll be playing and will randomly crash. Not on a map start/change or anything like that just in the middle of the game i'll get "hl2.exe has stopped working" and have to restart tf2. There's no message in game. In fact when I crash my character will stay in game doing what ever I was doing for a little while(Pushing Cart, Firing, Etc.) even when the game is completely closed. I've verified cache and re installed tf2 and it still happens. I can hardly go half an hour without at least one crash :/ Any help would be greatly appreciated.
TF2 Crashing
posted in
Q/A Help
So the last few weeks or so i'll be playing and will randomly crash. Not on a map start/change or anything like that just in the middle of the game i'll get "hl2.exe has stopped working" and have to restart tf2. There's no message in game. In fact when I crash my character will stay in game doing what ever I was doing for a little while(Pushing Cart, Firing, Etc.) even when the game is completely closed. I've verified cache and re installed tf2 and it still happens. I can hardly go half an hour without at least one crash :/ Any help would be greatly appreciated.
If you put '-condebug' as a launch option you'll get a copy of your console output in your tf folder as 'console.log.' If you do that and post the contents, I'll be able to help you better.
As for random crashes, in my experience it's almost always something with hardware and more specifically, memory. Run Memtest86+ overnight and let me know if any errors show up.
If you put '-condebug' as a launch option you'll get a copy of your console output in your tf folder as 'console.log.' If you do that and post the contents, I'll be able to help you better.
As for random crashes, in my experience it's almost always something with hardware and more specifically, memory. Run [url=http://www.memtest.org/]Memtest86+[/url] overnight and let me know if any errors show up.
As for random crashes, in my experience it's almost always something with hardware and more specifically, memory. Run [url=http://www.memtest.org/]Memtest86+[/url] overnight and let me know if any errors show up.
KBlairIf you put '-condebug' as a launch option you'll get a copy of your console output in your tf folder as 'console.log.' If you do that and post the contents, I'll be able to help you better.
As for random crashes, in my experience it's almost always something with hardware and more specifically, memory. Run Memtest86+ overnight and let me know if any errors show up.
I ran memtest for 5 hours with 4 passes and had 0 errors. I'll let you know what the console says if anything when I crash.
EDIT: From what I can see when I crash it doesn't say anything relevant in console.
"Rupee connected
gR| Mediarch killed raze soldjer with scattergun.
The_Salt killed Chumekin with tf_projectile_pipe_remote.
gR| Mediarch killed StateFromJakeFarm with scattergun." and then I crashed a few seconds after that.
Only thing I can think of is the way my medibeam is set up it spams the console with
"Attempt to set particle collection medicgun_beam_attrib_overheal_blue to invalid orientation matrix
Attempt to set particle collection medicgun_beam_blue_targeted to invalid orientation matrix"
alias secondary "slot2; medigun; +attack; r_drawviewmodel 0; viewmodel_fov 0
Maybe there is an error limit or something Idk
[quote=KBlair]If you put '-condebug' as a launch option you'll get a copy of your console output in your tf folder as 'console.log.' If you do that and post the contents, I'll be able to help you better.
As for random crashes, in my experience it's almost always something with hardware and more specifically, memory. Run [url=http://www.memtest.org/]Memtest86+[/url] overnight and let me know if any errors show up.[/quote]
I ran memtest for 5 hours with 4 passes and had 0 errors. I'll let you know what the console says if anything when I crash.
EDIT: From what I can see when I crash it doesn't say anything relevant in console.
"Rupee connected
gR| Mediarch killed raze soldjer with scattergun.
The_Salt killed Chumekin with tf_projectile_pipe_remote.
gR| Mediarch killed StateFromJakeFarm with scattergun." and then I crashed a few seconds after that.
Only thing I can think of is the way my medibeam is set up it spams the console with
"Attempt to set particle collection medicgun_beam_attrib_overheal_blue to invalid orientation matrix
Attempt to set particle collection medicgun_beam_blue_targeted to invalid orientation matrix"
alias secondary "slot2; medigun; +attack; r_drawviewmodel 0; viewmodel_fov 0
Maybe there is an error limit or something Idk
As for random crashes, in my experience it's almost always something with hardware and more specifically, memory. Run [url=http://www.memtest.org/]Memtest86+[/url] overnight and let me know if any errors show up.[/quote]
I ran memtest for 5 hours with 4 passes and had 0 errors. I'll let you know what the console says if anything when I crash.
EDIT: From what I can see when I crash it doesn't say anything relevant in console.
"Rupee connected
gR| Mediarch killed raze soldjer with scattergun.
The_Salt killed Chumekin with tf_projectile_pipe_remote.
gR| Mediarch killed StateFromJakeFarm with scattergun." and then I crashed a few seconds after that.
Only thing I can think of is the way my medibeam is set up it spams the console with
"Attempt to set particle collection medicgun_beam_attrib_overheal_blue to invalid orientation matrix
Attempt to set particle collection medicgun_beam_blue_targeted to invalid orientation matrix"
alias secondary "slot2; medigun; +attack; r_drawviewmodel 0; viewmodel_fov 0
Maybe there is an error limit or something Idk
Other things to try: mat_queue_mode 0 and mat_hdr_level 0. It might be annoying running without multicore rendering but it causes crashes sometimes, and it would be good thing to single it out.
Other things to try: mat_queue_mode 0 and mat_hdr_level 0. It might be annoying running without multicore rendering but it causes crashes sometimes, and it would be good thing to single it out.
KBlairOther things to try: mat_queue_mode 0 and mat_hdr_level 0. It might be annoying running without multicore rendering but it causes crashes sometimes, and it would be good thing to single it out.
Both of those are already like that in my autoexec.
[quote=KBlair]Other things to try: mat_queue_mode 0 and mat_hdr_level 0. It might be annoying running without multicore rendering but it causes crashes sometimes, and it would be good thing to single it out.[/quote]
Both of those are already like that in my autoexec.
Both of those are already like that in my autoexec.
If you think it's from the console spam, you could try filtering out the spam? Maybe it's the quantity of spam that crashes you, and not actually getting it in console would stop your crashes? Worth a shot at least.
con_filter_enable 1
con_filter_text "particle"
If you think it's from the console spam, you could try filtering out the spam? Maybe it's the quantity of spam that crashes you, and not actually getting it in console would stop your crashes? Worth a shot at least.
con_filter_enable 1
con_filter_text "particle"
con_filter_enable 1
con_filter_text "particle"
I'm pretty stumped. Btw that "Attempt to set particle collection <particle> to invalid orientation matrix" error is because of viewmodel_fov 0. If you use viewmodel_fov -360 the errors go away and it still disables the beam/bullet tracers, but I doubt that's the reason you're crashing.
I guess the only thing left for me to say is to enable crashdumps and send one to valve when it happens.
SizzlingCalamariA solution to get all dumps is:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
2. Create a new key called 'LocalDumps'
3. Your crash dumps will be here: %LOCALAPPDATA%\CrashDumps
I'm pretty stumped. Btw that "Attempt to set particle collection <particle> to invalid orientation matrix" error is because of viewmodel_fov 0. If you use viewmodel_fov -360 the errors go away and it still disables the beam/bullet tracers, but I doubt that's the reason you're crashing.
I guess the only thing left for me to say is to enable crashdumps and send one to valve when it happens.
[quote=SizzlingCalamari]A solution to get all dumps is:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
2. Create a new key called 'LocalDumps'
3. Your crash dumps will be here: %LOCALAPPDATA%\CrashDumps
[/quote]
I guess the only thing left for me to say is to enable crashdumps and send one to valve when it happens.
[quote=SizzlingCalamari]A solution to get all dumps is:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
2. Create a new key called 'LocalDumps'
3. Your crash dumps will be here: %LOCALAPPDATA%\CrashDumps
[/quote]
KBlairI'm pretty stumped. Btw that "Attempt to set particle collection <particle> to invalid orientation matrix" error is because of viewmodel_fov 0. If you use viewmodel_fov -360 the errors go away and it still disables the beam/bullet tracers, but I doubt that's the reason you're crashing.
I guess the only thing left for me to say is to enable crashdumps and send one to valve when it happens.
SizzlingCalamariA solution to get all dumps is:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
2. Create a new key called 'LocalDumps'
3. Your crash dumps will be here: %LOCALAPPDATA%\CrashDumps
Sweet thanks for the help! I'll do that and leave it up to the valve gods.
[quote=KBlair]I'm pretty stumped. Btw that "Attempt to set particle collection <particle> to invalid orientation matrix" error is because of viewmodel_fov 0. If you use viewmodel_fov -360 the errors go away and it still disables the beam/bullet tracers, but I doubt that's the reason you're crashing.
I guess the only thing left for me to say is to enable crashdumps and send one to valve when it happens.
[quote=SizzlingCalamari]A solution to get all dumps is:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
2. Create a new key called 'LocalDumps'
3. Your crash dumps will be here: %LOCALAPPDATA%\CrashDumps
[/quote][/quote]
Sweet thanks for the help! I'll do that and leave it up to the valve gods.
I guess the only thing left for me to say is to enable crashdumps and send one to valve when it happens.
[quote=SizzlingCalamari]A solution to get all dumps is:
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
2. Create a new key called 'LocalDumps'
3. Your crash dumps will be here: %LOCALAPPDATA%\CrashDumps
[/quote][/quote]
Sweet thanks for the help! I'll do that and leave it up to the valve gods.
Please
sign in through STEAM
to post a comment.