Re: Perpetual re:booting

From: Larry Samuels (larry_at_mvps.org)
Date: 08/29/04


Date: Sun, 29 Aug 2004 18:23:32 -0400

It sounds like the Prescott CPU problem caused by systembuilders installing
Prescott processors on boards which do not fully support them. As a result,
the processor microcode is not updating correctly.

The quick test is to boot into a safe build and rename
%windir%\system32\drivers\update.sys so that it does not load. This should
allow the machine to boot up with whatever microcode update the BIOS has
supplied. Then if a kernel debugger is attached a !cpuinfo or a !cpuid and
a "rdmsr 8b" will tell you the processor family/model/stepping and microcode
update id.

If you don't have a kernel debugger attached, the Intel Processor Frequency
ID Utility will provide this information:

http://support.intel.com/support/processors/tools/frequencyid/

The microcode version is identified by this utility as "CPU Revision"

So for this CPU:
. CPU Family = 15
. CPU Model = 3
. CPU Stepping = 4

The microcode revision should be at least 8 (if it is zero, then no
microcode update was installed at all):
. CPU Revision = 8

Renaming update.sys is NOT a fix--it will simply allow you to identify the
problem, boot the pc, and remove SP2 until you can obtain a bios update from
the motherboard manufacturer to properly support the Prescott processor.

-- 
Larry Samuels MS-MVP  (Windows-Shell/User)
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone
Unofficial FAQ for Windows Server 2003 at
http://pelos.us/SERVER.htm
"Bill Fraser" <willandcarol@av.eastlink.ca> wrote in message 
news:%23u8B2cGjEHA.2556@TK2MSFTNGP10.phx.gbl...
> Dennis:
> I have exactly the same problem.  See my post "XP won't run with SP2" 
> about
> 16 entries or so above yours.  Microsoft MVP thinks it's a hardware 
> problem,
> so I have sent my sustem specs in hopes he can sort it out.
> Let me know if you find an answer, and I'll do the same.
> Bill Fraser.
> "Dennis" <anonymous@discussions.microsoft.com> wrote in message
> news:177401c48c4d$8ce5b010$a301280a@phx.gbl...
>> after downloading S2 I cannot login itno Widows.  I get
>> the logo Windows XP Professional, but then it goes black
>> longer than usual and no login, instead reboots again and
>> again.... suggestion
>
> 


Relevant Pages

  • Re: How does this make you feel?
    ... >>>primitives to implement, say, a memcpy just as efficiently as microcode ... > The work is offloaded from the programmer in any case - this type of code ... library macros need updating for new CPU products, ... And designing such instruction such that they don't ...
    (comp.arch)
  • [patch 10/11] [PATCH 10/11] x86: Major refactoring.
    ... However, that is exclusive, there is only one vendor specific module ... A CPU vendor check makes sure only the corect ... you will be able to update the microcode on ... static void microcode_init_cpu ...
    (Linux-Kernel)
  • Re: [opensuse] swap not available
    ... The CPU was two 15 inch ... run the instruction set the applications would use. ... simulate several single-user IBM 360's and single-user IBM ... 704's by just switching microcode with each context switch. ...
    (SuSE)
  • Re: Linux Kernel Microcode Question
    ... microcode update on the fly, i.e. while the OS is running with no need ... rebooting or otherwise resetting the CPU causes the ... it does matter which Intel CPUs you have. ... The driver selects the ...
    (Linux-Kernel)
  • RE: Linux Kernel Microcode Question
    ... A microcode update is used to correct errata in the processor, ... > * it signals the kernel driver to release any buffers it may hold ... >Does it matter what type of Intel CPU you have? ...
    (Linux-Kernel)