BSOD error browsing firefox

[Bhillski]

So my computer randomly gets the BSOD. Can anyone help me. Here if my dxdiag and attached. Any help would be greatly appreciated
------------------
System Information
------------------
Time of this report: 4/11/2014, 05:40:17
Machine name: AMROTH-HP
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
Language: English (Regional Setting: English)
System Manufacturer: Hewlett-Packard
System Model: HPE-500f
BIOS: BIOS Date: 09/07/10 08:41:32 Ver: 6.04
Processor: AMD Phenom(tm) II X6 1045T Processor (6 CPUs), ~2.7GHz
Memory: 8192MB RAM
Available OS Memory: 8192MB RAM
Page File: 1987MB used, 14392MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 560
Manufacturer: NVIDIA
Chip type: GeForce GTX 560
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1201&SUBSYS_20693842&REV_A1
Display Memory: 4047 MB
Dedicated Memory: 1999 MB
Shared Memory: 2047 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: IPS236
Monitor Id: GSM580C
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.2049 (English)
Driver Version: 9.18.13.2049
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 6/21/2013 08:06:36, 15144928 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-5141-11CF-F353-64001CC2C435}
Vendor ID: 0x10DE
Device ID: 0x1201
SubSys ID: 0x20693842
Revision ID: 0x00A1

 

[koolkat77]

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


Loading Dump File [C:\Users\Usra\Downloads\AMROTH-HP-Fri_04_11_2014__52953_64\041114-29234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03450000 PsLoadedModuleList = 0xfffff800`036936d0
Debug session time: Fri Apr 11 15:23:21.496 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:13.729
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, fffffa80088b18f8, 0, 0}

Probably caused by : AuthenticAMD

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

0: 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: fffffa80088b18f8, 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

STACK_TEXT:  
fffff880`033846f0 fffff800`03710ca9 : fffffa80`088b18d0 fffffa80`06b00b50 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03384c10 fffff800`035f1ea7 : fffffa80`088b18d0 fffff800`0366b2d8 fffffa80`06b00b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03384c40 fffff800`03559275 : fffff800`036ccb40 00000000`00000001 fffffa80`079a9820 fffffa80`06b00b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03384c80 fffff800`034cf261 : fffff880`01123e00 fffff800`03559250 fffffa80`06b00b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03384cb0 fffff800`037622ea : 00000000`00000000 fffffa80`06b00b50 00000000`00000080 fffffa80`06a25740 : nt!ExpWorkerThread+0x111
fffff880`03384d40 fffff800`034b68e6 : fffff880`0328f180 fffffa80`06b00b50 fffff880`0329a040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03384d80 00000000`00000000 : fffff880`03385000 fffff880`0337f000 fffff880`033842e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

0: kd> !errrec fffffa80088b18f8
===============================================================================
Common Platform Error Record @ fffffa80088b18f8
-------------------------------------------------------------------------------
Record Id     : 01cf5567a79044a7
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 4/11/2014 9:23:21 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80088b1978
Section       @ fffffa80088b1a50
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    @ fffffa80088b19c0
Section       @ fffffa80088b1b10
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  @ fffffa80088b1b10

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

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

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