Your BSODs seem really random compared to a lot. You have USB audio references, memory and stack buffer overflow.
the one that has caught my eye is the stack buffer overflow which is caused by a driver dumping too much information into a stack which "overflows" into a nearby stack or sometimes a completely different stack causing random issues. However this bugcheck is suspicious and indicates a malicious attack has taken place.
Can you please run your Anti Virus and Malwarebytes to scan for viruses as that seems the most likely cause at the moment.
Post the results.
https://www.malwarebytes.org/free/
Also, when you install malwarebytes untick the box that says "Activate a free 60 day trial of malwarebytes pro
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 832067ab, 9fbcd9d4, 0}
Probably caused by : usbaudio.sys ( usbaudio!USBHwGetClockRatio+f7 )
Followup: MachineOwner
Code:
90006000 90ac4000 atikmdag (deferred)
Image path: atikmdag.sys
Image name: atikmdag.sys
Timestamp: Tue Oct 08 14:45:59 2013 (52540C97)
CheckSum: 00A72B72
ImageSize: 00ABE000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and bugcheck call is the one that overran its local
variable(s).
Arguments:
Arg1: a3cb3c53, Actual security check cookie from the stack
Arg2: 32801ed5, Expected security check cookie
Arg3: cd7fe12a, Complement of the expected security check cookie
Arg4: 00000000, zero
We'll focus on possible driver issues if your scans come back clean.