F
ferook
I have a Compaq Presario 7000US Special Edition with Windows XP Pro
SP1 (build 2600). For the past few months, it's been randomly
restarting itself. Upon examining the MiniDump files, I find that
nearly all of them are due to the same error (see below).
Does this indicate a problem with my processor (1.20 gigahertz AMD
Athlon) and/or its drivers? How would I go about fixing the error? I
did not add or remove any hardware prior to this. Please advise. Thank
you.
----------------------------
Microsoft (R) Windows Debugger Version 6.3.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\Mini121603-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\system32
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Tue Dec 16 17:25:30 2003
System Uptime: 0 days 0:00:44.714
Loading Kernel Symbols
.................................................................................
.....................................................
Loading unloaded module list
....
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, 805366f0, c455c000, 136}
Probably caused by : Machine_Check
Followup: MachineOwner
---------
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 M
CA.
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 I
NIT 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
Arguments:
Arg1: 00000000
Arg2: 805366f0
Arg3: c455c000
Arg4: 00000136
Debugging Details:
------------------
BUGCHECK_STR: 0x9C_IA32_AuthenticAMD
MODULE_NAME: Machine_Check
IMAGE_NAME: Machine_Check
DEBUG_FLR_IMAGE_TIMESTAMP: 0
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 806aed8f to 804f4103
STACK_TEXT:
805366c8 806aed8f 0000009c 00000000 805366f0 nt!KeBugCheckEx+0x19
805367f4 806abc3e 80042000 00000000 00000000
hal!HalpMcaExceptionHandler+0xdb
FOLLOWUP_NAME: MachineOwner
STACK_COMMAND: kb
BUCKET_ID: 0x9C_IA32_AuthenticAMD
Followup: MachineOwner
---------
SP1 (build 2600). For the past few months, it's been randomly
restarting itself. Upon examining the MiniDump files, I find that
nearly all of them are due to the same error (see below).
Does this indicate a problem with my processor (1.20 gigahertz AMD
Athlon) and/or its drivers? How would I go about fixing the error? I
did not add or remove any hardware prior to this. Please advise. Thank
you.
----------------------------
Microsoft (R) Windows Debugger Version 6.3.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\Mini121603-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\system32
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp2.030422-1633
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Tue Dec 16 17:25:30 2003
System Uptime: 0 days 0:00:44.714
Loading Kernel Symbols
.................................................................................
.....................................................
Loading unloaded module list
....
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, 805366f0, c455c000, 136}
Probably caused by : Machine_Check
Followup: MachineOwner
---------
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 M
CA.
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 I
NIT 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
Arguments:
Arg1: 00000000
Arg2: 805366f0
Arg3: c455c000
Arg4: 00000136
Debugging Details:
------------------
BUGCHECK_STR: 0x9C_IA32_AuthenticAMD
MODULE_NAME: Machine_Check
IMAGE_NAME: Machine_Check
DEBUG_FLR_IMAGE_TIMESTAMP: 0
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 806aed8f to 804f4103
STACK_TEXT:
805366c8 806aed8f 0000009c 00000000 805366f0 nt!KeBugCheckEx+0x19
805367f4 806abc3e 80042000 00000000 00000000
hal!HalpMcaExceptionHandler+0xdb
FOLLOWUP_NAME: MachineOwner
STACK_COMMAND: kb
BUCKET_ID: 0x9C_IA32_AuthenticAMD
Followup: MachineOwner
---------