BMS keeps crashing every 10-15 minutes.


BMS continues to crash my entire PC every 10-15 minutes after gameplay. As far as I know I have installed the game correctly and haven’t come across any issues like that. I also have this issue with CS-GO if that has anything to do with this game. My PC can dominate the reqs for this game so it shouldn’t be an issue with that but if anyone knows why this is happening and how I can fix it I would greatly appreciate it.

306.23 NVIDIA Drivers
2x GTX 590’s
i7 990x OC to 5 GHZ
Windows 7 Ult 64 bit



Same here, any help would be greatly appreciated!



What’s the error? You’re not really saying what the exact problem is. I have a bunch of crashes, but I mean my hardware is miles below sys. reqs.

I might be able to help depending on what the error is.



I can’t really tell you what is wrong because it just exits the game. I cannot check console when it happens, unless there is a log I am unaware of (I don’t believe there is).

I am indeed way below system requirements, but I use heavy FPS configs which bring the FPS up to 60+ 24/7.

I have attached my FPS configuration. I am also using DX 8 if that helps. (I have already went back to DX 9 and it didn’t help):

[code]// Unexplained crashes? Try changing mat_queue_mode to `-1’.
// ----------------------------------------------------------------------------
// Chris’ maxframes config, designed to get you a large performance boost
// v2.004 | 11 October 2011 |
// ----------------------------------------------------------------------------
// Problems or questions? Contact me at #christf2 on QuakeNet.
// ----------------------------------------------------------------------------
// Launch options:
// Fullscreen: -dxlevel 81 -full -w WIDTH -h HEIGHT -console -novid -useforcedmparms -noforcemaccel -noforcemspd
// Windowed: -dxlevel 81 -sw -w WIDTH -h HEIGHT -console -noborder -novid -useforcedmparms -noforcemaccel -noforcemspd
// Remove -dxlevel 81 from the launch options after the first launch!
// ----------------------------------------------------------------------------

// ----------------------------------------------------------------------------
// FPS cap
// ----------------------------------------------------------------------------
// The primary benefit of an FPS cap is to make the FPS more stable, other than
// that, it doesn’t do a lot. A moderate, consistent framerate is much more
// desirable than a variable but sometimes high framerate. A common
// misconception is that if any more frames are generated than your monitor can
// display, they are useless. This is wrong – frames are used for much more
// than mere display, and affect the way the game feels well past your
// refresh rate.
// This FPS cap should always be set to a value higher than cl_cmdrate' in // any case, or the discrepancy between clientside frame generation and frames // to be sent to the server will no doubt cause you many a headache, especially // when it comes down to hit registration. Other than that, I recommend // for everyone to use the value132’ (2*66), as long as you can generally
// keep that value stable without regular drops.
// ----------------------------------------------------------------------------
//fps_max 132 // Commented due to 2011-09-02 update causing jittering when fps is capped for some
fps_max 0
cl_showfps 0 // Show unsmoothed FPS meter

// ----------------------------------------------------------------------------
// Net settings
// ----------------------------------------------------------------------------
// Whilst net settings perhaps aren’t an integral part of an FPS config, they
// are a fact of life in competitive TF2, and as such, they are included here.
// A common question I am asked – what defines whether a good connection is
// good or bad? Mostly personal preference. If you’re not willing to make the
// choice, try both and see which is better for you.
// Generally, meeting both of the following conditions would classify it as a
// good connection:
// - Ping of <80 to the average server you join
// - Generally no/negligible choke/loss (can be checked with net_graph') // // There's some pretty good documentation on this here: // // // Uncomment (remove the//’ from) one of the groups if you want to use them.
// ----------------------------------------------------------------------------

// Good connection
cl_cmdrate 100
cl_interp 0.0152
cl_interp_ratio 1
cl_lagcompensation 1
cl_pred_optimize 2
cl_smooth 0
cl_smoothtime 0.01
cl_updaterate 100
rate 20000
ex_interp 0.010

// Bad connection
//cl_cmdrate 40
//cl_interp 0.025
//cl_interp_ratio 1
//cl_lagcompensation 1
//cl_pred_optimize 2
//cl_smooth 0
//cl_smoothtime 0.01
//cl_updaterate 40
//rate 35000

// ----------------------------------------------------------------------------
// Sprays
// ----------------------------------------------------------------------------
// Bear in mind that these are disabled on war servers due to `sv_pure 2’
// anyway, so if you play competitive TF2, this won’t help you.
// ----------------------------------------------------------------------------

// Disable sprays
//cl_playerspraydisable 1
//r_spray_lifetime 0

// Enable sprays – uncomment this section if you want these settings
cl_playerspraydisable 0
r_spray_lifetime 2

// ----------------------------------------------------------------------------
// Shadows
// ----------------------------------------------------------------------------

// Disable shadows
mat_shadowstate 0
r_shadowmaxrendered 0
r_shadowrendertotexture 0
r_shadows 0

// Enable shadows – uncomment this section if you want these settings
//mat_shadowstate 1
//r_shadowmaxrendered 11
//r_shadowrendertotexture 1 // Non-blobby shadows. Sometimes turned on by
// competitive TF2 players to see opponents standing
// near the other side of a wall. You may see some
// performance loss from setting this to `1’.
//r_shadows 1

// ----------------------------------------------------------------------------
// Facial features
// ----------------------------------------------------------------------------

// Disable facial features
//r_eyes 0
//r_flex 0
//r_lod 2
//r_rootlod 2
//r_teeth 0

// Enable facial features – uncomment this section if you want these settings
r_eyes 1
r_flex 1
r_lod 1 // Needs to be set to 1, otherwise they will still be disabled.
r_rootlod 1
r_teeth 1
flex_rules 1
flex_smooth 1

// ----------------------------------------------------------------------------
// Ragdolls
// ----------------------------------------------------------------------------
// You will have reduced performance on deaths which produce ragdolls.
// ----------------------------------------------------------------------------

// Disable ragdolls
//cl_ragdoll_fade_time 0
//cl_ragdoll_forcefade 1
//cl_ragdoll_physics_enable 0
//g_ragdoll_fadespeed 0
//g_ragdoll_lvfadespeed 0
//ragdoll_sleepaftertime 0

// Enable ragdolls – uncomment this section if you want these settings
cl_ragdoll_fade_time 15
cl_ragdoll_forcefade 0
cl_ragdoll_physics_enable 1
g_ragdoll_fadespeed 600
g_ragdoll_lvfadespeed 100
ragdoll_sleepaftertime “5.0f”

// ----------------------------------------------------------------------------
// Gibs
// ----------------------------------------------------------------------------
// You will have reduced performance on deaths which produce gibs.
// ----------------------------------------------------------------------------

// Disable gibs
//cl_phys_props_enable 0
//cl_phys_props_max 0
//props_break_max_pieces 0
//r_propsmaxdist 1
//violence_agibs 0
//violence_hgibs 0

// Enable gibs – uncomment this section if you want these settings
cl_phys_props_enable 1
cl_phys_props_max 128
props_break_max_pieces -1
r_propsmaxdist 1000
violence_agibs 1
violence_hgibs 1

// ----------------------------------------------------------------------------
// Graphical
// ----------------------------------------------------------------------------
// Now we come to the main brunt of the config. You probably don’t want to mess
// with this.
// ----------------------------------------------------------------------------
cl_detaildist 0
cl_detailfade 0
cl_drawmonitors 0
cl_ejectbrass 0
cl_new_impact_effects 0
cl_show_splashes 0
func_break_max_pieces 0
glow_outline_effect_enable 0 // Cart glow effect.
lod_transitiondist 0
mat_antialias 1 // 1 = off, I get too many questions about this :slight_smile:
mat_bumpmap 0 // Controls bumpmapping. Setting this to 0 on dx9 will cause
// a strange shine' effect to appear on all players. mat_colorcorrection 0 mat_disable_bloom 1 mat_disable_fancy_blending 1 mat_disable_lightwarp 1 mat_envmapsize 32 mat_envmaptgasize 16 mat_filterlightmaps 0 mat_filtertextures 0 mat_forceaniso 1 // See my comment onmat_antialias’.
mat_hdr_level 0
mat_max_worldmesh_vertices 1024
mat_monitorgamma 2.0 // Controls brightness, try 1.8 to make it brighter or 2.2
// to get it darker. Only works in fullscreen.
mat_motion_blur_enabled 0
mat_parallaxmap 0
mat_picmip 2 // Higher = more mipmapping. Without sv_cheats 1', you're looking // at a range from -1 to 2, -1 being the best quality, 2 being the // worst. mat_reducefillrate 1 mat_reduceparticles 1 mat_specular 0 // Controls specularity. Setting this to 0 will make ubers // non-shiny, and will remove some specular effects from in-game // entities which support it. Setting this to 1 on dx8 will // result in some strangefire’ textures replacing their
// appropriate counterparts, especially on medals, and certain
// hats.
mat_trilinear 0
mat_wateroverlaysize 1
mp_decals 300 // 9' is a good value to still see the spread pattern from a // scattergun without any real performance loss. r_3dsky 0 r_ambientboost 0 r_ambientfactor 0 r_ambientmin 0 r_avglight 0 r_cheapwaterend 1 r_cheapwaterstart 1 r_decals 300 r_decalstaticprops 0 r_decal_cullsize 15 r_dynamic 0 r_flashlightdepthtexture 0 r_lightaverage 0 r_maxdlights 1 // Specifies the maximum number of dynamic lights visible. // High values may cause significant performance loss in combat. r_propsmaxdist 0 r_renderoverlayfragment 0 r_staticprop_lod 4 r_waterdrawreflection 0 r_waterdrawrefraction 1 r_waterforceexpensive 0 r_waterforcereflectentities 0 r_worldlights 0 rope_averagelight 0 rope_collide 0 rope_rendersolid 0 rope_shake 0 rope_smooth 0 rope_subdiv 0 rope_wind_dist 0 tf_particles_disable_weather 1 // Disable weather effects on maps supporting // it, for example, setting this to1’
// disables rain effects on *_sawmill.
violence_ablood 0
violence_hblood 0

// ----------------------------------------------------------------------------
// Misc
// ----------------------------------------------------------------------------
cl_disablehtmlmotd 0
mat_clipz 1 // FX card users should set this to 0
//m_rawinput 1 // Turn on raw mouse input. Commented out by default due to
// silly incompatibility with the Xfire overlay. You should use
// it if you can!
mat_vsync 0 // Turn off vsync to avoid nasty I/O latency.
r_fastzreject -1 // Values >1 enable a fast Z rejection algorithm, to be
// performed on the GPU (as opposed to on the CPU). The
// value `-1’ autodetects hardware support for this
// feature, which is safer than forcing it.

// ----------------------------------------------------------------------------
// Sound
// ----------------------------------------------------------------------------
// I’d be hesitant to say that you would see a great deal of performance
// improvement from lowering the sound quality, but in my experience as a
// competitive TF2 player, lowering the sound quality makes determination of
// directionality and distance that much easier. You may see a small FPS gain
// with these settings, or you may not, either way will likely have a
// negligible effect on performance.
// ----------------------------------------------------------------------------
dsp_enhance_stereo 0
snd_async_fullyasync 1 // Having the sound run fully asynchronous has been
// helpful in the past, as it seems to (for whatever
// reason) reduce the number of TDRs experienced during
// gameplay. There’s some pretty good information on
// TDRs (nerds only) here:
snd_pitchquality 0
snd_spatialize_roundrobin 1

// ----------------------------------------------------------------------------
// Threading
// ----------------------------------------------------------------------------
mat_queue_mode 2 // mat_queue mode is another frequently asked about cvar, it
// defines the threading method to be used by the material
// system. It has been unstable to use in the past, but
// nowadays it’s generally okay.
// Here are the possible values:
// -2 legacy default
// -1 default
// 0 synchronous single thread
// 1 queued single thread
// 2 queued multithreaded
// If you have problems with the value 2', try setting it to //-1’.
// As an aside, there are quite a few bugs in the demo system
// that occur when mat_queue_mode is set to a value that is
// not `-1’. If you intend to do work with the demo system,
// maybe you should change this.
// In previous FPS configs I explicitly stated some threading
// settings. If there has been one thing I have learned, it’s
// best just to leave them well alone. What works for most
// often leads to completely unreproducable errors being
// reported.

// ----------------------------------------------------------------------------
// Misc
// ----------------------------------------------------------------------------
cl_forcepreload 1 // Force preloading

// ----------------------------------------------------------------------------
// Print to console
// ----------------------------------------------------------------------------
echo “-------------------------------------------------------”
echo " Chris’ maxframes config loaded. "
echo “-------------------------------------------------------”
echo “Please direct all comments/queries/whatnot to”
echo “#christf2 on QuakeNet.”
echo “”
echo “-------------------------------------------------------”
echo " Memory stats "
echo “-------------------------------------------------------”
echo “”
echo “-------------------------------------------------------”
echo " Code support "
echo “-------------------------------------------------------”
echo “-------------------------------------------------------”[/code]

It’s the same one I use for TF2, but that shouldn’t make a difference.




Did you even check the code you just posted?



First of all, take out the config, and see if it stops the crashes.
Secondly, please give us your system info (CPU, GPU, and Operating System: Example: 2.0 Ghz Core 2 Duo, Intel GMA 945, Windows XP Home Edition Service Pack 3)

I also have a config I can give you that works for BMS, if need be.



go to C:\Program Files (x86)\Steam\steamapps[b]ACCOUNTNAME[/b]\source sdk base 2007 and there should be a minidump / crash log



I will try modifying the unexplained crashes part of the config. XD

System specs:
Windows Vista home premium x64 (sp 2)
GeForce 6150SE nforce 430
Driver version 306.23
Memory: 7 GB’s
Processor: AMD Phenom 9150e quad core

Crash dump attached. Thanks!
hl2_4104_crash_2012_9_16T3_41_29C0.mdmp (83.7 KB)



The game was flawless the first few levels but now I am getting crashes to desktop every 10 mins.

Faulting application name: hl2.exe, version:, time stamp: 0x470c11ae
Faulting module name: client.dll, version:, time stamp: 0x504ecc4f
Exception code: 0xc0000005
Fault offset: 0x00362edd
Faulting process id: 0xcf8
Faulting application start time: 0x01cd940d22dd7064
Faulting application path: c:\steam\steamapps\lister8\source sdk base 2007\hl2.exe
Faulting module path: c:\steam\steamapps\sourcemods\bms\bin\client.dll
Report Id: 114eda50-0001-11e2-baff-f46d04af08c0



I cannot find a mini-dump / crash log anywhere in that folder as you explained earlier. The specifics of my crash is my monitor turns off and the sound from the exact point of the crash loops so you hear the continuous noise when a PC freezes and then I have to manually shut off my PC and restart. If there is anymore information you need please let me know.



Fixed! I just changed “mat_queue_mode” to “-1” and no more crashes! Completely playable!

Thanks bro! You made me look stupid, but it helped!



Nice find/fix. Why can’t this be an option in the Menu?



I have the exact same issue. Every 10 to 15 minutes of playing the game, my computer hangs. The screen suddenly goes black, turns off and the sound keeps looping. I have to shut off the computer by pressing and holding the power button. No crash log / mini-dump is created.

Here are my specs:

Win7 Home Premium, SP1 (64-bit)
Intel Core 15-2500K @ 3.30GHz
Radeon HD 6800 Series graphics card with Catalyst 12.8



You’re using DX8??:fffuuu:



Regular crashes would suggest either

a) an antivirus or other security software not liking the game accessing something - make sure you are running things as administrator. If you haven anything installed with ‘Norton’ written on it, destroy it. Destroy it now.

b) a heating issue. You sure all the fans in your PC are working?



If I can’t run it at 60 fps on DX 9, why not use DX 8? :stuck_out_tongue:



It’s def not a heating issue because I monitor all temperatures on my PC and they are all well below maximums. I do have Norton running on my PC so should I disable it and try to run the game? Heres another question as well but if I get rid of my Anti-virus software what should I use instead because to my knowledge Norton is the most preferred of all anit-virus software.



I’m having this same problem, but as a whole I’m pretty computer-illiterate. Rather than crashing to desktop though, my whole PC just switches off, so quick asif there’s a powercut. Which is irritating as I love HL and so far this BM looks amazing. But it’s switiching it off every 15 minutes or so too!
How do I get up this code thing to help this? all advice is fantastic :slight_smile:



Looks like I was able to resolve my issue. Have not had any crashes in the past couple of hours of play after these two operations:

  1. I thought the problem might be heat related, so I thoroughly dusted my case, fans & heatsinks (both processor and graphics card).

  2. Some people with similar problems seem to think the issue has to do with conflicting sound devices, so I disabled the AMD High Definition Audio Device under Device Manager in Control Panel. Only left the on-board audio (Realtek High Definition Audio) active.

Unfortunately I did both before trying the game, so I can’t tell for sure which was the cure. I’m leaning towards #2, since I’ve had no heat issues with more graphically intense games, and the cleaning operation only seemed to drop the temps by a couple of degrees. I even bumped up the resolution (up to 2560 x 1600) and the audio quality after things started to look stable.

Hope this helps!



I would advise uninstalling all your Norton stuff, yes. Here is a better AV:

The free version of it is the one you want. You still have to register it, but it never costs you anything as long as you stick to that version and ignore the offers to ‘go pro’.

It’s also got a very small memory footprint, so you should enjoy some better performance. It’s not let me down in about six years now.