Display static and IRQL BSOD

That's on my list after I'm done letting Windows update, though from what I can understand, faulty memory usually has issues with stressful situations, and I've never had the static issue when running photoshop or in a game so I'm not entirely sure that could be it.

Results are:

On Tue 04/03/2014 7:45:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-18579-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF880049EAFA0)
Bugcheck code: 0xD1 (0xFFFFF8800EE37000, 0x2, 0x0, 0xFFFFF880049EAFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 04/03/2014 7:45:12 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e22w7x64.sys (e22w7x64+0x19FA0)
Bugcheck code: 0xD1 (0xFFFFF8800EE37000, 0x2, 0x0, 0xFFFFF880049EAFA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 28/02/2014 2:43:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022714-17908-01.dmp
This was probably caused by the following module: e22w7x64.sys (0xFFFFF88004019FA0)
Bugcheck code: 0xD1 (0xFFFFF880046BD000, 0x2, 0x0, 0xFFFFF88004019FA0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e22w7x64.sys
product: Killer e2200 PCI-E Gigabit Ethernet Controller
company: Qualcomm Atheros, Inc.
description: Killer e2200 PCI-E Gigabit Ethernet Controller
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e22w7x64.sys (Killer e2200 PCI-E Gigabit Ethernet Controller, Qualcomm Atheros, Inc.).
Google query: Qualcomm Atheros, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

Currently downloading the drivers on Qualcomm's website, hopefully that will fix it, though it's estimated to take over an hour to download. Will report back.

Hmm, it says
Qualcomm Atheros Killer E2200 Gigabit Ethernet Controller
Bigfoot Networks Killer 2100/E2100/Xeno Pro
INF file date 12/12/2012
Driver version 6.1.0.603 WHQL
and also that that the driver is up to date, and this is the driver that the page links me to.

I'm using 64 bit. From what I understand the system32 location doesn't mean the OS is 32 bit.

Okay, I reinstalled the driver that Ma-Config recommended (after creating a system restore point), and then as I attempted to restart, it froze and did this:

and I had to just power it off from the tower.

And upon it restarting, it took a very long time to load. After I logged in it was a good 30 seconds of black screen and cursor (could get Ctrl Alt Delete to work) until the desktop elements started loading in.

edit: Attempted to run DisplayDriverUninstaller in Safe Mode w/ Networking, DDU didn't work for some reason, but it didn't do the freeze on shut down again.

Alright, I've installed new network adapter drivers that seems to have fixed the BSOD issue (haven't gotten one yet but it was completely unpredictable so... who knows), but the flickering static crash screen continues. Now so far, I've installed AMD's CCC driver suite thingy after uninstalling (without anything like display driver uninstaller, btw) the version I already had, which didn't fix the problem, and did make the computer think I didn't have a GPU installed. I system restore'd back to before I messed around with those drivers, and now I know several things; switching the monitor off does not make the problem go away, and in safe mode there isn't an issue with shutting down. I haven't tried just switching users because I don't want to keep having to shut it off from the power button, but both log off, shut down, and restart cause it to crash, usually right at the point where the task bar and things disappear and you're just left with your desktop background which then fades into the "Shutting down...." page or w/e it is.

It says the Max reported refresh rate for the monitor is 75 Hz

What do you mean by "his video chipset from the maker of the motherboard"?