BSOD 2-3 minutes after logging into Win 7

Welcome

Make sure you are not running out of hard drive space.

Please download the stable version of Intel Rapid Storage drivers from here:

• Intel® Rapid Storage Technology Version:11.2.0.1006

Code:

Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 83656b40, aecd3744, 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 : iaStor.sys ( iaStor+41b40 )

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

0: 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: 83656b40, The address that the exception occurred at
Arg3: aecd3744, 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: 
iaStor+41b40
83656b40 8b4704          mov     eax,dword ptr [edi+4]

TRAP_FRAME:  aecd3744 -- (.trap 0xffffffffaecd3744)
ErrCode = 00000000
eax=89c4ffb0 ebx=00000000 ecx=0000000e edx=89c4ff40 esi=89c4ff40 edi=00000000
eip=83656b40 esp=aecd37b8 ebp=aecd37c8 iopl=0         nv up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
iaStor+0x41b40:
83656b40 8b4704          mov     eax,dword ptr [edi+4] ds:0023:00000004=????????
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 82c8bc0e to 83656b40

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
aecd37c8 82c8bc0e 873c2030 89c4ffb0 94ff74f0 iaStor+0x41b40
aecd37e0 83781db5 aac929a8 82c8bb89 00000001 nt!IofCallDriver+0x63
aecd3814 8378dfa0 aecd38e8 6de24705 00000000 MpFilter+0xdb5
aecd38a8 8378db5f 00c68670 aecd38e8 00000000 MpFilter+0xcfa0
aecd38c4 8375019a 85c68670 aecd38e8 aecd3900 MpFilter+0xcb5f
aecd3930 837559ec 85c48008 85c68610 2db9e18d fltmgr!FltpPerformPreMountCallbacks+0x1d0
aecd3998 83755c5b 866f4918 85c75678 85c75678 fltmgr!FltpFsControlMountVolume+0x116
aecd39c8 82c8bc0e 866f4918 85c75678 82d8cb88 fltmgr!FltpFsControl+0x5b
aecd39e0 82deedc7 82c21870 873c2030 82c21900 nt!IofCallDriver+0x63
aecd3a44 82cfc8fa 873c2030 85b84001 00000000 nt!IopMountVolume+0x1d8
aecd3a7c 82e9ace3 85b84008 aecd3ba8 aecd3b40 nt!IopCheckVpbMounted+0x64
aecd3b60 82e7ac1e 873c2030 a59b2518 8a03c600 nt!IopParseDevice+0x7db
aecd3bdc 82e8b030 00000000 aecd3c30 00000040 nt!ObpLookupObjectName+0x4fa
aecd3c38 82e81b0e 00c5ea30 859b2518 00000001 nt!ObOpenObjectByName+0x165
aecd3cb4 82ea5366 00c5ea8c 80100080 00c5ea30 nt!IopCreateFile+0x673
aecd3d00 82c9289a 00c5ea8c 80100080 00c5ea30 nt!NtCreateFile+0x34
aecd3d00 76e27094 00c5ea8c 80100080 00c5ea30 nt!KiFastCallEntry+0x12a
00c5ea94 00000000 00000000 00000000 00000000 0x76e27094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+41b40
83656b40 8b4704          mov     eax,dword ptr [edi+4]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  iaStor+41b40

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a287809

FAILURE_BUCKET_ID:  0x8E_iaStor+41b40

BUCKET_ID:  0x8E_iaStor+41b40

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

0: kd> lmvm iaStor
start    end        module name
83615000 836ef000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Fri Jun 05 07:42:33 2009 (4A287809)
    CheckSum:         0005798D
    ImageSize:        000DA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Make scans with the following:

-Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

-ESET online scanner

• Free Online Virus Scanner | ESET

Perform a System File Check to check the integrity of all protected Windows 7:

• Click Start Menu
• Click All Programs
• Click Accessories
• Right click Command Prompt
• Click Run as administrator
• Type
• Code:

  sfc /scannow

• and press Enter

Full tutorial here:

• SFC /Scannow Command - System File Checker

Check your hard drive(s) for errors by running chkdsk:

• Check your hard disk for errors
• Disk Check

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

• Click on the Start button
• Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
• Select the “Startup” tab.
• Deselect all items other than the antivirus.
• Apply > OK
• Accept then restart.

Full tutorial:

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

For monitoring the heat/celsius of the system, use Speccy or HWMonitor:

• Speccy System Information
• HWMonitor

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Hope this helps for now.