Media Center/Netflix Crash twice within 24hrs

[Dert Nastee]

Backstory...

I have been having issues with my PC since the middle of December ('12). My computer (built by iBuypower) is under warranty, so I sent it back to them for diagnosis/repair (I had to pay $80 to ship it to them, just for your future reference). Before I shipped it back, their tech support had me run memory diagnostics (all 4 sticks, 1 at a time, 15 passes each) and they passed. I then shipped it. They had it about a week, I never heard anything, so I called them. Finally someone said "they're running tests but they THINK it is my graphics card (which at the time was a PowerColor Radeon HD 7970 3GB) causing the crashes". However, I was pretty sure it wasn't because I removed the card and its software and installed an EVGA GTX570HD I had from another PC in my house. The crashes were still happening.

Another week passes... I call again. This time they are "kinda" sure (by the sounds of it) that it was my graphics card. Being that I use Autodesk and Adobe design programs heavily, I assumed the "gaming" card couldn't handle the constant strain. So, I suggested that I upgrade to a Firepro v5900 workstation card more suited to my needs. They obliged, with a fee.

Task at hand...
Their repair department had my machine from 12/24/12 and I received it back 01/17/13. I turned it on the following day (18th), and by that night it crashed again. It seems to be crashing when I watch Netflix via browser and/or Media Center. I haven't streamed using the browser since the repair, only Media Center. Also, when i drag explorer windows around on my desktop they trail (or shadow) whatever term you use...

Cutting this short, screen just flickered. I'll return later with more info. hopefully I'll hear something by then.

 

[Arc]

Hello Dert Nastee.

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

[COLOR=Red][B]WHEA_UNCORRECTABLE_ERROR (124)[/B][/COLOR]
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, [B][COLOR=Red]Machine Check Exception[/COLOR][/B]
Arg2: fffffa800f0e18f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0358d5b0 fffff800`03b0fca9 : fffffa80`0f0e18d0 fffffa80`0cdaeb50 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0358dad0 fffff800`039f0557 : fffffa80`0f0e18d0 fffff800`03a6a2d8 fffffa80`0cdaeb50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0358db00 fffff800`03957935 : fffff800`03acbae0 00000000`00000001 fffffa80`0f0f3220 fffffa80`0cdaeb50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0358db40 fffff800`038d6641 : fffff880`01114e00 fffff800`03957910 fffffa80`0cdaeb00 00020000`02000001 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0358db70 fffff800`03b63e5a : 010d0101`0d01010d fffffa80`0cdaeb50 00000000`00000080 fffffa80`0ccea890 : nt!ExpWorkerThread+0x111
fffff880`0358dc00 fffff800`038bdd26 : fffff880`03389180 fffffa80`0cdaeb50 fffff880`033940c0 01000201`00020100 : nt!PspSystemThreadStartup+0x5a
fffff880`0358dc40 00000000`00000000 : fffff880`0358e000 fffff880`03588000 fffff880`03049740 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_TLB_PRV

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

1: kd> !errrec fffffa800f0e18f8
===============================================================================
Common Platform Error Record @ fffffa800f0e18f8
-------------------------------------------------------------------------------
Record Id     : 01cdf6ca952c4eaa
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 1/20/2013 4:57:11 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f0e1978
Section       @ fffffa800f0e1a50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : TLB error
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000600f12
Processor ID  : 0x0000000000000004

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f0e19c0
Section       @ fffffa800f0e1b10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000004
CPU Id        : 12 0f 60 00 00 08 08 04 - 0b 22 98 1e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800f0e1b10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f0e1a08
Section       @ fffffa800f0e1b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DTLBL1_ERR (Proc 4 Bank 0)
  Status      : 0xfe80000000020015
  Address     : 0x0000fa800d684000
  Misc.       : 0x0000000000000000

Stop 124 is a hardware relater crash, and a Machine Check Exception is a situation where the CPU detects a hardware problem and reports it to the OS. But nothing about the hardware is specific.

Here your duty is to find out the part of hardware which is causing the crash, and to repair/remove that hardware. For detailed information, follow the guide: Stop 0x124 - what it means and what to try

Let us know the results.

 

[Dert Nastee]

All that data and nothing to pin point the cause? Smh... not much of a "log" now is it.

 

[Arc]

All that data and nothing to pin point the cause? Smh... not much of a "log" now is it.

In this case, there is nothing more to pin point. You have to follow the stop 0x124 troubleshooting guide, and it does not contain a fix button unfortunately.

 

[Dert Nastee]

Could ANY hardware be the cause? i.e. external devices (wireless mouse, external hdd, etc...) not just core assets (RAM, graphics, etc...).

Is there any [background monitoring] software that could track these faults when and where they occur?

 

[Arc]

May be, but most likely a machinc check exception causes due to RAM, CPU, GPU, Motherboard or PSU. But, anything else it may be. Everything is detailed in Stop 0x124 - what it means and what to try.

 

[Dert Nastee]

Don't patronize sir, I know there is no "fix button." It just seems hard to fathom that, as complex as windows is, there is no feature that records where the CPU got the error from.

 

[Arc]

Don't patronize sir, I know there is no "fix button." It just seems hard to fathom that, as complex as windows is, there is no feature that records where the CPU got the error from.

See the code I posted. The first parameter, Arg1. For your case it is 0x0 (a series of zeros you can see). In this particular situation, it is kinda vague about the faulting hardware. See the link Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR (Windows Debuggers). Depending on the first parameter, WHEA stop is classified there. In some of those, the faulting hardware is pointed out, but not in your case.

You have to work to get it know. No other way available there.

 

[Dert Nastee]

Thanks for clarification. I apologize if I snapped. Though I am a programmer, I am not familiar with Microsoft proprietary code and debugging. That said, you may be as technical as necessary in your descriptions.

Also, I am just trying to gather as much info on the troubleshooting procedures so when I call the builder again, they can't blow smoke up my ass... excuse the expression.