Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
There maybe way to turn off such "functionality", and a google search would be the answer.
Ideally the server software would have the option of not crashing in a way that prevents it from restarting on an operating system which 80% of the world uses. I've had L4D2 server crash in a similar manner, although less often, so valve must at least be aware of the problem.
Dark_Stealth's answer was not useful as I already googled for a solution multiple times. I came here asking for help as a last resort because it is much more time consuming than a simple google search.
I think I found a way to solve this problem using an autohotkey script which I compiled into an executable. I have it start in the beginning of my server batch file outside of the main loop. It watches for the crash window and kills the process. It also watches for the server batch file window and quits when it's no longer running. I'm now waiting for my server to crash, which seems to be taking longer now that I need it to do so.
If anyone has a better solution I'd like to hear it.
You should give me a dollar, I did your work for you:
http://www.neowin.net/forum/topic/1055744-windows-7-disable-x-application-has-stopped-working-dialog/
Thanks. I wrote a small program which crashes to test it out and it does exactly that -- it hides the UI. As this is a machine I use every day I'll have to weigh the pros and cons of not knowing when when other programs crash. I think in this case my AutoHotkey solution works better.
What I previously tried is excluding the application from WER (Windows Error Reporting) and turning off WER altogether. Unfortunately instead of turning off the crash dialog it merely changes it.