cs:s randomly crashing

[kionay]

when i look your laptop up i see it come with windows 8, did you install windows 7 yourself? if so this may be a driver issue

have resource monitor running then start CS:S, join WCS, wait for it to crash, use the graphs to determine if there's partiular problems running WCS

when did this problem first occur? do you remember what you did beforehand that might've caused it?

you could try running in safe mode and see if it crashes, then it might be another problem on your computer closing it in the background (not to say safe mode is a guarentee it won't run, some have been able to bypass and run in safe mode, but the vast majority won't)

it doesn't sound like a crash so much as a program is just forcing CS:S to close, there are some advanced ways to see the calls on your computer to what might be closing it, but i haven't messed with those in quite some time, really i'm hoping it's some silly easy thing to overlook and not a major "core abstract Steam/Graphics DLL corrupt deep in some files that you have to just KNOW the problem already to fix it" kind of thing

hate those kinds of things

[brett friggin favre]

1. no, it came with windows 7, factory fresh from newegg. i suspect i got it cheap because they were pushing out the win 7 units to make room for the win 8 version. also i updated my graphics driver, no change

2. didn't see anything special, but i'm not sure what i'd be looking for. took a ss right after it happened, attaching it.

3. it started 2 days before i posted this, didn't make any changes but i hadn't played wcs in a while.

4. couldn't get it to run in safe mode.

5. yeah, sounds like that would suck

[ZERO]

If you suspect any OS issue try in cmd: sfc /verifyonly

It it comes back with an issue then do sfc /scannow

[brett friggin favre]

If you suspect any OS issue try in cmd: sfc /verifyonly

It it comes back with an issue then do sfc /scannow

didn't suspect any, but ran it anyway. no integrity violations

[SCRIBBLE]

Revert to last stable gfx driver before the crashes began and see if that helps. Might be several generations old but some of these new updates create conflict that may or may not be fixed. Another idea... I had an issue with a realtek HD/3d audio manager causing CSS to crash with no error - the fix to this issue being the realtek audio could not be ran in conjunction with CSS. In my case the realtek is superfluous due to other components.

[brett friggin favre]

i hadn't updated the drivers since around february, toshiba doesn't like to let us update with any drivers except their own, took me a while to figure out how to update them without any newer toshiba drivers to see if that fixed it. it was perfectly stable for ~10-11 months though.

[SCRIBBLE]

I meant PCI 3D audio, not realtek. Also check the gfx card manufacturers forum's to see what is the most popular signed driver for that particular game (could be a driver signed from a year ago).

[kionay]

does it crash when you spectate in the WCS server or do you have to be playing?

and how do you mean you couldn't get it to run in safe mode?

[brett friggin favre]

does it crash when you spectate in the WCS server or do you have to be playing?

and how do you mean you couldn't get it to run in safe mode?

Spectating also makes it crash. In safe mode, the game would launch momentarily, steam would recognize me as in-game, but apparently it closed immediately after because no window ever popped up or anything, and after a few more seconds steam recognized me as not in-game

[brett friggin favre]

i've been playing on other servers and i can't seem to get it to crash...looks like just ibis servers

update: it just crashed on another server. of course.