HyperTansport Sync Flood Error (Playing Fallout NV)

loudaslife · 08 Jan 2015

Happens at complete random while playing Fallout: New Vegas. The computer will hang for a second, looping the last split second of audio before rebooting, at which point my BIOS tells me there was a "HyperTransport Sync Flood Error". Technically I never see a blue screen at any point, however upon reboot windows tells me that it was a BSOD, and it does appear to generate a Minidump each time.

DM Log Collector .zip is attached.

Specs:
Windows 7 Home Premium 64-bit
AMD Phenom II X4 955 BE
MSI 785GTM-E45 motherboard
XFX Radeon HD 6790 1GB
2 sticks of Corsair VS2GB800D2 ram

Any help is greatly appreciated! I can provide any other information you'd like.

koolkat77 · 14 Jan 2015

Code:


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


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\JAKE-DESKTOP-Thu_01_08_2015_140523_59\010815-25708-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03215000 PsLoadedModuleList = 0xfffff800`03458890
Debug session time: Fri Jan  9 02:00:36.956 2015 (UTC + 6:00)
System Uptime: 0 days 0:00:09.236
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, fffffa80048c18f8, 0, 0}

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: 0000000000000000, Machine Check Exception
Arg2: fffffa80048c18f8, 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) x86fre

STACK_TEXT:  
fffff880`031b66f0 fffff800`034d5cb9 : fffffa80`048c18d0 fffffa80`03a76040 fffff8a0`00000003 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`033b6ea7 : fffffa80`048c18d0 fffff800`034302d8 fffffa80`03a76040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`0331e275 : fffff800`03491d00 00000000`00000001 fffffa80`0492e820 fffffa80`03a76040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`03294261 : fffff880`0104ae00 fffff800`0331e250 fffffa80`03a76000 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`0352673a : 00000000`00000000 fffffa80`03a76040 00000000`00000080 fffffa80`039c7b30 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`0327b8e6 : fffff880`02f64180 fffffa80`03a76040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b60a0 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