BSoD - Machine Check Exception

[conorvansmack]

When I'm running uTorrent, my PC will lock up (unresponsive to mouse, keyboard, etc.) and then I get a blue screen with Machine Check Exception. It only seems to happen when I'm DL'ing larger files, but it only happens when uTorrent is running. I've been DL'ing a larger file lately (1.5GB) and it happens all the time. Shortly before the BSoD, I get a regularly intermittent, high pictched beeping sound.

This happened twice when I was playing HL2 with the settings cranked. I took the side panel off my case and it doesn't happen when I'm playing anymore, but it still happens with uTorrent.

Since it's an MCE, I think it's heat related. I added an MSI 8800GT to my system and it's very close to my sound card. I had to move my sound card to the last PCI slot on my board and it only has about 3/4" of clearance from the bottom of my case.

Just to be sure, I ran memtest86 last night. It went through almost 5 times and had no errors. My CPU temps are in the mid 90s. In uTorrent, I lowered my upload rate, but I got the same error in about the same amount of time.

Software - I'm running WinXP SP3, but it was happening in SP2 as well. AVGFree antivirus, no firewall since I'm connected through a Buffalo WHR54G router.

Hardware
Epox EP-9NPA+Ultra (nForce4 Ultra)
Athlon64 X2 4400+ w/Arctic Cooling Freezer64 Pro
2GB (2 x 1GB) OCZ DDR 3200(PC 400)
MSI 8800GT (w/zalman cooler)
Creative Audigy 2zs sound card
OCZ ModStream 520W
My onboard ethernet port does not work so I'm using a D-Link DUB E-100 USB network adapter (also a possible culprit) My video card took up the other PCI slot that I had a wireless NIC in.

At the moment, I think the problem is being caused by the sound card (heat from new video card and high pitched beep) or the USB NIC since it's the only thing I wasn't running before with the exception of the video card.

Any advice is appreciated!

 

[dclive]

Debug the dumpfile - read my .sig and follow the guide and post the results/output of the debugger.

 

[conorvansmack]

Thanks for offering some help. Here's what it posted:

BugCheck 9C, {4, 8054e5f0, b2000000, 70f0f}

Probably caused by : memory_corruption ( nt!MmDeleteKernelStack+ab )

Followup: MachineOwner


I had 5 of them and they all said the same thing. At least it's consistent.

 

[conorvansmack]

I used !analyze-v and got:

0: 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: 00000004
Arg2: 8054e5f0
Arg3: b2000000
Arg4: 00070f0f

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:

- Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
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
----------------------------------------------------------------
1011001000000000000000000000000000000000000001110000111100001111


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_30F

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_AuthenticAMD

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from 806e9bfb to 804f9f33

STACK_TEXT:
8054e5c8 806e9bfb 0000009c 00000004 8054e5f0 nt!MmDeleteKernelStack+0xab
8054e6f4 806e4c52 80042000 00000000 00000000 hal!KeRevertToUserAffinityThread+0x1
00000000 00000000 00000000 00000000 00000000 hal!HalpWriteCmosTime+0xce


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmDeleteKernelStack+ab
804f9f33 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MmDeleteKernelStack+ab

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x9C_AuthenticAMD_nt!MmDeleteKernelStack+ab

BUCKET_ID: 0x9C_AuthenticAMD_nt!MmDeleteKernelStack+ab

Followup: MachineOwner

 

[dclive]

As it says, hardware. Call up your vendor and get a replacement.

 

[conorvansmack]

This is the first time I've ever analyzed a debug. Is it the processor, RAM, or mobo that is the cause? Is see where it says memory corruption, but I also see where it says BUSCONNERR, which makes me think mobo.

 

[dclive]

Your vendor will need to tell you; he needs to test all three, really, as any could be bad.

 

[conorvansmack]

I built this one myself, so I don't really have a vendor. My processor is an OEM and I think it's warranty runs out at the end of the month. My motherboard is certainly out of warranty and Epox is out of business. Do you think my best bet is taking it to a local company that builds PCs to have them check it out?

 

[dclive]

I'd guess that would be best - or finding a friend with similar parts so you can trade out and see when the issue stops. This, unfortunately, is why I got out of the build-it-yourself bits.

 

[conorvansmack]

Sounds good. I really appreciate the guidance you've given me so far.