Complete PC freeze/crash
lam3
Join Date: 2011-05-25 Member: 100613Members
Hey. I have recently put together a new system, which in principle runs NS perfectly apart from the gamma ramp issue, but there's a huge problem.
It randomly freezes, sound starts clipping and there's no way to get out of it, my only aid being the physical reset button on my PC.
<b>[edit]It's really completely frozen, even NumLock light doesn't respond[/edit]</b>
I have no stability issues in any form with my system. Including stress tests.
This does not happen in Half Life 1.
My specs are as follows:
Intel i5-2500K @ 4,2GHz
MSI P67-GD65
AMD Radeon 6950HD
Kingston 2x4GB DDR3 @ 1600MT (using Intel's XMP)
Samsung Spinpoint F3 1TB
Windows 7 Enterprise 64 bit
My video drivers are up to date, have reinstalled them already.
All relevant components are on the MoBo's QVL list.
Annoyingly it does run on my old other system (physically located elsewhere, can't just play NS on that one instead), with these specs:
Intel E8400 @ 3,0
Asus P5KPL
nVidia 8800GTS 512MB
OCZ DDR2 2x1GB 667
Samsung Spinpoint F1 1TB
Windows 7 Enterprise 32 bit
I WOULD APPRECIATE YOUR HELP SO MUCH. It's so annoying since I basically have to have nothing running during NS otherwise I risk losing that data.
Can anyone shed some light? Is there any community left? I sure hope so.
Thanks in advance
It randomly freezes, sound starts clipping and there's no way to get out of it, my only aid being the physical reset button on my PC.
<b>[edit]It's really completely frozen, even NumLock light doesn't respond[/edit]</b>
I have no stability issues in any form with my system. Including stress tests.
This does not happen in Half Life 1.
My specs are as follows:
Intel i5-2500K @ 4,2GHz
MSI P67-GD65
AMD Radeon 6950HD
Kingston 2x4GB DDR3 @ 1600MT (using Intel's XMP)
Samsung Spinpoint F3 1TB
Windows 7 Enterprise 64 bit
My video drivers are up to date, have reinstalled them already.
All relevant components are on the MoBo's QVL list.
Annoyingly it does run on my old other system (physically located elsewhere, can't just play NS on that one instead), with these specs:
Intel E8400 @ 3,0
Asus P5KPL
nVidia 8800GTS 512MB
OCZ DDR2 2x1GB 667
Samsung Spinpoint F1 1TB
Windows 7 Enterprise 32 bit
I WOULD APPRECIATE YOUR HELP SO MUCH. It's so annoying since I basically have to have nothing running during NS otherwise I risk losing that data.
Can anyone shed some light? Is there any community left? I sure hope so.
Thanks in advance
Comments
...
This does not happen in Half Life 1.<!--QuoteEnd--></div><!--QuoteEEnd-->
Nope, it's completely random. Happens crouching in a vent, happens jumping, happens on custom maps, happens on official maps, happens on NS, happens on CO.
however, all other games have no problems at all.
the only thing i could possibly link it to is either the psu or something ingame that's screwing up the card, for with my old HD 3870, i have no problem.
idkwot?
specs:
cpu: amd phenom ii x3 720 2.8ghz (4th core unlocked, overclocked @ 3.3ghz)
ram: 4x1gb G-Skill 1333mhz
psu: antec truepower trio 650w
sound: x-fi platinum with drive bay i-face
My specs are as follows:
Intel i5-2500K @ 4,2GHz<!--QuoteEnd--></div><!--QuoteEEnd-->
That is your problem right there. Try running your CPU at stock speed. I would bet money your problem will be solved.
I am having exactly same problem as OP. My comp specs are almost the same too, but I am so far using with CPU stock speed.
Tried reinstalling and stuff, but the game just keeps crashing?
Found any solutions ?
I use OpenGL. (res 1920x1080, 32bit) My graphic card is GB 6950 HD
Bet I could try those other renderers but they are just so horrible compared to OGL.
Anyways last night I found a solution to my problem at least and I thought I'd post it here since I've seen this thread so many times when I've searched about the issue.
What I did was set hl.exe(ns running) to only use one core of my processor. To do this you need to go to task manager, and on the processes tab find hl.exe. Right click it and choose "set affinity" and then uncheck all but core #0. This worked for me so if you're still struggling with this issue it's worth a try!!