Darrellg
Wed Jan 18 20:11:58 CST 2006
Hello Stan,
Try opening a cmd prompt while setup is running and edit the boot.ini file.
Try adding numproc=1 so that we only try to load one proccessor
Also try adding /burnmemory=1024 to reduce the amount of RAM available.
restart setup and see if you get the error again.
Normally with this type of error message we are looking at hardware items.
If the error still happens, then we may have to simplify the system
What device adapters do you have in the pci slots is it only the Stealth? l
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<Thread-Topic: Need help with MACHINE_CHECK_EXCEPTION during x64 install or
r
<thread-index: AcYciXrSX/ZXVTwITk6Hk58X9QCLbQ==
<X-WBNR-Posting-Host: 64.1.164.137
<From: =?Utf-8?B?c21pdGNoZWxs?= <smitchell@discussions.microsoft.com>
<References: <07FA32E9-1CDF-4F57-8319-7084412A3E0B@microsoft.com>
<uDfHZMHHGHA.2440@TK2MSFTNGP14.phx.gbl>
<EB579264-1FF3-4BED-B1F1-B7B038351162@microsoft.com>
<#4TaXIIHGHA.1032@TK2MSFTNGP15.phx.gbl>
<Subject: Re: Need help with MACHINE_CHECK_EXCEPTION during x64 install or r
<Date: Wed, 18 Jan 2006 15:47:02 -0800
<Lines: 37
<Message-ID: <F72D9F18-2271-4EF1-B5EE-61D406D9A6C7@microsoft.com>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 8bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
<Newsgroups: microsoft.public.windows.64bit.general
<NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
<Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
<Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.64bit.general:27707
<X-Tomcat-NG: microsoft.public.windows.64bit.general
<
<Tony, .... thanks for the suggestions.
<
<Yes, the "memory check" is nothing more than the BIOS post. In the "old
<days" it used to at least write/read a pattern & verify it. I'll try
swapping
<the DIMMs if the BIOS update doesn't resolve the problem.
<
<I did flash the BIOS last year - but there is a newer one now. From the
<release notes its hard to say if it will address my problem. But that's
the
<first thing I'll try.
<
<The only new driver I found at AMD is: "AMD Opteronâ?¢ Processor PowerNow!
<Driver for Windows XP x64 Edition". It is a power management driver and
since
<it comes as an InstallShield package, it would seem that a basic install
<would have to be successful before it can be used.
<
<When I have some results, I'll post an update.
<
<Thanks,
<-Stan
<
<"Tony Sperling" wrote:
<
<> Hi, Stan.
<>
<> If the memory check you mention is the Boot Post, that isn't checking
memory
<> at all - it just counts up the memory that it can see.
<>
<> Even though it all works fine in 32bit, that's no guarantee that the
64bit
<> won't exercise different parts of the memory, specifically perhaps
during
<> the Boot phase. Although you have to have the sticks in specific sockets
one
<> fast way to check for this would be to swap the sticks in those sockets.
<>
<> But, memory might not be the first thing to suspect, do you have the
very
<> latest BIOS? And, do you have the 64bit processor driver from AMD
installed?
<> Those items have 'thrown' a few here, as I recall.
<>
<> Tony. . .
<