BSOD when running media or playing games, error 0x000000e1

Welcome to the forum.

I have seen this bug code common when McAfee is installed. From the dump file it does show that you have McAfee installed. Please uninstall it and see if the BSOD's stop.

Code:

mfehidk	Wed Jan 16 00:21:15 2013 (50f59e1b)	000bc7fd		mfehidk.sys

• Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
  
  • Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
  • Help protect your PC with Microsoft Security Essentials
  • Malwarebytes Free

   Note

Do not start the trial version of MalwareBytes

• Also take a look at: Good & Free System Security Combination

Next time you get a BSOD. Please Grab all and upload the files.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck E1, {fffff80002dbaad0, 2, fffffa8004315320, fffffa8004315320}

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: fffff80002dbaad0, 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: fffffa8004315320, workitem parameter
Arg4: fffffa8004315320, workitem address

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


FAULTING_IP: 
nt!IopProcessWorkItem+0
fffff800`02dbaad0 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 fffff80002b4aef8 to fffff80002ac2b80

STACK_TEXT:  
fffff880`01fd5ca8 fffff800`02b4aef8 : 00000000`000000e1 fffff800`02dbaad0 00000000`00000002 fffffa80`04315320 : nt!KeBugCheckEx
fffff880`01fd5cb0 fffff800`02d60bae : 3f3f3f3f`3f3f3f3f fffffa80`03b3ab50 00000000`00000080 fffffa80`03b30040 : nt! ?? ::FNODOBFM::`string'+0x58286
fffff880`01fd5d40 fffff800`02ab38c6 : fffff880`01e5c180 fffffa80`03b3ab50 fffff880`01e66fc0 3f3f3f3f`3f3f3f3f : nt!PspSystemThreadStartup+0x5a
fffff880`01fd5d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!IopProcessWorkItem+0
fffff800`02dbaad0 fff3            push    rbx

SYMBOL_NAME:  nt!IopProcessWorkItem+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

FAILURE_BUCKET_ID:  X64_0xE1_nt!IopProcessWorkItem+0

BUCKET_ID:  X64_0xE1_nt!IopProcessWorkItem+0

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

Good luck!