ARRRGGGG!!!!! Halflife Crashes

ltk007

Banned
Feb 24, 2000
6,209
1
0
More specifically, Counterstrike lockups. :|:|:|:(:(:(

I'll be playing CS for a minute or two, maybe up to 5. Well anyway, I'll play, then all the sudden it will freeze and it will repeat a sound over and over again. I have to hit the reset button to get out of it finally. I don't know what the hell it is, I think it might be the via agp or the 4n1 drivers or maybe even sound but I have no idea for sure. My specs are

Athlon 700
Abit KA7
128mb PC133 2-2-2 Infineon
Geforce DDR
SB live value
Win2k Pro (just wiped)
Liveware 3
Direct X 8 (it does the same thing on 7)
Nvidia beta 6.49 (I've tried det 3 and 7.17 too)



HELP ME!!!!!!!!!
 

joburnet

Senior member
Aug 1, 2000
722
0
0
I have the EXACT same problem! I thought it might have been a patch that I added to my registry for soldier of fortune or that I upgraded to a v3 2000 pci but i'm really not sure. I played it for months with no problems but recently it's been doing that too me. It's actually not bad cause I get more work done but it can be annoying. Let me know if you find out why. Thanks
 

rhinox99

Golden Member
Sep 5, 2000
1,559
0
0
My comp does the problem you are describing when I enable "fast writes" in the bios. You might want to check whether that option is on or off.
 

Nih

Senior member
Sep 3, 2000
334
0
0
You could try going into the bios, setting agp 4x, and setting the agp driving control to manual. Set the value for da, ea, or e7. Whichever works best, gl :)
 

Subversal

Senior member
Aug 22, 2000
617
0
0
I had that problem... but it due to my high FSB (110) Mine is at 100 now and I have had no lockups at all. Could also try disabling fastwrites/sidebanding/ and setting at agp 2x. Also decrease your graphics hardware acceleration a notch to see if the lockups persist. And if your Geforce DDR is OC'ed set it down a few notches there as well. Also check to see what is sharing your vid cards IRQ, should be sharing with one thing (PCI steering, etc).
 

ltk007

Banned
Feb 24, 2000
6,209
1
0
Ok, nothing OCed, I've tried every imaginable fastwrites/agp setting and still no luck :(

I think I might have fixed it actually, I am used D3D instead of openGL. I should've tried that earlier.
 

jimmygates

Platinum Member
Sep 4, 2000
2,134
2
81
I get the same problem. I'm running Win2k with Detonator 6.31. :(


Could it be Windows 2k acting up?




-Jimbo
 

Subversal

Senior member
Aug 22, 2000
617
0
0
Did you just install Win2k? If so disable ACPI... you might have to do another clean install of Win2k. Just switch from a SCPI HAL to Standard PC HAL:

programs/administrive tool/computer management/device manager/computer then change ACPIPC to STANDARDPC

or when first setting up Win2k:


1. Hit F5 when prompted for additional drivers (during the first phase of Win2k setup). A screen will pop up where you can select from a variety of installation modes.

2. Hit F7 when prompted for additional drivers. Install mode will silently switch to standard PC(taken from Floyd).



 

Silvah

Junior Member
Feb 7, 2001
3
0
0
I have the same problem
Athlon 600
Biostar M7MKA
128 RAM
SB Live! Value
GeForce 2MX
 

gtd2000

Platinum Member
Oct 22, 1999
2,731
0
76
Actually I started to get this problem last night........only after I installed Liveware 3 for ME.
That could be the problem - was running perfectly before I made the "upgrade" :|
 

Kungfu72

Member
Apr 10, 2000
78
0
0
Long shot:

I had the same problem. If it isn't heat, check to see what your IO voltage on your mobo is set to. My K7M was defaulted to 3.4v from the factory, and my GF2 did not like it. Frequent lockups. I set the IO voltage jumper to 3.3v and VOILA! Problem solved.

Something worth checking.

 

mcbiff

Senior member
Feb 6, 2000
385
0
0
Put your SB Live in a slot where it doesn't share an IRQ. Usually #2 works fine.
 

paruhd0x

Diamond Member
Apr 2, 2000
3,100
0
0
Reinstall your sound drivers. (Get the latest drivers) If you are overclocked... go to normal speed and try playing for a while. Get the latest Detonator Drivers from Nvidia

I know for a fact that the Detonator drivers will either crash HL or your whole system if you alt-tab while in game.

If it is IRQ problems..

Disable ACPI

FOR WINDOWS 2000!

Under Windows 2000 you can disable ACPI from within Windows as follows:
[*]Go to Device Manager and select Computer -> Properties of ACPI PC
[*]Click the driver Tab and choose Update Driver
[*]When the wizard gets to the "What do you want the wizard to do?" page select "Display a list of the known drivers..."
[*]Then "Show all hardware of this device class"
[*]Then select "Standard PC"
[*]Reboot the machine
[*]When Windows 2000 restarts it'll redetect most of the hardware in your machine again and reassign IRQ's to them, turning off ACPI.
Note: If you installed Windows with ACPI enabled in the BIOS, and then you disable ACPI using the BIOS, you may need to do a fresh install of Windows!

FOR WINDOWS9x!
Link
 

Bartman

Senior member
Oct 9, 1999
750
0
0
I had this same problem. I did EVERYTHING, reinstall, update, format... what ever it dien't fix it. Come to find out the problem was on my internet connection sharing box, for some reason win98 ICS was crashing HL and causeing other problems. I got a Linksys router and everything is fine now.

Bart
 

Mem

Lifer
Apr 23, 2000
21,476
13
81
Working fine in my system,using 4.25a Via drivers, 6.50 Nvidia drivers,Win98 ,I wonder if this is a Win2000 problem,anyway there is a new patch coming soon 1.1.0.6 so don`t loose hope. Forgot to say using OpenGL.

:)
 

mpg

Banned
Nov 23, 2000
938
0
0
I had this problem when I was overclocking. Maybe AMD runs their CPUs above their expected specs?
 

gtd2000

Platinum Member
Oct 22, 1999
2,731
0
76
OK - my problem is now fixed....don't know if it will work for you?

1. I uninstalled Half-life, then deleted all the directories manually.
2. I the defragged my HD with Norton Speeddisk.
3. Then reinstalled HL
4. Installed the HL Update patch
5. Installed the CS 1.0 file
6. in the sounds config option I enabled EAX

Working perfectly now :)

Remember ...........I only had this problem "AFTER" I updated my liveware to Liveware for ME