win2003 R2 - BSOD on framework 2.0 install

Please help, I'm getting BSOD every time when I try to install .NET Framework
2.0 on win2003 server

OS: Win2003 R2 Standard x64 Edition, SP2


few last lines from install log file
C:\Documents and Settings\Administrator\Local
Settings\Temp\dd_netfx20UI1792.txt :

MSI (s) (E0:40) [22:48:10:468]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI131.tmp, Entrypoint: ConfigureNativeImage
06/08/07 22:48:10 DDSet_Status: LANGID: 1033
06/08/07 22:48:10 DDSet_Entry: ConfigureNativeImage started
06/08/07 22:48:10 DDSet_Status: Deferred or Commit action for NGEN
06/08/07 22:48:10 DDSet_Status: CustomActionData:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
"System.Data, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo;2937856
06/08/07 22:48:10 DDSet_Status: Running Command Line:
C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
"System.Data, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo
06/08/07 22:48:10 DDSet_Status: LANGID: 1033
Installing assembly System.Data, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089
Compiling 1 assembly:



MINIDUMP analysys:
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing
MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while
processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while
processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while
processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000002
Arg2: fffff80000075bc0
Arg3: 00000000f2002000
Arg4: 0000000000000863

Debugging Details:
------------------


BUGCHECK_STR: 0x9C_AuthenticAMD

CUSTOMER_CRASH_COUNT: 9

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

PROCESS_NAME: mscorsvw.exe

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff80001041690

STACK_TEXT:
fffff800`00075b88 fffff800`0080ef4c : 00000000`0000009c 00000000`00000002
fffff800`00075bc0 00000000`f2002000 : nt!KeBugCheckEx
fffff800`00075b90 fffff800`01040937 : 00000000`00000000 00000000`00000000
00000000`1cc4d010 fffff800`00075ef0 : hal!HalHandleMcheck+0x12c
fffff800`00075cf0 fffff800`01040775 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
fffff800`00075e70 00000000`7814e5d2 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
00000000`0012bc88 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : 0x7814e5d2


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxMcheckAbort+77
fffff800`01040937 488d8c2400010000 lea rcx,[rsp+100h]

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KxMcheckAbort+77

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45d69a26

FAILURE_BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77

BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77

Followup: MachineOwner

Tony
Sat Jun 09 07:54:31 CDT 2007

I'm affraid, I don't know anything about this, but I found a document that
may be of some value to you:

http://download.intel.com/design/Itanium/Downloads/24927802.pdf


Tony. . .


"Anton Gougevsky" <Anton Gougevsky@discussions.microsoft.com> wrote in
message news:CCD89933-7624-4D00-928B-67A4A03BC53D@microsoft.com...
> Please help, I'm getting BSOD every time when I try to install .NET
Framework
> 2.0 on win2003 server
>
> OS: Win2003 R2 Standard x64 Edition, SP2
>
>
> few last lines from install log file
> C:\Documents and Settings\Administrator\Local
> Settings\Temp\dd_netfx20UI1792.txt :
>
> MSI (s) (E0:40) [22:48:10:468]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI131.tmp, Entrypoint: ConfigureNativeImage
> 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> 06/08/07 22:48:10 DDSet_Entry: ConfigureNativeImage started
> 06/08/07 22:48:10 DDSet_Status: Deferred or Commit action for NGEN
> 06/08/07 22:48:10 DDSet_Status: CustomActionData:
> C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> "System.Data, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo;2937856
> 06/08/07 22:48:10 DDSet_Status: Running Command Line:
> C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> "System.Data, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo
> 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> Installing assembly System.Data, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089
> Compiling 1 assembly:
>
>
>
> MINIDUMP analysys:
> kd> !analyze -v
>
****************************************************************************
***
> *
> *
> * Bugcheck Analysis
> *
> *
> *
>
****************************************************************************
***
>
> MACHINE_CHECK_EXCEPTION (9c)
> A fatal Machine Check Exception has occurred.
> KeBugCheckEx parameters;
> x86 Processors
> If the processor has ONLY MCE feature available (For example Intel
> Pentium), the parameters are:
> 1 - Low 32 bits of P5_MC_TYPE MSR
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of P5_MC_ADDR MSR
> 4 - Low 32 bits of P5_MC_ADDR MSR
> If the processor also has MCA feature available (For example Intel
> Pentium Pro), the parameters are:
> 1 - Bank number
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
error
> 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
error
> IA64 Processors
> 1 - Bugcheck Type
> 1 - MCA_ASSERT
> 2 - MCA_GET_STATEINFO
> SAL returned an error for SAL_GET_STATEINFO while
processing
> MCA.
> 3 - MCA_CLEAR_STATEINFO
> SAL returned an error for SAL_CLEAR_STATEINFO while
> processing MCA.
> 4 - MCA_FATAL
> FW reported a fatal MCA.
> 5 - MCA_NONFATAL
> SAL reported a recoverable MCA and we don't support
currently
> support recovery or SAL generated an MCA and then couldn't
> produce an error record.
> 0xB - INIT_ASSERT
> 0xC - INIT_GET_STATEINFO
> SAL returned an error for SAL_GET_STATEINFO while
> processing INIT event.
> 0xD - INIT_CLEAR_STATEINFO
> SAL returned an error for SAL_CLEAR_STATEINFO while
> processing INIT event.
> 0xE - INIT_FATAL
> Not used.
> 2 - Address of log
> 3 - Size of log
> 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
> AMD64 Processors
> 1 - Bank number
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
error
> 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
error
> Arguments:
> Arg1: 0000000000000002
> Arg2: fffff80000075bc0
> Arg3: 00000000f2002000
> Arg4: 0000000000000863
>
> Debugging Details:
> ------------------
>
>
> BUGCHECK_STR: 0x9C_AuthenticAMD
>
> CUSTOMER_CRASH_COUNT: 9
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
>
> PROCESS_NAME: mscorsvw.exe
>
> CURRENT_IRQL: f
>
> LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff80001041690
>
> STACK_TEXT:
> fffff800`00075b88 fffff800`0080ef4c : 00000000`0000009c 00000000`00000002
> fffff800`00075bc0 00000000`f2002000 : nt!KeBugCheckEx
> fffff800`00075b90 fffff800`01040937 : 00000000`00000000 00000000`00000000
> 00000000`1cc4d010 fffff800`00075ef0 : hal!HalHandleMcheck+0x12c
> fffff800`00075cf0 fffff800`01040775 : 00000000`00000000 00000000`00000000
> 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
> fffff800`00075e70 00000000`7814e5d2 : 00000000`00000000 00000000`00000000
> 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
> 00000000`0012bc88 00000000`00000000 : 00000000`00000000 00000000`00000000
> 00000000`00000000 00000000`00000000 : 0x7814e5d2
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> nt!KxMcheckAbort+77
> fffff800`01040937 488d8c2400010000 lea rcx,[rsp+100h]
>
> SYMBOL_STACK_INDEX: 2
>
> SYMBOL_NAME: nt!KxMcheckAbort+77
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: nt
>
> IMAGE_NAME: ntoskrnl.exe
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 45d69a26
>
> FAILURE_BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
>
> BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
>
> Followup: MachineOwner

Chris
Sat Jun 09 15:39:01 CDT 2007

Tony,

I am working with Anton on the issue. It is killing us... it is on an AMD
64 Optron processor...
Chris

"Tony Sperling" wrote:

> I'm affraid, I don't know anything about this, but I found a document that
> may be of some value to you:
>
> http://download.intel.com/design/Itanium/Downloads/24927802.pdf
>
>
> Tony. . .
>
>
> "Anton Gougevsky" <Anton Gougevsky@discussions.microsoft.com> wrote in
> message news:CCD89933-7624-4D00-928B-67A4A03BC53D@microsoft.com...
> > Please help, I'm getting BSOD every time when I try to install .NET
> Framework
> > 2.0 on win2003 server
> >
> > OS: Win2003 R2 Standard x64 Edition, SP2
> >
> >
> > few last lines from install log file
> > C:\Documents and Settings\Administrator\Local
> > Settings\Temp\dd_netfx20UI1792.txt :
> >
> > MSI (s) (E0:40) [22:48:10:468]: Invoking remote custom action. DLL:
> > C:\WINDOWS\Installer\MSI131.tmp, Entrypoint: ConfigureNativeImage
> > 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> > 06/08/07 22:48:10 DDSet_Entry: ConfigureNativeImage started
> > 06/08/07 22:48:10 DDSet_Status: Deferred or Commit action for NGEN
> > 06/08/07 22:48:10 DDSet_Status: CustomActionData:
> > C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> > "System.Data, Version=2.0.0.0, Culture=neutral,
> > PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo;2937856
> > 06/08/07 22:48:10 DDSet_Status: Running Command Line:
> > C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> > "System.Data, Version=2.0.0.0, Culture=neutral,
> > PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo
> > 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> > Installing assembly System.Data, Version=2.0.0.0, Culture=neutral,
> > PublicKeyToken=b77a5c561934e089
> > Compiling 1 assembly:
> >
> >
> >
> > MINIDUMP analysys:
> > kd> !analyze -v
> >
> ****************************************************************************
> ***
> > *
> > *
> > * Bugcheck Analysis
> > *
> > *
> > *
> >
> ****************************************************************************
> ***
> >
> > MACHINE_CHECK_EXCEPTION (9c)
> > A fatal Machine Check Exception has occurred.
> > KeBugCheckEx parameters;
> > x86 Processors
> > If the processor has ONLY MCE feature available (For example Intel
> > Pentium), the parameters are:
> > 1 - Low 32 bits of P5_MC_TYPE MSR
> > 2 - Address of MCA_EXCEPTION structure
> > 3 - High 32 bits of P5_MC_ADDR MSR
> > 4 - Low 32 bits of P5_MC_ADDR MSR
> > If the processor also has MCA feature available (For example Intel
> > Pentium Pro), the parameters are:
> > 1 - Bank number
> > 2 - Address of MCA_EXCEPTION structure
> > 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> > 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> > IA64 Processors
> > 1 - Bugcheck Type
> > 1 - MCA_ASSERT
> > 2 - MCA_GET_STATEINFO
> > SAL returned an error for SAL_GET_STATEINFO while
> processing
> > MCA.
> > 3 - MCA_CLEAR_STATEINFO
> > SAL returned an error for SAL_CLEAR_STATEINFO while
> > processing MCA.
> > 4 - MCA_FATAL
> > FW reported a fatal MCA.
> > 5 - MCA_NONFATAL
> > SAL reported a recoverable MCA and we don't support
> currently
> > support recovery or SAL generated an MCA and then couldn't
> > produce an error record.
> > 0xB - INIT_ASSERT
> > 0xC - INIT_GET_STATEINFO
> > SAL returned an error for SAL_GET_STATEINFO while
> > processing INIT event.
> > 0xD - INIT_CLEAR_STATEINFO
> > SAL returned an error for SAL_CLEAR_STATEINFO while
> > processing INIT event.
> > 0xE - INIT_FATAL
> > Not used.
> > 2 - Address of log
> > 3 - Size of log
> > 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
> > AMD64 Processors
> > 1 - Bank number
> > 2 - Address of MCA_EXCEPTION structure
> > 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> > 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> > Arguments:
> > Arg1: 0000000000000002
> > Arg2: fffff80000075bc0
> > Arg3: 00000000f2002000
> > Arg4: 0000000000000863
> >
> > Debugging Details:
> > ------------------
> >
> >
> > BUGCHECK_STR: 0x9C_AuthenticAMD
> >
> > CUSTOMER_CRASH_COUNT: 9
> >
> > DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
> >
> > PROCESS_NAME: mscorsvw.exe
> >
> > CURRENT_IRQL: f
> >
> > LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff80001041690
> >
> > STACK_TEXT:
> > fffff800`00075b88 fffff800`0080ef4c : 00000000`0000009c 00000000`00000002
> > fffff800`00075bc0 00000000`f2002000 : nt!KeBugCheckEx
> > fffff800`00075b90 fffff800`01040937 : 00000000`00000000 00000000`00000000
> > 00000000`1cc4d010 fffff800`00075ef0 : hal!HalHandleMcheck+0x12c
> > fffff800`00075cf0 fffff800`01040775 : 00000000`00000000 00000000`00000000
> > 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
> > fffff800`00075e70 00000000`7814e5d2 : 00000000`00000000 00000000`00000000
> > 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
> > 00000000`0012bc88 00000000`00000000 : 00000000`00000000 00000000`00000000
> > 00000000`00000000 00000000`00000000 : 0x7814e5d2
> >
> >
> > STACK_COMMAND: kb
> >
> > FOLLOWUP_IP:
> > nt!KxMcheckAbort+77
> > fffff800`01040937 488d8c2400010000 lea rcx,[rsp+100h]
> >
> > SYMBOL_STACK_INDEX: 2
> >
> > SYMBOL_NAME: nt!KxMcheckAbort+77
> >
> > FOLLOWUP_NAME: MachineOwner
> >
> > MODULE_NAME: nt
> >
> > IMAGE_NAME: ntoskrnl.exe
> >
> > DEBUG_FLR_IMAGE_TIMESTAMP: 45d69a26
> >
> > FAILURE_BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
> >
> > BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
> >
> > Followup: MachineOwner
>
>
>

Tony
Sat Jun 09 17:46:08 CDT 2007

Well, 'MCA' seems to be a recurring statement in the log and I was curious
as to what it could be referring to - there were lots of options, so I typed
in the term "Processor MCA" in Yahoo and I got lots of hits - I thought the
articel looked 'deep and thorough and not knowing what was your actual
processor hoped that something in there could ring the bell for you.

The framework installed without issues for me and there have been few and
old reports here about it - if I'm not mistaken there have been considerable
more issues with people having trouble with the actual installer, which
could also be what you're experiencing.

Have you tested the memory - are you seing other weird behaviour with this
machine? It could be Hardware, you know.


Tony. . .


"Chris" <Chris @discussions.microsoft.com> wrote in message
news:5AFFC6B6-1F23-4FBB-8372-552846CA4F24@microsoft.com...
> Tony,
>
> I am working with Anton on the issue. It is killing us... it is on an
AMD
> 64 Optron processor...
> Chris
>
> "Tony Sperling" wrote:
>
> > I'm affraid, I don't know anything about this, but I found a document
that
> > may be of some value to you:
> >
> > http://download.intel.com/design/Itanium/Downloads/24927802.pdf
> >
> >
> > Tony. . .
> >
> >
> > "Anton Gougevsky" <Anton Gougevsky@discussions.microsoft.com> wrote in
> > message news:CCD89933-7624-4D00-928B-67A4A03BC53D@microsoft.com...
> > > Please help, I'm getting BSOD every time when I try to install .NET
> > Framework
> > > 2.0 on win2003 server
> > >
> > > OS: Win2003 R2 Standard x64 Edition, SP2
> > >
> > >
> > > few last lines from install log file
> > > C:\Documents and Settings\Administrator\Local
> > > Settings\Temp\dd_netfx20UI1792.txt :
> > >
> > > MSI (s) (E0:40) [22:48:10:468]: Invoking remote custom action. DLL:
> > > C:\WINDOWS\Installer\MSI131.tmp, Entrypoint: ConfigureNativeImage
> > > 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> > > 06/08/07 22:48:10 DDSet_Entry: ConfigureNativeImage started
> > > 06/08/07 22:48:10 DDSet_Status: Deferred or Commit action for NGEN
> > > 06/08/07 22:48:10 DDSet_Status: CustomActionData:
> > > C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> > > "System.Data, Version=2.0.0.0, Culture=neutral,
> > > PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo;2937856
> > > 06/08/07 22:48:10 DDSet_Status: Running Command Line:
> > > C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> > > "System.Data, Version=2.0.0.0, Culture=neutral,
> > > PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo
> > > 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> > > Installing assembly System.Data, Version=2.0.0.0, Culture=neutral,
> > > PublicKeyToken=b77a5c561934e089
> > > Compiling 1 assembly:
> > >
> > >
> > >
> > > MINIDUMP analysys:
> > > kd> !analyze -v
> > >
> >
****************************************************************************
> > ***
> > > *
> > > *
> > > * Bugcheck Analysis
> > > *
> > > *
> > > *
> > >
> >
****************************************************************************
> > ***
> > >
> > > MACHINE_CHECK_EXCEPTION (9c)
> > > A fatal Machine Check Exception has occurred.
> > > KeBugCheckEx parameters;
> > > x86 Processors
> > > If the processor has ONLY MCE feature available (For example
Intel
> > > Pentium), the parameters are:
> > > 1 - Low 32 bits of P5_MC_TYPE MSR
> > > 2 - Address of MCA_EXCEPTION structure
> > > 3 - High 32 bits of P5_MC_ADDR MSR
> > > 4 - Low 32 bits of P5_MC_ADDR MSR
> > > If the processor also has MCA feature available (For example
Intel
> > > Pentium Pro), the parameters are:
> > > 1 - Bank number
> > > 2 - Address of MCA_EXCEPTION structure
> > > 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had
the
> > error
> > > 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the
> > error
> > > IA64 Processors
> > > 1 - Bugcheck Type
> > > 1 - MCA_ASSERT
> > > 2 - MCA_GET_STATEINFO
> > > SAL returned an error for SAL_GET_STATEINFO while
> > processing
> > > MCA.
> > > 3 - MCA_CLEAR_STATEINFO
> > > SAL returned an error for SAL_CLEAR_STATEINFO while
> > > processing MCA.
> > > 4 - MCA_FATAL
> > > FW reported a fatal MCA.
> > > 5 - MCA_NONFATAL
> > > SAL reported a recoverable MCA and we don't support
> > currently
> > > support recovery or SAL generated an MCA and then
couldn't
> > > produce an error record.
> > > 0xB - INIT_ASSERT
> > > 0xC - INIT_GET_STATEINFO
> > > SAL returned an error for SAL_GET_STATEINFO while
> > > processing INIT event.
> > > 0xD - INIT_CLEAR_STATEINFO
> > > SAL returned an error for SAL_CLEAR_STATEINFO while
> > > processing INIT event.
> > > 0xE - INIT_FATAL
> > > Not used.
> > > 2 - Address of log
> > > 3 - Size of log
> > > 4 - Error code in the case of x_GET_STATEINFO or
x_CLEAR_STATEINFO
> > > AMD64 Processors
> > > 1 - Bank number
> > > 2 - Address of MCA_EXCEPTION structure
> > > 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had
the
> > error
> > > 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the
> > error
> > > Arguments:
> > > Arg1: 0000000000000002
> > > Arg2: fffff80000075bc0
> > > Arg3: 00000000f2002000
> > > Arg4: 0000000000000863
> > >
> > > Debugging Details:
> > > ------------------
> > >
> > >
> > > BUGCHECK_STR: 0x9C_AuthenticAMD
> > >
> > > CUSTOMER_CRASH_COUNT: 9
> > >
> > > DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
> > >
> > > PROCESS_NAME: mscorsvw.exe
> > >
> > > CURRENT_IRQL: f
> > >
> > > LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff80001041690
> > >
> > > STACK_TEXT:
> > > fffff800`00075b88 fffff800`0080ef4c : 00000000`0000009c
00000000`00000002
> > > fffff800`00075bc0 00000000`f2002000 : nt!KeBugCheckEx
> > > fffff800`00075b90 fffff800`01040937 : 00000000`00000000
00000000`00000000
> > > 00000000`1cc4d010 fffff800`00075ef0 : hal!HalHandleMcheck+0x12c
> > > fffff800`00075cf0 fffff800`01040775 : 00000000`00000000
00000000`00000000
> > > 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
> > > fffff800`00075e70 00000000`7814e5d2 : 00000000`00000000
00000000`00000000
> > > 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
> > > 00000000`0012bc88 00000000`00000000 : 00000000`00000000
00000000`00000000
> > > 00000000`00000000 00000000`00000000 : 0x7814e5d2
> > >
> > >
> > > STACK_COMMAND: kb
> > >
> > > FOLLOWUP_IP:
> > > nt!KxMcheckAbort+77
> > > fffff800`01040937 488d8c2400010000 lea rcx,[rsp+100h]
> > >
> > > SYMBOL_STACK_INDEX: 2
> > >
> > > SYMBOL_NAME: nt!KxMcheckAbort+77
> > >
> > > FOLLOWUP_NAME: MachineOwner
> > >
> > > MODULE_NAME: nt
> > >
> > > IMAGE_NAME: ntoskrnl.exe
> > >
> > > DEBUG_FLR_IMAGE_TIMESTAMP: 45d69a26
> > >
> > > FAILURE_BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
> > >
> > > BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
> > >
> > > Followup: MachineOwner
> >
> >
> >

John
Mon Jun 11 19:06:52 CDT 2007

As a secondary track, you can get free assistance from Microsoft to install
this. I had a similar problem with mine and got a very sharp technician
and after about 5-6 thoughtful, not rote, steps the problem got solved. You
could get a case started while you are working with Chris.


"Anton Gougevsky" <Anton Gougevsky@discussions.microsoft.com> wrote in
message news:CCD89933-7624-4D00-928B-67A4A03BC53D@microsoft.com...
> Please help, I'm getting BSOD every time when I try to install .NET
> Framework
> 2.0 on win2003 server
>
> OS: Win2003 R2 Standard x64 Edition, SP2
>
>
> few last lines from install log file
> C:\Documents and Settings\Administrator\Local
> Settings\Temp\dd_netfx20UI1792.txt :
>
> MSI (s) (E0:40) [22:48:10:468]: Invoking remote custom action. DLL:
> C:\WINDOWS\Installer\MSI131.tmp, Entrypoint: ConfigureNativeImage
> 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> 06/08/07 22:48:10 DDSet_Entry: ConfigureNativeImage started
> 06/08/07 22:48:10 DDSet_Status: Deferred or Commit action for NGEN
> 06/08/07 22:48:10 DDSet_Status: CustomActionData:
> C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> "System.Data, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo;2937856
> 06/08/07 22:48:10 DDSet_Status: Running Command Line:
> C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ngen.exe install
> "System.Data, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089" /NoDependencies /nologo
> 06/08/07 22:48:10 DDSet_Status: LANGID: 1033
> Installing assembly System.Data, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=b77a5c561934e089
> Compiling 1 assembly:
>
>
>
> MINIDUMP analysys:
> kd> !analyze -v
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> MACHINE_CHECK_EXCEPTION (9c)
> A fatal Machine Check Exception has occurred.
> KeBugCheckEx parameters;
> x86 Processors
> If the processor has ONLY MCE feature available (For example Intel
> Pentium), the parameters are:
> 1 - Low 32 bits of P5_MC_TYPE MSR
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of P5_MC_ADDR MSR
> 4 - Low 32 bits of P5_MC_ADDR MSR
> If the processor also has MCA feature available (For example Intel
> Pentium Pro), the parameters are:
> 1 - Bank number
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> IA64 Processors
> 1 - Bugcheck Type
> 1 - MCA_ASSERT
> 2 - MCA_GET_STATEINFO
> SAL returned an error for SAL_GET_STATEINFO while
> processing
> MCA.
> 3 - MCA_CLEAR_STATEINFO
> SAL returned an error for SAL_CLEAR_STATEINFO while
> processing MCA.
> 4 - MCA_FATAL
> FW reported a fatal MCA.
> 5 - MCA_NONFATAL
> SAL reported a recoverable MCA and we don't support
> currently
> support recovery or SAL generated an MCA and then couldn't
> produce an error record.
> 0xB - INIT_ASSERT
> 0xC - INIT_GET_STATEINFO
> SAL returned an error for SAL_GET_STATEINFO while
> processing INIT event.
> 0xD - INIT_CLEAR_STATEINFO
> SAL returned an error for SAL_CLEAR_STATEINFO while
> processing INIT event.
> 0xE - INIT_FATAL
> Not used.
> 2 - Address of log
> 3 - Size of log
> 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
> AMD64 Processors
> 1 - Bank number
> 2 - Address of MCA_EXCEPTION structure
> 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the
> error
> Arguments:
> Arg1: 0000000000000002
> Arg2: fffff80000075bc0
> Arg3: 00000000f2002000
> Arg4: 0000000000000863
>
> Debugging Details:
> ------------------
>
>
> BUGCHECK_STR: 0x9C_AuthenticAMD
>
> CUSTOMER_CRASH_COUNT: 9
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
>
> PROCESS_NAME: mscorsvw.exe
>
> CURRENT_IRQL: f
>
> LAST_CONTROL_TRANSFER: from fffff8000080ef4c to fffff80001041690
>
> STACK_TEXT:
> fffff800`00075b88 fffff800`0080ef4c : 00000000`0000009c 00000000`00000002
> fffff800`00075bc0 00000000`f2002000 : nt!KeBugCheckEx
> fffff800`00075b90 fffff800`01040937 : 00000000`00000000 00000000`00000000
> 00000000`1cc4d010 fffff800`00075ef0 : hal!HalHandleMcheck+0x12c
> fffff800`00075cf0 fffff800`01040775 : 00000000`00000000 00000000`00000000
> 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
> fffff800`00075e70 00000000`7814e5d2 : 00000000`00000000 00000000`00000000
> 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
> 00000000`0012bc88 00000000`00000000 : 00000000`00000000 00000000`00000000
> 00000000`00000000 00000000`00000000 : 0x7814e5d2
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_IP:
> nt!KxMcheckAbort+77
> fffff800`01040937 488d8c2400010000 lea rcx,[rsp+100h]
>
> SYMBOL_STACK_INDEX: 2
>
> SYMBOL_NAME: nt!KxMcheckAbort+77
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: nt
>
> IMAGE_NAME: ntoskrnl.exe
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 45d69a26
>
> FAILURE_BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
>
> BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
>
> Followup: MachineOwner