BSOD Error 0x0000008E Mini dump check

elitehass

Can some please check this mini dump to figure out whats wrong with my system?

<DD>http://www.megaupload.com/?d=VM0ST742
As soon as I log in I reccieve the BSOD error 0x0000008E and it restarts my system. Ive tried everything mentioned on this thread apart from reinstalling windows http://tech.icrontic.com/articles/columns/fix-the-0x0000008e-bsod-once-and-for-all/
</DD>

EMT

Based on seeing MpFilter involved, I suggest updating/uninstalling Microsoft Security Essentials. Something like this solution: http://answers.microsoft.com/en-us/protect/forum/protect_start/bluescreen-mpfiltersys-driver/1550825c-1c53-4e58-bc96-ec96deef1d51

OSR Instant Crash Dump Analysis:

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x8304d000 PsLoadedModuleList = 0x83195810
Debug session time: Thu Apr 21 12:27:20.734 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:19.513
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 839c7487, The address that the exception occurred at
Arg3: b938475c, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
ataport!IdePortDispatchDeviceControl+b
839c7487 80b98600000000  cmp     byte ptr [ecx+86h],0

TRAP_FRAME:  b938475c -- (.trap 0xffffffffb938475c)
ErrCode = 00000000
eax=85d709a8 ebx=00000000 ecx=00000000 edx=850443a8 esi=85d709a8 edi=830893e1
eip=839c7487 esp=b93847d0 ebp=b93847d0 iopl=0         nv up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
ataport!IdePortDispatchDeviceControl+0xb:
839c7487 80b98600000000  cmp     byte ptr [ecx+86h],0       ds:0023:00000086=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 830894ac to 839c7487

STACK_TEXT:  
b93847d0 830894ac 85d709a8 850443a8 af1392b8 ataport!IdePortDispatchDeviceControl+0xb
b93847e8 837d9bf1 837dd290 accb5ef0 85040000 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
b9384818 837e6d73 b93848e8 3a459459 00000000 MpFilter+0xbf1
b93848ac 837e74d6 85d6e240 b93848e8 00000000 MpFilter+0xdd73
b93848c4 837a819a 85d6e240 003848e8 b9384900 MpFilter+0xe4d6
b9384930 837ad9ec 84eeaad8 85d6e1e0 3a4210d5 fltmgr!FltpPerformPreMountCallbacks+0x1d0
b9384998 837adc5b 85a5e650 869a6b30 869a6b30 fltmgr!FltpFsControlMountVolume+0x116
b93849c8 830894ac 85a5e650 869a6b30 83183d80 fltmgr!FltpFsControl+0x5b
b93849e0 8320502b 83019870 85d709a8 83019900 nt!IofCallDriver+0x63
b9384a44 830e9514 85d709a8 84ed8d01 00000000 nt!IopMountVolume+0x1d8
b9384a7c 8328d3ef 84ed8d20 b9384ba8 b9384b40 nt!IopCheckVpbMounted+0x64
b9384b60 8326e57b 85d709a8 a5d758f0 8750a800 nt!IopParseDevice+0x7c9
b9384bdc 83294729 00000000 b9384c30 00000040 nt!ObpLookupObjectName+0x4fa
b9384c38 8328ca7b 011be72c 84d758f0 00000001 nt!ObOpenObjectByName+0x165
b9384cb4 83298392 011be788 80100080 011be72c nt!IopCreateFile+0x673
b9384d00 8309043a 011be788 80100080 011be72c nt!NtCreateFile+0x34
b9384d00 775b6344 011be788 80100080 011be72c nt!KiFastCallEntry+0x12a
011be790 00000000 00000000 00000000 00000000 0x775b6344


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdePortDispatchDeviceControl+b
839c7487 80b98600000000  cmp     byte ptr [ecx+86h],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ataport!IdePortDispatchDeviceControl+b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf16

FAILURE_BUCKET_ID:  0x8E_ataport!IdePortDispatchDeviceControl+b

BUCKET_ID:  0x8E_ataport!IdePortDispatchDeviceControl+b

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