BlackSOD 256 124 Hardware problem. Usually under heavy loads.

Xntd · 02 Nov 2013

Attachment 292037

Hello, I have been having Black Screens of Death starting about 6 months ago. These BSOD 95% of the time occur when under heavier loads such as World of Warcraft + a few other heavy loads. The other 5% is just browsing. It mainly started when I would boot up my computer and see American Mega Trends cpu fan error press 1 to continue. I checked my temps with Cpu/Gpu/speedfan and the temps are around 30-50 degrees celsius when idle/heavy load.

I dbanned my computer yesterday to finally narrow down if it was hardware related (I knew it was most likely since the BSOD error code is said to almost always be a hardware related issue). I have done several tests consisting of using memtest etc... to test ram etc...(I followed the answer advice to other peoples basic hardware problems found in tech forums such as this as to use these programs) to my surprise I got no errors at all (I did these tests the past few days).

Now I am 99% positive it is hardware related the problem is I don't know which piece of hardware has failed.

P.S. my BSOD usually happen within the same time period when doing heavy loads. (such as 2minutes into world of warcraft and several other things). The monitor goes black I hear a buzz and then the computer reboots. The computer would get BSOD occasionally the past several months however, the past few months have been terrible. Everything looks fine inside my computer and it is clean as well.

Once again I just 2 days ago Dbanned reinstalled windows + World of Warcraft Gpu-z Cpu-z speedfan etc...

I can't even guess which piece of hardware is causing this as I am lost after the tests I've done etc...

I chose to come here after doing almost everything I can possibly think of. I need some expert help.

I thank all who choose to help me with this issue.

Edit: I also wanted to add that before I dbanned I also updated every driver on my PC, just to rule out if it was a driver issue.

System Information

OS Name - Microsoft Windows 7 Ultimate
Version - 6.1.7601 Service Pack 1 Build 7601
System Type - x64-based PC
Processor - AMD Phenom(tm) II X4 965 Processor 3400 Mhz, 4 Core(s), 4 Logical Process...
BIOS Versions/Date - American Megatrends Inc. 0307 12/15/2010
SMBIOS Version - 2.5
Installed Physical Memory (RAM) - 8.00GB
Total Physical Memory - 8.00 GB
Available Physical Memory - 5.60 GB
Total Virtual Memory - 16.0 GB
Available Virtual Memory - 13.1 GB
DirectX Version: DirectX 11
Graphics Card: NVIDIA GeForce GTX 460

Arc · 03 Nov 2013

A stop 0x124 is usually a hardware issue.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the CPU.
Hardware - Stress Test With Prime95

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

If possible, plan to update the BIOS, too.

And, fill up your system specs.
See your system specs and fill it up here.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800839e468, 0, 0}

Probably caused by : AuthenticAMD

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

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: fffffa800839e468, 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`031c46f0 fffff800`03128d29 : fffffa80`0839e440 fffffa80`06a29720 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031c4c10 fffff800`03008217 : fffffa80`0839e440 fffff800`03082658 fffffa80`06a29720 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031c4c40 fffff800`02f6f865 : fffff800`030e43a0 00000000`00000001 fffffa80`082eb1e0 fffffa80`06a29720 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031c4c80 fffff800`02eefa21 : fffff880`00e9fe00 fffff800`02f6f840 fffffa80`06a29700 fffffa80`06a29720 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031c4cb0 fffff800`03182cce : 00000000`00000000 fffffa80`06a29720 00000000`00000080 fffffa80`06a25040 : nt!ExpWorkerThread+0x111
fffff880`031c4d40 fffff800`02ed6fe6 : fffff880`02f64180 fffffa80`06a29720 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031c4d80 00000000`00000000 : fffff880`031c5000 fffff880`031bf000 fffff880`037af540 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_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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