BSOD about every 2 or 3 days

I bought a pc of office about 3-4 months ago and it has been a huge headache. It has windows 7 with what seems like AMD controlling a lot of the material (I think). I'm not the most computer and I tried to get error codes each time but nothing I found so far seems to help.

I've uninstalled and reinstalled drivers until my fingers are ready to bleed (mouse, usb, video, enabled updates constantly, etc.). I get the error code is not always the same no more. I'm at my wits end trying to get this resolved. Here's my last werfault, I got.

problem signature:
Problem event name: BlueScreen
OS version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

More information about the problem:
BCCode: 1a
BCP1: 0000000000005003
BCP2: FFFFF70001080000
BCP3: 000000000004A31E
BCP4: 000000002BE68009
OS version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files helping to describe the problem:
C:\Windows\Minidump\081716-22323-01.dmp
C:\Users\Stewge\AppData\Local\Temp\WER-54522-0.SysData.XML

Read our privacy statement online:
http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409

If the online privacy statement is not available, please read our offline privacy statement:
C:\Windows\system32\en-US\erofflps.txt

Here are 2 recent minidumps I.

Minidump on 8/13:

Loading dump file [C:\Windows\Minidump\081316-20046-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are available

Symbol search path is: * invalid *.
****************************************************************************
* Loading of the symbol may be unreliable without a symbol search path.           *
* Use .symfix to get the debugger to choose a symbol path.                   *
* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* with the help of the there when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) free x 64
Product: WinNt, suite: TerminalServer SingleUserTS
By: 7601.23455.amd64fre.win7sp1_ldr.160516 - 0600
Computer name:
Kernel base = 0xfffff800'03a5e000 PsLoadedModuleList = 0xfffff800'03 ca 0730
The debugging session: Sat Aug 13 14:26:06.989 2016 (UTC - 04:00)
System Uptime: 0 days 3:19:44.440
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* with the help of the there when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
..........................................
Loading user symbols
Loading unloaded module list
......

Summary of the symbol load error *.
Name of the module error
Ntoskrnl the system cannot find the specified file

You can solve most symbol related issues by turning the symbol loading diagnostics (! sym noisy) and repeating the command that caused the symbols to load.
You should also check that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

BugCheck C2, {99, fffff8a00dac3810, 0, 0}

The kernel symbols are FALSE. Correct symbols to do the analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
Probably caused by: ntoskrnl.exe (nt + 6f400)

Follow-up: MachineOwner
---------

1: kd >! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is doing a bad pool request.  In general, it is an IRQL bad or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000099, try free pool with invalid address (or corruption in pool header)
Arg2: fffff8a00dac3810, free address
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

Debugging information:
------------------

The kernel symbols are FALSE. Correct symbols to do the analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbols path and of loading symbol.

MODULE_NAME: nt

FAULTING_MODULE: fffff80003a5e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 573a38fc

BUGCHECK_STR: 0xc2_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers (dbg). 150226-1500) x86fre

LAST_CONTROL_TRANSFER: from fffff80003f614ec to fffff80003acd400

STACK_TEXT:
"fffff880 '03-17858 fffff800' 03f614ec: 00000000 ' 000000 c 2 00000000'00000099 fffff8a0 ' 0dac3810 00000000' 00000000: nt + 0x6f400
"fffff880 '03 a 17860 00000000' 000000 c 2: 00000000 ' 00000099 fffff8a0 ' 0dac3810 00000000'00000000 00000000'00000000: nt + 0x5034ec
fffff880 '03 a 17868 00000000' 00000099: fffff8a0 '0dac3810 00000000'00000000 00000000'00000000 fffffa80' b 0, 918701: 0xc2
fffff880 '03-17870 fffff8a0' 0dac3810: 00000000'00000000 00000000'00000000 fffffa80 '0b 918701 fffff8a0' 0dac3810: 0 x 99
"fffff880 '03 has 17878 00000000' 00000000: 00000000 ' 00000000 '0b 918701 fffff8a0' fffffa80 0dac3810 fffff800 ' 03b86be1: 0xfffff8a0'0dac3810

STACK_COMMAND: kb

FOLLOWUP_IP:
NT + 6f400
fffff800'03acd400 48894c 2408 mov qword ptr [rsp + 8], rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt + 6f400

FOLLOWUP_NAME: MachineOwner

Nom_image: ntoskrnl.exe

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}

Follow-up: MachineOwner
---------

Minidump 8/17:

Loading dump file [C:\Windows\Minidump\081716-22323-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are available

Symbol search path is: * invalid *.
****************************************************************************
* Loading of the symbol may be unreliable without a symbol search path.           *
* Use .symfix to get the debugger to choose a symbol path.                   *
* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* with the help of the there when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) free x 64
Product: WinNt, suite: TerminalServer SingleUserTS
By: 7601.23455.amd64fre.win7sp1_ldr.160516 - 0600
Computer name:
Kernel base = 0xfffff800 '03a 50000 PsLoadedModuleList = 0xfffff800' 03C 92730
The debugging session: 02:40:45.576 Wed Aug 17 2016 (UTC - 04:00)
System Uptime: 0 days 16:14:47.653
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* with the help of the there when you start the debugger argument. *.
* using the .sympath and .sympath + *.
*********************************************************************
Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
..........................................
Loading user symbols
Loading unloaded module list
......

Summary of the symbol load error *.
Name of the module error
Ntoskrnl the system cannot find the specified file

You can solve most symbol related issues by turning the symbol loading diagnostics (! sym noisy) and repeating the command that caused the symbols to load.
You should also check that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

Error checking 1A, {5003, fffff70001080000, 4a31e, 2be68009}

The kernel symbols are FALSE. Correct symbols to do the analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
Probably caused by: ntoskrnl.exe (nt + 6f400)

Follow-up: MachineOwner
---------

2: kd >! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1A)
# All other values for parameter 1 must be examined individually.
Arguments:
Arg1: 0000000000005003, the subtype of the error checking.
Arg2: fffff70001080000
Arg3: 000000000004a31e
Arg4: 000000002be68009

Debugging information:
------------------

The kernel symbols are FALSE. Correct symbols to do the analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol.  Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down.     ***
***                                                                   ***
For some commands work properly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbols path and of loading symbol.

MODULE_NAME: nt

FAULTING_MODULE: fffff80003a50000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 573a38fc

BUGCHECK_STR: 0x1a_5003

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers (dbg). 150226-1500) x86fre

LAST_CONTROL_TRANSFER: from fffff80003a5f97c to fffff80003abf400

STACK_TEXT:
fffff880 '0409b 218 fffff800' 03a5f97c: 00000000' 0000001 a 00000000 '00005003 fffff700'01080000 00000000' 0004a31e: nt + 0x6f400
fffff880' 0409b 220 00000000' 0000001 has: 00000000 ' 00005003 fffff700' 01080000 00000000' 0004a31e 00000000' 2be68009: nt + 0xf97c
"fffff880' 0409b 228 00000000'00005003: fffff700 '01080000 00000000' 0004a31e 00000000' 2be68009 fffff880 ' 0409b 380: 0x1a
fffff880'0409 b 230 fffff700'01080000: 00000000' 0004a31e 00000000' 2be68009 fffff880' 0409b 380 00000000 00000000': 0 x 5003
fffff880' 0409b 238 00000000' 0004a31e: 00000000' 2be68009 fffff880 '0409b 380 00000000 00000000' fffff880' 0409b 300: 0xfffff700'01080000
fffff880' 0409b 240 00000000' 2be68009: fffff880 '0409b 380 00000000 00000000' fffff880' 0409b 300 00010000'00000000: 0x4a31e
"fffff880 '0409b 248 fffff880' 0409b 380: 00000000 ' 00000000 fffff880 ' 0409b 300 00010000'00000000 00040004'00030002: 0x2be68009
fffff880' 0409b 250 00000000 00000000': fffff880' 0409b 300 00010000'00000000 00040004'00030002 00000000'00000000: 0xfffff880'0409 b 380

STACK_COMMAND: kb

FOLLOWUP_IP:
NT + 6f400
fffff800'03abf400 48894c 2408 mov qword ptr [rsp + 8], rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt + 6f400

FOLLOWUP_NAME: MachineOwner

Nom_image: ntoskrnl.exe

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}

Follow-up: MachineOwner
---------

I have some more dumps 8 if more if more is needed. I honestly tried to figure this point but it's beyond my small skills.

Thanks for any help/suggestions

Stew