The issue "went away" for about two weeks, but it's plagued me for several days now. The problem, I've added 8gb of ram on April 20th (ran windows self-test memory, no "errors") as well as a 600w modular Corsair power supply about 2-3 days before the errors began, and then upgraded (ugh) to Windows 8.1 on Sunday, when the errors began (I believe May 17th) in preparation of Win10.

•OS: Windows 8.1 Pro 64-bit (6.3, Build 9600)

•MB: Gigabyte B85M-DS3H

•i5 4690k CPU (not overlocked), 16gb of memory

•120gb SSD (ran ssdlife test on it, came back excellent)

I've uninstalled, reinstalled the display drivers, and it doesn't seem to help any. Some of the BSOD errors include: system thread exception not handled, msrpc.sys. system_thread_exception_not_handled (with no sys this time), 0xc000021a (nothing else listed), and MEMORY_MANAGEMENT (which is why I ran the ram tests). Not sure how to find the dump, though, to post that here.

Here's some of the Event Viewer logs:
•The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.
•Name resolution for the name www.bis.doc.gov timed out after none of the configured DNS servers responded. (WTF? not even sure what this website is)
•wuaueng.dll (1184) SUS20ClientDataStore: The database page read from the file "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 98304 (0x0000000000018000) (database page 2 (0x2)) for 32768 (0x00008000) bytes failed verification. Bit 149234 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.
EDIT: Sorry for the trash formatting, not familiar with Reddit so much. Also, before the system crashed, it gave the "oops" error for both Chrome, and crashed out of Firefox.