NS2 locks up my computer when I click Exit and needs to be hard shut down
Xao
Join Date: 2012-12-12 Member: 174840Members
Join Date: 2012-12-12 Member: 174840Members
See title for my problem, it has happened 3 times in 3 days, click exit, computer freezes, wait 1 min, can't ctrl alt delete, can't alt F4, computer stops responding, hold down power button etc.
Never had this problem before but I've missed the last 10 or so builds.
Specs:
Win7, 3.4k intel, 7970, 12 gig or ram, no weird programs running in background except...last fm...since I last played and never had this problem, not sure what else to add or whether a crash log is submitted because the computer hangs up.
Never had this problem before but I've missed the last 10 or so builds.
Specs:
Win7, 3.4k intel, 7970, 12 gig or ram, no weird programs running in background except...last fm...since I last played and never had this problem, not sure what else to add or whether a crash log is submitted because the computer hangs up.
Comments
Use borderless window mode for those games, also you had like 8 mods running at least two of them are outdated. Look in the menu under mods which are activated by you.
a ps/2 works on a deepper level (with IRQ) and may react where usb fails.
ns2 itself does not run in kernel mode and can not hang the kernel. (If windows freezes, the kernel 'hangs.')
So the list is as follows:
* its something usb, if ps/2 works.
* drivers.
* software running under kernel. (like many AV, firewall)
* hardware.
* corrupt windows installation. (run sfc /scannow)
- check your event viewer.
- While ns2 can not hang the kernel, a vid driver can. ns2 however can wrongly use the vid driver. The vid driver should not allow it to be wrongly used. (In this example, both are at fault)
So basicly you need more info & need to look into your windows environment.
sfc found nothing, I'll see how no mods goes over the weekend, thanks for the help.
For starters, every game is different, and the spec requirements of NS2 is an example of how it is not exempt from this rule.
Not to mention, drivers not only can conflict with preexisting games in negative ways, (making some older ones unusable for instance) but they can also be tweaked to behave differently PER GAME, mostly by using what are commonly referred to as "profiles". This allows for very specific settings and methods per game.
I recommend what others have suggested:
Check windows event viewer and see if you can pull a hint out of that one (like error codes etc)
Rollback the recent drivers
Then inspect the next possible culprits like failing hardware etc
edit: this is IF the symptom continues after you removed all dem mods!
I'll be in some games later and see if it hangs at all, thanks for the help.
If I wait long enough eventually it closes.
Note it can be ANY driver. (or ns2 pushing a driver wrong, which is as I said before, a fault of both ns2 and the driver).
* Really try with ps/2 keyboard if you can.
* Does winkey + L (to lock your pc) work?
* Another idea is to do nothing..wait...long. Lets say 15 mins. Does it suddenly react? (If not I hope the prolonged time will produce errors in the event viewer log).
Why does waiting matter? lets ASSUME something.
If for some reason a harddisk is in sleepmode it would take a few seconds to wake up. I doubt it is the case for you, but its a example of why I suggest to wait.
Ctrl alt delete close ns2 process. This happens a lot to me now too. I also get black screen no loading sometimes when connecting to a map after loading.
This is a good example. Your computer does not freeze so it does not hang the kernel. It just hangs the game. There is a good chance that it would react to input with ps/2.
Windows still thinks that on that screen where the game hangs, it should priorise keyboard/mouse input of the game. On the other screen, you do not have that issue.
That is how it should work and you should be able to loadup anything you want by that screen to kill the game easy.
Sometimes I do kill it, but if I'm feeling patient enough I like to let the game close itself properly.
I could easily attribute 500-600 hours of "Game Played" in steam to ns2.exe not shutting down and sitting there until I get back later on at night, go to run it and it tells me it's already active.