RC5 Keyrate hit in 2k?

[Dennis]

Installed Windows 2000 on my 1Ghz Duron yesterday, had been running Windows ME. Anyway, with Windows ME, when I was on the computer just surfing the net and light stuff like that, my keyrate dropped some, but not too much (2-300Kkeys). With Windows 2k, whenever I'm on here, my keyrate drops from 3.57Mkeys to 2.3Mkeys on some blocks, but other blocks come out at 3.4Mkeys???....Don't have much running, only ICQ, Callwave & Internet Exploder...Callwave stays running all the time. The keyrate just seems to be inconsistent when I'm on here, whereas with ME it dropped some, but stayed consistent.

Would upping the priority of the process help? If so, how do I make the priority I set stick?

Thanks...pretty new to Win2k, but love the stability so far.

Dennis

 

[Train]

Win2k is supposed to have the best keyrate of the MS OS's it has always been the fastest from me, though some poeple have had problems finding processes that take away from your keyrate, look for a thread by DanC in which a few poeple posted tips for getting the best keyrate out of Win2k

 

[JonB]

The Win2k task manager is your first clue as to where your clock cycles are going. After at least an hour of continuous use, open the Task Manager, click on the elapsed CPU Time header and see what has been using clock cycles. Of course, DNETC will be at the top, but look at what else may be there. If System Idle Processes has accumulated any significant time (more than 1 percent of the DNETC time - Mine is 0.14%), then you have a problem.

Also, the client will pause when some programs run, like the defrag utility or your Anti-virus program. A quick check of your client log file will nail that one.

I have used Win2k for a long time now and haven't observed this problem, but each install seems to be just a little different.

 

[Viztech]

Here is that Win 2K thread
Task manager is your best friend for finding these things in NT/2K.

viz

 

[Dennis]

Thanks, every time I check, dnet is at 99%...oh well, got a much bigger problem killing my keyrate right now...posted in the Operating systems forum...here's a copy/paste, in case you have any ideas...

________________________________________________________________________________________________
Wierd problem. Happened twice now. Computer locks up solid, nothing will respond, not even power-button on case, reset button works. After I hit reset, the computer will NOT detect my hard drives, just sits at the screen saying "Detecting IDE Devices." I have to power it down, then back up, and everything's fine after that. Had been running Windows ME on this setup for a few weeks with no problems.

System is as follows:
Abit KT7 Motherboard
Duron 600 @ 1Ghz
128MB CAS3 PC133 (Mushkin)
Maxtor 30GB Hard Drive (7,200 rpm)
Maxtor 4.3GB Hard Drive (4,300 rpm)
Voodoo3 2k
SIIG PCI Sound Card
Kingston Network Card
Tekram DC390 SCSI2 Card

I've checked and the hard drives are jumpered properly, both are on the same ATA-66 cable on the primary port.

Any ideas? I'm not sure what to try next.

Thanks,

Dennis
_______________________________________________________________________________________________


Again, thanks for any help.

 

[JimMc]

W2K is very tough on overclocked systems, more so than 98. Not sure about ME, it was such a buggy POS I dumped it before forming any conclusions. What temps are you getting on your machine? Have you tried dropping the speed () a little to see if the freezes disappear?

 

[Fingers]

i have had that problem before and it ended up that my ide cables vibrated loose, and i had to re plug them in, and it took care of it for me. I dunno about you, but that may be a pssibility but if i were to put money on it, yo've overclocked too far and your just not stabl. Try runnign your duron at 950 or 900 and see if that takes care of it.

 

[Dennis]

Thanks for the advice...I actually bumped the speed down to 900 early this morning....hasn't happened again, yet, but this problem is very intermittent, so I'll give it a while.

I have another question...how accurate is the voltage readout on these motherboards??? I have mine set to 1.85V, but it reads out 1.98V. The processor was pre-tested and guaranteed for stable operation at 1Ghz, 1.85V....but if I try to lower the voltage to where it actually reads 1.85V, it is unstable. The motherboard has NOT been modified (I checked).

My temps run 36-37 idle and about 41-42 with RC5 or Prime95 running. First thing I checked was the IDE cables...unplugged and replugged all of them.....

Is there a reason that Win2k lists both my drives as being SCSI? They aren't, they are IDE, I know that on the KT7-RAID, the HighPoint ports are considered SCSI by Windows, but this is a plain KT7 motherboard I have. My 30GB drive is listed in Device Manager as a "Maxtor 5 3073U6 SCSI Disk Device"

I have installed the latest Via Win2k IDE drivers, also, and have updated my BIOS to the latest Beta (WZ). The problem first happened before I flashed the BIOS and I had UL on here.

Thanks,

Dennis

 

[Viztech]

I would see how it runs out at 900 before getting too worried. I like to not run my OCed systems on the ragged edge. When I see signs of trouble, it's time to up the core voltage or back of the mhz.

Speaking of core voltage, that does seem a bit strange. Do you have a windows monitoring program that is giving you that result, the system BIOS, or both?

Best of luck. That will be a nice machine when you get it done.

viz

 

[JimMc]

Are you running the Via 4.26 drivers? They have a W2K bug, still beta, IDE's are reported as SCSI. I'd ease off the throttle a little and see if some of your problems go away.

 

[Dennis]

Well, just got the system up and running (again). I'm sure it's the Via 1426 drivers I was running that was causing the problem.

Even clocked down to 600Mhz and running my PC133 memory at 100Mhz, I got corrupt files. Unfortunately, I did not realize that 1426 of the 4in1's were beta. Am running the Microsoft driver that came with 2k right now (for a few days) just to make sure it doesn't happen again, then I'll install 1425 and see how it all goes. Figured it out when I was getting corrupt system files running at all defaults that it must be a driver....oh well, at least I can install Win2k and all my software in a matter of minutes after all the practice I got!


About the voltage, both the PC Health section in the BIOS and any temp/voltage monitoring software I've used all report the same thing, showing vCore .13V higher that where it's set....

Thanks for the info,

Dennis