BSOD and freezes under a variety of conditions

Hi EBIB777.

Your issue is a bit critical, and hard to solve on a permanent basis without a clean install with some adjustments in BIOS.

If you are reluctant to go for a clean install, get the F13 BIOS from GIGABYTE - Motherboard - Socket 1366 - GA-EX58-UD5 (rev. 1.0) , and free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

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

One more thing, NetWorx is always problematic. Everywhere. Better you uninstall it.

If the BIOS update is not enough to solve the issue, or if you want to go for the clean install, let us know after the BIOS update is done. We will suggest you the adjustments those are to be done in the BIOS.
_____________________________________

Code:

*** 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, {fffff880094128c0, fffff880094128c4, fffff880094128d0, fffff880094128d4}

Probably caused by : iaStor.sys ( iaStor+4b41e )

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

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

Unknown bugcheck code (9088)
Unknown bugcheck description
Arguments:
Arg1: fffff880094128c0
Arg2: fffff880094128c4
Arg3: fffff880094128d0
Arg4: fffff880094128d4

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9088

PROCESS_NAME:  IAANTmon.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8800147a41e to fffff80002e78bc0

STACK_TEXT:  
fffff880`09412858 fffff880`0147a41e : 00000000`00009088 fffff880`094128c0 fffff880`094128c4 fffff880`094128d0 : nt!KeBugCheckEx
fffff880`09412860 00000000`00009088 : fffff880`094128c0 fffff880`094128c4 fffff880`094128d0 fffff880`094128d4 : iaStor+0x4b41e
fffff880`09412868 fffff880`094128c0 : fffff880`094128c4 fffff880`094128d0 fffff880`094128d4 00000000`00000000 : 0x9088
fffff880`09412870 fffff880`094128c4 : fffff880`094128d0 fffff880`094128d4 00000000`00000000 fffffa80`0a09e000 : 0xfffff880`094128c0
fffff880`09412878 fffff880`094128d0 : fffff880`094128d4 00000000`00000000 fffffa80`0a09e000 00000000`00000000 : 0xfffff880`094128c4
fffff880`09412880 fffff880`094128d4 : 00000000`00000000 fffffa80`0a09e000 00000000`00000000 fffffa80`0ecd13f0 : 0xfffff880`094128d0
fffff880`09412888 00000000`00000000 : fffffa80`0a09e000 00000000`00000000 fffffa80`0ecd13f0 fffffa80`0c716540 : 0xfffff880`094128d4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
iaStor+4b41e
fffff880`0147a41e ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  iaStor+4b41e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStor

IMAGE_NAME:  iaStor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a287aa4

FAILURE_BUCKET_ID:  X64_0x9088_iaStor+4b41e

BUCKET_ID:  X64_0x9088_iaStor+4b41e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9088_iastor+4b41e

FAILURE_ID_HASH:  {e1b3ff64-da9d-b5b1-9107-148fac89e5ca}

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

2: kd> lmvm iaStor
start             end                 module name
fffff880`0142f000 fffff880`0154b000   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:23:40 2009 (4A287AA4)
    CheckSum:         000640D7
    ImageSize:        0011C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Hi Arc,

Thanks a lot for responding so quickly.

I followed your link to the BIOS update and can download and unzip it but it appears as if F13 is not supported by Windows 64 bit. I get a windows 64 bit support error when running the downloaded exe or when using @BIOS utility to flash. The Gigabyte website does not have a specific 64bit option for BIOS updates however there are drivers specific to Win64b. I am no expert and thought I should tell you before trying anything else. I've already removed Networx (do you know of another stable network usage monitor?) and cleaned the startup but now stuck with the BIOS update

Thanks again

As far as I say, @BIOS should not work with Intel X58 Chipset, and BIOS updates are OS irrespective.

Now the question is ... why I suggested for that particular BIOS update. Because the issue is ....

Code:

*** 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, {fffff880094128c0, fffff880094128c4, fffff880094128d0, fffff880094128d4}

Probably caused by : iaStor.sys ( iaStor+4b41e )

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

The failing module here is .....

Code:

Name    Intel(R) ICH8R/ICH9R/ICH10R/DO/PCH SATA RAID Controller
Driver    c:\windows\system32\drivers\iastor.sys (8.9.0.1023, 399.02 KB (408 600 bytes), 2013/12/28 10:44 PM)

And which is too old.

Code:

fffff880`0142f000 fffff880`0154b000   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:23:40 2009 (4A287AA4)
    CheckSum:         000640D7
    ImageSize:        0011C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Updating the driver will not be a solution. It will fail to crash again after one or two months; 0r may be after one week. The BIOS update has a RAID ROM update, so it might be helpful.

Attachment 314673

From your earlier post it appears that you are not very aware of the process of BIOS update. So I will not lead you to that risky operation anymore. Rather I would guide you to take the lengthy but sure way ... to avoid RAID. That is the best practice, as RAID is always problematic.

Boot into the BIOS. Change the Storage controller mode to AHCI. Disable Intel Rapid Storage, or Intel Smart Response, or anything in this line.

But, now the computer will refuse to boot up anymore. Do a Clean Reinstall - Factory OEM Windows 7 .... which will give you the perfect windows installation.

Apparently there is nothing more to do ATM, than wait ans wee. :)

My debugging experience says the BSODs caused by iAstor.sys does not stop till a clean install is done alongwith disabling RAID. I will hope it will be a different experience for you. :) Specially for the specific BIOS update. :)

You may add PS3 server to startup, if you find it is needed there. :)