Machine Check Execption

My computer at random times are giving me a blue screen with a message of Machine_Check_Execption with the error code/stop code of: 0x0000009c (0x00000000, 0x805555f0, 0xb2000000, 0x1040080f), and quicky reboots, even though the settings are placed on do not reboot on error. I have a couple of saved minidump files and I tried to debug them with a Windows utility but its really over my head and can't get it to work right. So I need a little help to figure out what the issue is. Sorry I can't tell much more about the error, the blue screen only sticks around for like 2~3 seconds before rebooting the system.

 

Since you posted this in the OC section
Are you OCing? return to stock speed,or reduce the OC and or lighten mem timmings


This might help:
http://support.microsoft.com/?kbid=329284

 

Well I was OCing, and the 0x0000009c is regarding a hardware error, but I am not sure what is the cause. I have been told from two different sources two different things. One is that the possible cause is listed in the saved memory dump data and another source tells me it doesn't. And the biggest problem for me is that I can not seem to examine the memory dump data.

 

Zip and post the minidumps. Did you check the tutorial here?

http://forums.majorgeeks.com/showthread.php?t=35246

I had a poster email me recently ( by my request, don't email me!) with a stop 0x9c, and sure nuff it was his overclock failing.

 

Oh yes I did I try with that tutorial for a couple of hours. I really couldn't get it to work. Most I think because I couldn't get any symbols downloaded. After I could get any from the Microsoft Symbol Store, I tried to download them off the site directly and just save it but I discovered that the symbol package I need is 188MB... which isn't going to work on my 56k dialup. So I was left scraching my head on that one.

But anyway, I went ahead and attached my minidumps. I hope can have more luck with them All I really need is just direction, what direction should I troubleshoot with, because I haven't got a clue which direction to take.

 

You have pushed your machine past its limits. Back off the overclock entirely. If it doesn't help, your CPU is probably toast.

0x9C_IA32_GenuineIntel_nt!KdPitchDebugger+ef4


You must have an Intel CPU, eh?

 

The full debug:




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


Loading Dump File [C:\Documents and Settings\Jeremy\Desktop\Minidumps\Mini040306-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:
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 = 0x805624a0
Debug session time: Mon Apr 3 00:26:55.414 2006 (GMT-7)
System Uptime: 0 days 1:07:38.875
Loading Kernel Symbols
......................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, 805535f0, b2000000, 1040080f}

Probably caused by : ntkrnlmp.exe ( nt!KdPitchDebugger+ef4 )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* 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: 805535f0
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

LAST_CONTROL_TRANSFER: from 80702bff to 805371aa

SYMBOL_ON_RAW_STACK: 1

STACK_TEXT:
805535c8 80702bff 0000009c 00000000 805535f0 nt!KeBugCheckEx+0x1b
805536f4 806fdc52 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
805536f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a


STACK_COMMAND: dds @$csp ; kb

FOLLOWUP_IP:
nt!KdPitchDebugger+ef4
805535f0 0200 add al,[eax]

FAULTING_SOURCE_CODE:


FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KdPitchDebugger+ef4

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

FAILURE_BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!KdPitchDebugger+ef4

BUCKET_ID: 0x9C_IA32_GenuineIntel_nt!KdPitchDebugger+ef4

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

 

Well glad you can read that, can't make out about 90% of it. Well I won't be toying with my CPU much more, but does the error say what was going wrong or does it just say, fatel hardware error and things aren't looking good?

 

I'm sure it says a heck of a lot more than I can delve from it, but I couldn't tell you.

I only know how to decipher certain culprits out of it, but not much more than that.

I too, can't read 90% of it, but I know where to look for the important stuff, hence the tutorial I wrote

Some dumps are easier than others, and full memory dumps provide the most info.

Those, however, are exactly the size of the ram amount in your machine.

 

If you want to get really granular about it:

Here is the error code in the debug:

_VAL_UC_EN_PCC_BUSCONNERR_F

And the explanations for each part:

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

 

So it looks like an error with the system Bus? If thats it that tells me everything. But thanks for your help. Kind of sucks that I can't read my own minidump files.