Blue screen authenticamd

[Gaza336]

So I recently upgraded my psu, GPU, and cpu on my rig, triple checked all compatibility for this and ensured that my motherboards bios was upgraded as I hadn't upgraded that.
Keep receiving random restarts (at the oddest moments see below).

Kernel power error/reboots
Probably caused my AuthenticAMD (windows debugger)

Now I'm not on the machine now to provide the dump files or detailed error message so bare with me.

Weird parts are, I can play assassins creed unity at the ultra graphics setting with no delay no error and it will not crash out at all. However on the desktop it will crash randomly (no specific tasks) and it will always crash out when playing mount and blade Viking conquest within 10 mins or less.

Specs are since upgrade (will be more detailed later)
Motherboard - M5A78L-M/usb3 (upgraded bios to version 2001)
Cpu - amd fx 8350
GPU - asus radeon r9 290 dc2oc
Psu - Evga 600b 80+ (also troubleshot with corsair psu 650w)
Cpu cooler - Evo hyper 212 with just one fan and an exhaust for more cool and hot hair relief on chasis.
Ram 16gb ddr3

Win 7 64x home basic

DVD/cd rewritable standard sata
1tb standard sata hdd

Like I've said I've tried the old hardware one by one same error repeating.

Troubleshooting -
Tested each hardware with memtest86, furmark, cpu stability, occt etc. Works fine. Only crashed on cpu stability once.
Tested with different psu/cpu/GPU same again.
Heat is fine GPU ranges from 50-68 Celsius (depending on game) and cpu idle is 28-30 and 40-50 during games (Celsius). GPU idle is 40 normally. Used with speed fan and afterburner.

I've removed amd catalyst control and installed drivers only as sometimes win7 has an issue no change.
I do not understand nor do I overclock however my asus motherboard does have it auto built into the bios (not sure if I can change?)
Tried using afterburner to increase 25mv+ as a previous solution, increased run time.
Corsair psu 650w has increased run time.

Strange thing is this only occurs when I believe the GPU/cpu is under performing.. As in I can play new recent games high demanding graphics at top quality with no performance or crash issue but desktop and smaller older games.. More hassle.

Any questions please ask, will upload the detailed info as requested in morning (1am at present UK).

 

[okcnaline]

1) Give us the dumps.
2) Are you sure? authenticAMD is simply the CPUID brand for AMD CPUs.
3) Is the motherboard a AMD 780 chipset or A78 chipset?

 

[Paul NZ]

I think that stop error can mean a faulty core on that CPU

According to the ASUS site the chipset is AMD 760G (780L)/SB710

 

[Gaza336]

Will find a way to upload a detailed dump etc in morning (few hours). The CPU was newly bought so hopefully not faulty fingers crossed however my old cpu which was a phenom II X6 worked fine prior to upgrade on that board and now the same error occurs with that within the same time frame..

Anyways guys thank you for the prompt replies I shall get back in touch soon as I access my computer for files! Have spent the last week of my holidays attempting to resolve this clutching at straws ha!

 

[Gaza336]

Sorry for the delay guys, actually thought I had resolved this issue, was RMA'd a new PSU at 750W from Evga which allowed me to play the game that caused an error (M&B Viking conquest). However, after the initial installation of the AMD Catalyst drivers it blue screened during the installation (who crashed info as below). This was a different error code from previous attempts which made me believe the original error was resolved and this was new. It then decided to reboot (no blue screen) twice randomly after resulting in the same error codes and definitions.


Whocrashed error report -

Spoiler

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 24/12/2014 16:54:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122414-28392-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008C938F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 24/12/2014 16:47:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122414-30856-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800A9DB8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 24/12/2014 16:15:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122414-58781-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x5D000)
Bugcheck code: 0x116 (0xFFFFFA800BAC94E0, 0xFFFFF88006A32D88, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation VIDEO_TDR_ERROR



On Wed 24/12/2014 16:15:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x214)
Bugcheck code: 0x116 (0xFFFFFA800BAC94E0, 0xFFFFF88006A32D88, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Google query: Microsoft Corporation VIDEO_TDR_ERROR



On Tue 23/12/2014 21:00:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122314-26457-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008D978F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 23/12/2014 20:30:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122314-37221-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008E068F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 23/12/2014 19:01:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122314-30435-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008D6F038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 23/12/2014 18:56:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122314-30076-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008DCC808, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 23/12/2014 16:09:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122314-42104-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008F181B8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 23/12/2014 15:30:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122314-28797-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B18CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8008C50538, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Windows Debugger report -

Spoiler

*******************************************************************************
* *
* 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: fffffa8008c938f8, 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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`0218d5b0 fffff800`02313c59 : fffffa80`08c938d0 fffffa80`06be3680 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0218dad0 fffff800`021f3fa7 : fffffa80`08c938d0 fffff800`0226e2b8 fffffa80`06be3680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0218db00 fffff800`0215b5c5 : fffff800`022cfac0 00000000`00000001 fffffa80`08f82960 fffffa80`06be3680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0218db40 fffff800`020db021 : fffff880`00e70e00 fffff800`0215b5a0 fffffa80`06be3600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0218db70 fffff800`0236d32e : 00000000`00000000 fffffa80`06be3680 00000000`00000080 fffffa80`06bd6040 : nt!ExpWorkerThread+0x111
fffff880`0218dc00 fffff800`020c2666 : fffff880`020a5180 fffffa80`06be3680 fffff880`020b00c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0218dc40 00000000`00000000 : fffff880`0218e000 fffff880`02188000 fffff880`02997400 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
---------

Windows debugger from new error -

Spoiler

*******************************************************************************
* *
* 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: fffffa800a9db8f8, 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.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:
fffff880`033775b0 fffff800`02ee0c59 : fffffa80`0a9db8d0 fffffa80`06cafb60 fffffa80`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03377ad0 fffff800`02dc0fa7 : fffffa80`0a9db8d0 fffff800`02e3b2b8 fffffa80`06cafb60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03377b00 fffff800`02d285c5 : fffff800`02e9cac0 00000000`00000001 fffffa80`09b26e60 fffffa80`06cafb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03377b40 fffff800`02ca8021 : fffff880`0103de00 fffff800`02d285a0 fffffa80`06cafb00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03377b70 fffff800`02f3a32e : 00000000`00000000 fffffa80`06cafb60 00000000`00000080 fffffa80`06baf740 : nt!ExpWorkerThread+0x111
fffff880`03377c00 fffff800`02c8f666 : fffff880`03189180 fffffa80`06cafb60 fffff880`031940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03377c40 00000000`00000000 : fffff880`03378000 fffff880`03372000 fffff880`0412d400 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
---------

Currently in safe mode, but for todays crashes the first two were different from previously and now have resulted in the same continuous error reboots.

 

[johnbl]

- cpu called a bugcheck because of a error generated by the CPU cache controller.
- you had a graphics card that failed to respond

this is a common overclocking failure, (reset the BIOS, remove any overclocking software)
if you are not overclocking:


most likely cause would be poor power being delivered to the secondary power connections from your power supply to your graphics card. I would check these connections and the PSU and make sure all of the connection are connected and if your power supply had multi rails that the leads are connected from different rails of the power supply (not jumped off of the same power supply line)
(will not be a issue with a single rail power supply)

other things can cause the problem also, (outdated bios, old motherboard with failing power regulation, power supply that is poorly regulating power)

 

[Gaza336]

So as per your comment I have trouble checked the wiring my evga 750w is a modular set up and can confirm that it is two seperste wires running into the gpu of that is what you meant?

I have updated the bios to 2001 which is above the compatibility for my cpu which was 1401 I bekieve?

As for overclocking I don't know how to do I'm assuming im not however the bios does show CPU overclocking as auto as well as other options, is there a specific setting I could change it to, to rule out/troubleshoot that it isn't automatically overclocking?

As for power from the motherboard is there any way I can troubleshoot this?

If I've misunderstood you I apologise! This was a little more complicated than the simple upgrade I was hoping for ha, always something happening!

 

[okcnaline]

Just to make sure, is your OS 5.1.2600, 6.0.6000, 6.1.7600, 6.1.7601, 6.2.9200, or 6.3.9600.16497? You can check using WinKey + R, and typing "slmgr.vbs /dlv".

And also, try installing this.
http://dlcdnet.asus.com/pub/ASUS/misc/utils/AMD_Chipset_V13254_51010008_XPVISTAWIN7.zip

 

[Gaza336]

Just to make sure, is your OS 5.1.2600, 6.0.6000, 6.1.7600, 6.1.7601, 6.2.9200, or 6.3.9600.16497? You can check using WinKey + R, and typing "slmgr.vbs /dlv".

And also, try installing this.
http://dlcdnet.asus.com/pub/ASUS/misc/utils/AMD_Chipset_V13254_51010008_XPVISTAWIN7.zip

OS is currently 6.1.7600.16385

I am also installing the amd chipset just now however I'm going to work soon so will keep you updated later tonight. Again thank you very much!

 

[okcnaline]

So you are using Windows 7. Even better, since that chipset driver is designed for Win7. You're Welcome!!!

 

[Gaza336]

So you are using Windows 7. Even better, since that chipset driver is designed for Win7. You're Welcome!!!

Currently at work at the minute and as I'm surrounded by technical support staff started asking them as well, they explained it could be my RAM not beinggn compatible with my new CPU which I will also check when I'm home but im 50/50 on this.

My partner thought it would be a good idea to recently resort in reformatting my computer to eliminate any driver issues and updating drivers one by one as well as the default settings on the bios. (Need to lock either her or the computer away from each other ha!) However, before I left the house (only tried once) updating my GPU timed out on the device manager being unable to communicate. But I will see how it is later tonight as it was updating windows as I left. Apologies if this probably causes an issue in your troubleshooting! Do appreciate all your help and merry Christmas to you all!

 

[Gaza336]

So guys,

It seems to maybe be related to the hard drive? Reason I say this as one once I done a defrag the computer rebooted a couple times then recommended I do a chkdsk for consistency check. It came back clear and moved some 'corrupt clusters' once it passes the starting windows page I get a continuous blue screen whenever it tries to load windows.
The only way I can get into windows is reformatting and installing windows as it blue screens even when accessing safe mode.

Unsure how I can resolve this or if it is accurate.. Could be wrong but seems to be more related to that. Any thoughts?

 

[Paul NZ]

One of the stop errors as above is CPU related, the other 0x116 can mean the videocard is faulty / or the drivers

 

[johnbl]

person is running build 6.1.7600.16385
you will bugcheck, get over it or install the service pack and updates to windows 7 rtm

 

[Gaza336]

Could a bad motherboard cause the cpu to have this bugcheck error/reboot? Reason I ask is that I've tested on another AMD cpu and the same error occurs.

How can I rule out the motherboard if possible?