BSOD started while streaming, now is consistant. PSU issue?

Don't worry, it's not your PSU or any hardware.
McAfee

Code:

mfeapfk.sys                 Wed Jan 16 00:21:56 2013 (50F59E44)
mfeavfk.sys                 Wed Jan 16 00:22:16 2013 (50F59E58)
mfefirek.sys                Wed Jan 16 00:24:04 2013 (50F59EC4)
mfehidk.sys                 Wed Jan 16 00:21:15 2013 (50F59E1B)
mfewfpk.sys                 Wed Jan 16 00:21:30 2013 (50F59E2A)

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck E1, {fffff800037c8d50, 2, fffffa80101b8860, fffffa80101b8860}

Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WORKER_THREAD_RETURNED_AT_BAD_IRQL (e1)
Arguments:
Arg1: fffff800037c8d50, address of worker routine (do ln on this to find guilty driver)
Arg2: 0000000000000002, IRQL returned at (should have been 0, but isn't).
Arg3: fffffa80101b8860, workitem parameter
Arg4: fffffa80101b8860, workitem address

Debugging Details:
------------------


FAULTING_IP: 
nt!IopProcessWorkItem+0
fffff800`037c8d50 fff3            push    rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xE1

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003558ef8 to fffff800034d0c00

STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!IopProcessWorkItem+0
fffff800`037c8d50 fff3            push    rbx

SYMBOL_NAME:  nt!IopProcessWorkItem+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0xE1_nt!IopProcessWorkItem+0

BUCKET_ID:  X64_0xE1_nt!IopProcessWorkItem+0

Followup: MachineOwner
---------            
Unloaded modules:
fffff880`0b086000 fffff880`0b0f7000   spsys.sys
fffff880`0b195000 fffff880`0b1cb000   WUDFRd.sys
fffff880`0a3ab000 fffff880`0a3f5000   mfeavfk01.sy
fffff880`01d98000 fffff880`01da6000   crashdmp.sys
fffff880`04435000 fffff880`047d9000   dump_iaStor.
fffff880`047d9000 fffff880`047ec000   dump_dumpfve

We have seen McAfee cause BSOD's on several systems and recommend uninstalling it with the McAfee Removal Tool and replace with Microsoft Security Essentials. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do.

Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free

   Information

• Do not start the free trial of MalwareBytes, unselect that option when prompted.
  
  
  
• Update and make full scans with both separately.

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Drivers:

Atheros Driver

Code:

athrx.sys                   Mon Dec 12 19:02:13 2011 (4EE5FB55)
Atheros network adapter driver

If its wireless, match your device from here:
ATHEROS Wireless drivers for Windows

If its not a wireless, match your device from here:
ATHEROS Network drivers for Windows


BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat Jun  8 05:05:48.000 2013 (UTC + 6:00)
System Uptime: 1 days 0:16:43.218
BugCheck E1, {fffff800037c8d50, 2, fffffa80101b8860, fffffa80101b8860}
Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )
BUGCHECK_STR:  0xE1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jun  7 04:48:35.790 2013 (UTC + 6:00)
System Uptime: 0 days 0:57:35.008
BugCheck E1, {fffff800037b8d50, 2, fffffa800999e0f0, fffffa800999e0f0}
Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )
BUGCHECK_STR:  0xE1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Jun  7 03:50:17.001 2013 (UTC + 6:00)
System Uptime: 0 days 17:55:51.219
BugCheck E1, {fffff800037c1d50, 2, fffffa8015ec42a0, fffffa8015ec42a0}
Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )
BUGCHECK_STR:  0xE1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue May 28 07:01:43.346 2013 (UTC + 6:00)
System Uptime: 0 days 0:39:44.564
BugCheck E1, {fffff80003777d50, 2, fffffa80102e10e0, fffffa80102e10e0}
Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )
BUGCHECK_STR:  0xE1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Is there any update to this thread.