Win2k: lockups/BSODs in games + other weird stuff

[Psych0]

PROBLEM #1

I am having very annoying problems with Windows 2000 Profressional lately. I am using a P3-600e overclocked to 800 with a GeForce DDR, a Soundblaster live value, 128 megs of PC-133 RAM, 20 gigs of HD space and connect to the net using ADSL.

First off, the most annoying and baffling problem. In terms of my OS in general with programs, it seems pretty damn solid.

But in games, I get lock ups. I get Blue Screens of Death and occasionally, I will simply be booted out of a game. 90% of the time, these 3 symptoms happen in Counter-strike, and it frusterates me to hell because I play it a lot. Lately I have mostly been getting either booted out of the game, or more commonly, the blue screen. Lately, I will be playing along for about 5-15 mins, sometimes more (but not usually more than 1 hour) and BOOM, I will see a blue screen and it will usually say something about 0x000x000 or something and then reffers to the following:

A. tcp.sys or B. ntkernel

I just finished trying out Counter-strike and it gave me a BSOD with some key information. It mentioned Kmixer.sys and nv4_mini.sys. Did a search on Kmixer.sys and it appears to be in

c:\winnt\system32\drivers
and
c:\winnt\system32\\dllcache

the nv4_mini.sys is a GeForce file because I found it in a directory where I store my GeForce drivers. It's also in c:\winnt\system32\drivers

I have tried turning my clockspeed down to 600 but that doesn't seem to help. The BIOS says the CPU is running at roughly 35c, in games i think it gets to around 44 or maybe a bit more but i have never seen it over 50 after intense game playing so I am pretty sure heat is not an issue (I am running it with the case off plus a fan is blowing onto the CPU).

I have the latest 6.18 win2k detonator drivers installed, as well as Liveware 3.0 for Win2k.
I have Direct x 7a installed (comes with win2k i think) and my drives have all been recently cleaned. I have made sure that most of my devices have their own IRQ, especially the video card and soundcard cause I heard that can DEFINATELY cause problems.

Does anyone have any specific BIOS tweaks for me? My video shadow in the bios is disabled as well as all the other shadowed stuff (I think thats what its called). Maybe my PC133 ram is doing something? AUugggh I just want win2k to act freaking normal in games!

PROBLEM #2

When I boot up, my volumn control and Audio HQ pop up quickly, but both my LAN connection and Internet connection (the icons) take like 2-3 mins to pop up on the toolbar and many programs don't seem to function or run UNTIL the connections are popped up. Outlook express seems to function, but programs like mIRC and Internet Explorer will semi-freeze until the icons pop up.

PROBLEM #3

I cannot seem to see my HP 8100 burner anymore, it shows my CD-ROM, but not my burner. I have checked the wiring, maybe I should reseed it again??


I am about to give up on Windows 2000 but i don't really go with ME yet cause I LIKED Win2k when it was running good.

HEEEELP!! Any help would be greatly appreciated!!

 

[paulip88]

I don't know any of this from personal experience, but I have heard some of the following on the forums:

First thing is that Counterstrike does not get along well with SP1. If you can uninstall SP1, that may solve the issue with CS.

Another thing that I have heard is that the newest Detonator drivers do not work well with the KT133 chipset, which is used for Durons and TBirds. In other words, the older drivers may run more stable, especially under Win2K.

When you say you can't see your burner anymore, are you saying that its not detected by your CDR software? If that's the case, there may be a software issue. THe wiring should be fine if the drive shows up in My Computer. You should check with the software company to see if there are any issues with their software and Win2K.

Hope this helps. If not, hopefully someone who has some direct experience with such problems can chime in and give a helping hand.

 

[icculus]

As far as the CDR goes, you might need to get yourself ASPI drivers for Win2000. I forget where they are, try adaptec's website.

 

[Mem]

Paulip88 is on the ball here about drivers ,this is from evga.com,


VIA KT133 and nVidia 6.18 Driver Problem - UPDATE!
Last week we repoted a problem with the KT133 AGP Chipset and the newest nVidia drivers v6.18. So, we will be releasing a new driver v6.20 that will correct this, but we wanted to let you know WHY this happened.

The ID codes on VIA's KX133 and KT133 are the same, but their features are not. When the 6.18 drivers install, they cannot tell the difference between the two chipsets because VIA did not give them different ID codes. nVidia is working on a way to tell the difference without VIA's ID codes, and a solution (the v6.20 drivers) will be available shortly.



--------------------------------------------------------------------------------

There seems to be some type of problem with the Detonator 3 drivers (v6.18, v6.11, and v6.16) and the VIA KT133 chipset.

This problem happens when you use the above Detonator 3 drivers on a motherboard with the VIA KT133 chipset. If you have this combination, either you will not be able to get into Windows, and/or you will receive garbage on the screen.

This problem is currently being investigated and a solution will be forthcoming.

In the meantime, Disabling Fast Writes in your motherboard BIOS has been shown to help emiminate or reduce this problem, and you may want to consider using driver v5.22 or v5.32 for customers with the e-GeForce2 MX (available from this page) until this problem is resolved.

More information will be posted as it becomes available".

I hope this helps.