BSOD STOP : 0x00000124 hardware problem

Before we start with hardware testing, do the following:

► Uninstall Google Chrome and use any other (whatever) web browser.

► Daemon Tools uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

► Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus and the touchpad driver, SynTPEnh.
5. Apply > OK
6. Accept then restart.

Then run the computer normally and report us for any further BSOD.
___________________________________________________

Code:

BugCheck 124, {0, 873fd024, b6000000, 10015}

Probably caused by : AuthenticAMD

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

1: 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: 00000000, Machine Check Exception
Arg2: 873fd024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00010015, 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:  1f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
807cc8cc 83a28fcd 00000124 00000000 873fd024 nt!KeBugCheckEx+0x1e
807cc908 836d792c 8742ebd1 873fd024 8367d8b0 hal!HalBugCheckSystem+0xab
807cc938 83a2927f 873fdea8 83a36e40 456e37ee nt!WheaReportHwError+0x230
807cca4c 83a29371 873fdea8 873fdef8 00000000 hal!HalpMcaReportError+0x3b
807cca70 83a295dd 00000000 873fdef8 807ccb90 hal!HalpMceHandler+0x8b
807cca80 83a1f5f5 00000000 3bf1f7df 39c13ff8 hal!HalpHandleMachineCheck+0x3b
807ccb90 83a1c261 00000000 807c7750 67dc99bb hal!HalpMcaExceptionHandler+0x87
807ccb90 00000000 00000000 807c7750 67dc99bb hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_TLB

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_TLB

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_tlb

FAILURE_ID_HASH:  {577a9b4c-6a3b-1ebf-1603-d910408323f0}

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