Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD 2-3 minutes after logging into Win 7

18 Mar 2013   #1

Windows 7 Professional 32 bit
BSOD 2-3 minutes after logging into Win 7

Hello everyone,

I have been struggling with my laptop for hours; when I log into Win 7 after 2-3 minutes I get a BSOD but in safe mode I have no problem at all (I'm posting this from safe mode).

I have tried updating my graphics card driver (NVidia GeForce 9300M GS), uninstalling most recent programs, disabling different hardware from device manager and uninstalling their drivers, running check disk, and a full virus scan with MS security essentials but the problem still exists.

Please help me solve this problem, thank you for your time and help in advance :)

My System SpecsSystem Spec
18 Mar 2013   #2

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit


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

Please download the stable version of Intel Rapid Storage drivers from here:
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                                    *
*                                                                             *

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

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
83656b40 8b4704          mov     eax,dword ptr [edi+4] ds:0023:00000004=????????
Resetting default scope






LAST_CONTROL_TRANSFER:  from 82c8bc0e to 83656b40

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


83656b40 8b4704          mov     eax,dword ptr [edi+4]


SYMBOL_NAME:  iaStor+41b40

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  iaStor.sys


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-ESET online scannerPerform 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:Check your hard drive(s) for errors by running chkdsk: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:For monitoring the heat/celsius of the system, use Speccy or HWMonitor:Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Note   Note
Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Do this test overnight, before going to bed.

Hope this helps for now.
My System SpecsSystem Spec

 BSOD 2-3 minutes after logging into Win 7

Thread Tools

Similar help and support threads
Thread Forum
I always get a BSOD a few minutes after logging in.
Hi, I keep getting the Blue Screen of Death a few minutes after logging in. This always happens unless I'm in safe mode in which case the computer works fine. Here's the screen I get: Here's what DM Log Collector...
BSOD Help and Support
BSOD after logging on for around 2 minutes, error 0x0000008E
BSOD occurs whenever i select start normally after a crash. Even if shutdown is successful it will still crash. I did a few system restores and had a successful log on w/o a BSOD. After shutdown with the first log on after system restore BSOD occurred every time after the first successful log on. ...
BSOD Help and Support
BSOD 5 minutes after logging onto computer error 0x00000019
After logging onto the computer, I would get the bsod error after 5 minutes. I uses that tIme to upload the minidump. The error code is Stop 0x00000019 (0x0000000000000020,0xfffff900c01e5000,0xffff900c01e5240,x0000000025240000 Note, I did not update any drivers recently. I just got this error...
BSOD Help and Support
BSOD Occurs 5 Minutes After Logging In
Hello, I'm a student technician at a university. A customer brought in a laptop, which bluescreens after approximately 5 minutes of logging in. -Windows 7 Home Premium 32-bit / HP 620 Laptop / Model # D40 / 2GB RAM -It does not crash in Safe Mode -Windows Update will not open (normal or...
BSOD Help and Support
BSOD within minutes of logging in
When I tried logging in this morning I got a BSOD saying "PAGE_FAULT_IN_NONPAGED_AREA". It kept happening after rebooting so I used system restore and that went away. But then I got a BSOD saying "a clock interrupt was not received on the secondary processor". This happens either right when I log...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 21:22.
Twitter Facebook Google+