Disable the HLT instruction in w2k, freeze problem on k7vza motherbaoard

  • Thread starter Thread starter Hello
  • Start date Start date
H

Hello

I recently updated an Athalon mother board ( ECS k7vza) to windows
2000 from win 98. The computer has started to freeze at random (no
keyboard no mouse no task manager). This used to happen under win 98
when I used a program called rain, the freeezing stopped when I
stopped using rain, and has been freeze free for nearly 2 years until
I updated to w2k.

Apparently the problem is the HLT instruction windows 2000 issues. Is
there anyway can disable this instruction?


http://www.pricelessware.org/2004/PL2004SYSTEMUTILITIES.htm#CpuCooler

"Rain issues the HLT (halt) command during periods of inactivity and
the processor remains cooler because of it. Plain and simple. The
benefits of running a cooler CPU are that it reduces power
consumption, can extend laptop battery life, and prevents CPU heat
related freezes and lockups. More important, it can prolong the life
of your PC. NOTES: Windows NT/2000/XP don't need CPU cooling programs
that execute HLT instructions (such as Rain) because they already
comes with an option to execute HLT instructions when the CPU is
idle."
 
Anyone know how to disable the c2 or c3 pci?


http://vcool.occludo.net/ Notes



"also Anyway here's what I found in the Athlon Revision docs:



14 Processors with Half-Frequency Multipliers May Hang Upon Wake-up
from Disconnect
Products Affected: A4, A5, A6, A7, A9
Suggested Workaround: Do not use the C2 or C3 ACPI states on
processors that run at a nominal operating frequency generated with a
half-frequency multiplier. This can be accomplished by having the BIOS
not declare C2 or C3 support to the operating system in the Fixed ACPI
 
Both these items you have dredged
up are NOT OS issues, they are BIOS issues and must
be addressed by the motherboard manufacturer (if
indeed they are your problem-which they likely are not-you
probably just have some defective component and/or hardware
incompatibility).
 
Both these items you have dredged
up are NOT OS issues, they are BIOS issues and must
be addressed by the motherboard manufacturer (if
indeed they are your problem-which they likely are not-you
probably just have some defective component and/or hardware
incompatibility).
Click to expand...

You seem to have missed the main point. I had no problems for ~2 years
under win98 se,I had problems starting with the install of w2k. That's
and OS problem


Thank you for the SWAG
 
Hello said:
You seem to have missed the main point. I had no problems for ~2 years
under win98 se,I had problems starting with the install of w2k. That's
and OS problem
Click to expand...

Nope.

Hardware problem.

W2K is MUCH more picky about hardware than W9X ever was.
Things that'll trip up W2K just get masked/overlooked/ignored
by lesser OS's.

You are just learning about it the hard way.
Thank you for the SWAG
Click to expand...

You're welcome.

Start examining your hardware, if you ever wanna
get this thing running.

Update your BIOS like the other post said.
 
Update your BIOS like the other post said.
Click to expand...

This reference seems to describe the problem

http://support.microsoft.com/defaul...port/kb/articles/Q270/7/15.ASP&NoWebContent=1

I was once again getting lockups, then implemented this procedure. So
far so good. The BIOS has nothing to do with it, good guess, but a
SWAG not the less

~~~~~ Reference~~~~~

Start Registry Editor (Regedt32.exe).
Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management

On the Edit menu, click Add Value, and then add the following registry
value:
Value name: LargePageMinimum
Data type: REG_DWORD
Radix: Hexadecimal
Data value: 0xffffffff

Quit Registry Editor.
Restart the computer.
 
georgess said:
This reference seems to describe the problem

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:
80/support/kb/articles/Q270/7/15.ASP&NoWebContent=1

I was once again getting lockups, then implemented this procedure. So
far so good. The BIOS has nothing to do with it, good guess, but a
SWAG not the less
Click to expand...

WHY are you so opposed to updating your BIOS
that you will use the "fix" described
in the MSKB (which looks like it'll impact overall system
peformance) INSTEAD of updating your BIOS, a newer version of which
which may well contain a fix for the problem?

Whatever...
 
Back
Top