BSOD/Random Restarts Playing Smite/browsing

Hello, I just bought a Cyberpower PC a few months ago and I have been having issues with randoms restarts and Blue screens. It mostly occurs when I am playing Smite. I have tried various "fixes" but have had no luck.

Thanks! Jordan.

Your recent BSODs are stop 0x124; which is supposed to be a hardware error. So at that point Driver verifier is not needed. Disable it, following the option two of the tutorial: Driver Verifier - Enable and Disable

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Uninstall Trend Micro. You have MSE installed, and that is enough. Multiple security programs are not a good idea, they clash, and causes issues including BSODs. Use Microsoft Security Essentials as your antivirus (which you already have) with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Now, check for some hardware elements.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is good. Also let us know the wattage of your PSU.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Let us know the results.
_______________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008bb3038, 0, 0}

Probably caused by : AuthenticAMD

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

2: kd> !sysinfo machineid
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
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: fffffa8008bb3038, 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`031bd5b0 fffff800`034cfca9 : fffffa80`08bb3010 fffffa80`06766660 fffffa80`61656857 00000000`00000609 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031bdad0 fffff800`033b0e87 : fffffa80`08bb3010 fffff800`0342a2d8 fffffa80`06766660 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031bdb00 fffff800`03318285 : fffff800`0348bae0 00000000`00000001 fffffa80`08be9160 fffffa80`06766660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031bdb40 fffff800`0328e251 : fffff880`01101e00 fffff800`03318260 fffffa80`06766600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031bdb70 fffff800`03522ede : 00000000`00000000 fffffa80`06766660 00000000`00000080 fffffa80`0673f9e0 : nt!ExpWorkerThread+0x111
fffff880`031bdc00 fffff800`03275906 : fffff880`02fd7180 fffffa80`06766660 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdc40 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bcb90 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:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

2: kd> !errrec fffffa8008bb3038
===============================================================================
Common Platform Error Record @ fffffa8008bb3038
-------------------------------------------------------------------------------
Record Id     : 01ce8b2124f1630b
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/27/2013 23:29:40 (UTC)
Flags         : 0x00000002 PreviousError

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

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

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

Local APIC Id : 0x0000000000000000
CPU Id        : 12 0f 60 00 00 08 04 00 - 0b 22 98 1e 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  @ fffffa8008bb3250

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

Error         : DCACHELG_WR_ERR (Proc 0 Bank 4)
  Status      : 0xf300000000190127

Its good to know :)