SRCDS Crash = Windows Reset?

[thetwistedpanda]

Server OS: Windows Web Server 2008 R2 (x64)
Processor: Intel® Core™2 Quad CPU Q8200 @ 2.33Ghz
Ram: 4.00 GB
Game(s):
Counter:Strike-Source

PHP Code:

@echo off
cls
echo Server 4: Mini-Games
title Server 4: Mini-Games
:srcds
echo (%time%) Start
start /wait C:\SRCDS\CSS-4\srcds.exe -console -game cstrike +ip 67.214.162.117 -port 27015 +maxplayers 25 +exec server.cfg -tickrate 66 +fps_max 300 -tvdisable +map mg_smash_cannonsz -nobots -secure -timeout 60   
echo (%time%) Restart
goto srcds 


Admin Mods: MetaMod, SourceMod, SRCDS DoS Protect (MetaMod), Stripper:Source, SteamBans

The Problem: I brought online a new server for my community, the one provided above specifically, and for the past week I've experienced several "hard" crashes on my server which has resulted in the machine resetting on it's own accord. As near as I can tell, it's SRCDS faulting and causing the crash. Here is a report from the event viewer:

PHP Code:

Faulting application name: srcds.exe, version: 0.0.0.0, time stamp: 0x444d93d2
Faulting module name: steamclient.dll, version: 3.0.0.1, time stamp: 0x4820b946
Exception code: 0xc0000005
Fault offset: 0x000345c6
Faulting process id: 0xa60
Faulting application start time: 0x01ca4e8983d1cfa0
Faulting application path: C:\SRCDS\CSS-4\srcds.exe
Faulting module path: C:\SRCDS\CSS-4\bin\steamclient.dll
Report Id: 37257970-ba7e-11de-bd04-001a4d5cb492 


It presents me with the following error after the server restarts:

PHP Code:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000000a (0xfffffffffff946c0, 0x0000000000000002, 0x0000000000000000, 0xfffff8000169cb35). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101709-13509-01. 


Unfortunately the MEMORY.DMP file is currently 266mb, so I'm not able to post it anywhere. I'm at a loss as to what's causing it specifically in SRCDS, and more importunately, why SRCDS would be hard faulting my system. Could anyone point me in the right direction as to go about handling/resolving this issue? I can provided additional information if needed.

[realchamp]

Try to unload all plugins on it.

[thetwistedpanda]

I've already attempted that, there's no plug-in that I can single out that's causing the hard crashes. I run the same configuration on 5 other servers and do not have any problems.

[realchamp]

(10-18-2009, 07:40 AM)thetwistedpanda Wrote:  I've already attempted that, there's no plug-in that I can single out that's causing the hard crashes. I run the same configuration on 5 other servers and do not have any problems.

Try to set a different port instead of 27015.

[thetwistedpanda]

Sorry but I fail to see how changing an arbitrary port would have any effect what so ever on a memory fault.

[loopyman]

Try it, it wont hurt any.

[realchamp]

And btw. isn't x64 = 64bit?

[BloodAngel]

(10-18-2009, 10:13 AM)realchamp Wrote:  And btw. isn't x64 = 64bit?

Yes it is

Have you changed its priority and/or affinity?

[realchamp]

I do believe 64bit has some compatility problems with SRCDS, after my experience.

[loopyman]

Yea, since srcds only runs in 32bit.

[dualcore1289]

Should'nt matter, when I ran my GSP, I ran nothing but x64, the performance is better, even on 32 bit applications. I had no issues what so ever. I mean it is always possible, but highly doubt it. . . I would try a fresh install of the server personally. . .

[thetwistedpanda]

Since SRCDS still runs in 32bit mode, there shouldn't' be any issues concerning the actual operating system being x64. My current provider runs x64 on all the machines and no one else seems to have reported an "incompatibility" which is causing windows to issue STOP 0x0000000a errors. While I haven't touched the Affinity, I was running in High priority for some time; yet swapping back to Normal made no differences in the crashes (already ruled that one out).

As I ran out of solutions and given the initial responses I received here, I decided just to scrap the idea of fixing it, got a copy of firedaemon, and am now running the servers a process to negate this issue.