Shoutbox

Counter Strike Crashes My Machine! - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Skype & Technology (/forumdisplay.php?fid=9)
+---- Forum: Tech Talk (/forumdisplay.php?fid=17)
+----- Thread: Counter Strike Crashes My Machine! (/showthread.php?tid=78937)

Counter Strike Crashes My Machine! by WaqasTariq on 11-11-2007 at 08:59 AM

Hello,

Everytime i try starting CS I get a BSOD, now it can not be the processor / memory over heating as i thought of it my seelf to, as I have just turned on my machine after 10-14 hours and launched CS it crashed...

I think the problem it the when I put the CS Video into OPENGL and 32 BITS... or even SOFTWARE 32BITS it crashes...

It might work on 16BITS but I have to try that....

also can anyone tell me... what does these mean in any games...

OPENGL =  ???
SOFTWARE = ???
D3D = ???

my computer specs are in my signature....

please anyone I need help.... also to note is that I used to play CS on this same machine (pir) and it was working Ok, and when I bought CS last morning the troubles started.


*EDIT* ok now it crashed in 16BIT mode to so it doesnt work at all...

the BSOD says ... PAGE_FAULT_IN_NONPAGED_AREA


RE: Counter Strike Crashes My Machine! by vikke on 11-11-2007 at 09:06 AM

Try updating your GPU drivers, they are most likely the problem. If you got a Nvidia card, download your drivers from http://www.nvidia.com/.

OpenGL, Software, Direct3D are three different render engines. I recommend reading about them on Wikipedia. Software is the only engine that doesn't use your graphic card, that's why it's slow and the outcome is bad.

I would recommend using 16 bits instead of 32 bits, because you can see through smoke-grenades with no fps-drops. You won't notice any other difference using 16 bits.


RE: Counter Strike Crashes My Machine! by Mike on 11-11-2007 at 09:24 AM

First do what vikee suggested (update your GPU drivers).

If that doesn't work, then go in steam -> right click CS: S -> Properties -> Set launch parameters for this game -> Type "-dxlevel 8" -> OK.
See if that solves your problem.


RE: Counter Strike Crashes My Machine! by Vilkku on 11-11-2007 at 09:29 AM

Did it ever work on that specific machine?

Edit: :<


RE: Counter Strike Crashes My Machine! by vikke on 11-11-2007 at 09:34 AM

quote:
Originally posted by Vilkku
Did it ever work on that specific machine?
quote:
Originally posted by WaqasTariq
I used to play CS on this same machine

RE: RE: Counter Strike Crashes My Machine! by WaqasTariq on 11-11-2007 at 10:01 AM

quote:
Originally posted by vikke
Try updating your GPU drivers, they are most likely the problem. If you got a Nvidia card, download your drivers from http://www.nvidia.com/.

OpenGL, Software, Direct3D are three different render engines. I recommend reading about them on Wikipedia. Software is the only engine that doesn't use your graphic card, that's why it's slow and the outcome is bad.

I would recommend using 16 bits instead of 32 bits, because you can see through smoke-grenades with no fps-drops. You won't notice any other difference using 16 bits.

I have a built-in graphics "Intel Graphics Media Accelerator 950 with (e) "

and it is upto date.

and 16 BITS is also crashing :'(
RE: RE: Counter Strike Crashes My Machine! by WaqasTariq on 11-11-2007 at 10:05 AM

quote:
Originally posted by Mike
First do what vikee suggested (update your GPU drivers).

If that doesn't work, then go in steam -> right click CS: S -> Properties -> Set launch parameters for this game -> Type "-dxlevel 8" -> OK.
See if that solves your problem.

Ok I will do that but first i think I might have figured the problem...


My local intranet CS servers require and OLD software version of sXe Injected v3.9 to be run before the CS is launched...

I just close sXe Injected v3.9 and CS is working fi9 in OPENGL 32BITS

what should I do??? i can not play on my local intranet with out first launching sXe Injected v3.9....
RE: Counter Strike Crashes My Machine! by Discrate on 11-11-2007 at 10:33 AM

It is most likely your drivers update them.