Dump en W2003 Server

Buenas tardes,

Tengo un DL580 G" con W2003 Server con todas las actualizaciones al día.
Desde hace unos 6 meses, a razón de 4 o 5 al mes, se reinicia sólo
reportando
los errores que abajo se describen:


Microsoft (R) Windows Debugger Version 6.10.0000.151 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:
SRV*c:\sympriv*\\symbols\symbols;SRV*c:\sympub*http://msdl.microsoft.com/download/symbols
;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (6 procs) Free
x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_rtm.070216-1710
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Wed Jul 9 11:37:22.015 2008 (GMT+2)
System Uptime: 5 days 17:35:28.346
WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
Loading Kernel Symbols
..
Loading User Symbols

Loading unloaded module list
..
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, f773d2b0, be000300, 1008081f}

Debugger CompCtrlDb Connection::Open failed 80004005
This problem has been reported before and has a response.
Please connect to the following URL for details:

http://oca.microsoft.com/resredir.aspx?sid433&State=1

1: 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: 00000000
Arg2: f773d2b0
Arg3: be000300
Arg4: 1008081f

Debugging Details:


NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
-
1011111000000000000000110000000000010000000010000000100000011111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows
the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the
processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of
the
IA32_MCi_CTL register.

MISCV - IA32_MCi_MISC Register Valid
Indicates that the IA32_MCi_MISC register contains additional
information regarding the error. When clear, this flag indicates
that the IA32_MCi_MISC register is either not implemented or does
not contain additional information regarding the error.

ADDRV - IA32_MCi_ADDR register valid
Indicates that the IA32_MCi_ADDR register contains the address
where
the error occurred.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
_VAL_UC_EN_MISCV_ADDRV_PCC_BUSCONNERR_1F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_GenuineIntel

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

CURRENT_IRQL: 2

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x9C_GenuineIntel

BUCKET_ID: 0x9C_GenuineIntel


Todo apunta a un error de Hardware pero físicamente no hay nada en fallo y
en los diagnósticos del servidor, no aparece ningún error de Hardware..

Me podeis ayudar?

gracias

Has mirado la web de HP sobre ello?

Debugging Details:


NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Salu2!!
Javier Inglés
https://mvp.support.microsoft.com/p...B5567431B0
MS MVP, Windows Server-Directory Services



"Arturo" escribió en el mensaje
news:
> Buenas tardes,
>
> Tengo un DL580 G" con W2003 Server con todas las actualizaciones al día.
> Desde hace unos 6 meses, a razón de 4 o 5 al mes, se reinicia sólo
> reportando
> los errores que abajo se describen:
>
>
> Microsoft (R) Windows Debugger Version 6.10.0000.151 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Kernel Summary Dump File: Only kernel address space is available
>
> Symbol search path is:
> SRV*c:\sympriv*\\symbols\symbols;SRV*c:\sympub*http://msdl.microsoft.com/download/symbols
> ;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (6 procs) Free
> x86 compatible
> Product: Server, suite: Enterprise TerminalServer SingleUserTS
> Built by: 3790.srv03_sp2_rtm.070216-1710
> Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
> Debug session time: Wed Jul 9 11:37:22.015 2008 (GMT+2)
> System Uptime: 5 days 17:35:28.346
> WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
> WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
> Loading Kernel Symbols
> ..
> Loading User Symbols
>
> Loading unloaded module list
> ..
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 9C, {0, f773d2b0, be000300, 1008081f}
>
> Debugger CompCtrlDb Connection::Open failed 80004005
> This problem has been reported before and has a response.
> Please connect to the following URL for details:
>
> http://oca.microsoft.com/resredir.aspx?sid433&State=1
>
> 1: 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: 00000000
> Arg2: f773d2b0
> Arg3: be000300
> Arg4: 1008081f
>
> Debugging Details:
>
>
> NOTE: This is a hardware error. This error was reported by the CPU
> via Interrupt 18. This analysis will provide more information about
> the specific error. Please contact the manufacturer for additional
> information about this error and troubleshooting assistance.
>
> This error is documented in the following publication:
>
> - IA-32 Intel(r) Architecture Software Developer's Manual
> Volume 3: System Programming Guide
>
> Bit Mask:
>
> MA Model Specific MCA
> O ID Other Information Error Code Error Code
> VV SDP ___________|____________ _______|_______ _______|______
> AEUECRC| | | |
> LRCNVVC| | | |
> ^^^^^^^| | | |
> 6 5 4 3 2 1
> 3210987654321098765432109876543210987654321098765432109876543210
> -
> 1011111000000000000000110000000000010000000010000000100000011111
>
>
> VAL - MCi_STATUS register is valid
> Indicates that the information contained within the IA32_MCi_STATUS
> register is valid. When this flag is set, the processor follows
> the
> rules given for the OVER flag in the IA32_MCi_STATUS register when
> overwriting previously valid entries. The processor sets the VAL
> flag and software is responsible for clearing it.
>
> UC - Error Uncorrected
> Indicates that the processor did not or was not able to correct the
> error condition. When clear, this flag indicates that the
> processor
> was able to correct the error condition.
>
> EN - Error Enabled
> Indicates that the error was enabled by the associated EEj bit of
> the
> IA32_MCi_CTL register.
>
> MISCV - IA32_MCi_MISC Register Valid
> Indicates that the IA32_MCi_MISC register contains additional
> information regarding the error. When clear, this flag indicates
> that the IA32_MCi_MISC register is either not implemented or does
> not contain additional information regarding the error.
>
> ADDRV - IA32_MCi_ADDR register valid
> Indicates that the IA32_MCi_ADDR register contains the address
> where
> the error occurred.
>
> PCC - Processor Context Corrupt
> Indicates that the state of the processor might have been corrupted
> by the error condition detected and that reliable restarting of the
> processor may not be possible.
>
> BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
> These errors match the format 0000 1PPT RRRR IILL
>
>
>
> Concatenated Error Code:
> _VAL_UC_EN_MISCV_ADDRV_PCC_BUSCONNERR_1F
>
> This error code can be reported back to the manufacturer.
> They may be able to provide additional information based upon
> this error. All questions regarding STOP 0x9C should be
> directed to the hardware manufacturer.
>
> BUGCHECK_STR: 0x9C_GenuineIntel
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT
>
> PROCESS_NAME: Idle
>
> CURRENT_IRQL: 2
>
> MODULE_NAME: hardware
>
> IMAGE_NAME: hardware
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 0
>
> STACK_COMMAND: kb
>
> FAILURE_BUCKET_ID: 0x9C_GenuineIntel
>
> BUCKET_ID: 0x9C_GenuineIntel
>
>
> Todo apunta a un error de Hardware pero físicamente no hay nada en fallo y
> en los diagnósticos del servidor, no aparece ningún error de Hardware..
>
> Me podeis ayudar?
>
> gracias
>
>

Buenas tardes,

Tengo un DL580 G" con W2003 Server con todas las actualizaciones al día.
Desde hace unos 6 meses, a razón de 4 o 5 al mes, se reinicia sólo reportando
los errores que abajo se describen:


Microsoft (R) Windows Debugger Version 6.10.0000.151 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:
SRV*c:\sympriv*\\symbols\symbols;SRV*c:\sympub*http://msdl.microsoft.com/download/symbols
;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (6 procs) Free
x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_rtm.070216-1710
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Wed Jul 9 11:37:22.015 2008 (GMT+2)
System Uptime: 5 days 17:35:28.346
WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
Loading Kernel Symbols
..
Loading User Symbols

Loading unloaded module list
..
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, f773d2b0, be000300, 1008081f}

Debugger CompCtrlDb Connection::Open failed 80004005
This problem has been reported before and has a response.
Please connect to the following URL for details:

http://oca.microsoft.com/resredir.aspx?sid433&State=1

1: 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: 00000000
Arg2: f773d2b0
Arg3: be000300
Arg4: 1008081f

Debugging Details:


NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
-
1011111000000000000000110000000000010000000010000000100000011111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

MISCV - IA32_MCi_MISC Register Valid
Indicates that the IA32_MCi_MISC register contains additional
information regarding the error. When clear, this flag indicates
that the IA32_MCi_MISC register is either not implemented or does
not contain additional information regarding the error.

ADDRV - IA32_MCi_ADDR register valid
Indicates that the IA32_MCi_ADDR register contains the address where
the error occurred.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
_VAL_UC_EN_MISCV_ADDRV_PCC_BUSCONNERR_1F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_GenuineIntel

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

CURRENT_IRQL: 2

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x9C_GenuineIntel

BUCKET_ID: 0x9C_GenuineIntel


Todo apunta a un error de Hardware pero físicamente no hay nada en fallo y
en los diagnósticos del servidor, no aparece ningún error de Hardware..

Me podeis ayudar?

gracias

Hola,

Tal como apuntas, bugcheck 9C es un error de hardware, te recomendaria que
lo consultaras con HP porque normalmente no tiene que ver con el O.S., puede
ser causado por algun driver o memoria,etc..
Puedes intentar instalar el SP2 si todavia no lo tienes instalado para
tratar de actualizar todos los drivers, pero te recomiendo contactar con HP
para verificar el hardware:

http://welcome.hp.com/country/us/en...ct_us.html

Saludos

Alejandro Penado

MCSE 2003+Messaging


"Arturo" wrote:

> Buenas tardes,
>
> Tengo un DL580 G" con W2003 Server con todas las actualizaciones al día.
> Desde hace unos 6 meses, a razón de 4 o 5 al mes, se reinicia sólo reportando
> los errores que abajo se describen:
>
>
> Microsoft (R) Windows Debugger Version 6.10.0000.151 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Kernel Summary Dump File: Only kernel address space is available
>
> Symbol search path is:
> SRV*c:\sympriv*\\symbols\symbols;SRV*c:\sympub*http://msdl.microsoft.com/download/symbols
> ;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (6 procs) Free
> x86 compatible
> Product: Server, suite: Enterprise TerminalServer SingleUserTS
> Built by: 3790.srv03_sp2_rtm.070216-1710
> Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
> Debug session time: Wed Jul 9 11:37:22.015 2008 (GMT+2)
> System Uptime: 5 days 17:35:28.346
> WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
> WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
> Loading Kernel Symbols
> ..
> Loading User Symbols
>
> Loading unloaded module list
> ..
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 9C, {0, f773d2b0, be000300, 1008081f}
>
> Debugger CompCtrlDb Connection::Open failed 80004005
> This problem has been reported before and has a response.
> Please connect to the following URL for details:
>
> http://oca.microsoft.com/resredir.aspx?sid433&State=1
>
> 1: 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: 00000000
> Arg2: f773d2b0
> Arg3: be000300
> Arg4: 1008081f
>
> Debugging Details:
>
>
> NOTE: This is a hardware error. This error was reported by the CPU
> via Interrupt 18. This analysis will provide more information about
> the specific error. Please contact the manufacturer for additional
> information about this error and troubleshooting assistance.
>
> This error is documented in the following publication:
>
> - IA-32 Intel(r) Architecture Software Developer's Manual
> Volume 3: System Programming Guide
>
> Bit Mask:
>
> MA Model Specific MCA
> O ID Other Information Error Code Error Code
> VV SDP ___________|____________ _______|_______ _______|______
> AEUECRC| | | |
> LRCNVVC| | | |
> ^^^^^^^| | | |
> 6 5 4 3 2 1
> 3210987654321098765432109876543210987654321098765432109876543210
> -
> 1011111000000000000000110000000000010000000010000000100000011111
>
>
> VAL - MCi_STATUS register is valid
> Indicates that the information contained within the IA32_MCi_STATUS
> register is valid. When this flag is set, the processor follows the
> rules given for the OVER flag in the IA32_MCi_STATUS register when
> overwriting previously valid entries. The processor sets the VAL
> flag and software is responsible for clearing it.
>
> UC - Error Uncorrected
> Indicates that the processor did not or was not able to correct the
> error condition. When clear, this flag indicates that the processor
> was able to correct the error condition.
>
> EN - Error Enabled
> Indicates that the error was enabled by the associated EEj bit of the
> IA32_MCi_CTL register.
>
> MISCV - IA32_MCi_MISC Register Valid
> Indicates that the IA32_MCi_MISC register contains additional
> information regarding the error. When clear, this flag indicates
> that the IA32_MCi_MISC register is either not implemented or does
> not contain additional information regarding the error.
>
> ADDRV - IA32_MCi_ADDR register valid
> Indicates that the IA32_MCi_ADDR register contains the address where
> the error occurred.
>
> PCC - Processor Context Corrupt
> Indicates that the state of the processor might have been corrupted
> by the error condition detected and that reliable restarting of the
> processor may not be possible.
>
> BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
> These errors match the format 0000 1PPT RRRR IILL
>
>
>
> Concatenated Error Code:
> _VAL_UC_EN_MISCV_ADDRV_PCC_BUSCONNERR_1F
>
> This error code can be reported back to the manufacturer.
> They may be able to provide additional information based upon
> this error. All questions regarding STOP 0x9C should be
> directed to the hardware manufacturer.
>
> BUGCHECK_STR: 0x9C_GenuineIntel
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT
>
> PROCESS_NAME: Idle
>
> CURRENT_IRQL: 2
>
> MODULE_NAME: hardware
>
> IMAGE_NAME: hardware
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 0
>
> STACK_COMMAND: kb
>
> FAILURE_BUCKET_ID: 0x9C_GenuineIntel
>
> BUCKET_ID: 0x9C_GenuineIntel
>
>
> Todo apunta a un error de Hardware pero físicamente no hay nada en fallo y
> en los diagnósticos del servidor, no aparece ningún error de Hardware..
>
> Me podeis ayudar?
>
> gracias
>
>

Buenas tardes,

Tengo un DL580 G" con W2003 Server con todas las actualizaciones al día.
Desde hace unos 6 meses, a razón de 4 o 5 al mes, se reinicia sólo reportando
los errores que abajo se describen:


Microsoft (R) Windows Debugger Version 6.10.0000.151 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:
SRV*c:\sympriv*\\symbols\symbols;SRV*c:\sympub*http://msdl.microsoft.com/download/symbols
;srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (6 procs) Free
x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_rtm.070216-1710
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Wed Jul 9 11:37:22.015 2008 (GMT+2)
System Uptime: 5 days 17:35:28.346
WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
WARNING: Process directory table base 0052E000 doesn't match CR3 DFFEC020
Loading Kernel Symbols
..
Loading User Symbols

Loading unloaded module list
..
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, f773d2b0, be000300, 1008081f}

Debugger CompCtrlDb Connection::Open failed 80004005
This problem has been reported before and has a response.
Please connect to the following URL for details:

http://oca.microsoft.com/resredir.aspx?sid433&State=1

1: 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: 00000000
Arg2: f773d2b0
Arg3: be000300
Arg4: 1008081f

Debugging Details:


NOTE: This is a hardware error. This error was reported by the CPU
via Interrupt 18. This analysis will provide more information about
the specific error. Please contact the manufacturer for additional
information about this error and troubleshooting assistance.

This error is documented in the following publication:

- IA-32 Intel(r) Architecture Software Developer's Manual
Volume 3: System Programming Guide

Bit Mask:

MA Model Specific MCA
O ID Other Information Error Code Error Code
VV SDP ___________|____________ _______|_______ _______|______
AEUECRC| | | |
LRCNVVC| | | |
^^^^^^^| | | |
6 5 4 3 2 1
3210987654321098765432109876543210987654321098765432109876543210
-
1011111000000000000000110000000000010000000010000000100000011111


VAL - MCi_STATUS register is valid
Indicates that the information contained within the IA32_MCi_STATUS
register is valid. When this flag is set, the processor follows the
rules given for the OVER flag in the IA32_MCi_STATUS register when
overwriting previously valid entries. The processor sets the VAL
flag and software is responsible for clearing it.

UC - Error Uncorrected
Indicates that the processor did not or was not able to correct the
error condition. When clear, this flag indicates that the processor
was able to correct the error condition.

EN - Error Enabled
Indicates that the error was enabled by the associated EEj bit of the
IA32_MCi_CTL register.

MISCV - IA32_MCi_MISC Register Valid
Indicates that the IA32_MCi_MISC register contains additional
information regarding the error. When clear, this flag indicates
that the IA32_MCi_MISC register is either not implemented or does
not contain additional information regarding the error.

ADDRV - IA32_MCi_ADDR register valid
Indicates that the IA32_MCi_ADDR register contains the address where
the error occurred.

PCC - Processor Context Corrupt
Indicates that the state of the processor might have been corrupted
by the error condition detected and that reliable restarting of the
processor may not be possible.

BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err
These errors match the format 0000 1PPT RRRR IILL



Concatenated Error Code:
_VAL_UC_EN_MISCV_ADDRV_PCC_BUSCONNERR_1F

This error code can be reported back to the manufacturer.
They may be able to provide additional information based upon
this error. All questions regarding STOP 0x9C should be
directed to the hardware manufacturer.

BUGCHECK_STR: 0x9C_GenuineIntel

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: Idle

CURRENT_IRQL: 2

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x9C_GenuineIntel

BUCKET_ID: 0x9C_GenuineIntel


Todo apunta a un error de Hardware pero físicamente no hay nada en fallo y
en los diagnósticos del servidor, no aparece ningún error de Hardware..

Me podeis ayudar?

gracias