BSOD a few minutes after reboot

Hello,

I'm receiving a BSOD (unreadable) everytime machines boots up. I have attached results of the SF diagnostics along with screenshots of the BSOD that is unreadable, along with the Windows has expected an error seen after each bootup after the BSOD. In addition, the SF diagnostics report does not seem to complete fully before the BSOD happens.nly have a minute or two before the BSOD. So, there's not much time to do anything.

Windows 7 Home Premium 32-bit.

Thanks,
Mike

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 83350487, a08b7754, 0}

*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : ataport.SYS ( ataport!IdePortDispatchDeviceControl+b )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 83350487, The address that the exception occurred at
Arg3: a08b7754, 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
83350487 80b98600000000  cmp     byte ptr [ecx+86h],0

TRAP_FRAME:  a08b7754 -- (.trap 0xffffffffa08b7754)
ErrCode = 00000000
eax=85b4c030 ebx=00000000 ecx=00000000 edx=85c959e8 esi=85b4c030 edi=a08b7800
eip=83350487 esp=a08b77c8 ebp=a08b77c8 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:
83350487 80b98600000000  cmp     byte ptr [ecx+86h],0       ds:0023:00000086=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82a48c29 to 83350487

STACK_TEXT:  
a08b77c8 82a48c29 85b4c030 85c959e8 9246cf88 ataport!IdePortDispatchDeviceControl+0xb
a08b77e0 833bbef7 a38d1288 82a48bb9 00000001 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
a08b7814 833c84a2 a08b78e8 43979d43 00000000 MpFilter+0xef7
a08b78a8 833c8061 009aa6e8 a08b78e8 00000000 MpFilter+0xd4a2
a08b78c4 8338a19a 859aa6e8 a08b78e8 a08b7900 MpFilter+0xd061
a08b7930 8338f9ec 84d0f438 859aa688 23b301a3 fltmgr!FltpPerformPreMountCallbacks+0x1d0
a08b7998 8338fc5b 85884c40 86238428 86238428 fltmgr!FltpFsControlMountVolume+0x116
a08b79c8 82a48c29 85884c40 86238428 82b4ab88 fltmgr!FltpFsControl+0x5b
a08b79e0 82bacdd2 82e28870 85b4c030 82e28900 nt!IofCallDriver+0x63
a08b7a44 82ab9bea 85b4c030 84d09001 00000000 nt!IopMountVolume+0x1d8
a08b7a7c 82c58d39 84d09008 a08b7ba8 a08b7b40 nt!IopCheckVpbMounted+0x64
a08b7b60 82c38c4e 85b4c030 a5be2588 84d61480 nt!IopParseDevice+0x7c9
a08b7bdc 82c49060 00000000 a08b7c30 00000040 nt!ObpLookupObjectName+0x4fa
a08b7c38 82c3fb3e 00dbe948 84be2588 00000001 nt!ObOpenObjectByName+0x165
a08b7cb4 82c633c4 00dbe9a4 80100080 00dbe948 nt!IopCreateFile+0x673
a08b7d00 82a4f8fa 00dbe9a4 80100080 00dbe948 nt!NtCreateFile+0x34
a08b7d00 77ce7094 00dbe9a4 80100080 00dbe948 nt!KiFastCallEntry+0x12a
00dbe9ac 00000000 00000000 00000000 00000000 0x77ce7094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdePortDispatchDeviceControl+b
83350487 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:  4ce788e8

FAILURE_BUCKET_ID:  0x8E_ataport!IdePortDispatchDeviceControl+b

BUCKET_ID:  0x8E_ataport!IdePortDispatchDeviceControl+b

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

Update your MSE version to the latest version.

Make sure you have latest video drivers.

Check that you have adequate disk space, especially for new installations.

Disable any newly installed drivers. You might also want to disable a service associated with the driver or any newly installed programs.

If the computer will not start normally, try starting it in Last Known Good Configuration or in Safe Mode, and then remove or disable newly added programs or drivers. For information about how to start your computer in Safe Mode, see Start the computer in Safe Mode. For more information about how to start your computer in Last Known Good Configuration, see Start the computer using the last known good configuration.

Troubleshooting specific Stop messages

Not sure how this is done:

"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".

mstritt4302 said:

Not sure how this is done:

"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".

Just skip that part.

Follow the other steps

BSOD happens about 30 seconds after desktop loads. So, I don't have time to uninstall MSE and install new version. After booting in SAFE mode, it will not allow me to uninstall MSE. Says I have to be in standard mode. If I attempt to update video driver via SAFE mode with networking, it says I have the latest driver version. Concerning system information file, as I mentioned, I can't really do anything on bootup in standard mode. I receive BSOD shortly after desktop loads. I tried running System Information in SAFE mode, however, after it began to collect/refresh information, it just hangs.

Update from the manufacturer`s website to update drivers.

Don`t use device manager to update them