Is the dumpfiles rarely nail what the issue is. I continue to use the same old methods to solve BSODs. That is, know as much as I can about the machine, always hit google with the BSOD like https://www.google.com/search?q=0x124_AuthenticAMD&ie=utf-8&oe=utf-8 and see where it all lines up.
No one I know to date has nailed BSOD issues using the dump.
Bob
I had some BSOD'S during games (which does not need good pc) so i decided to check out the minidump file.
Here is the Minidump file:
FAULTING_MODULE: fffff80231872000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUGCHECK_STR: 0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:
ffffd000`208fb500 ffffe000`02355000 : 00000000`00000000 ffffe000`022928f8 fffff802`3180963e ffffe000`022928f8 : nt+0x5b1f85
ffffd000`208fb508 00000000`00000000 : ffffe000`022928f8 fffff802`3180963e ffffe000`022928f8 00000000`00000000 : 0xffffe000`02355000
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
IMAGE_VERSION:
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
What may be the reason of these BSOD'S?

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic