Complete random BSOD, tried everything...

Hello,

I have a problem since i build my pc, it restart randomly and when it is on desktop there is a pop-up that i have had a blue screen, but no actual blue screen is shown when shutting down. BCCode 124. And i also get (mostly on youtube video's) displaydriver AMD driver has stopped and is recovered, i thought maybe its related to the blue screen or something...

I have litterally tried everything... Clearing CMOS, GPU/CPU/PSU stress test, ran a chkdsk (or something like that) /r command and a sfc /scannow command, fresh install of windows, updated GPU drivers and BIOS, ran a memtest for 10 hours long, searched for artifacts with atitool an hour long... Does anyone has any suggestions what it could be?

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSSIKAT\Downloads\BRAM-PC-do_18-06-2015_170049,06\061615-15600-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`03259000 PsLoadedModuleList = 0xfffff800`034a0730
Debug session time: Tue Jun 16 22:51:54.473 2015 (UTC + 6:00)
System Uptime: 0 days 0:00:08.675
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800753e8f8, 0, 0}

Probably caused by : AuthenticAMD

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

4: 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: fffffa800753e8f8, 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

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`0335b5b0 fffff800`0351dcb9 : fffffa80`0753e8d0 fffffa80`06c2f040 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0335bad0 fffff800`033fc697 : fffffa80`0753e8d0 fffff800`034772d8 fffffa80`06c2f040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0335bb00 fffff800`033636e5 : fffff800`034d9ba0 00000000`00000001 fffffa80`07546c10 fffffa80`06c2f040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0335bb40 fffff800`032d74b5 : fffff880`0118ae00 fffff800`033636c0 fffffa80`06c2f000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0335bb70 fffff800`03567456 : 00000000`00000000 fffffa80`06c2f040 00000000`00000080 fffffa80`06bf3040 : nt!ExpWorkerThread+0x111
fffff880`0335bc00 fffff800`032bf2c6 : fffff880`0316d180 fffffa80`06c2f040 fffff880`031780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0335bc40 00000000`00000000 : fffff880`0335c000 fffff880`03356000 fffff880`03508730 00000000`00000000 : nt!KxStartSystemThread+0x16


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_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH:  {78c2f422-5335-4ef3-5cef-a28518da5023}

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

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try