BSOD with video. AuthenticAMD failure? WinDbg analyze -v attached.

[unpocoloco]

Hi all,

I'm a software professional but this one has me stumped. Typically when viewing video, either through Windows Media Center or streaming on Chrome, the computer will eventually BSOD. I have added Artic Silver 5 thermal compound and the CPU temp is at worst 52 degrees Celsius (typically at around 37-42 unless I'm streaming video), so I don't think it is an overheat issue. I suspect the video card or the processor itself, but I'm not sure what to do. I'm not overclocking.

Trying to not take a baseball bat to my computer as that will only fix the BSODs at the expense of nothing else working. But it is sorely tempting.

System specs:
MB: ASUS M4A87TD EVO
Processor: AMD Phenom II X4 970
BIOS: ASUS ver 08.00.15
RAM: 8GB, I forget what speed. (4x2GB)
Video: ATI Radeon HD 4600
OS: Win7 Professional (x64), SP 1

Help would be super appreciated! I will even buy whomever solves this one a 6-pack as a token of my appreciation.

Thanks!

------------------------------------------------------------------------------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800814c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b60ac000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:
fffff880`031dda88 fffff800`045fba3b : 00000000`00000124 00000000`00000000 fffffa80`0814c028 00000000`b60ac000 : nt!KeBugCheckEx
fffff880`031dda90 fffff800`0418e713 : 00000000`00000001 fffffa80`0814dd30 00000000`00000000 fffffa80`0814dd80 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddad0 fffff800`045fb700 : 00000000`00000728 fffffa80`0814dd30 fffff880`031dde30 00000000`0ee30200 : nt!WheaReportHwError+0x263
fffff880`031ddb30 fffff800`045fb052 : fffffa80`0814dd30 fffff880`031dde30 fffffa80`0814dd30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddc80 fffff800`045eee8f : 00000000`0d7d1000 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddcc0 fffff800`040757ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`031ddcf0 fffff800`04075613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dde30 00000000`52888012 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`02f6f7a4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x52888012


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION:

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_CACHE

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_authenticamd_processor_cache

FAILURE_ID_HASH: {8bb1abe1-5cc5-4642-921b-5e3d4790100e}

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

 

[SGT Oddball]

As you have not provided the files from our bsod posting instructions it's very difficult to pinpoint the cuase of your crash, however 0x124 hardware errors are very difficult to track down and I suggest you have a read of the following posts to help find the cause -

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

http://www.sevenforums.com/crash-lockup-debug-how/274565-stop-0x124-troubleshooting-new-method.html