Server Crashed - Bell_sys

Hello,

I'm facing a redandent server crash, I downloaded windbg tool and
here
what got from !analyze -v command :


Loading Dump File [E:\Documents and Settings\acer\My
Documents\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available


Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/
download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (4 procs)
Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp1_gdr.070304-2232
Kernel base =3D 0x80800000 PsLoadedModuleList =3D 0x808af988
Debug session time: Mon Oct 29 13:15:46.757 2007 (GMT-4)
System Uptime: 7 days 11:15:19.376
WARNING: Process directory table base 00039000 doesn't match CR3
CFB01000
WARNING: Process directory table base 00039000 doesn't match CR3
CFB01000
Loading Kernel Symbols
.=2E.......................................................................=
.=2E=AD.....................................
Loading User Symbols


Loading unloaded module list
.=2E...
***************************************************************************=
=AD
****
*
*
*                        Bugcheck
Analysis                                    *
*
*
***************************************************************************=
=AD
****


Use !analyze -v to get detailed debugging information.


BugCheck 9C, {0, f773d2b0, be000000, 20020189}


Probably caused by : intelppm.sys ( intelppm!AcpiC1Idle+12 )


Followup: MachineOwner
---------


0: kd> !analyze -v
***************************************************************************=
=AD
****
*
*
*                        Bugcheck
Analysis                                    *
*
*
***************************************************************************=
=AD
****


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: be000000
Arg4: 20020189


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
----------------------------------------------------------------
1011111000000000000000000000000000100000000000100000000110001001


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.


MEMHIRERR - Memory Hierarchy Error   {TT}CACHE{LL}_{RRRR}_ERR
These errors match the format 0000 0001 RRRR TTLL


Concatenated Error Code:
--------------------------
_VAL_UC_EN_MISCV_ADDRV_PCC_MEMHIRERR_89


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


LAST_CONTROL_TRANSFER:  from 80a7ebd8 to 8087b71e


STACK_TEXT:
808a0770 80a7ebd8 0000009c 00000000 808a07a0 nt!KeBugCheckEx+0x1b
808a08a4 80a7686f 80042000 00000000 00000000 hal!
HalpMcaExceptionHandler+0x11e
808a08a4 f7619ca2 80042000 00000000 00000000 hal!
HalpMcaExceptionHandlerWrapper+0x77
808a3600 8083abf2 00000000 0000000e 00000000 intelppm!AcpiC1Idle+0x12
808a3604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xa


STACK_COMMAND:  kb


FOLLOWUP_IP:
intelppm!AcpiC1Idle+12
f7619ca2 6a00            push    0


SYMBOL_STACK_INDEX:  3


SYMBOL_NAME:  intelppm!AcpiC1Idle+12


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: intelppm


IMAGE_NAME:  intelppm.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  42435b38


FAILURE_BUCKET_ID:  0x9C_GenuineIntel_intelppm!AcpiC1Idle+12


BUCKET_ID:  0x9C_GenuineIntel_intelppm!AcpiC1Idle+12


Followup: MachineOwner.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
After that a performed  !process 0 ff  command and here the result :


The only running process was :
THREAD 869fa3c8  Cid 0970.0dfc  Teb: 7ffa6000 Win32Thread: 00000000
RUNNING on processor 2
Not impersonating
DeviceMap                 e1002930
Owning Process            86983be0       Image:
RaidServ.exe
Wait Start TickCount      41300440       Ticks: 0
Context Switch Count      269275755
UserTime                  00:53:09.531
KernelTime                00:49:51.734
Win32 Start Address 0x77bcb4bc
Start Address 0x77e6b5f3
Stack Init b9744000 Current b9743b30 Base b9744000 Limit
b9741000 Call 0
Priority 9 BasePriority 8 PriorityDecrement 0
ChildEBP RetAddr
f773d280 80a7ebd8 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f773d3b4 80a7686f hal!HalpMcaExceptionHandler+0x11e (FPO:
[Non-
Fpo])
f773d3b4 f7619ca2 hal!HalpMcaExceptionHandlerWrapper+0x77
(FPO: TSS 28:0)
808a3600 8083abf2 intelppm!AcpiC1Idle+0x12 (FPO: [0,2,0])
808a3604 00000000 nt!KiIdleLoop+0xa (FPO: [0,0,0])


and if you see I found the same stacks who caused this issue.


Could you please what exactely happened and caused this server
crash??


I appreciat your help


Thank you

Sorry. This newsgroup is for supporting the debugger itself. - Pat Styles [MSFT]

Sorry.  This newsgroup is for supporting the debugger itself.  I do not
know if you will find any expertise for solving particular driver issues.

.pat styles [microsoft]