Solved BSOD from waking up from sleep

[abhishek33]

This morning when I tried to wake up my computer, nothing would display on the computer screen. I had to turn it off and then turn it back on. As it tried to resume windows, I got the BSOD. When I restarted my computer, I got the following message:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105

Additional information about the problem:
BCCode: 9088
BCP1: FFFFF88008E388C0
BCP2: FFFFF88008E388C4
BCP3: FFFFF88008E388C8
BCP4: FFFFF88008E388CC
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Does anyone know what the issue is?

 

[Arc]

Hello abhishek33.

A stop 0x9088 is somehow common with the intel storage drivers. So I would suggest you to get rid of intel matrix storage. First uninstall Intel® Matrix Storage Manager from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Next, do you encrypt data using Axantum AxCrypt? As it is a storage related issue, uninstall it too, as least as a test.

Let us know the results.
__________________________________________________________________________
BSOD ANALYSIS:

*** 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 9088, {fffff88008e388c0, fffff88008e388c4, fffff88008e388c8, fffff88008e388cc}

Probably caused by : iaStor.sys ( iaStor+50ceb )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Unknown bugcheck code (9088)
Unknown bugcheck description
Arguments:
Arg1: fffff88008e388c0
Arg2: fffff88008e388c4
Arg3: fffff88008e388c8
Arg4: fffff88008e388cc

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9088

PROCESS_NAME:  IAANTmon.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800110fceb to fffff80002e8dc00

STACK_TEXT:  
fffff880`08e38858 fffff880`0110fceb : 00000000`00009088 fffff880`08e388c0 fffff880`08e388c4 fffff880`08e388c8 : nt!KeBugCheckEx
fffff880`08e38860 00000000`00009088 : fffff880`08e388c0 fffff880`08e388c4 fffff880`08e388c8 fffff880`08e388cc : iaStor+0x50ceb
fffff880`08e38868 fffff880`08e388c0 : fffff880`08e388c4 fffff880`08e388c8 fffff880`08e388cc fffffa80`03d05c30 : 0x9088
fffff880`08e38870 fffff880`08e388c4 : fffff880`08e388c8 fffff880`08e388cc fffffa80`03d05c30 fffffa80`04a72000 : 0xfffff880`08e388c0
fffff880`08e38878 fffff880`08e388c8 : fffff880`08e388cc fffffa80`03d05c30 fffffa80`04a72000 fffffa80`03bcd1a0 : 0xfffff880`08e388c4
fffff880`08e38880 fffff880`08e388cc : fffffa80`03d05c30 fffffa80`04a72000 fffffa80`03bcd1a0 fffffa80`08b7d300 : 0xfffff880`08e388c8
fffff880`08e38888 fffffa80`03d05c30 : fffffa80`04a72000 fffffa80`03bcd1a0 fffffa80`08b7d300 fffffa80`03bcd1a0 : 0xfffff880`08e388cc
fffff880`08e38890 fffffa80`04a72000 : fffffa80`03bcd1a0 fffffa80`08b7d300 fffffa80`03bcd1a0 00000000`00000000 : 0xfffffa80`03d05c30
fffff880`08e38898 fffffa80`03bcd1a0 : fffffa80`08b7d300 fffffa80`03bcd1a0 00000000`00000000 fffff880`0110a7e9 : 0xfffffa80`04a72000
fffff880`08e388a0 fffffa80`08b7d300 : fffffa80`03bcd1a0 00000000`00000000 fffff880`0110a7e9 00000000`00ab6651 : 0xfffffa80`03bcd1a0
fffff880`08e388a8 fffffa80`03bcd1a0 : 00000000`00000000 fffff880`0110a7e9 00000000`00ab6651 00000000`0088e065 : 0xfffffa80`08b7d300
fffff880`08e388b0 00000000`00000000 : fffff880`0110a7e9 00000000`00ab6651 00000000`0088e065 ffffffff`ffb3b4c0 : 0xfffffa80`03bcd1a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+50ceb
fffff880`0110fceb ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  iaStor+50ceb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b20515f

FAILURE_BUCKET_ID:  X64_0x9088_iaStor+50ceb

BUCKET_ID:  X64_0x9088_iaStor+50ceb

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

3: kd> lmvm iaStor
start             end                 module name
fffff880`010bf000 fffff880`012c7000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Thu Dec 10 07:09:43 2009 (4B20515F)
    CheckSum:         0008DB9F
    ImageSize:        00208000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[abhishek33]

Thanks Arc, I followed your steps and am attaching the results. Is there anything else I can do?

 

[Arc]

Thanks Arc, I followed your steps and am attaching the results. Is there anything else I can do?

Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[abhishek33]

Here's the file

 

[Arc]

Thanks Arc, I followed your steps and am attaching the results. Is there anything else I can do?

Intel matrix storage manager is not uninstalled.

Start Menu\Programs\Intel® Matrix Storage Manager    Public:Start Menu\Programs\Intel® Matrix Storage Manager    Public

The driver is not uninstalled in Device manager, too.

Name    Intel(R) 5 Series/3400 Series SATA AHCI Controller
Manufacturer    Intel
Status    OK
PNP Device ID    PCI\VEN_8086&DEV_3B22&SUBSYS_04271025&REV_06\3&11583659&0&FA
I/O Port    0x0000CC00-0x0000CC07
I/O Port    0x0000C880-0x0000C883
I/O Port    0x0000C800-0x0000C807
I/O Port    0x0000C480-0x0000C483
I/O Port    0x0000C400-0x0000C41F
Memory Address    0xFBDF4000-0xFBDF47FF
IRQ Channel    IRQ 19
Driver    c:\windows\system32\drivers\iastor.sys (9.5.5.1003, 525.02 KB (537,624 bytes), 02/02/2010 9:17 PM)

If the steps are followed, the situation would have been different.

 

[abhishek33]

Hey Arc,

You're correct, I did not follow the steps, my apologies. Attached is the updated info after following the steps. I did notice that in the device manager the intel driver remains even after uninstalling and allowing Win7 install re-install the driver. The matrix manager is gone.

 

[Arc]

Hey Arc,

You're correct, I did not follow the steps, my apologies. Attached is the updated info after following the steps. I did notice that in the device manager the intel driver remains even after uninstalling and allowing Win7 install re-install the driver. The matrix manager is gone.

Why will you make a false statement? Its not good as a practice... and it does not depict a fair picture of the person saying so.

Have you tried at all? Or saying it in the way you said earlier?

If you let the failing driver stay in the system, it will continue to crash. If you cannot remove (or cannot try; as everybody who tried got the result) it the way I said, better you go for a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164

When the reinstall is done, keep away from Daemon tools and virtual clone drive.

 

[abhishek33]

Easy with the attitude. It was not intentional to not follow your steps. In any case thanks for your help, but I'll take it from here and figure it out myself. I don't need someone with attitude to help.

 

[Arc]

Easy with the attitude. It was not intentional to not follow your steps. In any case thanks for your help, but I'll take it from here and figure it out myself. I don't need someone with attitude to help.

Sorry mate. If you say that you have done one thing, and when it came from verification that you havent done it actually then you confess that you havent done it, it is the attitude of help seeker, not the helper.

If we can stay clean at our stand, we can blame someone else successfully. Pointing to a lie is not attitude, but telling a lie is. That is what I have learned from my childhood.

I tried to help you, at my best. You failed to accept it.