Bluescreen , AuthenticAMD , Windows 8.1/64bytes

[ParisIannis1]

After i got rid of my broken ram stick ( running win 7 64 back then )now i`m still stuck with a BSOD that`s "Probably caused by : AuthenticAMD" . I want to know how can i solve this problem
psu: recom power engine 600 plus
cpu: amd phenom II x6 1100T
gpu: gigabyte 650TI OC ( NOTE: it`s overclocked my manufactur can this be related with the bsod)
ram: sticks crosair vengeanceLP 12 gb
motherboard: asus m5a78l/usb3


BSOD happens in games only ( world of tanks , battlefield 3 ) sometimes after a while of playing and sometimes i can play like 6h..

My hardware is in average pretty cooled



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


Loading Dump File [C:\Windows\Minidump\062614-15718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`64a1a000 PsLoadedModuleList = 0xfffff802`64ce42d0
Debug session time: Thu Jun 26 23:10:19.383 2014 (UTC + 3:00)
System Uptime: 0 days 0:00:05.219
Loading Kernel 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, ffffe0001bad6768, 0, 0}

Probably caused by : AuthenticAMD

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

2: 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: ffffe0001bad6768, 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: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
ffffd000`209a86c0 fffff802`64d9302c : fffff802`64d00180 ffffe000`1bad6740 fffff802`64cf3800 fffff802`64a70779 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`209a8bf0 fffff802`64bdad30 : ffffe000`1bad6740 ffffd000`209a8d10 fffff802`64cf3840 ffffe000`19be3880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`209a8c20 fffff802`64bdbb4d : fffff802`64cf3840 ffffd000`209a8d10 fffff802`64cf3840 00000000`00000246 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`209a8c60 fffff802`64a6dadb : fffff801`401ddfd8 fffff802`64bdbb28 ffffe000`19fa6930 ffffe000`19a085e0 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`209a8c90 fffff802`64ae9794 : ffffe000`19127880 ffffe000`19be3880 ffffe000`19be3880 ffffe000`19069900 : nt!ExpWorkerThread+0x293
ffffd000`209a8d40 fffff802`64b745c6 : ffffd000`2052e180 ffffe000`19be3880 ffffe000`19127880 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`209a8da0 00000000`00000000 : ffffd000`209a9000 ffffd000`209a3000 00000000`00000000 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: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

2: 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: ffffe0001bad6768, 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: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
ffffd000`209a86c0 fffff802`64d9302c : fffff802`64d00180 ffffe000`1bad6740 fffff802`64cf3800 fffff802`64a70779 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`209a8bf0 fffff802`64bdad30 : ffffe000`1bad6740 ffffd000`209a8d10 fffff802`64cf3840 ffffe000`19be3880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`209a8c20 fffff802`64bdbb4d : fffff802`64cf3840 ffffd000`209a8d10 fffff802`64cf3840 00000000`00000246 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`209a8c60 fffff802`64a6dadb : fffff801`401ddfd8 fffff802`64bdbb28 ffffe000`19fa6930 ffffe000`19a085e0 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`209a8c90 fffff802`64ae9794 : ffffe000`19127880 ffffe000`19be3880 ffffe000`19be3880 ffffe000`19069900 : nt!ExpWorkerThread+0x293
ffffd000`209a8d40 fffff802`64b745c6 : ffffd000`2052e180 ffffe000`19be3880 ffffe000`19127880 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`209a8da0 00000000`00000000 : ffffd000`209a9000 ffffd000`209a3000 00000000`00000000 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: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

2: 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: ffffe0001bad6768, 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: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
ffffd000`209a86c0 fffff802`64d9302c : fffff802`64d00180 ffffe000`1bad6740 fffff802`64cf3800 fffff802`64a70779 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`209a8bf0 fffff802`64bdad30 : ffffe000`1bad6740 ffffd000`209a8d10 fffff802`64cf3840 ffffe000`19be3880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`209a8c20 fffff802`64bdbb4d : fffff802`64cf3840 ffffd000`209a8d10 fffff802`64cf3840 00000000`00000246 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`209a8c60 fffff802`64a6dadb : fffff801`401ddfd8 fffff802`64bdbb28 ffffe000`19fa6930 ffffe000`19a085e0 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`209a8c90 fffff802`64ae9794 : ffffe000`19127880 ffffe000`19be3880 ffffe000`19be3880 ffffe000`19069900 : nt!ExpWorkerThread+0x293
ffffd000`209a8d40 fffff802`64b745c6 : ffffd000`2052e180 ffffe000`19be3880 ffffe000`19127880 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`209a8da0 00000000`00000000 : ffffd000`209a9000 ffffd000`209a3000 00000000`00000000 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: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

2: 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: ffffe0001bad6768, 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: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
ffffd000`209a86c0 fffff802`64d9302c : fffff802`64d00180 ffffe000`1bad6740 fffff802`64cf3800 fffff802`64a70779 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`209a8bf0 fffff802`64bdad30 : ffffe000`1bad6740 ffffd000`209a8d10 fffff802`64cf3840 ffffe000`19be3880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`209a8c20 fffff802`64bdbb4d : fffff802`64cf3840 ffffd000`209a8d10 fffff802`64cf3840 00000000`00000246 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`209a8c60 fffff802`64a6dadb : fffff801`401ddfd8 fffff802`64bdbb28 ffffe000`19fa6930 ffffe000`19a085e0 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`209a8c90 fffff802`64ae9794 : ffffe000`19127880 ffffe000`19be3880 ffffe000`19be3880 ffffe000`19069900 : nt!ExpWorkerThread+0x293
ffffd000`209a8d40 fffff802`64b745c6 : ffffd000`2052e180 ffffe000`19be3880 ffffe000`19127880 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`209a8da0 00000000`00000000 : ffffd000`209a9000 ffffd000`209a3000 00000000`00000000 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: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

 

[johnbl]

this error is generated directly from the CPU. you can use the debugger to dump the information on why the CPU called the bugcheck.

the commnad is
!errrec on the address of the of the WHEA_ERROR_RECORD structure arg2 in the bugcheck.
so the command would be
!errrec ffffe0001bad6768
in your first crash dump case.

most of the time it will be a write error to the cache memory of the CPU, caused by incorrect power levels or clock frequency to the CPU memory controller. (often just caused by bad overclock values, heating,...)

 

[ParisIannis1]

this error is generated directly from the CPU. you can use the debugger to dump the information on why the CPU called the bugcheck.

the commnad is
!errrec on the address of the of the WHEA_ERROR_RECORD structure arg2 in the bugcheck.
so the command would be
!errrec ffffe0001bad6768
in your first crash dump case.

most of the time it will be a write error to the cache memory of the CPU, caused by incorrect power levels or clock frequency to the CPU memory controller. (often just caused by bad overclock values, heating,...)

Here is the data after executing !errrec ffffe0001bad6768 :

2: kd> !errrec ffffe0001bad6768
===============================================================================
Common Platform Error Record @ ffffe0001bad6768
-------------------------------------------------------------------------------
Record Id : 01cf917aa4826f40
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 6/26/2014 20:10:19 (UTC)
Flags : 0x00000002 PreviousError

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

Proc. Type : x86/x64
Instr. Set : x64
Error Type : BUS error
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000100fa0
Processor ID : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id : a0 0f 10 00 00 08 06 00 - 09 20 80 00 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 @ ffffe0001bad6980

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

Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
Status : 0xfa00000000070f0f

 

[johnbl]

BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)

error from the cache memory controller inside the CPU
reporting that cpu processor 0 got a error on cache memory bank 4.
I think it is a error generated when you have a failure to move a block of memory from thru the bus in the CPU.

I would expect that it is a incorrect volatage or clock frequency applied to the CPU. Common problem with overclocking, often fixed in BIOS updates and labled as a stablity fix. I would update the BIOS or reset it back to defaults and see if that helps. Otherwise you have to tweek the voltages and clock frequency to certain settings in your BIOS. (the values depend on the actual CPU)

it can also, indicate voltage regulation problems. for example, you can get this if your power supply is under powered for your graphics card. you start a 3d game, your graphics card pulls a lot of power and the power to your CPU drops slightly. Not enough to cause your CPU to reset and start counting memory but enough that the CPU get underpowered for a short duration.

Note: some motherboards will auto overclock, and a BIOS update is the quickest fix to these issues. otherwise you have to look up your chip and start confirming each CPU voltage and clock setting to each pin via setting BIOS setting.

 

[ParisIannis1]

BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)

error from the cache memory controller inside the CPU
reporting that cpu processor 0 got a error on cache memory bank 4.
I think it is a error generated when you have a failure to move a block of memory from thru the bus in the CPU.

I would expect that it is a incorrect volatage or clock frequency applied to the CPU. Common problem with overclocking, often fixed in BIOS updates and labled as a stablity fix. I would update the BIOS or reset it back to defaults and see if that helps. Otherwise you have to tweek the voltages and clock frequency to certain settings in your BIOS. (the values depend on the actual CPU)

it can also, indicate voltage regulation problems. for example, you can get this if your power supply is under powered for your graphics card. you start a 3d game, your graphics card pulls a lot of power and the power to your CPU drops slightly. Not enough to cause your CPU to reset and start counting memory but enough that the CPU get underpowered for a short duration.

Note: some motherboards will auto overclock, and a BIOS update is the quickest fix to these issues. otherwise you have to look up your chip and start confirming each CPU voltage and clock setting to each pin via setting BIOS setting.

Thanks mate for the response , i think its clearly the psu i calculated the wattage via http://www.extreme.outervision.com/psucalculatorlite.jsp and they suggested a 584W Psu , then i looked at my psu box where they say Max Combined Wattage to be 581.5W . Thanks again for the help i appreciate it !

 

[ryanperkins352]

BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)

error from the cache memory controller inside the CPU
reporting that cpu processor 0 got a error on cache memory bank 4.
I think it is a error generated when you have a failure to move a block of memory from thru the bus in the CPU.

I would expect that it is a incorrect volatage or clock frequency applied to the CPU. Common problem with overclocking, often fixed in BIOS updates and labled as a stablity fix. I would update the BIOS or reset it back to defaults and see if that helps. Otherwise you have to tweek the voltages and clock frequency to certain settings in your BIOS. (the values depend on the actual CPU)

it can also, indicate voltage regulation problems. for example, you can get this if your power supply is under powered for your graphics card. you start a 3d game, your graphics card pulls a lot of power and the power to your CPU drops slightly. Not enough to cause your CPU to reset and start counting memory but enough that the CPU get underpowered for a short duration.

Note: some motherboards will auto overclock, and a BIOS update is the quickest fix to these issues. otherwise you have to look up your chip and start confirming each CPU voltage and clock setting to each pin via setting BIOS setting.

Thanks mate for the response , i think its clearly the psu i calculated the wattage via http://www.extreme.outervision.com/psucalculatorlite.jsp and they suggested a 584W Psu , then i looked at my psu box where they say Max Combined Wattage to be 581.5W . Thanks again for the help i appreciate it !

Hi, I have this exact same error as you. Our numbers in the dmp file are basically identical as well. Could you link me or quickly explain how exactly you fixed the power issue to the cpu? I have no idea how to do it, even though you guys have found the solution!

Our parts may differ just a bit.
http://pcpartpicker.com/user/ryansperkins/saved/sZZQzy