black screen of death

hi!
i can install and play right after, but that s all.

if i quit and launch warsow again i get a black screen and can't even ctrl+alt+supp.
i launched foobar to check if it was only a gfx freeze. the sound stops too. it s a real computer crash.

i tried all the usual stuff, not uncheck the directory thing, run as admin, even installed as admin. no luck

all i can get is a game i need to install each time i want to play ... not cool.

got an asus G53JW win7 shitty i7, 8gig ram and nvidia460m. on some games i had troubles with the screen resolution (1366*768) but warsow set my native resolution by itself on install so i guess that s not it.
i tried low quality and default with same results.
didn't have 0.6 on this computer before. but all the usual Q3 engine games are working.

gotta tell i m not too keen on crashing my computer again and again just to try things.

any idea better than "did you try rebooting you pc?" is welcome. thx for the help!

g51j here
all is fine
any bios updates?
and it comes into years
mebe too dirty (overheating) or an old windows install that got messed up?

im using nv 301.24 btw

bios is the last asus gave us (so it s pretty old)
windows and all the system are pretty clean and stable. anytime i mess up something i put back a clean image of the system hard drive.

temperature is not the problem, i ve disassembled the entire computer at the beginning of summer just to clean it up. and it gets a lot hotter with sc2 or tribes ascend without any issue.

as for nvidia i m on v295.73 . i ll update to be sure but i guess we would see loads of posts if a driver version was causing crashes.

and as i said, i can play the game right after installing with no issue.
it s as if the installer could launch the game and i could not (even if i right click and select "exec as an admin", then it crashes the computer.

I have the black screen except when I run the _x86 exe file. Try that if nothing else works.

Do you change any settings when you start the game? They could be the problem.

Specifically, if you choose OpenAL sound and don't have OpenAL installed, this can happen. In that case, you can disable it in the cfg, or install OpenAL.
(updated 2012-09-29 22:38:59)

Specifically, if you choose OpenAL sound and don't have OpenAL installed, this can happen.

What kind of toy OS crashes on an attempt of loading non-existing shared library?

twbaker1 wrote:
I have the black screen except when I run the _x86 exe file. Try that if nothing else works.

i had given up on playing with this computer, thx for bumping my post and my motivation.
launching with the x86.exe made me crash too, but then i installed on a different disc (not C:) and the x86 worked \o/ the x64 still crashes my computer, but who cares!


thanks a lot mate, i can now go and get raped at wsw like it s 2007 again ;)


ps: thx to all who spent time looking to help me.
(updated 2012-10-06 17:00:03)

Out 64 bit windows binary is actually compiled on linux/mingw while 32bit one is visual studio build. So 64bit win is kinda hitnmiss ..

crizis wrote:
Out 64 bit windows binary is actually compiled on linux/mingw while 32bit one is visual studio build. So 64bit win is kinda hitnmiss ..

why not build that one with x64 vs.net ?

mingw is quite an abortion tbfh.

crizis wrote:
Out 64 bit windows binary is actually compiled on linux/mingw while 32bit one is visual studio build. So 64bit win is kinda hitnmiss ..

Is that why it takes forever and a day to load? I mean, I use it it thinking it'll make use of more RAM, but maybe I should just switch to the 32bit launcher.

UrLossMyGain wrote:

crizis wrote:
Out 64 bit windows binary is actually compiled on linux/mingw while 32bit one is visual studio build. So 64bit win is kinda hitnmiss ..

Is that why it takes forever and a day to load? I mean, I use it it thinking it'll make use of more RAM, but maybe I should just switch to the 32bit launcher.

Both versions precache a lot of GLSL shaders to avoid loading them at playtime, that could possibly the reason.. But there's nothing particular about the x64 version that'd slow it down considerably.

I may have exaggerated just a bit, it's only about 8 seconds from hitting the .exe to the main menu; that's better than any steam game lol. I'll stick with the 64bit launcher though, thanks for the info Vic!

learn_more wrote:

crizis wrote:
Out 64 bit windows binary is actually compiled on linux/mingw while 32bit one is visual studio build. So 64bit win is kinda hitnmiss ..

why not build that one with x64 vs.net ?

mingw is quite an abortion tbfh.

Express can only compile 32 bits and we wont pirate anything to compile wsw.

already told you, i got 2k8 and 2k10 pro legal.

crizis wrote:

learn_more wrote:

crizis wrote:
Out 64 bit windows binary is actually compiled on linux/mingw while 32bit one is visual studio build. So 64bit win is kinda hitnmiss ..

why not build that one with x64 vs.net ?

mingw is quite an abortion tbfh.

Express can only compile 32 bits and we wont pirate anything to compile wsw.

first link in google)
http://stackoverflow.com/questions/1865069/how-to-compile-a-64-bit-application-using-visual-c-2010-express

we're not using vc2010 because it's a pile of poop

then use 2k8 if you can't work with 10

learn_more: are you even allowed to distribute vc licenses?

not sure, but i could build?

FYI I have vs08, vs10, vs12 professional versions too.