Solved: Machine Check Exception 0x9C

[Evil_Intentions]

----THE POINT----
Well, I am at my wits end on this one. After weeks of lurking, I have decided it's time to just ask someone to look at my .dmps and tell me WHERE this error is occurring.

---THE BACKGROUND---
I have recently received an Hp m8100e computer that has a few upgrades. The two primary ones being a LightScribe DVD burner and a GeForce 8500gt. I am normally quite adept at fixing computer problems, but I have exhausted almost all of my energy the past few days. I am aware that this error is caused by hardware, and have been slowly eliminating hardware.

First, the TV tuner, No change, errors occur every 8 hours or so

Second, Backup DVD drive, No change, 8 hours

*Installed 64bit windows*

Third, Lightscribe, still errors, 10-12 hours

Increased fans to 75% at all times, underclock gpu when not in use, still errors, ALMOST got 20 hours today

I am about to try taking the RAM out of dual channel, if the error persists, I will remove One stick.



Attached are my last 4 dumps. Im hoping they will point to a specific piece of hardware as I have seen in other topics similar to this one. There are only 4 since I have switched to x64, there were many more when I had x32 But I forgot to save them.

 

[Phantom010]

Probable cause: AmdK8.sys - AMD Athlon64 Processor Driver.

 

[Evil_Intentions]

seems I have all the most recent drivers. I will attemp uninstalling the AmdK8.sys drivers as they are only used for cool n quiet.

Will post update tomorrow

 

[Evil_Intentions]

Okay, the processor has been defaulted to the AmdPPM64 driver. Which I am sure is a windows default driver.

If there are no errors for three days straight, this thread will be marked solved

 

[Evil_Intentions]

Just woke up, and a BSOD occurred. overnight. Here is the dmp.

I have no clue what's going on here.

 

[Frank4d]

The latest log shows "unable to load image AmdPPM64.sys" and "unable to verify checksum for hal.dll". It looks like Windows doesn't like the processor driver.

 

[Evil_Intentions]

The latest log shows "unable to load image AmdPPM64.sys" and "unable to verify checksum for hal.dll". It looks like Windows doesn't like the processor driver.

The last errors were due to Amdk8.sys, the previous driver. After permanently uninstalling them, windows defaulted to this new one. SHould I try permanently uninstalling it as well?


EDIT: It is uninstalled. REbooting now. I have oticed both drivers are used for power management of the CPU. Just wanted to point that out

 

[Evil_Intentions]

Okay after uninstalling those, the system then defaulted to processr.sys which is ANOTHER cpu power management driver. I think the problem lies in power management, so I uninstalled it as well (saving backups of course) and now device manager shows two unknown devices, and cpuz is still showing the correct clock speed. Hopefully if I am right, there should not be a blue screen. If one does occur, I have no clue what the probable cause would be.

 

[Evil_Intentions]

Okay, I have just received another bluescreen. Interestingly, It was when I started an Installer. This has happened on 2 other occasions when I had x32. Attached is the minidump. What does the probable cause point to?

 

[Phantom010]

I've included the whole report:


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

Loading Dump File Mini011611-02\Mini011611-02.dmp
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_qfe.090319-1204
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d8280
Debug session time: Sun Jan 16 14:00:46.750 2011 (GMT-5)
System Uptime: 0 days 2:02:22.375
*** WARNING: Unable to verify checksum for ntkrnlmp.exe
Loading Kernel Symbols
...............................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.................
*** WARNING: Unable to verify checksum for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {1, fffff80000075bc0, b6000000, 181}
Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+77 )
Followup: MachineOwner
---------
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: 0000000000000001
Arg2: fffff80000075bc0
Arg3: 00000000b6000000
Arg4: 0000000000000181
Debugging Details:
------------------

BUGCHECK_STR: 0x9C_AuthenticAMD
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: Idle
CURRENT_IRQL: f
LAST_CONTROL_TRANSFER: from fffff8000080ef6c to fffff8000102e8d0
STACK_TEXT:
fffff800`00075b88 fffff800`0080ef6c : 00000000`0000009c 00000000`00000001 fffff800`00075bc0 00000000`b6000000 : nt!KeBugCheckEx
fffff800`00075b90 fffff800`0102db77 : 00000000`00000000 00000000`00000000 fffff800`011b4180 fffff800`00075ef0 : hal!HalHandleMcheck+0x12c
fffff800`00075cf0 fffff800`0102d9b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x77
fffff800`00075e70 fffff800`0102fe86 : fffff800`00069c28 00000000`000001a0 fffff800`011b4180 fffffadf`cc5d5a60 : nt!KiMcheckAbort+0xf5
fffff800`00069c30 fffff800`0081dcd2 : fffff800`0106771e fffff800`011b4180 fffff800`011b4180 fffff800`011b8540 : nt!KiInterruptDispatchNoLock+0xc6
fffff800`00069dc8 fffff800`0106771e : fffff800`011b4180 fffff800`011b4180 fffff800`011b8540 fffffadf`cc2f3bf0 : hal!HalProcessorIdle+0x2
fffff800`00069dd0 fffff800`014191d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x1e
fffff800`00069e00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1bf

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KxMcheckAbort+77
fffff800`0102db77 488d8c2400010000 lea rcx,[rsp+100h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KxMcheckAbort+77
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49c22d6e
FAILURE_BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
BUCKET_ID: X64_0x9C_AuthenticAMD_nt!KxMcheckAbort+77
Followup: MachineOwner

 

[Evil_Intentions]

Thanks for that. I have a question. I finished running chkdsk on my HDD, it said that there were errors and it was able to correct all of them. The reason I have this computer in the first place, is because my teacher gave it to me saying that I could have it if I could fix it. I did not use the computer right away, and had used the 500gb HDD as an external drive for a month or so, never running chkdsk, but formatting/reformatting a few times.

Now, if there was an error in the HDD from the beginning (that would've caused the BSOD for my teacher), would it have still been present even AFTER reformatting? And can an error detected by chkdsk really have been the cause for this BSOD?

I have also updated my nvidia whql drivers from 169 to 260, could his have also been a cause?

 

[Phantom010]

If the HDD is failing, it's quite possible.

 

[Evil_Intentions]

Searching around I found this: http://www.techsupportforum.com/forums/f10/solved-xp-64-bsod-out-of-ideas-347597.html

The last 2 posts make me extremely optimistic. As long as I dont have to replace an OEM mobo I'll be happy.

 

[Evil_Intentions]

GAH, just received another BSOD, again a MCE but this time, BlueScreenView pins netbt.sys as the culprit. Whereas it was always hal.dll before.

I feel we are narrowing down the cause. Hopefully I'm right.

 

[Evil_Intentions]

ugh, and yet another. Im going to sleep, I'll run memtest overnight. Will post the latest dump tomorrow.