I think the only other way of getting more detail is to run the server
through a debugger. Ive done this before, eg. you use Visual Studio 2008
on your home computer, set up remote debugging on the server machine
(including opening the relevant ports and stuff), and then remote debug
it via the internet... when it crashes, you see exactly where.
On 2012/07/29 21:19, Bruno Garcia wrote:
Hello,
I'm running a CS: S server on a windows 2003 server computer. I know
that it's outdated, and windows is highly unstable at times, but I've
been getting a lot of server crashes for the last two weeks and with
each crash comes a dump file. These dump files don't appear to hold many
information about the crash, pretty useless to me.
But they must be there for a reason. So I was wondering if there's a
'smart' way to "pin-point" at what instance the srcds crashed.
I'll leave some dox about the server that I'm running, maybe you'll find
something 'un-usual'
Windows 2003 Server
Counter-Strike: Source dedicated server
Running process with all cpus (process affinity)
Running on RealTime priority (might change it to High)
Addons:
Mani Admin System
Mattie's Eventscripts
DAF DoS Fix (Blocks flood of server queries to the server)
Any help is appreciated
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
