PC Reboots Randomnly - MACHINE_CHECK_EXCEPTION

Hello All,

I have recently built a new computer from scratch and it randomly reboots with a MACHINE_CHECK_EXCEPTION. I captured and evaluated the minidump log (below) , but not sure what to do next. My suspicion is the cdaudio.sys driver is not loading. But...I wanted to check it with the experts. Any feedback is extremely helpful. Thanks! Joe


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


Loading Dump File [c:\temp\Mini012907-01.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\i386
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Jan 29 07:28:38.939 2007 (GMT-7)
System Uptime: 0 days 13:19:46.111
Loading Kernel Symbols
.........................................................................................................................
Loading User Symbols
Loading unloaded module list
........................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, bab3c050, b2000000, 1040080f}

Probably caused by : Cdaudio.SYS ( Cdaudio+13b3 )

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

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: bab3c050
Arg3: b2000000
Arg4: 1040080f

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


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.

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_PCC_BUSCONNERR_F

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_IA32_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from 806e7bff to 804f9c37

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: 17002000010004

STACK_COMMAND: dds BAB3C1C8-0x20 ; kb

STACK_TEXT:
bab3c1a8 0000ffff
bab3c1ac 00cffb00
bab3c1b0 0000ffff
bab3c1b4 00cff300
bab3c1b8 8d7020ab
bab3c1bc ba008bb3
bab3c1c0 80000001
bab3c1c4 bac093b3 <Unloaded_Cdaudio.SYS>+0x13b3
bab3c1c8 90000fff
bab3c1cc 7f40f3fd
bab3c1d0 0400ffff
bab3c1d4 0000f200
bab3c1d8 00000000
bab3c1dc 00000000
bab3c1e0 b0800068
bab3c1e4 ba0089b3
bab3c1e8 b0f00068
bab3c1ec ba0089b3
bab3c1f0 2f30ffff
bab3c1f4 00009302
bab3c1f8 80003fff
bab3c1fc 0000920b
bab3c200 700003ff
bab3c204 ff0092ff
bab3c208 0000ffff
bab3c20c 80009a40
bab3c210 0000ffff
bab3c214 80009240
bab3c218 00000000
bab3c21c 00009200
bab3c220 00000000
bab3c224 00000000


FOLLOWUP_IP:
Cdaudio+13b3
bac093b3 ?? ???

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Cdaudio+13b3

MODULE_NAME: Cdaudio

IMAGE_NAME: Cdaudio.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_Cdaudio+13b3

BUCKET_ID: 0x9C_IA32_GenuineIntel_Cdaudio+13b3

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

1: kd> lmvm Cdaudio
start end module name

 

Maybe Hardware problem of M/B

There have two confirmed cases with the same error code (ie Bugcheck code parameter 4 is the same). They are related to hardware error of M/B.

http://www.windowsbbs.com/showthread.php?t=60800
http://www.techspot.com/vb/topic48843.html

What is manufacturer and model of your M/B?

 

Thanks cpc2004. Here are the details. It doesn't look like it is one of the motherboards listed in the two links.

Motherboard ECS P4M800PRO-M7(V2.0) Motherboard

Still sounding like motherboard to you?

 

Correction, this is my true motherboard type:
Elite (ECS) - K7S5A

Sorry, the box said differently.

 

Hi,

Base upon the error code (ie 1040080f) and it is a generic bus connection time out error. Try downclock the RAM. Maybe it can fix the blue screen problem.

I am not a hardware guy. You have 3 horses to bet: CPU, RAM and M/B. As there have 2 confirmed cases relating to M/B, I believe it is M/B problem. You can email the M/B manufacturer and ask for their opinion.

 

I did a 48 hour memtest86 on the RAM, so I am confident it is not that. I wrote an email to the manufacturer with the symptoms. I'll keep the thread posted. Thanks.

 

Swapped out the mobo and no reboots. It has been 4 days since replacement. Usually I would get several reboots a day!

Thanks for the help!